Bug 430245 - Xen: clock stopped after reboot save/restore
Summary: Xen: clock stopped after reboot save/restore
Keywords:
Status: CLOSED DUPLICATE of bug 426861
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel
Version: 5.2
Hardware: i386
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: Xen Maintainance List
QA Contact: Martin Jenner
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-01-25 15:17 UTC by Joe Orton
Modified: 2008-02-19 08:17 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-02-19 08:17:33 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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 ***


Note You need to log in before you can comment on or make changes to this bug.