On Thu, Aug 8, 2024 at 7:45 PM <fedora@xxxxxxxxxxxxxx> wrote: > > I received no response (well, one me-too) and it may be time to just trash the saved file. I'd rather not. > > Nobody knows how to get around this problem? Really? > [...] > On 13/7/24 3:07 pm, Eyal Lebedinsky wrote: > > Following an upgrade of the host (38->40) I could not start the vm. > > > > The VM was running f40 for a while just fine. It was "virsh save"d a few days ago. > > $ sudo virsh save e4 /data1/VMs/libvirt/images/e4.saved > > > > Normally I actually stop it but forgot to do it this time. > > > > $ sudo virsh restore '/data1/VMs/libvirt/images/e4.saved' > > -rw-r--r-- 1 qemu qemu 512110190592 Jul 8 18:36 /data1/VMs/libvirt/images/e4.raw > > -rw------- 1 root root 8472278573 Jul 8 18:37 /data1/VMs/libvirt/images/e4.saved > > > > 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-intr,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 Warning - I have no real idea regarding the underlying issue and therefore how to address it *properly*. Shot-in-the-dark ideas... If you haven't already done so, you can try: - exporting the VM, deleting it without deleting the storage, and then importing it back in (reattaching storage as needed) - creating a new VM and attaching the existing storage But tbh my best guess is that these won't help. You may just have to boot without restoring from the saved state. -- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
