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


Re: [Xen-users] xm console freeze after change time backend in dom0.

To: "Yi, Shunli" <syi@xxxxxxxxxxxx>
Subject: Re: [Xen-users] xm console freeze after change time backend in dom0.
From: vu pham <vu@xxxxxxxxxx>
Date: Wed, 15 Apr 2009 08:07:06 -0500
Cc: "xen-users@xxxxxxxxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 15 Apr 2009 06:08:26 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <E6ED841B7ED3FA4AB123FEAEF42B0ACA03F658792F@xxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <E6ED841B7ED3FA4AB123FEAEF42B0ACA03F658792F@xxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird (X11/20090320)

Yi, Shunli wrote:
HI :

I have a dell 1950 server with domu running, when I change the time backend, I find the “xm console” doesn’t work anymore( after 5~8 characters input, it will freeze) . Sometimes, I change the time forward, it works again. Could somebody tell me the reason? If there is a way, how to avoid this problem?

Details steps:

1.       Current date:  2009-04-15

2.       Change date by “date –s 20090410”

3.       Connect to domu by “xm console “

4.       I can input 5~8 characters, but after that, it freeze.

5.       Just change the date forward, ( such as “date –s 20090416” )

6.       Xm console works well again.

Interesting ! I do not know the answer but I notice it happens on my RHEL5.3, too.


Xen-users mailing list