kernel does not support hotplug removal of virtio devices

Bug #368978 reported by Scott Moser on 2009-04-29
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux-meta (Ubuntu)

Bug Description

hotplug removal of virtio devices (in kvm guests) will not work without commit at;a=commitdiff;h=29f9f12ec7 . Fedora bug: .

To reproduce:
- create a disk image to attach: qemu-img create -f qcow2 /tmp/my-disk.img 1G
- boot jaunty guest, with -server or -generic kernel so as to have access to acpiphp.ko module (bug 364916). I've verified on
- inside guest: 'modprobe acpiphp.ko' and 'modprobe virtio_blk'
- from kvm monitor: pci_add 0 storage file=/tmp/my-disk.img,if=virtio
  watch to see what slot this is put on
- inside guest: dmesg and cat /proc/partitions should show a new 'vd*' device
- from kvm monitor: pci_del 0 X
  where X is the slot from the add
- inside guest: see message on console or dmesg:
  "modprobe virtio_blk ... Device 'virtio2' does not have a release() function, it is broken and must be fixed"

Scott Moser (smoser) wrote :

I've verified this is functioning with kvm on lucid beta 1 (2.6.32-16-generic / x86_64) host, with lucid beta 1 guest. Thus, marking this fix released. Only difference from the text in the bug open comment is that 'pci_add auto storage file=/tmp/my-disk.img,if=virtio' and then, to detach: pci_del 0:X (':', not space)

affects: linux-ports-meta (Ubuntu) → linux-meta (Ubuntu)
Changed in linux-meta (Ubuntu):
importance: Undecided → Low
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers