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

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-devel] [Bug 1014681] Re: BSOD with newer host kernels (x64) and W2k8S guest (x64)

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)

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 990364] Re: virtio_ioport_write: unexpected address 0x13 value 0x1

It doesn't look like as a vritio-win driver problem. you get the following message virtio_ioport_write: unexpected address 0x13 value 0x1 because netkvm driver triggers BSOD event, which happened in different stack, and then kills the hosting QEMU prccess by writing to ISR register. In your

[Qemu-devel] [Bug 990364] Re: virtio_ioport_write: unexpected address 0x13 value 0x1

Hard to say at the moment. In both cases the crash stack looks absolutely the same: nt!KiDeliverApc+0x66 hal!HalpApcInterrupt+0xc5 hal!HalRequestSoftwareInterrupt+0x3b

[Qemu-devel] [Bug 990364] Re: virtio_ioport_write: unexpected address 0x13 value 0x1

http://support.microsoft.com/kb/316450 -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/990364 Title: virtio_ioport_write: unexpected address 0x13 value 0x1 Status in QEMU: New Bug description:

[Qemu-devel] [Bug 990364] Re: virtio_ioport_write: unexpected address 0x13 value 0x1

can you upload the corresponding dump file? -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/990364 Title: virtio_ioport_write: unexpected address 0x13 value 0x1 Status in QEMU: New Bug

Re: [Qemu-devel] [Bug 990364] Re: virtio_ioport_write: unexpected address 0x13 value 0x1

On Thursday, May 03, 2012 10:17:15 PM Vitalis wrote: And what? Where can I get new drivers for WinXP? http://people.redhat.com/vrozenfe/build-27/virtio-win-prewhql-0.1.zip -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https

[Qemu-devel] [Bug 818673] Re: virtio: trying to map MMIO memory

I have no idea regarding Ubuntu, but you can find the new drivers at Fedora project site http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/bin/virtio-win-0.1-22.iso -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU.

[Qemu-devel] [Bug 818673] Re: virtio: trying to map MMIO memory

Hi Alon, Unfortunately, qxl and virtio-serial hang is a different problem. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/818673 Title: virtio: trying to map MMIO memory Status in QEMU: New

[Qemu-devel] [Bug 818673] Re: virtio: trying to map MMIO memory

It was a long journey. But now it seem like we've managed to fix this problem. https://bugzilla.redhat.com/show_bug.cgi?id=771390#c45 I put new drivers here: http://people.redhat.com/vrozenfe/vioscsi.vfd Best regards, Vadim. -- You received this bug notification because you are a member

[Qemu-devel] [Bug 818673] Re: virtio: trying to map MMIO memory

Thank you, Rick. I will start checking virtio-serial driver tomorrow. Best, Vadim. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/818673 Title: virtio: trying to map MMIO memory Status in QEMU:

[Qemu-devel] [Bug 818673] Re: virtio: trying to map MMIO memory

Thank you, Rick. Could you help me to narrow this problem down? As I see, you have three virtio drivers installed on your system - block, net, and virtio serial. Technically, anyone of them can create trying to map MMIO memory problem. The best way to find a buggy driver ( or drivers) will be

[Qemu-devel] [Bug 818673] Re: virtio: trying to map MMIO memory

of sync, but I'm going to update it soon) I put our recent (WHQL candidates) drivers here: http://people.redhat.com/vrozenfe/virtio-win-prewhql-0.1.zip Please give them a try and share your experience. Best, Vadim. ** Bug watch added: Red Hat Bugzilla #727034 https://bugzilla.redhat.com

[Qemu-devel] [Bug 697510] Re: Machine shut off after tons of lsi_scsi: error: MSG IN data too long

Red Hat driver means driver from rhel virtio-win.prm? -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/697510 Title: Machine shut off after tons of lsi_scsi: error: MSG IN data too long Status in

[Qemu-devel] [Bug 697510] Re: Machine shut off after tons of lsi_scsi: error: MSG IN data too long

Can you try viostor with sptd (scsi pass through direct) disabled? -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/697510 Title: Machine shut off after tons of lsi_scsi: error: MSG IN data too long