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

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

Re: KVM image fails to resume after f38->40 upgrade

Thanks Barry, On 11/8/24 5:21 pm, Barry Scott wrote: On 13 Jul 2024, at 06:07, Eyal Lebedinsky wrote: Normally I actually stop it but forgot to do it this time. I think this was discussed on https://discussion.fedoraproject.org  a while ago. Sorry I

Re: KVM image fails to resume after f38->40 upgrade

> On 13 Jul 2024, at 06:07, Eyal Lebedinsky wrote: > > Normally I actually stop it but forgot to do it this time. I think this was discussed on https://discussion.fedoraproject.org a while ago. Sorry I do not have a link to the discussion. You should be

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

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???]

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???]

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???]

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???]

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???]

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

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

I did not receive any answers here, and none for a thread I created https://lists.libvirt.org/archives/list/us...@lists.libvirt.org/thread/DHYRALPVDMT2LFT2WYXRKHIOU6IAQVBX/ So, can anyone recommend a list/forum where this issue is more likely to attract some help? TIA Eyal On

Re: KVM image fails to resume after f38->40 upgrade

On 19/7/24 6:42 am, Samuel Sieb wrote: On 7/13/24 8:47 AM, fed...@eyal.emu.id.au wrote: I still do not have a solution. Changing the CPU model in the vm details is mostly "to be applied on next boot", but I am not in a position to boot (I need to unpause). If anyone understands what model to s

Re: KVM image fails to resume after f38->40 upgrade

On 7/13/24 8:47 AM, fed...@eyal.emu.id.au wrote: I still do not have a solution. Changing the CPU model in the vm details is mostly "to be applied on next boot", but I am not in a position to boot (I need to unpause). If anyone understands what model to set, or how else to get past this issu

Re: KVM image fails to resume after f38->40 upgrade

I still do not have a solution. Changing the CPU model in the vm details is mostly "to be applied on next boot", but I am not in a position to boot (I need to unpause). If anyone understands what model to set, or how else to get past this issue then please offer your wisdom. As an aside, what

KVM image fails to resume after f38->40 upgrade

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