From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:48570) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XK0zU-0006io-FY for qemu-devel@nongnu.org; Wed, 20 Aug 2014 04:11:38 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XK0zL-0001HZ-Vb for qemu-devel@nongnu.org; Wed, 20 Aug 2014 04:11:32 -0400 Received: from mx1.redhat.com ([209.132.183.28]:21135) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XK0zL-0001GD-Og for qemu-devel@nongnu.org; Wed, 20 Aug 2014 04:11:23 -0400 Received: from int-mx11.intmail.prod.int.phx2.redhat.com (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id s7K8BLHH017043 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Wed, 20 Aug 2014 04:11:21 -0400 Message-ID: <53F45826.8040106@redhat.com> Date: Wed, 20 Aug 2014 10:11:18 +0200 From: Michal Privoznik MIME-Version: 1.0 References: <075846faf30f2244fbaaf2c9f47cbae58a9524db.1408004697.git.mprivozn@redhat.com> <53F21B82.4050006@redhat.com> <53F229F6.6090602@redhat.com> <20140819165713.GA4488@amt.cnet> <53F382AA.5020405@redhat.com> <20140819172324.GA5717@amt.cnet> In-Reply-To: <20140819172324.GA5717@amt.cnet> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit 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: Marcelo Tosatti , Eric Blake Cc: libvir-list@redhat.com, qemu-devel On 19.08.2014 19:23, Marcelo Tosatti wrote: > 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. > Okay then. I'm posting v3 here [1] which unconditionally calls the monitor command right after the guest agent command. Michal 1: https://www.redhat.com/archives/libvir-list/2014-August/msg00867.html