FYI,
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
Xen-community@lists.xensource.com
http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-community
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
Xen-community@lists.xensource.com
http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-community