
I upgraded f38->f40 but left the vm saved rather than shutdown (my bad but here we are) Attempting to restore the vm with 'virsh restore /data1/VMs/libvirt/images/e4.saved' I get: error: Failed to restore domain from /data1/VMs/libvirt/images/e4.saved error: operation failed: guest CPU doesn't match specification: extra features: vmx-ins-outs,vmx-true-ctls,vmx-store-lma,vmx-activity-hlt,vmx-vmwrite-vmexit-fields,vmx-apicv-xapic,vmx-ept,vmx-desc-exit,vmx-rdtscp-exit,vmx-vpid,vmx-wbinvd-exit,vmx-unrestricted-guest,vmx-rdrand-exit,vmx-invpcid-exit,vmx-vmfunc,vmx-shadow-vmcs,vmx-rdseed-exit,vmx-pml,vmx-ept-execonly,vmx-page-walk-4,vmx-ept-2mb,vmx-ept-1gb,vmx-invept,vmx-eptad,vmx-invept-single-context,vmx-invept-all-context,vmx-invvpid,vmx-invvpid-single-addr,vmx-invvpid-all-context,vmx-intr-exit,vmx-nmi-exit,vmx-vnmi,vmx-preemption-timer,vmx-vintr-pending,vmx-tsc-offset,vmx-hlt-exit,vmx-invlpg-exit,vmx-mwait-exit,vmx-rdpmc-exit,vmx-rdtsc-exit,vmx-cr3-load-noexit,vmx-cr3-store-noexit,vmx-cr8-load-exit,vmx-cr8-store-exit,vmx-flexpriority,vmx-vnmi-pending,vmx-movdr-exit,vmx-io-exit,vmx-io-bitmap,vmx-mtf,vmx-msr-bitmap,vmx-monitor-exit,vmx-pause-exit,vmx-secondary-ctls,vmx-exit-nosave-debugctl,vmx-exit-load-perf-global-ctrl,vmx-exit-ack-i ntr,vmx-exit-save-pat,vmx-exit-load-pat,vmx-exit-save-efer,vmx-exit-load-efer,vmx-exit-save-preemption-timer,vmx-entry-noload-debugctl,vmx-entry-ia32e-mode,vmx-entry-load-perf-global-ctrl,vmx-entry-load-pat,vmx-entry-load-efer,vmx-eptp-switching Then, trying to resume from the "virtual Machine Manager" UI gets the message: ===== Error unpausing domain: Requested operation is not valid: domain is not running Error unpausing domain: Requested operation is not valid: domain is not running Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 72, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/asyncjob.py", line 108, in tmpcb callback(*args, **kwargs) File "/usr/share/virt-manager/virtManager/object/libvirtobject.py", line 57, in newfn ret = fn(self, *args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/share/virt-manager/virtManager/object/domain.py", line 1437, in resume self._backend.resume() File "/usr/lib64/python3.12/site-packages/libvirt.py", line 2425, in resume raise libvirtError('virDomainResume() failed') libvirt.libvirtError: Requested operation is not valid: domain is not running I searched for a solution and most say to fiddle with some settings and reboot. I cannot reboot, I want to resume (unpause). How can I restore the vm without crashing it (throwing away the saved memory), if it even boots this way? TIA

Me (the OP) again. Did some testing. First copied the files and booted the copied image on another machine (nfs mounted the image). First, made a copy of the image (e4.raw). Renamed it to ex.raw. Booted a second machine (call it ex) from a f38 iso. Installed the necessary packages and started the image. Had to subdue selinux and change the uuid. It came up and looks OK. Shut down this VM and the host (ex). I then booted the clone (ex) vm on my original machine. It came up here too (this is f40). So, while I still cannot properly resume the original vm (e4), at lease I know that I can cold boot it. Does anyone know how to resume the image (my original question)?

Sadly, no solution was found so I decided to cold boot and move on. I tried to boot with a number of command line options to no avail. dis_ucode_ldr mitigations=off kvm-intel.nested=1 Regards, Eyal -- Eyal at Home (libvirt@eyal.emu.id.au)

Sadly, no solution was found so I decided to cold boot and move on. I tried to boot with a number of command line options to no avail. dis_ucode_ldr mitigations=off kvm-intel.nested=1 If anyone knows a way to resume this image, reply to this thread. I kept a copy of the paused image and can try again, for next time this happens to me. TIA, Eyal
participants (2)
-
Eyal Eyal
-
libvirt@eyal.emu.id.au