On 9/8/24 10:32 pm, Go Canes wrote:
On Fri, Aug 9, 2024 at 12:00 AM <fedora@xxxxxxxxxxxxxx> 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 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. Maybe you can explain where to extract it to.
Just
long enough to get it resumed and properly shutdown, then go back to
the current version.
Is there really anything important in the paused VM that will be lost
if you just reboot it?
Not really. I already did just that and it booted just fine (from a quick check).
I feel that proceeding to use it will be OK. It is just what crash+reboot looks like
for a real linux machine, and I had this many times and never lost much.
While this may be an interesting academic
exercise, it seems to be "off in the weeds",
"off in the weeds" is a good observation, and it really is just me wanting to understand
the situation and how it can be resolved properly. I hoped someone here knows how to resume,
I have only rudimentary understanding of libvirt and friends.
and even if you get the
paused VM resumed, I would have a certain amount of distrust for it
going forward.
If I can resume this image "correctly" then I will trust it more than a cold boot.
And BTW, I do have good backups of files that I care about. Naturally.
Regards,
--
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
