From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:44796) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TEMIu-0004PZ-Ce for qemu-devel@nongnu.org; Wed, 19 Sep 2012 11:35:14 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TEMIn-0007xL-4y for qemu-devel@nongnu.org; Wed, 19 Sep 2012 11:35:08 -0400 Received: from mx1.redhat.com ([209.132.183.28]:11558) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TEMIm-0007xE-Qz for qemu-devel@nongnu.org; Wed, 19 Sep 2012 11:35:01 -0400 Message-ID: <5059E616.5080500@redhat.com> Date: Wed, 19 Sep 2012 18:34:46 +0300 From: Avi Kivity MIME-Version: 1.0 References: <87pq5r5otp.fsf@codemonkey.ws> <20120912151549.GT20907@redhat.com> <87y5kfrtne.fsf@codemonkey.ws> <20120913104940.GA20907@redhat.com> <5051DC20.4090204@redhat.com> <20120913132804.GO7767@redhat.com> <87r4q6xbiy.fsf@codemonkey.ws> <20120913142228.GK20907@redhat.com> <5051EF0D.4070109@redhat.com> <5051F0CB.9040303@redhat.com> <5051FE85.6070904@redhat.com> <87har1orbl.fsf@codemonkey.ws> <50520189.3050707@redhat.com> <87627h7p7n.fsf@codemonkey.ws> <5055A459.1030909@redhat.com> <87vcfenieq.fsf@codemonkey.ws> In-Reply-To: <87vcfenieq.fsf@codemonkey.ws> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] Rethinking missed tick catchup List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: Gleb Natapov , Jan Kiszka , Michael Roth , qemu-devel@nongnu.org, Paolo Bonzini , Luiz Capitulino , Eric Blake On 09/16/2012 05:37 PM, Anthony Liguori wrote: > Avi Kivity writes: > >> On 09/13/2012 09:27 PM, Anthony Liguori wrote: >>> If there was a better/equivalent solution that didn't depend on qemu-ga, >>> I'd be all for it. But there isn't AFAICT. >> >> Perhaps there is. We fixed the problem for Linux by adding kvmclock and >> backporting it to distros that users are most likely to use. Windows >> fixed the problem by adding their own pv clock interface. So we need to >> implement that, then focus on tick catchup for Windows XP and other >> guests with no pv interface (*BSD, etc.) > > Tick catchup simply isn't going to work. That's the whole point of the thread. I'll restate. Windows and Linux don't need either qemu-ga or tick catchup since they have pv time interfaces. FreeBSD and less frequently used guests are unlikely to get a qemu-ga port, so they need tick catchup. Is there reason to believe tick catchup won't work on FreeBSD? >> >> Those older guests are also less likely to have a qemu-ga port or >> administrator motivation to install it. > > That's a strange assertion to make. FWIW, the issue with hibernation > was reported to me with a combination of WinXP and Windows 7 guests, in > this case, it's a totally new deployment. Adding qemu-ga is totally > reasonable. Windows 7 doesn't need anything if we implement the pv time interface. That is less effort than requiring a qemu-ga installation. Windows XP is an edge case. We can of course support qemu-ga for it, or we can massage the tick code to work with it, since it's timekeeping is likely a lot less sophisticated than 7's. -- error compiling committee.c: too many arguments to function