RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

- start vm with Spice console e
- suspend vm 
- restore vm 

the guest params, in our case, video devices configuration, gets corrupted during the saving state (parameters to save). 
we are not sure wither its a problem with the function of saving the configuration, or the extraction. 

result: vdsm is failed to restore the vm, qemu process dies, and vm gets re-run on different host if exits.

http://gerrit.ovirt.org/#change,3107,patchset=1

this was only fixed for vm's that are created as new or as cloned (meaning they are not linked to template) 
vm's that are created as thin (linked to template) are still rerun on other host after restoring. 

reproduce:
1) create a vm from template with thin provision
2) rn vm -> suspend -> resume. 

vdsm + backend logs will be attached.

Created attachment 578548 [details]
logs

vm XP was run first on blond-vdsh and rerun after suspend on orange-vdsd.

I retested this and the vm is starting on a different host but without the same error. 
so I am verifying this bug on vdsm-4.9.6-8.el6.x86_64

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/RHSA-2012-1508.html