|
|
|
|
|
|
|
|
|
|
xen-devel
[Xen-devel] repeatable time jump
I got the time jump to reproduce. Shutting down xenU shifts system time on
xen0 by over an hour. xen0 hwclock stays steady:
xen0# date
Tue Sep 28 10:45:13 EDT 2004
xen0# xm list
Name Id Mem(MB) CPU State Time(s) Console
Domain-0 0 34 0 r---- 120.1
xen0# xm create memory=800 name=athos14
builder=linux kernel=/boot/vmlinuz-2.6.8.1-xenU ipaddr=172.16.11.24
ip=172.16.11.24 gateway= netmask=255.255.255.0 hostname=athos14
interface=eth0 dhcp=off disk=phy:/dev/xenvg/athos14.root,hda1,w cpu=-1
disk=phy:/dev/xenvg/athos14.swap,hda2,w root=/dev/hda1
Using config file "/etc/xen/xmdefconfig".
Started domain athos14, console on port 9605
xen0# date
Tue Sep 28 10:47:16 EDT 2004
xen0# xm shutdown athos14
xen0# xm list
Name Id Mem(MB) CPU State Time(s) Console
Domain-0 0 34 0 r---- 129.2
xen0# date
Tue Sep 28 11:59:01 EDT 2004
xen0# hwclock
Tue Sep 28 10:48:02 2004 -0.000000 seconds
The xen0 shift happens when xen0 clock is correct. Further starting/stopping
of domains after the xen0 clock is off has more effect on xen0's system time.
xenU does not run ntp or hwclock. If xenU is started after xen0's
system time is off, xenU has the right time. I assume xenU is synced to
the hwclock time.
This is with today's pull of 2.6.8.1. I'm using 2.6 for all domains.
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Xen-devel] repeatable time jump,
David Becker <=
|
|
|
|
|