Re: Freezing Windows 2008 x64bit guest

[Gleb Natapov <gleb@redhat.com>]

On Wed, Jul 28, 2010 at 12:53:02AM +0300, Harri Olin wrote:
> Gleb Natapov wrote:
> >On Wed, Jul 21, 2010 at 09:25:31AM +0300, Harri Olin wrote:
> >>Gleb Natapov kirjoitti:
> >>>On Mon, Jul 19, 2010 at 10:17:02AM +0300, Harri Olin wrote:
> >>>>Gleb Natapov kirjoitti:
> >>>>>On Thu, Jul 15, 2010 at 03:19:44PM +0200, Christoph Adomeit wrote:
> >>>>>>But one Windows 2008 64 Bit Server Standard is freezing regularly.
> >>>>>>This happens sometimes 3 times a day, sometimes it takes 2 days
> >>>>>>until freeze. The Windows Machine is a clean fresh install.
> >>>>I think I have seen same problem occur on my Windows 2008 SBS SP2
> >>>>64bit system, but a bit less often, only like once a week.
> >>>>Now I haven't seen crashes but only freezes with qemu on 100% and
> >>>>virtual system unresponsive.
> >Does sendkey from monitor works? qemu-kvm-0.11.1 is very old and this is
> >not total freeze which even harder to debug. I don't see anything
> >extraordinary in your logs. 4643 interrupt per second for 4 cpus is
> >normal if windows runs multimedia or other app that need hi-res timers.
> >Does your host swapping? Is there any chance that you can try upstream qemu-kvm?
> 
> I tried running qemu-kvm from git but it exhibited the same problem
> as 12.x that I tried before, BSODing once in a while, running kernel
> 2.6.34.1.
> 
That should be pretty stable config, although it would be nice if you
could try running in qemy-kvm.git head.

> sample BSOD failure details:
> These two with Realtec nic and qemu cpu
> 0x00000019 (0x0000000000000020, 0xfffff88007e65970,
> 0xfffff88007e65990, 0x000000000502040f)
> 0x00000019 (0x0000000000000020, 0xfffff88007a414c0,
> 0xfffff88007a414e0, 0x000000000502044c)
> 
> These are with e1000 and -cpu host
> 0x0000003b (0x00000000c0000005, 0xfffff80001c5d842,
> 0xfffffa60093ddb70, 0x0000000000000000)
> 0x0000003b (0x00000000c0000005, 0xfffff80001cb8842,
> 0xfffffa600c94ab70, 0x0000000000000000)
> 0x0000000a (0x0000000000000080, 0x000000000000000c,
> 0x0000000000000001, 0xfffff80001cadefd)
> 
Can you attach screenshots of BSODs? Have you reinstalled your guests or
are you running the same images you ran in 11.x?

> I'll see if I can analyze minidumps later.
> 
> In addition to these there have been as many reboots that have been
> only logged as 'disruptive shutdown'.
> 
> Right now I'm running the problematic guest under Xen
> 3.2.1-something from Debian to see if it works better.
> 
> -- 
> Harri.

--
			Gleb.