From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: S3 sleep in dom0 breaks dom0<->domU wallclock synchronization Date: Thu, 1 Jul 2010 17:12:10 +0100 Message-ID: References: <4C2CB1BE.2080804@invisiblethingslab.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4C2CB1BE.2080804@invisiblethingslab.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Joanna Rutkowska Cc: "xen-devel@lists.xensource.com" , Jeremy Fitzhardinge , Rafal Wojtczuk List-Id: xen-devel@lists.xenproject.org On 01/07/2010 16:18, "Joanna Rutkowska" wrote: > Actually we're running a pvops kernel in DomUs (in fact a fairly recent > pvops0, as we had some bad experience with regular Fedora kernels in DomU). > > Running an NTP in every VM is not a good solution. Some VMs might be > forbidden any access to the network (e.g. my "vault" VM, that I use for > storing passwords, and other very sensitive stuff, doesn't have any > networking), while some other might be allowed only very limited network > traffic, e.g. only HTTPS to specific, white-listed servers (e.g. > "banking" VM). Well it would be good to confirm first that this is a pv_ops domU issue. If so, it can probably be solved with a command-line option or somesuch, even if the default policy will not change. -- Keir