Bug 624396
| Summary: | migration failed after hot-unplug virtserialport - Unknown savevm section or instance '0000:00:07.0/virtio-console' 0 | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | lihuang <lihuang> |
| Component: | qemu-kvm | Assignee: | Amit Shah <amit.shah> |
| Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 6.1 | CC: | ajia, amit.shah, gyue, michen, mkenneth, quintela, snagar, tburke, virt-maint, wihocob |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | qemu-kvm-0.12.1.2-2.114.el6 | Doc Type: | Bug Fix |
| Doc Text: |
Migrating a VM after a virtio-serial device was hot-unplugged resulted in migration failure. This was due to not removing the device's state from migration data from the source machine. The source then sent the device data to the destination, which did not expect that device, resulting in a failed migration condition. The fix is to unregister the device state from the migration state to ensure the removed device is not considered for migration.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-05-19 11:31:16 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 580954 | ||
|
Description
lihuang
2010-08-16 10:11:16 UTC
That's expected. You start src with two virtio-serial devices with 1 port each. Then hot-unplug one port. And then migrate, but specify two devices with one port each on the dst host. So the load is going to fail as the source now only knows of two devices and one port on one of the devices, but the destination expects two devices with one port each. libvirt is supposed to take care of making sure it spawns qemu on the destination host considering all the hot-plug/unplug operations that have been performed since the src host start. This doesn't look like a bug, unless you're doing something different from what I described. Hi Amit My steps is : 1. start src with two virtio-serial devices with 1 port each. 2. remove all ports and virtio-serial devices from qemu monitor (qemu) device_del org.linux-kvm.port.0 (qemu) device_del org.linux-kvm.port.1 (qemu) device_del virtio-serial0 (qemu) device_del virtio-serial1 3. start dst without virtserialport and virtio-serial devices A. with chardev B. without chardev ==> both failed Can you try just removing the ports and not the devices? It's possible that device hot-unplug doesn't go through. OK, I found the culprit. We don't unregister the savevm section on device hot-unplug. Can you try the build in http://brewweb.devel.redhat.com/brew/taskinfo?taskID=2691710 Give it some time to build, though. With that change, it works for me. yes. it also works for me (In reply to comment #6) > yes. it also works for me Great. Patch is sent upstream, will target 6.1: http://article.gmane.org/gmane.comp.emulators.qemu/78336 Verified in qemu-kvm-0.12.1.2-2.129.el6.x86_64 The steps as #Description and the guest running normally after migration. cmd: /usr/libexec/qemu-kvm -m 2G -smp 2 -uuid `uuidgen` -rtc base=utc,clock=host,driftfix=slew -boot c -drive file=/home/image/rhel6.qcow2,index=0,if=none,id=drive-virtio-disk1,media=disk,cache=none,format=qcow2 -device virtio-blk-pci,bus=pci.0,drive=drive-virtio-disk1,id=virtio-disk0 -netdev tap,id=hostnet0,script=/etc/qemu-ifup-switch -device virtio-net-pci,netdev=hostnet0,mac=00:10:12:20:77:0c,bus=pci.0,addr=0x7,id=hostnet0 -monitor stdio -vnc :1 -device virtio-serial-pci,id=virtio-serial0,max_ports=16,bus=pci.0,addr=0x4 -chardev socket,id=channel0,path=/home/rhel6.channel0,server,nowait -device virtserialport,chardev=channel0,name=org.linux-kvm.port.0,bus=virtio-serial0.0,id=port1
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
Migrating a VM after a virtio-serial device was hot-unplugged resulted in migration failure. This was due to not removing the device's state from migration data from the source machine. The source then sent the device data to the destination, which did not expect that device, resulting in a failed migration condition. The fix is to unregister the device state from the migration state to ensure the removed device is not considered for migration.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2011-0534.html An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2011-0534.html My BK Experience Welcome Bk 2018 - News Channel 3 Dec 12, 2017 - Welcome to the My BURGER KING Experience Survey We value your candid feedback and appreciate you taking the time to complete our survey When younbspThis website uses cookies to automatically collect information about your visit and your systems All of your information is used solely to provide ... http://www.mybk-experience.xyz/ |