This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-bugs] [Bug 265] New: Time stood still


           Summary: Time stood still
           Product: Xen
           Version: unstable
          Platform: x86
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Hypervisor
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: dbarrera@xxxxxxxxxx
                CC: hohnbaum@xxxxxxxxxx

While running xm-test on two IBM xSeries 335s, one FC4 and the other one SLES 9,
I noticed that time has stopped:

[root@x335a xm-test]# date
Wed Sep 28 13:59:18 CDT 2005
[root@x335a xm-test]# date
Wed Sep 28 13:59:18 CDT 2005
>> 15 minutes later,
[root@x335a xm-test]# date
Wed Sep 28 13:59:18 CDT 2005
[root@x335a xm-test]#

changeset:   7076:46046d5fb354
tag:         tip
user:        emellor@ewan
date:        Tue Sep 27 16:09:46 2005 +0100
summary:     Remove unused import, mark unused variables.

The last output lines produced by xm-test are:
cp 06_destroy_dom0_neg.py 06_destroy_dom0_neg.test
chmod +x 06_destroy_dom0_neg.test

The machines in quiestion are running xm-test at the moment and appear 'stuck'.
Both are displaying the "(XEN) Ouch! We are seriously BEHIND schedule!"
messages. However, the static time issue may not be related to the Ouch! issue,
bug # 257, as Paul Larson observed it on a machine that was not running xm-test
at the time, hence we are submitting it as a different bug.

Configure bugmail: 
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Xen-bugs mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-bugs] [Bug 265] New: Time stood still, bugzilla-daemon <=