[Qemu-devel] [Bug 1014681] Re: BSOD with newer host kernels (x64) and W2k8S guest (x64)

2017-04-07 Thread Thomas Huth
** Changed in: qemu Status: Incomplete => Won't Fix -- 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: W

[Qemu-devel] [Bug 1014681] Re: BSOD with newer host kernels (x64) and W2k8S guest (x64)

2017-04-07 Thread Arndt Kritzner
Sorry, but I have moved to ESXI more than 4 years ago. -- 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: Incom

[Qemu-devel] [Bug 1014681] Re: BSOD with newer host kernels (x64) and W2k8S guest (x64)

2017-04-07 Thread Thomas Huth
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://

[Qemu-devel] [Bug 1014681] Re: BSOD with newer host kernels (x64) and W2k8S guest (x64)

2012-06-28 Thread Arndt Kritzner
Is there any hope to get this fixed in the near future or probably not? -- 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

[Qemu-devel] [Bug 1014681] Re: BSOD with newer host kernels (x64) and W2k8S guest (x64)

2012-06-24 Thread Arndt Kritzner
Booting in safe mode works, but only without networking. -- 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

[Qemu-devel] [Bug 1014681] Re: BSOD with newer host kernels (x64) and W2k8S guest (x64)

2012-06-22 Thread vrozenfe
Could you try booting in safe mode with and without networking? -- 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

[Qemu-devel] [Bug 1014681] Re: BSOD with newer host kernels (x64) and W2k8S guest (x64)

2012-06-21 Thread Arndt Kritzner
Most (by far) crashes end with the same bug check code: Loading Dump File [\\Lw\arndt\Kanzlei\Mini061612-01.dmp] BugCheck 3B, {8003, f800016a6700, fa6002c89e60, 0} Probably caused by : afd.sys ( afd!AfdIssueDeviceControl+18f ) - Loading Dump File [\\Lw\arndt\Kanzlei\Mini061612-

[Qemu-devel] [Bug 1014681] Re: BSOD with newer host kernels (x64) and W2k8S guest (x64)

2012-06-20 Thread vrozenfe
Does it always crash with the same bug check code? -- 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

[Qemu-devel] [Bug 1014681] Re: BSOD with newer host kernels (x64) and W2k8S guest (x64)

2012-06-19 Thread Arndt Kritzner
** Attachment added: "Minidump of BSOD with e1000 + ide" https://bugs.launchpad.net/qemu/+bug/1014681/+attachment/3196480/+files/Mini061912-01.dmp -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/101

[Qemu-devel] [Bug 1014681] Re: BSOD with newer host kernels (x64) and W2k8S guest (x64)

2012-06-19 Thread vrozenfe
"virtio_ioport_write: unexpected address 0x13 value 0x1" indicates that you got a BSOD. Could you try switching from virtio to e1000, and ide and check if you still getting DRIVER_CORRUPTED_EXPOOL (c5) bug check error? Vadim. -- You received this bug notification because you are a member of

[Qemu-devel] [Bug 1014681] Re: BSOD with newer host kernels (x64) and W2k8S guest (x64)

2012-06-19 Thread Arndt Kritzner
With e1000 and ide I also get BSOD (tried this already), but I don't have a matching dump by hand at the moment. I will "produce" and provide a dump till tomorrow morning (germany). Arndt -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEM

[Qemu-devel] [Bug 1014681] Re: BSOD with newer host kernels (x64) and W2k8S guest (x64)

2012-06-18 Thread Arndt Kritzner
** Attachment added: "qemu run arguments" https://bugs.launchpad.net/bugs/1014681/+attachment/3194721/+files/ads.w2k8s.qcow2.start -- 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: B

[Qemu-devel] [Bug 1014681] Re: BSOD with newer host kernels (x64) and W2k8S guest (x64)

2012-06-18 Thread Arndt Kritzner
** 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.

[Qemu-devel] [Bug 1014681] Re: BSOD with newer host kernels (x64) and W2k8S guest (x64)

2012-06-18 Thread Arndt Kritzner
** Attachment added: "example windows minidump" https://bugs.launchpad.net/qemu/+bug/1014681/+attachment/3194733/+files/Mini061612-12.dmp -- 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 Tit

[Qemu-devel] [Bug 1014681] Re: BSOD with newer host kernels (x64) and W2k8S guest (x64)

2012-06-18 Thread Arndt Kritzner
** Tags added: qemu-kvm -- 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 att