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

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:

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

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)

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

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:

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

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

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

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

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

** 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.

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

** 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

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

** 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

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

Public bug reported: 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.

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

** 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)

** 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: