Bug 245099
Summary: | incomplete domU save file when domain-0 reboot | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Wesly Chen <wesly_chen> | ||||||||
Component: | xen | Assignee: | Xen Maintainance List <xen-maint> | ||||||||
Status: | CLOSED DUPLICATE | QA Contact: | |||||||||
Severity: | medium | Docs Contact: | |||||||||
Priority: | low | ||||||||||
Version: | 5.0 | ||||||||||
Target Milestone: | --- | ||||||||||
Target Release: | --- | ||||||||||
Hardware: | All | ||||||||||
OS: | Linux | ||||||||||
Whiteboard: | |||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||
Doc Text: | Story Points: | --- | |||||||||
Clone Of: | Environment: | ||||||||||
Last Closed: | 2007-06-21 12:43:21 UTC | Type: | --- | ||||||||
Regression: | --- | Mount Type: | --- | ||||||||
Documentation: | --- | CRM: | |||||||||
Verified Versions: | Category: | --- | |||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||
Embargoed: | |||||||||||
Attachments: |
|
Description
Wesly Chen
2007-06-21 02:23:16 UTC
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. |