Red Hat Bugzilla – Bug 486308
HVM guest stops running when xm save fails
Last modified: 2014-02-02 17:36:49 EST
Created attachment 332523 [details]
Description of problem:
When xm save of an HVM guest fails, the guest stops running.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. create an HVM guest
2. xm save guest /mnt/small/guest.save
The guest stops running, xm list shows no status:
fv-rhel5-64 4 511 2 ------ 45.3
The guest should remain running as if no xm save command was ever issued
No qemu-dm is running in dom0 after failed xm save
Created attachment 332524 [details]
Well, I have tried this on 83-jd2 with my patches (available at http://people.redhat.com/minovotn/xen ) and I was unable to replicate it using this scenario:
1. xm create -c FVguest
2. wait to login
3. make domain working using eg. `find /` in domain console (or ssh)
4. do `xm save FVguest /mnt/small/guest.save` -> error
5. `xm list` still shows domain
6. attach to console for domain, console is working and listing files
7. terminate console and shutdown the guest, system starts shutting down
I probably should have made it more clear... xm save guest /mnt/small/guest.save is supposed to fail because of insufficient space on the drive mounted to /mnt/small and not because the path does not exist at all.
Ok, thanks for clarification :) It's good to know that ;)
Created attachment 404212 [details]
Recreate device model when HVM save fails
This is the patch to recreate device model when xm save on HVM domains fails, also device reinitialization had to be added since otherwise the guest network was not working.
Created attachment 405944 [details]
New version of device model recreation patch
This is the new version of my patch to recreate device model when HVM guest save fails with the reconnection logic moved to DevController class.
This bug has been verified in xen-3.0.3-115.el5
The PV guest runs WELL after "xm save" failed.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.