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-community] Back in time..

To: xen-community@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-community] Back in time..
From: b52@xxxxxxxxx
Date: Thu, 21 Feb 2008 19:33:17 +0100 (CET)
Delivery-date: Fri, 22 Feb 2008 09:15:31 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
Importance: Normal
List-archive: <http://lists.xensource.com/archives/html/xen-community>
List-help: <mailto:xen-community-request@lists.xensource.com?subject=help>
List-id: Community Discussion <xen-community.lists.xensource.com>
List-post: <mailto:xen-community@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-community>, <mailto:xen-community-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-community>, <mailto:xen-community-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-community-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: SquirrelMail/1.4.9a

I did a live migration of a domU between two hosts (xen3.1.3).
The time at the destination host was 10 seconds behind the time at the
source host. After migrating from "the future to the past" I discoverd
that the time stops inside the domU, until the destination host reaches
the migration time of the source host. Then time and space is normal again

You may verify this with date in a domU console.

I discovered this, because after migration the domU was not able to ping
any hosts and got 0.000ms values. Everything else, which wasn't related to
time (and space) worked normal.

 CYA yesterday .. *plop*
 -- Holger

Xen-community mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-community] Back in time.., b52 <=