Thanks Barry,
On 11/8/24 5:21 pm, Barry Scott wrote:
On 13 Jul 2024, at 06:07, Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx> wrote:
Normally I actually stop it but forgot to do it this time.
I think this was discussed on https://discussion.fedoraproject.org <https://discussion.fedoraproject.org> a while ago.
Sorry I do not have a link to the discussion. You should be able to search and find it.
Tried many searches but failed to find the thread. If you (or anyone else) can find it then do tell.
I think the issue is that some defaults changed in KVM/libvirt and that meant that the checks
done to see if the resume of the VM can be done do not pass.
There was a way to change the defaults are get the VM to resume.
My understanding is that the saved state requires vmx-* features which are not available now (f40),
but were enabled when the vm was saved under f38.
Either the kernel turns these off, or a mitigation does this, or something else.
I tried many boot command options (one at a time):
dis_ucode_ldr
mitigations=off
kvm-intel.nested=1
but I still see (after a reboot) in lscpu:
KVM: Mitigation: VMX disabled
How to I force vmx to be enabled?
Eyal
Barry
--
Eyal at Home (fedora@xxxxxxxxxxxxxx)
--
_______________________________________________
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
