[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] localtime=1 broken on HVM guests
- To: Randy McAnally <rsm@xxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
- From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
- Date: Tue, 29 Jan 2008 11:03:23 +0000
- Delivery-date: Tue, 29 Jan 2008 03:04:09 -0800
- List-id: Xen developer discussion <xen-devel.lists.xensource.com>
- Thread-index: AchiZpB3zygW0s5ZEdyyYwAX8io7RQ==
- Thread-topic: [Xen-devel] localtime=1 broken on HVM guests
With current xen-3.1-testing tip (which is basically not much different from
-rc2) I find the localtime option works fine for me. What I did was change
my dom0 timezone to US Pacific, then create a domU with 'localtime=1' in its
config file, and then create a domU with no localtime config. The former
showed output in 'date' 8 hours behind the 'date' output of the latter. The
guests were created using the usual 'xm create <config file>' method.
Are your dom0 user-space tools definitely up to date?
On 28/1/08 22:24, "Randy McAnally" <rsm@xxxxxxxxxxxxx> wrote:
> I have confirmed that the localtime option in guest config is broken in Xen
> 3.1.3-rc2. No matter what the setting, UTC is always given to the guest.
> I have tried putting the HC in UTC and in Localtime, it makes no
> difference. Aside from setting the system clock to the wrong time (or
> defining an offset in guest config), it is impossible to send localtime to
> the guest.
> Is there anyone who has the knowledge to look at this lingering bug and
> finally squash it?
Xen-devel mailing list