Bug 1016700
Summary: | Cloning VM from snapshot of another VM results in corruption of original VM | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | rhev-integ |
Component: | ovirt-engine-webadmin-portal | Assignee: | Tomas Jelinek <tjelinek> |
Status: | CLOSED ERRATA | QA Contact: | Pavel Novotny <pnovotny> |
Severity: | urgent | Docs Contact: | |
Priority: | urgent | ||
Version: | 3.2.0 | CC: | acathrow, bazulay, cboyle, ecohen, grajaiya, hateya, iheim, jkt, lpeer, lyarwood, mavital, michal.skrivanek, pnovotny, rcyriac, Rhev-m-bugs, rhs-bugs, scohen, shaines, sputhenp, surs, tjelinek, yeylon |
Target Milestone: | --- | Keywords: | Regression, ZStream |
Target Release: | 3.2.5 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | virt | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
In a hypervisor environment, and cloning a VM from the snapshot of another VM, the new VM booted up fine, but the original VM of which the snapshot was taken was rendered as not bootable. The failure message on boot-up was:
"VM <VM name> is down. Exit message: unsupported configuration: non-primary video device must be type of 'qxl'.
Failed to run VM <VM name> on Host <Hypervisor name>."
There was a chance that the devices from the original VM were not cloned to the new VM but rewritten over the original, which meant the original VM was corrupted. This has been fixed by cloning the devices to the new VM, meaning the original VM will not be corrupted.
|
Story Points: | --- |
Clone Of: | 982636 | Environment: | |
Last Closed: | 2013-12-18 14:09:23 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: | 982636 | ||
Bug Blocks: |
Description
rhev-integ
2013-10-08 14:37:14 UTC
This bug is currently attached to errata RHBA-2013:16431. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag. Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information: * Cause: What actions or circumstances cause this bug to present. * Consequence: What happens when the bug presents. * Fix: What was done to fix the bug. * Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore') Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug. For further details on the Cause, Consequence, Fix, Result format please refer to: https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes Thanks in advance. Verified in rhevm-3.2.5-0.48.el6ev.noarch (sf22) Verification steps: 1. Create VM "original" and run it. 2. Create live snapshot and from it clone new VM "cloned-live". 3. Shut down VM "original", create another snapshot and from it clone second VM "cloned-offline". 4. Boot up both "cloned-*" VMs and check via console if they work correctly. 5. Remove both snapshots created in step 2 and 3 and check again the "clone-*" VMs (do so also after both VMs are rebooted). All VMs (the original one and both cloned) were operating normally, i.e., no disk corruption was experienced nor errors/warnings were reported by RHEVM or in the guest OS. 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-1831.html |