Description of problem: When domain-0 is rebooted without shutting down the domU gracefully, it creates an incomplete save file in /var/lib/xen/save/<domU name>, and you can not start that domU anymore unless you remove /var/lib/xen/save/<domU name> Version-Release number of selected component (if applicable): xen-3.0.3-25.0.3.el5.x86_64 How reproducible: easy Steps to Reproduce: 1. create a runable domU, say rhel3_32 2. xm create rhel3_32 3. reboot domain-0 (host) machine without shutting down rhel3_32 Actual results: Expected results: Additional info:
Please provide the guest config file and /var/log/xen/xend.log and /var/log/xen/xend-debug.log
Created attachment 157509 [details] /var/log/xen/xend.log
Created attachment 157510 [details] /var/log/xen/xend-debug.log
Please trace back the time stamp before 17:30 June 20 in the log. Because I have remove the /var/lib/xen/save/rhel3_32 before reboot after 17:30 June 20.
Created attachment 157511 [details] bash -x /etc/init.d/xendomains start (with /var/lib/xen/save/rhel3_32)
The xend.log file shows that rhel3_32 is a fully virtualized guest. Save and restore does not work for fullvirtualized guests in Xen 3.0.3. *** This bug has been marked as a duplicate of 214995 ***
OK. If fully virtualized guest is not supported in in Xen 3.0.3, then it should not save the fully-virtualized domU when the dom0 reboot. It should destroy the fully-virtualized domU to avoid restoring issue, shouldn't it? Otherwise, when dom0 crashes or power outage, all the fully-virtualized domUs will have the issue to bring on up.