From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:57802)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <vrozenfe@redhat.com>) id 1S8GlU-00005x-9R
	for qemu-devel@nongnu.org; Thu, 15 Mar 2012 15:55:34 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <vrozenfe@redhat.com>) id 1S8GlS-000451-D0
	for qemu-devel@nongnu.org; Thu, 15 Mar 2012 15:55:11 -0400
Received: from mx1.redhat.com ([209.132.183.28]:64093)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <vrozenfe@redhat.com>) id 1S8GlS-00044n-4q
	for qemu-devel@nongnu.org; Thu, 15 Mar 2012 15:55:10 -0400
From: Vadim Rozenfeld <vrozenfe@redhat.com>
Date: Thu, 15 Mar 2012 21:54:59 +0200
References: <20120315191439.GM2894@illuin>
In-Reply-To: <20120315191439.GM2894@illuin>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <201203152155.01481.vrozenfe@redhat.com>
Subject: Re: [Qemu-devel] BSOD when using Hyper-V extensions with Win2k8R2
	guests
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Michael Roth <mdroth@linux.vnet.ibm.com>
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org

On Thursday, March 15, 2012 09:14:39 PM Michael Roth wrote:
> Hi Vadim,
> 
> I've been trying to use -cpu qemu64,hv_relaxed as a workaround for a
> CLOCK_WATCHDOG_TIMEOUT BSOD on Windows 2008 R2 guests when a vcpu's
> execution is delayed for an extended period. When I do this however I get
> the following the BSOD:
> 
> http://msdn.microsoft.com/en-us/library/windows/hardware/ff559206(v=vs.85).
> aspx
> 
> I've also tried -cpu qemu64,hv_spinlocks=4 and -cpu qemu64,hv_vapic as a
> sanity check and this results in the same error being thrown.
> 
> Host is RHEL6.1 using latest qemu.git, guests are win2k8 server r2 (same

I'm pretty much sure that hyper-v support was not backported into RHEL 6.1 
KVM.
Best regards,
Vadim.  

> behavior for both SP0 and SP1). Here's the full command-line:
> 
> qemu-upstream -L ../qemu-build/pc-bios -cpu qemu64,hv_relaxed --enable-kvm
> \ -M pc-1.1 -enable-kvm -m 4096 -smp 4,sockets=4,cores=1,threads=1 \ -name
> ichigo-dom45 -nodefconfig -nodefaults -rtc base=utc,driftfix=slew \ -drive
> file=/scratch/mdroth/win2k8r2sp1.raw,if=none,id=drive0,format=raw,cache=wr
> itethrough,snapshot=on \ -device
> virtio-blk-pci,bus=pci.0,drive=drive0,id=disk0,bootindex=1 \ -netdev
> tap,id=hostnet0,script=/etc/qemu-ifup \
>     -device
> virtio-net-pci,netdev=hostnet0,id=net0,mac=00:FF:FE:00:00:2d,bus=pci.0 \
> -device virtio-balloon-pci,id=balloon0,bus=pci.0 \
>     -usb -device usb-tablet,id=input0 -vnc 0.0.0.0:45 -vga cirrus
> 
> Unfortunately the BSOD is too early to get a kernel dump, but here are
> the error params in case that's useful:
> 
> 0xFC0000096, 0xF800027F6200, 0x0, 0x0
> 
> Let me know if you need any other details.
> 
> Thanks!