Re: KVM image fails to resume after f38->40 upgrade [anyone???]

2024-08-09 Thread Go Canes
On Fri, Aug 9, 2024 at 10:57 AM wrote: > > On 9/8/24 10:32 pm, Go Canes wrote: > > Maybe extract the xml file from e4.saved and use it for the VM? > > I do not understand this. Why extract it? I am rather convinced that the > embedded xml is used on resume, > and the one in /etc is not consulted.

Re: KVM image fails to resume after f38->40 upgrade [anyone???]

2024-08-09 Thread fedora
On 9/8/24 10:32 pm, Go Canes wrote: On Fri, Aug 9, 2024 at 12:00 AM wrote: I looked into the saved memory (e4.saved for me) and I see that it contains the e4.xml file that is usually in /etc/libvirt/qemu/. Any other ideas? Maybe extract the xml file from e4.saved and use it for the VM? I

Re: KVM image fails to resume after f38->40 upgrade [anyone???]

2024-08-09 Thread Go Canes
On Fri, Aug 9, 2024 at 12:00 AM wrote: > I looked into the saved memory (e4.saved for me) and I see that it contains > the e4.xml file > that is usually in /etc/libvirt/qemu/. > > Any other ideas? Maybe extract the xml file from e4.saved and use it for the VM? Just long enough to get it resumed

Re: KVM image fails to resume after f38->40 upgrade [anyone???]

2024-08-08 Thread fedora
On 9/8/24 1:23 pm, Go Canes wrote: On Thu, Aug 8, 2024 at 7:45 PM 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

Re: KVM image fails to resume after f38->40 upgrade [anyone???]

2024-08-08 Thread Go Canes
On Thu, Aug 8, 2024 at 7:45 PM 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

Re: KVM image fails to resume after f38->40 upgrade [anyone???]

2024-08-08 Thread fedora
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? I tried to boot with each of the following options without success: dis_ucode_ldr mitigations=off kvm-intel.nes