From: Andrew Cooper <andrew.cooper3@citrix.com>
To: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
Jan Beulich <JBeulich@suse.com>
Subject: Re: Results from the Xen 4.4-rc2 test day
Date: Thu, 23 Jan 2014 11:54:28 +0000 [thread overview]
Message-ID: <52E102F4.3060503@citrix.com> (raw)
In-Reply-To: <52DE4BD8.7060209@citrix.com>
On 21/01/14 10:28, Andrew Cooper wrote:
> Hello,
>
> I participated in (a rather extended version of) the 4.4-rc2 test day,
> and rc2 got a full XenRT nightly run in the XenServer testing system.
>
> For the setup, the comparison is against XenServer trunk, which is
> currently Xen-4.3-staging based (plus patch queue), Linux 3.10.y dom0
> kernel, CentOS 6.4 based dom0 userspace.
>
> The tested version had Xen 4.4 (staging, as I needed the ABI fix) in
> place of Xen-4.3, but identical dom0 kernel, dom0 userspace, qemu,
> toolstack and windows PV drivers.
>
>
> The major issue identified is with Windows 8/8.1 and Server 2012/2012r2,
> which have problems on live migrate. Some source of time is
> unexpectedly jumping forwards by two days, from the correct time to 2
> days in the future. The observed result is that it looses its DHCP
> lease, drops its IP address and networking ceases to work (It appears
> that windows will not attempt to renew the lease itself).
>
This is caused by commit e36cd2cdc9674a7a4855d21fb7b3e6e17c4bb33b
"x86/viridian: Time Reference Count MSR"
After double checking with the specification, it does appear to be
implemented as required (subject to a potential issue with multiple vcpu
guests).
I am currently experimenting to see whether hvm_get_guest_time() is
returning unexpected values, or whether it is returning expected values
and Windows is interpreting them differently.
At this point in the 4.4 release cycle, reverting the patch should be
seriously considered, although I would like to see whether it is
possible to work out why it is wrong and whether there is an obvious fix
first.
~Andrew
next prev parent reply other threads:[~2014-01-23 11:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-21 10:28 Results from the Xen 4.4-rc2 test day Andrew Cooper
2014-01-23 11:54 ` Andrew Cooper [this message]
2014-01-23 12:53 ` Jan Beulich
2014-01-23 17:17 ` Andrew Cooper
2014-01-24 9:23 ` Jan Beulich
2014-01-24 11:37 ` Andrew Cooper
2014-01-24 16:19 ` George Dunlap
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52E102F4.3060503@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=george.dunlap@eu.citrix.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.