Bug 1184325
Summary: | [PowerKVM] QEMU aborted after booting from snapshot | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Retired] RHEV for Power | Reporter: | Xu Han <xuhan> | ||||||
Component: | qemu-kvm-rhev | Assignee: | David Gibson <dgibson> | ||||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Virtualization Bugs <virt-bugs> | ||||||
Severity: | high | Docs Contact: | |||||||
Priority: | unspecified | ||||||||
Version: | unspecified | CC: | audgiri, bugproxy, dgibson, fnovak, gklein, hannsj_uhl, hhuang, knoel, michal.skrivanek, michen, ngu, qzhang, thuth, virt-maint, xuhan, ypu | ||||||
Target Milestone: | rc | ||||||||
Target Release: | --- | ||||||||
Hardware: | ppc64 | ||||||||
OS: | Unspecified | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2016-06-08 08:26:35 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: | 1155673, 1182933, 1185286, 1308609, 1359843 | ||||||||
Attachments: |
|
Description
Xu Han
2015-01-21 05:35:16 UTC
Created attachment 982169 [details]
qemu.log
Created attachment 982170 [details]
full backtrace
------- Comment From fnovak.com 2015-01-21 13:13 EDT------- reverse mirror of RHBZ 1184325 - [PowerKVM] QEMU aborted after booting from snapshot This is clearly a host bug in PowerKVM, so I don't think it's a blocker for the RHEL 7.1 LE release. Xu Han, one clarification. In your steps to reproduce, where you say "repeat step 1" do you mean repeat step 1 exactly as originaly executed, or repeat step 1 with the original disk replaced with the new snapshot? (In reply to David Gibson from comment #6) > Xu Han, one clarification. > > In your steps to reproduce, where you say "repeat step 1" do you mean repeat > step 1 exactly as originaly executed, or repeat step 1 with the original > disk replaced with the new snapshot? Uh, sorry, I forgot to clear that "repeat step 1" means booting guest with the new snapshot(snA.qcow2 for step 2, snB.qcow2 for step 3), then copy a new file from host to guest with using a new filename(snA, snB) and finally shutdown the guest. Xu Han, Thanks for the clarificiation. I'll get this mirrored to IBM, and investigate when I can. If you have a chance to see if this can be reproduced under a RHEL host, that would be useful. (In reply to David Gibson from comment #8) > If you have a chance to see if this can be reproduced under a RHEL host, > that would be useful. Have not reproduced this bug by testing 50 times with a RHEL host. Thanks, Ok, probably an upstream bug in 2.0. IBM, I'll leave this one to you. ------- Comment From fnovak.com 2015-02-12 03:23 EDT------- making another comment visible from an internal look as well...... I tried this on Build35 and I was not able to reproduce the problem. BTW - I did not run qemu command line directly, I did through virsh - but basically followed same steps - boot the guest, copy file, create a snapshot, use snapshot to boot the guest, copy file - repeat with next snapshot etc.. ------------------------------------ I sent a separate email out to umber of folks on RHEV side that there is a PowerKVM update (at the time of note coming up for release, just now released 11Feb )... Above build 35 was the all but GA version.. So hopefully the PowerKVM 2.1.1.1 version fixes this as well as slew of CVEs and other bug fixes.. Still need to close on how this moves to the RHEV for Power stream.... Once this makes it over, RH please verify.. Has this been checked against the PowerKVM 2.1.1.1 update? Is this still a problem, or can this be closed out? Xu Han, It looks like this was never a problem on the RHEL host, and comment 11 suggests it has now been fixed in IBM PowerKVM. Can we close this as CURRENTRELEASE? Hi Frank, Currently, We can not fetch the updates because yum repo can not be accessed. Could you please provide those packages for us, otherwise, we suggest to close this bug. Thanks, Xu Xu Han -- 2.1.1.1 was released to Red Hat.. actually expecting that RH released update.. ------- Comment From fnovak.com 2015-05-28 01:07 EDT------- (In reply to comment #18) > Xu Han -- 2.1.1.1 was released to Red Hat.. > actually expecting that RH released update.. Based on https://bugzilla.redhat.com/show_bug.cgi?id=1197197 and https://rhn.redhat.com/errata/RHEA-2015-1028.html closing as fixed,,, Frank, What's the specific qemu package version in which this is fixed in PowerKVM? I know it's PowerKVM 2.1.1.1 overall, but we've got a customer hitting this and the situation is a bit unclear. We can more easily and precisely check the exact qemu package version than the overall hypervisor version. May I ask what's the current status here? Could we now close this issue as CURRENTRELEASE as it has been suggested earlier? According to the earlier comments on this BZ, I think we can consider this bug to be fixed in the current version of RHEV, so closing this now as CURRENTRELEASE. If anybody disagrees, please feel free to re-open it again. |