[Pkg-libvirt-maintainers] Bug#551660: libvirt-bin: virsh fails to add disk to domain, says it succeeded

[Uli Martens]

Package: libvirt-bin
Version: 0.7.1-2
Severity: normal

Hi Guido,

I'm the guy from the debconf who told you about the problem hot-adding disks to
kvm domains with libvirt.

First, thanks again for looking into the bug there, the first half of it seems
to be fixed already. [ftr: trying to add a disk to a kvm domain failed because
of changed kvm command line syntax, was fixed in 0.6.5-3 by
0005-Fix-PCI-device-hotplug-unplug-with-newer-QEMU.patch]

Unfortunatelly, this still seems to only cold-add the disk to the
domain-specification internal to libvirt, but not to the running domain.

| virsh # attach-disk brann /dev/sde vdg
| Disk attached successfully
| 
| virsh # dumpxml brann
[..]
|     <disk type='block' device='disk'>
|       <driver name='phy'/>
|       <source dev='/dev/sde'/>
|       <target dev='vdg' bus='virtio'/>
|     </disk>
[..]

The domain itself seems not to notice at all. dmesg shows no changes,
/proc/partitions is unchanged. /var/log/libvirt/qemu/brann.log is unchanged, too.

Host system is an lenny amd64 system. kernel was linux-image-2.6.30-bpo.1-amd64
(2.6.30-6~bpo50+1)

from backports.org:
ii  kvm                 85+dfsg-4~bpo50+1   Full virtualization on x86 hardware

own rebuilds from clean lenny+bpo chroot, no further changes beside version number:
ii  libvirt-bin         0.7.1-2~bpo50+1     the programs for the libvirt library
ii  libvirt0            0.7.1-2~bpo50+1     library for interfacing with different virtualization

The guest domain is running an amd64 kernel with i386 userland. Tried kernels were a
self-made 2.6.30 and linux-image-2.6.30-bpo.2-amd64 (2.6.30-7~bpo50+1) from
bpo.

I'll happily try whatever guesses you might have for me...

greetings,
	Uli / youam