Red Hat Bugzilla – Bug 1278011
Restoring a RAM snapshots in RHEL7.2 shows error and fails to connect via spice (SetVmTicket: Unexpected exception)
Last modified: 2015-12-02 04:45:58 EST
Created attachment 1089713 [details]
engine and vdsm logs
Description of problem:
Restoring a snapshot works but I cannot access via spice fails with "Error while executing action SetVmTicket: Unexpected exception". Also the engine shows an error starting the vm even though it starts successfully.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create a VM with an OS, start it, make a snapshot and stop it.
2. start the vm and start a process (in my example: cat /dev/zero)
2. Create a RAM snapshot
3. Shutdown the vm
5. Restore the RAM snapshot
6. Start the vm and open spice console
Raz, how is this storage related? I'd say it's more virt
Raz, are you sure the VM is properly up and running?
2015-11-03 22:24:13,346 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (DefaultQuartzScheduler_Worker-19) Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: VM vm_ram_snapshot_nfs is down with error. Exit message: Wake up from hibernation failed.
2015-11-03 22:24:13,347 INFO [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] (DefaultQuartzScheduler_Worker-19) Running on vds during rerun failed vm: null
Which VM is the problematic one in the logs?
Yes, I successfully ssh to the vm to make sure the cat proc (step 2) is still running.
The problematic vm is vm ram_snapshot_nfs
Fixed in https://bugzilla.redhat.com/show_bug.cgi?id=1273551
*** This bug has been marked as a duplicate of bug 1273551 ***