From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:56676) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XJn8V-0002er-6D for qemu-devel@nongnu.org; Tue, 19 Aug 2014 13:24:01 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XJn8P-0003cV-1W for qemu-devel@nongnu.org; Tue, 19 Aug 2014 13:23:55 -0400 Received: from mx1.redhat.com ([209.132.183.28]:20244) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XJn8O-0003c4-Qq for qemu-devel@nongnu.org; Tue, 19 Aug 2014 13:23:48 -0400 Received: from int-mx13.intmail.prod.int.phx2.redhat.com (int-mx13.intmail.prod.int.phx2.redhat.com [10.5.11.26]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id s7JHNm4C006859 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Tue, 19 Aug 2014 13:23:48 -0400 Date: Tue, 19 Aug 2014 14:23:24 -0300 From: Marcelo Tosatti Message-ID: <20140819172324.GA5717@amt.cnet> References: <075846faf30f2244fbaaf2c9f47cbae58a9524db.1408004697.git.mprivozn@redhat.com> <53F21B82.4050006@redhat.com> <53F229F6.6090602@redhat.com> <20140819165713.GA4488@amt.cnet> <53F382AA.5020405@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <53F382AA.5020405@redhat.com> Subject: Re: [Qemu-devel] [libvirt] [PATCHv2 libvirt] qemu: Issue rtc-reset-reinjection command after guest-set-time List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Eric Blake Cc: libvir-list@redhat.com, Michal Privoznik , qemu-devel On Tue, Aug 19, 2014 at 11:00:26AM -0600, Eric Blake wrote: > On 08/19/2014 10:57 AM, Marcelo Tosatti wrote: > > > > rtc-reset-reinjection has been introduced because certain Windows > > versions will advance the guest system time (via rtc interrupt > > reinjection). > > > > So if libvirt adjusts the guest system time via guest-set-time, > > allowing rtc interrupt reinjection to compensate for lost time, > > as well, will cause an incorrect guest system time. > > > > So you should always use the > > > > guest-set-time > > rtc-reset-reinjection > > > > pair. > > But is that true both for the 'guest-set-time' no-arg case (which tells > the guest to read the current RTC and update in-memory time > accordingly), as well as the 'guest-set-time with time argument' case > (which tells the guest to forcefully set in-memory time, then write that > time back to the RTC)? Yes.