Open Stack

On Jun 8, 2012, at 9:03 AM, Pádraig Brady wrote:
> 
>> $ qemu-img info cirros-0.3.0-x86_64-disk.img
>> image: cirros-0.3.0-x86_64-disk.img
>> file format: qcow2
>> virtual size: 39M (41126400 bytes)
>> disk size: 11M
>> cluster_size: 65536
>> $ sudo qemu-nbd -c /dev/nbd15 $PWD/cirros-0.3.0-x86_64-disk.img
>> $ ls -l /dev/nbd15*
>> brw-rw---- 1 root disk 43, 240 Jun  8 11:32 /dev/nbd15
>> brw-rw---- 1 root disk 43, 241 Jun  8 11:32 /dev/nbd15p1
> 
> Very interesting. I don't get the ...p1 device here
> on a 3.3.7.fc17.x86_64 kernel


did you modrpobe nbd with max_part=8 or some such? It won't detect partitions automatically unless you do so.

We really should stop using kpartx and force people to modprobe nbd with max_part=X

There seem to be various issues with kpartx

Vish

> 
> cheers,
> Pádraig.
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack at lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp