Red Hat Bugzilla – Bug 1032208
virtio-scsi controller causes migration to fail
Last modified: 2014-03-24 02:39:50 EDT
Description of problem:
Migration fails on VMs with <controller type="scsi" device present.
Version-Release number of selected component (if applicable):
same setup on both source (dev-11) and destination (dev-15)
Steps to Reproduce:
1. virsh create vm-min-scsi.xml (see attachment)
2. virsh migrate vm qemu+ssh://dev-15/system
3. check qemu logs for VM 'vm'
Vm is killed during migration after
qemu-system-x86_64: virtio: trying to map MMIO memory
Vm should be up and running on destination after migration
Migration fails only when the scsi controller is present in the domain xml.
Also tested migration with vm-min.xml (attached, scsi controller removed) and that works - last entry in dst_qemu.log @ 17:05
Created attachment 826217 [details]
Created attachment 826218 [details]
Created attachment 826219 [details]
destination qemu vm.log
Created attachment 826220 [details]
source qemu vm.log
Created attachment 826221 [details]
source libvirt log
Created attachment 826222 [details]
destination libvirt log
Looks like this is:
Which is fixed with a seabios patch:
Needed in f19, f20, and rawhide
seabios-184.108.40.206-3.fc19 has been submitted as an update for Fedora 19.
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing seabios-220.127.116.11-3.fc19'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
seabios-18.104.22.168-3.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.