qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: Matthew Anderson <matthewa@base3.com.au>
Cc: 'mdroth' <mdroth@linux.vnet.ibm.com>,
	"'qemu-devel@nongnu.org'" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] BUG: RTC issue when Windows guest is idle
Date: Tue, 19 Mar 2013 19:53:49 +0200	[thread overview]
Message-ID: <20130319175349.GK19292@redhat.com> (raw)
In-Reply-To: <208f1bef31464d119e3b6801288b6d3b@Exchange2013.corit.local>

On Thu, Mar 14, 2013 at 04:15:10AM +0000, Matthew Anderson wrote:
> Thanks for the suggestion but so far it hasn't made any difference.
> 
> I thought I may be an issue with the mainline kernel I was using so I changed over to Ubuntu 12.10 and QEMU 1.2.0. Stability is slightly better but I still get 2-3 VM's a day out of about 120 experiencing this bug in the exact same way as before.  Time in the guest simply stop's ticking over and when you attempt to interact with the VM the lost ticks get replayed as fast as possible. Because of the time being out practically nothing works as it breaks crypto support (as well as practically everything else).
> 
> In addition to what I posted previously I've tried -
> Setting the CPU type to host, qemu64 and kvm64
> Setting the machine type to 0.14, 0.15, 1.0, 1.1 and 1.2 (plus 1.3 and 1.4 from previous testing)
> With and without the HPET timer using combinations of the above
> 
> The settings I'm using work fine on the Centos 6.3 (2.6.32) kernel and QEMU 1.4.0. I've only had this problem since upgrading the kernel which is the only evidence I have of it being a kernel/KVM bug. I'm incredibly desparate for any solution or advice that may lead to getting this problem sorted,I'm getting a tyrade of angry phone called every morning that's making me want to go postal. 
> 
Is this happening to all VMs on the same machine simultaneously?

--
			Gleb.

  reply	other threads:[~2013-03-19 17:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5C390CF7F373CC4AB58A6684FF6C8712013DD0E2@Exchange2010-2.corit.local>
     [not found] ` <20130221222246.GH10005@vm>
2013-03-14  4:15   ` [Qemu-devel] BUG: RTC issue when Windows guest is idle Matthew Anderson
2013-03-19 17:53     ` Gleb Natapov [this message]
2013-10-08  9:38 Xiexiangyou
2013-10-16 14:56 ` Matthew Anderson
2013-10-21 14:56   ` Alex Bligh
2013-10-21 15:13     ` Alex Bligh
2013-10-22  8:28     ` Xiexiangyou
2013-10-22  9:35       ` Alex Bligh
2013-10-28  6:58         ` Matthew Anderson
2013-10-28  7:44           ` Alex Bligh
2013-10-28  8:46             ` Alex Bligh
2013-10-30  0:44             ` Xiexiangyou
2013-10-30  7:23               ` Alex Bligh
2013-10-28 11:51           ` Paolo Bonzini
2013-10-30  1:29           ` Xiexiangyou
2013-10-30  7:26             ` Alex Bligh

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130319175349.GK19292@redhat.com \
    --to=gleb@redhat.com \
    --cc=matthewa@base3.com.au \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).