Bug 830900
Summary: | Unable to restore saved VM after upgrade from F16 to F17 | |||
---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Darryl L. Pierce <dpierce> | |
Component: | qemu | Assignee: | Fedora Virtualization Maintainers <virt-maint> | |
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | |
Severity: | unspecified | Docs Contact: | ||
Priority: | unspecified | |||
Version: | 17 | CC: | amit.shah, berrange, cfergeau, crobinso, dwmw2, itamar, knoel, pbonzini, scottt.tw, tross, virt-maint | |
Target Milestone: | --- | |||
Target Release: | --- | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Bug Fix | ||
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 857126 (view as bug list) | Environment: | ||
Last Closed: | 2013-04-01 12:23:21 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: | 857126 |
Description
Darryl L. Pierce
2012-06-11 15:24:03 UTC
Can you find what version you had for QEMU in F16? Since I've been looking at other migration issues, I looked into this too. This patch in f16 is the culprit: http://pkgs.fedoraproject.org/cgit/qemu.git/tree/0022-qxl-bump-pci-rev.patch?h=f16 It's an upstream change that went in after 0.15 and was in the 1.0 release. But it messes with various migration properties. So F16 pc-0.14 (the default) is different from upstream pc-0.14. We could 'fix' this in F17+ by adding compat properties to pc-0.14 that match what F16 qxl is using, but then we deviate from upstream, and have the carry that patch for an indefinite amount of time. Which isn't that big of a deal, but then again since there hasn't been much noise about this, and F16 is EOL, I'm tempted to not even bother. If anyone else has strong opinions feel free to chime in. If nothing else I keep this bug open till F17 EOL for documentation purposes. I think that now that it is analyzed, we should close it as WONTFIX. (Does it even happen with the latest F16 qemu, which is 0.15.1?). (In reply to comment #3) > I think that now that it is analyzed, we should close it as WONTFIX. (Does > it even happen with the latest F16 qemu, which is 0.15.1?). Yes, all F16 versions are affected. I'd prefer to keep it open for a bit, since F16 has only been EOL for less than a month. There are plenty of people who I'm sure are still running it, and who will upgrade over the next few months. And really this could be called a F17/F18/rawhide 'bug' since the fix wouldn't have lived in F16 anyways. I don't anticipate many people complaining but I'm willing to see if there's more demand. No extra response for a month, closing as suggested in Comment #3. |