Bug 430245

Summary: Xen: clock stopped after reboot save/restore
Product: Red Hat Enterprise Linux 5 Reporter: Joe Orton <jorton>
Component: kernelAssignee: Xen Maintainance List <xen-maint>
Status: CLOSED DUPLICATE QA Contact: Martin Jenner <mjenner>
Severity: low Docs Contact:
Priority: low    
Version: 5.2CC: zbrown
Target Milestone: rc   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-02-19 08:17:33 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:

Description Joe Orton 2008-01-25 15:17:46 UTC 
Description of problem:
After rebooting the dom0, two guests have come back up without a ticking clock.
 dom0 is running xendomains so the guests were automatically save/restored over
the reboot.

[root@dhcp-0-208 ~]# date
Thu Jan 24 11:18:08 GMT 2008
[root@dhcp-0-208 ~]# date
Thu Jan 24 11:18:08 GMT 2008
[root@dhcp-0-208 ~]# date
Thu Jan 24 11:18:08 GMT 2008

This corresponds roughly to the time at which the guest state would have been saved:

reboot   system boot  2.6.18-53.1.6.el Thu Jan 24 11:20          (00:02)    
root     pts/4        vpn-6-11.fab.red Thu Jan 24 11:15 - down   (00:01)    
root     pts/0        vpn-6-11.fab.red Thu Jan 24 11:10 - down   (00:07)    

The guests seem otherwise fine; userspace is working albeit system calls act as
if time stands still (e.g. poll doesn't time out, nanosleep sleeps forever).

Version-Release number of selected component (if applicable):
dom0: 2.6.18-53.1.6.el5xen
guest: 2.6.18-53.el5xen

How reproducible:
This has affected 2/6 guests on the system; 4 of which were running RHEL 5.1
Comment 1 Joe Orton 2008-02-19 08:17:33 UTC 

*** This bug has been marked as a duplicate of 426861 ***