[Qemu-devel] [Bug 1308341] Re: Multiple CPUs causes blue screen on Windows guest (14.04 regression)

[Gordon Kaltofen]

Hallo to all, this is my first post here.

I have exactly the same problem occurred after Distribution Update
Ubuntu Server x64 from 12.04.4 to 14.04.

1. I have Windows 7 32/64-Bit and Windows 2008 Server 64-Bit VMs, all
show the same error with two dedicated cores (no pinning). In
combination with the other statements I would say it is a general
Windows problem - not specific.

2. I have an AMD Opteron 6272 (fam: 15, model: 01, stepping: 02, 16
cores) system. Therefore, this problem does not seem to be Intel/AMD
architecture-specific.

3. I configured a couple of VMs ONE core and let it run over the
weekend. They didn't crashing, but they reacted only very slowly an
choppy. It seems that there is a fundamental error, which is responsible
for the multi-core errors. After restarting the VM, the error is
initially gone, even though the VM is still slow due to only one core.

4. I have the latest virtio drivers are installed in the Windows guest
systems and use the devices Red Hat VirtIO SCSI and Ethernet (vers.
61.65.104.7400) drivers. Are these drivers installed in your VMs or do
you use the IDE/SATA and RTL/Intel-NIC standard driver?

5. The VM images (qcow2) are located on a mdadm Raid1 volume of two
SSDs. Since Linux kernel 3.7 ATA TRIM is possible with Linux software
RAID, so I use the mount option 'discard'. I do not want to completely
exclude the possibility that the error has to do with it.

Is there now an indication of the cause of the failure and possibly even
a workaround?

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1308341

Title:
  Multiple CPUs causes blue screen on Windows guest (14.04 regression)

Status in QEMU:
  New
Status in “qemu” package in Ubuntu:
  Confirmed
Status in “virt-manager” package in Ubuntu:
  Confirmed

Bug description:
  Configuring a Windows 7 guest using more than one CPU cases the guest to 
fail. This happens after a few hours after guest boot. This is the error on the 
blue screen:
  "A clock interrupt was not received on a secondary processor within the 
allocated time interval"

  After resetting, the guest will never boot and a new bluescreen with
  the error "STOP: 0x0000005c" appears. Shutting down the guest
  completely and restarting it will allow it to boot and run for a few
  hours again.

  The guest was created using virt-manager. The error happens with or
  without virtio devices and with both 32-bit and 64-bit Windows 7
  guests.

  I am using Ubuntu 14.04 release candidate.

  qemu-kvm version 2.0.0~rc1+dfsg-0ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1308341/+subscriptions