Bug 869981
Summary: | Cross version migration between different host with spice is broken | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Qunfang Zhang <qzhang> |
Component: | qemu-kvm | Assignee: | Alon Levy <alevy> |
Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 6.4 | CC: | acathrow, areis, bili, bsarathy, dblechte, ddumas, dyasny, dyuan, hdegoede, juzhang, malittle, michen, minovotn, mkenneth, mzhan, ngalvin, owasserm, quintela, virt-maint, weizhan, zhpeng, zpeng |
Target Milestone: | rc | Keywords: | Regression |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | qemu-kvm-0.12.1.2-2.353.el6 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-02-21 07:43:57 UTC | Type: | Bug |
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: | 890050 |
Description
Qunfang Zhang
2012-10-25 09:44:31 UTC
Live migration from 6.3 to 6.4 with spice and qxl (excluding seamless migration) should part of the test plan for RHEL 6.4 Could you try without global qxl-vga.vram_size=33554432 ? (In reply to comment #3) > Could you try without global qxl-vga.vram_size=33554432 ? Orit It has the same result without "-global qxl-vga.vram_size=33554432". #/usr/libexec/qemu-kvm ..... -spice port=5930,disable-ticketing -vga qxl -incoming tcp:0:5800 QEMU 0.12.1 monitor - type 'help' for more information (qemu) qemu: warning: error while loading state for instance 0x0 of device 'ram' by the way did you test with vnc ? (In reply to comment #5) > by the way did you test with vnc ? Cross migration with vnc finished successfully. I couldn't reproduce while building source vm from source with 0.12.0-295, and when using package qemu-kvm-0.12.1.2-2.295.el6_3.5 I cannot use Conroe cpu: Unknown cpu model: Conroe So are you sure that's the source qemu version & command line used? Alon OK, can reproduce when changed the cpu version to qemu64. QEMU 0.12.1 monitor - type 'help' for more information (qemu) qemu: warning: error while loading state for instance 0x0 of device 'ram' load of migration failed Forgot to remove the needinfo. (In reply to comment #9) > Forgot to remove the needinfo. Alon, hah, seems you added the needinfo again. I guess you have already reproduced this issue so clear it now. Please feel free to add comment if there's any thing I could do. Hi, Alon Cross migration works between rhel6.1<->rhel6.3 and rhel6.2<->rhel6.3, so this is a regression. Refer to bug 698936 that is fixed in rhel6.3. Thanks for the clue, I spent yesterday creating yet another script to automate the checks for bisection, but stepping through the code appears to have been faster (now that I tried it following your mention of bug 698936), now just to find where we set that size exactly (and to add this message to upstream/rhel for the future): DEBUG: ram length mismatch: 0000:00:02.0/qxl.vrom: 8192 in != 16384 qemu: warning: error while loading state for instance 0x0 of device 'ram' load of migration failed Hi, Alon Do you know when the build will be ready? As it is in a late stage of rhel6.4 and QE need to verify this issue and also some other additional test for it. Thanks, Qunfang Please test the brew-build provided by Alon for bug 876982: https://bugzilla.redhat.com/show_bug.cgi?id=876982#c26 Alon, I don't see a downstream version of the patch, so it shouldn't be in POST. Please submit a patch to rhvirt-patches and ask for the 3 acks. (In reply to comment #21) > Please test the brew-build provided by Alon for bug 876982: > https://bugzilla.redhat.com/show_bug.cgi?id=876982#c26 Ok, will dive into it soon and update the result here. Thanks. > > Alon, I don't see a downstream version of the patch, so it shouldn't be in > POST. Please submit a patch to rhvirt-patches and ask for the 3 acks. Hi, Ademar and Alon I just tested this bug with the build in bug 876982#c26, and this bug can NOT be reproduced, cross migration between rhel6.3 and rhel6.4 host works well with spice+qxl. As Alon said in bug 876982 that the build has no direct relation with this bug, so is there another patch for this bug itself? When the patch could get into the official build? Thanks, Qunfang Just to clarify and make sure we're in sync, the fix for this bug is: """ Date: Tue, 22 Jan 2013 19:33:21 +0200 From: Alon Levy <alevy> Subject: [PATCHv2 RHEL-6.4 qemu-kvm 0/2] fix qxl migration revision 4 bug To: rhvirt-patches Cc: hdegoede, mlureau, armbru, kraxel v1->v2: (Markus +) remove unwanted whitespace fix disable added trace events by default like all the rest fill in commit message for "stop using non revision 4 rom fields" remove a non related trace event that got in there (there is no interface_client_monitors_config in RHEL 6.4) Alon Levy (2): qxl: stop using non revision 4 rom fields for revision < 4 qxl: change rom size to 8192 hw/qxl.c | 22 +++++++++++++++------- trace-events | 1 + 2 files changed, 16 insertions(+), 7 deletions(-) """ v2 got an ACK from Markus, but is missing the ACKs from v1 (Gerd and Hans). Hi, Gerd and Hans As Ademar's comment above, could you guys help ack from v1? It's planned to be include in snapshot 5. Currently it's urgent for QE as we need to verify this bug and also bug 733302 that is in the qemu-kvm errata. And also, QE need to arrange function test for "stable guest abi" and "compatibility" that will take several days to finish after get the official build. Thanks! Qunfang If it misses the train of rhel6.4, cross version migration with spice from rhel6.4 host to older rhel host will be broken. That is a very common scenario. As we already have the patch now after lots of effort, so guys please help give it a push and let it proceed. Thanks a lot. Acked v2. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-0527.html |