From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: S3 sleep in dom0 breaks dom0<->domU wallclock synchronization Date: Tue, 06 Jul 2010 09:24:18 -0700 Message-ID: <4C3358B2.30903@goop.org> References: <4C33051B.30109@invisiblethingslab.com C858E525.197BC%keir.fraser@eu.citrix.com> <27792449-1cec-47b2-9821-163e9b713153@default> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <27792449-1cec-47b2-9821-163e9b713153@default> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Dan Magenheimer Cc: xen-devel@lists.xensource.com, Joanna Rutkowska , Konrad Wilk , Jan Beulich , Jeremy Fitzhardinge , Keir Fraser , Rafal Wojtczuk List-Id: xen-devel@lists.xenproject.org On 07/06/2010 07:53 AM, Dan Magenheimer wrote: > In the meantime, is there any easy way to stop dom0 > from entering S3? (E.g., like the Xen max_cstate parameter > for C states?) > > I've been seeing some similar guest issues recently running > RHEL6beta guests and wonder if I am seeing the same problem. > S3 is lid-close suspend on a laptop, or putting a desktop into sleep mode. It isn't something that occurs except when user initiated (or by policy, such as suspend on low battery). J