Bug#657617: xen-qemu-dm-4.0: Windows 2008 R2 VM reboot with SMP and high I/O-Load (bugcheck 101)

January 27th, 2012 - 08:30 am ET by Markus Jansen | Report spam
Package: xen-qemu-dm-4.0
Version: 4.0.1-2
Severity: normal

"Windows 2008 R2" virtual machine reboots after ~ 10 minutes of high I/O load in case of using more than one vcpu (see xen configuration below). The qemu-dm-Logile says "XenPCI Bug check 0x00000101 (0x0000000000000030, 0x0000000000000000, 0xFFFFF880009B8180, 0x0000000000000001)" (see logfile below). Microsoft says, bug check 0x101 is caused by "The specified processor is not processing interrupts. Typically, this occurs when the processor is nonresponsive or is deadlocked. " (see here: http://msdn.microsoft.com/en-us/lib...85%29.aspx)

To reproduce this error, i just copied some big files (~ 5 GiB each file) within the virtual machine from one folder on drive C: to another folder concurrently. After approx. 10 minutes, the crashs and reboots automatically. I disable "shadow_memory", "acpi" and "apic" but this doesn't work either.

But when I remove the cpus and vcpus - parameter from the xen config files, the default value of only 1 cpu to be used by the virtual machine, everything works fine. The virtual machine seems to be stable although copying files as done before some hours long.

import os, re
arch = os.uname()[4]
if re.search('64', arch):
arch_libdir = 'lib64'
arch_libdir = 'lib'

name = 'filemaker11'

memory = 12000
shadow_memory = 24

kernel = '/usr/lib/xen-default/boot/hvmloader'

device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm'
builder = 'hvm'

disk = [ 'file:/home/filemaker/image.img,hda,w', 'file:/home/filemaker-backup/image.img,hdb,w' ]

vif = [ 'bridge=eth0, mac:99:27:2d:39:1a' ]

cpus = ['1', '2', '3', '4']
vcpus = 4

acpi = 1
apic = 1

on_crash = 'restart'





Debian Release: 6.0.3
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages xen-qemu-dm-4.0 depends on:
ii etherboot 5.4.4-9 Bootstrapping for various network
ii libasound2 1.0.23-2.1 shared library for ALSA applicatio
ii libbluetooth3 4.66-3 Library to use the BlueZ Linux Blu
ii libbrlapi0.5 4.2-7+squeeze1 braille display access via BRLTTY
ii libc6 2.11.2-10 Embedded GNU C Library: Shared lib
ii libesd0 0.2.41-8 Enlightened Sound Daemon - Shared
ii libgl1-mesa-glx [l 7.7.1-5 A free implementation of the OpenG
ii libgnutls26 2.8.6-1 the GNU TLS library - runtime libr
ii libpci3 1:3.1.7-6 Linux PCI Utilities (shared librar
ii libpulse0 0.9.21-3+squeeze1 PulseAudio client libraries
ii libsdl1.2debian 1.2.14-6.1 Simple DirectMedia Layer
ii libx11-6 2:1.3.3-4 X11 client-side library
ii libxenstore3.0 4.0.1-4 Xenstore communications library fo
ii libxext6 2:1.1.2-1 X11 miscellaneous extension librar
ii qemu 0.12.5+dfsg-3squeeze1 fast processor emulator
ii qemu-system 0.12.5+dfsg-3squeeze1 QEMU full system emulation binarie
ii xen-hypervisor-4.0 4.0.1-4 The Xen Hypervisor on AMD64
ii zlib1g 1: compression library - runtime

xen-qemu-dm-4.0 recommends no packages.

xen-qemu-dm-4.0 suggests no packages.

To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
email Follow the discussionReplies 2 repliesReplies Make a reply

Similar topics


#1 Thomas Goirand
January 27th, 2012 - 11:40 am ET | Report spam
Hi Markus,

What driver did you use? Did you install some Windows PV drivers?


To UNSUBSCRIBE, email to
with a subject of "unsubscribe". Trouble? Contact
Replies Reply to this message
#2 Markus Jansen
February 01st, 2012 - 11:50 am ET | Report spam
On 27.01.2012 17:34, Thomas Goirand wrote:
Hi Markus,

What driver did you use? Did you install some Windows PV drivers?


I tried both, with and without PV driver, but it doesn't make any
difference. I used driver version, haven't tried the signed driver, yet.

To UNSUBSCRIBE, email to
with a subject of "unsubscribe". Trouble? Contact
email Follow the discussion Replies Reply to this message
Help Create a new topicReplies Make a reply
Search Make your own search