Public bug reported:
qemu version: 1.4.50 (0ca5aa4f4c4a8bcc73988dd52a536241d35e5223)
host: x86_64, Linux 3.6.10 (Fedora 17)
client: x86_64 Centos 6.3 (doesn't matter, really)
If a device, e.g. an lsi53c895a, is on a pci-bridge, after migration, the
device stops working (e.g., commands like "poweroff"
get an Input/Output error. Fails under either xen or kvm. If "top" was running,
some cpus go to ~100% wait.
Sample KVM invocation line:
qemu-system-x86_64 -machine type=pc,accel=kvm -m 4096 -device
pci-bridgemsi=on,chassis_nr=1,id=pciBridge1.0,addr=0x11.0 -device
lsi53c895a,id=sas,bus=pciBridge1.0,addr=0x1.0x0 -drive
if=none,id=disk0,file=/path/to/disk/image -device
scsi-disk,bus=sas.0,scsi-id=0,drive=disk0 -vnc 127.0.0.1:0,to=99 -serial pty
-boot order=cda -smp 4,maxcpus=4 -monitor vc
** Affects: qemu
Importance: Undecided
Status: New
** Tags: migration pci-bridge
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1187529
Title:
Devices on PCI bridge stop working when live-migrated
Status in QEMU:
New
Bug description:
qemu version: 1.4.50 (0ca5aa4f4c4a8bcc73988dd52a536241d35e5223)
host: x86_64, Linux 3.6.10 (Fedora 17)
client: x86_64 Centos 6.3 (doesn't matter, really)
If a device, e.g. an lsi53c895a, is on a pci-bridge, after migration, the
device stops working (e.g., commands like "poweroff"
get an Input/Output error. Fails under either xen or kvm. If "top" was
running, some cpus go to ~100% wait.
Sample KVM invocation line:
qemu-system-x86_64 -machine type=pc,accel=kvm -m 4096 -device
pci-bridgemsi=on,chassis_nr=1,id=pciBridge1.0,addr=0x11.0 -device
lsi53c895a,id=sas,bus=pciBridge1.0,addr=0x1.0x0 -drive
if=none,id=disk0,file=/path/to/disk/image -device
scsi-disk,bus=sas.0,scsi-id=0,drive=disk0 -vnc 127.0.0.1:0,to=99 -serial pty
-boot order=cda -smp 4,maxcpus=4 -monitor vc
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1187529/+subscriptions
