OpenStack ignores device name for attached volume

[Alex Nehaichik]

OpenStack ignores device name for attached volume:

# on my laptop
$ euca-attach-volume-2.7 -i i-00000014 -d /dev/vdz vol-00000002
VOLUME vol-00000002

# on compute node
# grep vdz /var/log/nova/nova-compute.log
2012-12-10 11:41:16 AUDIT nova.compute.manager [req-254b675d-0d9c-4efa-929d-be5208750c05 63cd6e85896b47a9af0d10ddcfc911b5 e40b7627b5d346408734148f6192bea7] [instance: 1523c0a2-7d53-4160-8af6-014e38fd9ddc] Attaching volume 35308823-c859-4354-8bb3-cafdc21241ea to /dev/vdz

# inside instance i-00000014
$ cat /proc/partitions
major minor #blocks name

 253 0 2097152 vda
 253 1 2088450 vda1
 253 16 26214400 vdb
 253 32 10485760 vdc

$ dmeg | tail
...
[ 2208.047616] vdc: unknown partition table

nova-compute 2012.2-0ubuntu5~cloud0
libvirt-bin 0.9.13-0ubuntu12~cloud0
cinder-volume 2012.2-0ubuntu2~cloud0

compute/controller/volume are ubuntu 12.04.1 amd64
instances are ubuntu-12.04-server-cloudimg-i386

[Davanum Srinivas (DIMS) (dims-v)]

Same problem with config drives as well virsh xml says vdz and the drive is added as vdb

    <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='none'/>
      <source file='/opt/stack/data/nova/instances/instance-0000000b/disk.config'/>
      <target dev='vdz' bus='virtio'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
    </disk>

root@dims-desktop:~# ssh cirros@10.0.2.3
cirros@10.0.2.3's password:
$ cat /proc/partitions
major minor #blocks name

 253 0 40162 vda
 253 1 32130 vda1
 253 16 394 vdb

I *don't* see vdb or vdz on the command line. so this looks like a libvirt problem

/usr/bin/kvm -name instance-0000000b -S -M pc-1.2 -enable-kvm -m 512 -smp 1,sockets=1,cores=1,threads=1 -uuid a2448824-0fa8-4abd-8599-e9b1633bba07 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/instance-0000000b.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -no-kvm-pit-reinjection -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/opt/stack/data/nova/instances/instance-0000000b/disk,if=none,id=drive-virtio-disk0,format=qcow2,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive file=/opt/stack/data/nova/instances/instance-0000000b/disk.config,if=none,id=drive-virtio-disk25,format=raw,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk25,id=virtio-disk25 -netdev tap,fd=25,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=fa:16:3e:f7:2d:fb,bus=pci.0,addr=0x3 -chardev file,id=charserial0,path=/opt/stack/data/nova/instances/instance-0000000b/console.log -device isa-serial,chardev=charserial0,id=serial0 -chardev pty,id=charserial1 -device isa-serial,chardev=charserial1,id=serial1 -device usb-tablet,id=input0 -vnc 127.0.0.1:1 -k en-us -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6

Can we please log a bug againt libvirt?

[wangpan (hzwangpan)]

I believe this is a bug of kvm, so close this one, may be we need to wait for kvm fixes it.