On 19/7/24 6:42 am, Samuel Sieb wrote:
On 7/13/24 8:47 AM, fedora@xxxxxxxxxxxxxx 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 issue then please offer your wisdom.
As an aside, what lead to this problem in the first place? The same problem when booting my last f30 kernel
so it must be (?) some libvirt change.
I hope that as a last resort I will be able to cold boot the vm, linux is rather good with crash recovery.
Last resort.
I ran into this as well. Something changed with CPU flags. I couldn't find any way to get it to resume, it will most likely need to be restarted.
I tested a restart (using a clone) and it came up.
I only needed to change the watchdog
old <watchdog model="itco" action="reset"/>
new <watchdog model="i6300esb" action="reset"/>
I created a thread on the users list
https://lists.libvirt.org/archives/list/users@xxxxxxxxxxxxxxxxx/thread/DHYRALPVDMT2LFT2WYXRKHIOU6IAQVBX/
but got no response :-)
--
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
