All of lore.kernel.org
 help / color / mirror / Atom feed
* Windows 8.1 64 bit domU crash, from log seems for virtio driver from virtio-win-0.1-81
@ 2014-09-26 12:09 Fabio Fantoni
  2014-09-29  8:27 ` Christophe Fergeau
  0 siblings, 1 reply; 2+ messages in thread
From: Fabio Fantoni @ 2014-09-26 12:09 UTC (permalink / raw)
  To: spice-devel, xen-devel

I tried new xen pv drivers and virtio/spice drivers on Windows 8.1 64 
bit domUs.
Virtio serial driver from virtio-win-0.1-81, vdagent service from latest 
spice guest tools (0.74) and qxl driver from qxlwddm-0.6.
Mouse was not visible, so I tried to remove vdagent from qemu config and 
at next domU's start crash on windows loading with this error in xl dmesg:
> (d6) XEN|BUGCHECK: ====>
> (d6) XEN|BUGCHECK: DRIVER_IRQL_NOT_LESS_OR_EQUAL: 0000000000000008 
> 0000000000000002
> (d6) 0000000000000000 FFFFF800DF7EE41F
> (d6) XEN|BUGCHECK: MEMORY REFERENCED: 0000000000000008
> (d6) XEN|BUGCHECK:              IRQL: 02
> (d6) XEN|BUGCHECK:            ACCESS: 0000000000000000
> (d6) XEN|BUGCHECK:           ADDRESS: vioser.sys + 000000000000341F
> (d6) XEN|BUGCHECK: CONTEXT (FFFFD001218E37F0):
> (d6) XEN|BUGCHECK: - GS = 002B
> (d6) XEN|BUGCHECK: - FS = 0053
> (d6) XEN|BUGCHECK: - ES = 002B
> (d6) XEN|BUGCHECK: - DS = 002B
> (d6) XEN|BUGCHECK: - SS = 0018
> (d6) XEN|BUGCHECK: - CS = 0010
> (d6) XEN|BUGCHECK: - EFLAGS = 00000082
> (d6) XEN|BUGCHECK: - RDI = 0000000000000002
> (d6) XEN|BUGCHECK: - RSI = 0000000000000000
> (d6) XEN|BUGCHECK: - RBX = 00000000DF7EE41F
> (d6) XEN|BUGCHECK: - RDX = 0000000000000000
> (d6) XEN|BUGCHECK: - RCX = 00000000218E37F0
> (d6) XEN|BUGCHECK: - RAX = 000000000000000F
> (d6) XEN|BUGCHECK: - RBP = 0000000000000000
> (d6) XEN|BUGCHECK: - RIP = 00000000DF3153BE
> (d6) XEN|BUGCHECK: - RSP = 00000000218E37B0
> (d6) XEN|BUGCHECK: - R8 = 0000000000000000
> (d6) XEN|BUGCHECK: - R9 = 0000000000000000
> (d6) XEN|BUGCHECK: - R10 = 0000000000000000
> (d6) XEN|BUGCHECK: - R11 = 0000000000000000
> (d6) XEN|BUGCHECK: - R12 = 0000000000000000
> (d6) XEN|BUGCHECK: - R13 = 0000000000000001
> (d6) XEN|BUGCHECK: - R14 = 00000000DF317860
> (d6) XEN|BUGCHECK: - R15 = 0000000080000000
> (d6) XEN|BUGCHECK: STACK:
> (d6) XEN|BUGCHECK: 00000000218E3D00: (0000000000000003 
> 00000000DF3180D0 00000000DF31
> (d6) 7860 00000000DF31D258) xen.sys + 0000000000004A25
> (d6) XEN|BUGCHECK: 00000000218E3D50: (00000000DF3200D0 
> 00000000218E3E90 00000000DF32
> (d6) 0110 0000000092555B20) ntoskrnl.exe + 00000000001DDBB6
> (d6) XEN|BUGCHECK: 00000000218E3D90: (00000000DF3200D0 
> 0000000092555B20 000000000000
> (d6) 000A 000000000000000A) ntoskrnl.exe + 00000000001DCEAB
> (d6) XEN|BUGCHECK: 00000000218E44A0: (0000000000000000 
> 00000000922B3B23 000000000000
> (d6) 0000 0000000000000001) ntoskrnl.exe + 0000000000153DA4
> (d6) XEN|BUGCHECK: 00000000218E44E0: (000000000000000A 
> 0000000000000008 000000000000
> (d6) 0002 0000000000000000) ntoskrnl.exe + 000000000015F7E9
> (d6) XEN|BUGCHECK: 00000000218E4620: (0000000000000000 
> 0000000000000000 00000000218E
> (d6) 4700 00000000218E4620) ntoskrnl.exe + 000000000015E03A
> (d6) XEN|BUGCHECK: 00000000218E47B0: (00000000218E47B0 
> 00000000218E47B0 0000000060C7
> (d6) 2010 0000000060422A70) vioser.sys + 000000000000341F
> (d6) XEN|BUGCHECK: 00000000218E47E0: (0000000060423840 
> 0000000060423840 00000000218E
> (d6) 48B9 0000000060422A70) vioser.sys + 0000000000003AC2
> (d6) XEN|BUGCHECK: 00000000218E4810: (0000000060250560 
> 00000000DF107D9C 0000000060C7
> (d6) 2010 0000000000000000) wdf01000.sys + 000000000000A9D8
> (d6) XEN|BUGCHECK: 00000000218E4920: (0000000000000000 
> 0000000092318800 000000000000
> (d6) 0000 000000005EE07170) wdf01000.sys + 0000000000006A18
> (d6) XEN|BUGCHECK: 00000000218E4A00: (0000000000000000 
> 0000000000000000 0000000060C7
> (d6) 2010 0000000092675049) ntoskrnl.exe + 00000000003D584C
> (d6) XEN|BUGCHECK: 00000000218E4A80: (0000000000000000 
> 0000000060ED4710 000000005EE1
> (d6) 4F20 0000000060ED46E0) ntoskrnl.exe + 00000000003F0EC4
> (d6) XEN|BUGCHECK: 00000000218E4AE0: (0000000000000000 
> 00000000218E4BD9 0000000060ED
> (d6) 4710 000000005EE14F20) ntoskrnl.exe + 000000000004FA2F
> (d6) XEN|BUGCHECK: 00000000218E4B20: (0000000060ED46E0 
> 00000000FFFF800F 000000000000
> (d6) 7FF1 0000000000007FF1) ntoskrnl.exe + 00000000003D4BB4
> (d6) XEN|BUGCHECK: 00000000218E4C40: (0000000000000008 
> 000000006FB01520 000000000023
> (d6) FB10 000000000023FB30) ntoskrnl.exe + 000000000015F4B3
> (d6) XEN|BUGCHECK: 000000000023F9E8: (000000006F8A150B 
> 0000000000000000 000000000074
> (d6) 3730 0000000000743D30) 00007FFF7230176A
> (d6) XEN|BUGCHECK: 000000000023F9F0: (0000000000000000 
> 0000000000743730 000000000074
> (d6) 3D30 000000006FD71B70) 00007FFF6F8A150B
> (d6) XEN|BUGCHECK: 000000000023F9F8: (0000000000743730 
> 0000000000743D30 000000006FD7
> (d6) 1B70 00000000009C5D30) 0000000000000000
> (d6) XEN|BUGCHECK: <====

On windows 7 64 bit domU instead with spice guest tools 0.74 all works 
correctly (except qxl problem after restore already reported).
If you need more informations or tests tell me and I'll post them.

Thanks for any reply and sorry for my bad english.

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Windows 8.1 64 bit domU crash, from log seems for virtio driver from virtio-win-0.1-81
  2014-09-26 12:09 Windows 8.1 64 bit domU crash, from log seems for virtio driver from virtio-win-0.1-81 Fabio Fantoni
@ 2014-09-29  8:27 ` Christophe Fergeau
  0 siblings, 0 replies; 2+ messages in thread
From: Christophe Fergeau @ 2014-09-29  8:27 UTC (permalink / raw)
  To: Fabio Fantoni; +Cc: spice-devel, xen-devel


[-- Attachment #1.1: Type: text/plain, Size: 962 bytes --]

Hey,

On Fri, Sep 26, 2014 at 02:09:56PM +0200, Fabio Fantoni wrote:
> I tried new xen pv drivers and virtio/spice drivers on Windows 8.1 64 bit
> domUs.
> Virtio serial driver from virtio-win-0.1-81, vdagent service from latest
> spice guest tools (0.74) and qxl driver from qxlwddm-0.6.
> Mouse was not visible, so I tried to remove vdagent from qemu config and at
> next domU's start crash on windows loading with this error in xl dmesg:
> >(d6) XEN|BUGCHECK: ====>
> >(d6) XEN|BUGCHECK: DRIVER_IRQL_NOT_LESS_OR_EQUAL: 0000000000000008
> >0000000000000002
> >(d6) 0000000000000000 FFFFF800DF7EE41F
> >(d6) XEN|BUGCHECK: MEMORY REFERENCED: 0000000000000008
> >(d6) XEN|BUGCHECK:              IRQL: 02
> >(d6) XEN|BUGCHECK:            ACCESS: 0000000000000000
> >(d6) XEN|BUGCHECK:           ADDRESS: vioser.sys + 000000000000341F

This mailing list is not the right place to report a vioser.sys bug, but
I'm not sure either where this should go :(

Christophe

[-- Attachment #1.2: Type: application/pgp-signature, Size: 819 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2014-09-29  8:27 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-09-26 12:09 Windows 8.1 64 bit domU crash, from log seems for virtio driver from virtio-win-0.1-81 Fabio Fantoni
2014-09-29  8:27 ` Christophe Fergeau

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.