All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arndt Kritzner <kritzner@logicway.de>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1014681] Re: BSOD with newer host kernels (x64) and W2k8S guest	(x64)
Date: Mon, 18 Jun 2012 14:51:05 -0000	[thread overview]
Message-ID: <20120618145105.21022.99366.malone@chaenomeles.canonical.com> (raw)
In-Reply-To: 20120618143358.15172.76386.malonedeb@wampee.canonical.com

** Attachment added: "table of testet component variants"
   https://bugs.launchpad.net/qemu/+bug/1014681/+attachment/3194732/+files/varianten.txt

** Description changed:

  Hallo, I attempted to move virtual machines from one host to another but
  got stuck with Windows-BSODs on the target host. The host-side console
  message is "virtio_ioport_write: unexpected address 0x13 value 0x1".
  Eventually there are overlaps to bug #990364, but I'm not sure.
  
  Host machine: 2x Opteron 4238 a 6 cores, 32GB RAM, Linux x86_64
  Guest machine(s): Windows 2008 Server R2 x64
  
  I tried different combinations of component versions, but only kernel
- 2.6.34 could run the guests (but has other difficulties):
- 
- host kernel	Qemu-KVM	paravirtualization	guest paravirt driver
- =============================================
- 2.6.34		1.0.1		virtio				0.1.15		ok
- 										0.1.22		ok
- 										0.1.prewhql	ok
- 			git 20120615	virtio				0.1.15		ok
- 										0.1.22		ok
- 										0.1.prewhql	ok
- =============================================
- 2.6.39		1.0.1		virtio				0.1.15		BSOD
- 			git 20120615	virtio				0.1.15		BSOD
- 3.0.3		1.0.1		virtio				0.1.15		BSOD
- 			git 20120615	virtio				0.1.15		BSOD
- 3.3.8		1.0.1		virtio				0.1.15		BSOD
- 			git 20120615	virtio				0.1.15		BSOD
- 						virtio-pci			0.1.15		BSOD
- 3.4.2		1.0.1		virtio				0.1.15		BSOD
- 										0.1.prewhql	BSOD
- 						virtio-pci			0.1.15		BSOD
- 			git 20120615	virtio				0.1.15		BSOD
- 										0.1.prewhql	BSOD
- 						virtio-pci			0.1.15		BSOD
- =============================================
+ 2.6.34 could run the guests (but has other difficulties). See testet
+ variants in comment.
  
  Run arguments are attached. Minidump follows immediately.

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

Title:
  BSOD with newer host kernels (x64) and W2k8S guest (x64)

Status in QEMU:
  New

Bug description:
  Hallo, I attempted to move virtual machines from one host to another
  but got stuck with Windows-BSODs on the target host. The host-side
  console message is "virtio_ioport_write: unexpected address 0x13 value
  0x1". Eventually there are overlaps to bug #990364, but I'm not sure.

  Host machine: 2x Opteron 4238 a 6 cores, 32GB RAM, Linux x86_64
  Guest machine(s): Windows 2008 Server R2 x64

  I tried different combinations of component versions, but only kernel
  2.6.34 could run the guests (but has other difficulties). See testet
  variants in comment.

  Run arguments are attached. Minidump follows immediately.

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

  parent reply	other threads:[~2012-06-18 15:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-18 14:33 [Qemu-devel] [Bug 1014681] [NEW] BSOD with newer host kernels (x64) and W2k8S guest (x64) Arndt Kritzner
2012-06-18 14:33 ` [Qemu-devel] [Bug 1014681] " Arndt Kritzner
2012-06-18 14:51 ` Arndt Kritzner [this message]
2012-06-18 14:53 ` Arndt Kritzner
2012-06-18 15:21 ` Arndt Kritzner
2012-06-18 17:38 ` vrozenfe
2012-06-19  6:31 ` Arndt Kritzner
2012-06-19 19:46 ` Arndt Kritzner
2012-06-20 20:36 ` vrozenfe
2012-06-21  7:10 ` Arndt Kritzner
2012-06-22 18:24 ` vrozenfe
2012-06-24  9:08 ` Arndt Kritzner
2017-04-07 13:32 ` Thomas Huth
2017-04-07 14:38 ` Arndt Kritzner
2017-04-07 19:23 ` Thomas Huth

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120618145105.21022.99366.malone@chaenomeles.canonical.com \
    --to=kritzner@logicway.de \
    --cc=1014681@bugs.launchpad.net \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.