From: Thomas Huth <1014681@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1014681] Re: BSOD with newer host kernels (x64) and W2k8S guest (x64)
Date: Fri, 07 Apr 2017 13:32:09 -0000 [thread overview]
Message-ID: <20170407133209.1943.4008.malone@chaenomeles.canonical.com> (raw)
In-Reply-To: 20120618143358.15172.76386.malonedeb@wampee.canonical.com
Which version of QEMU have you been using here? Can you still reproduce
this with the latest version of QEMU (version 2.9)?
** Changed in: qemu
Status: New => Incomplete
--
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:
Incomplete
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
next prev parent reply other threads:[~2017-04-07 13:45 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
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 [this message]
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=20170407133209.1943.4008.malone@chaenomeles.canonical.com \
--to=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.