From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@bugzilla.kernel.org
Subject: [Bug 86161] New: PROBLEM: On KVM, Window 7 32bit guests sometimes
run into blue screen(0x0000005c) during reboot
Date: Mon, 13 Oct 2014 02:14:32 +0000
Message-ID:
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
To: kvm@vger.kernel.org
Return-path:
Received: from mail.kernel.org ([198.145.19.201]:39304 "EHLO mail.kernel.org"
rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
id S1752626AbaJMCOg (ORCPT );
Sun, 12 Oct 2014 22:14:36 -0400
Received: from mail.kernel.org (localhost [127.0.0.1])
by mail.kernel.org (Postfix) with ESMTP id 8445320212
for ; Mon, 13 Oct 2014 02:14:35 +0000 (UTC)
Received: from bugzilla1.web.kernel.org (bugzilla1.web.kernel.org [172.20.200.51])
by mail.kernel.org (Postfix) with ESMTP id A117D201EC
for ; Mon, 13 Oct 2014 02:14:33 +0000 (UTC)
Sender: kvm-owner@vger.kernel.org
List-ID:
https://bugzilla.kernel.org/show_bug.cgi?id=86161
Bug ID: 86161
Summary: PROBLEM: On KVM, Window 7 32bit guests sometimes run
into blue screen(0x0000005c) during reboot
Product: Virtualization
Version: unspecified
Kernel Version: 3.10.0 and newer
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: kvm
Assignee: virtualization_kvm@kernel-bugs.osdl.org
Reporter: ngugc@qq.com
Regression: No
Created attachment 153371
--> https://bugzilla.kernel.org/attachment.cgi?id=153371&action=edit
The blue screen snapshot
When running Windows 7 32bit guests on qemu-kvm, sometimes the guests run into
blue screen during reboot(Windows' reboot instead of qemu's).
Blue screen stop code:
0x0000005c(0x0000010b,0x00000003,0x00000000,0x00000000)
Once the error happens to a guest, use qemu 'system_reset' command to restart
it, the error can be reproduced.
Unfortunately, there is neither mini dump nor memory dump, only the above stop
code.
Kernel versions:
I have tested 3.10.0, 3.10.32, 3.10.57, 3.14.21. All of them are affected.
3.9.11 and 3.8.13 are not affected.
I guest the bug is introduced in 3.10.0, and exists in all 3.10 and newer
versions.
Guest OS:
Currently only Windows 7 32bit is affected.
Windows xp 32bit and Windows 7 64 bit are not affected.
Host CPU:
Intel(R) Xeon(R) CPU E5-2620 v2
Host OS:
CentOS 6.5
Recreate steps:
This error can not be recreated every reboot.
With below scenario, it can be recreated within 30 minutes:
* Prepare a Windows 7 32bit image as base image. Put below content into a batch
file(like auto_restart.bat):
shutdown /r /t 60
and put the batch file into the Windows startup folder, or anywhere so long
as it will be called after system startup.
This will make the Windows guests automatically restart after system startup
in 60 seconds.
* And create 30 child images as below:
qemu-img create -f qcow2 -o backing_file=win7_base,size=20G inst1.img
* Run all the guests:
nohup /usr/bin/qemu-system-x86_64 -name inst1 -machine
pc-i440fx-1.5,accel=kvm,usb=off -m 1024 -smp 1,sockets=1,cores=1,threads=1
-drive file=inst1.img,if=none,id=drive-ide0-0-0,format=qcow2,cache=writeback
-device ide-hd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1
-vnc 0.0.0.0:6100 -vga qxl -global qxl-vga.ram_size=67108864 -global
qxl-vga.vram_size=67108864 -chardev
socket,id=charmonitor,path=/var/lib/libvirt/qemu/inst1.monitor,server,nowait
-mon chardev=charmonitor,id=monitor,mode=readline -device
piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device usb-tablet,id=input0 2>&1
> /tmp/inst.out &
Remember to change the vnc port for each guest.
* After 30 minutes, check all the guests with vnc client, you will find some of
the guests have run into blue screen.
--
You are receiving this mail because:
You are watching the assignee of the bug.