Hi Han,
The easiest way to help contributing with the virtio-serial crashes
debug is to provide the system failure information when a BSOD occurs.
You should copy the PDB (debug symbols) file (vioser.pdb) in the
C:\Windows\system32\drivers directory (it where the vioser.sys driver
file exists too).
Enable the memory dump: Computer >> Properties >> Advanced system
settings >> Advanced tab >> Startup and Recovery Settings button and set
"Write debugging information" to (at least) "Small memory dump".
When a crash occurs, either open a bug or contact me directly and
provide a description on how to reproduce the crash (if possible) and
attach the MEMORY.DMP and PDB files.
I can also provide you with an updated and newer driver.
Thanks,
Gal.
On 16/01/2013 17:14, agilboa@xxxxxxxxxx wrote:
On 01/16/2013 03:41 PM, Han Pilmeyer wrote:
On 10/01/2013 15:53, Erik Lotspeich wrote:
Hi,
Just as a datapoint, I've seen a similar crash in guest-tools-0.2 on my
Windows 8 VM. I switched back to IDE from VIO disk and the crashing stopped.
Regards
Erik
On 01/10/2013 04:44 AM, Han Pilmeyer wrote:
It appears that I spoke too soon, i.e. the cut/paste problem is indeed
fixed and I am still happy about that. Unfortunately the guest-tools-0.3
drivers seem to have introduced a new problem that is even worse than
what I experienced before, they crash the Windows 7 guest images. I have
had multiple crashes so far and these happen when I am not specifically
doing anything in the guest (I try to avoid saying they are idle, as I
never quite know what Windows is doing behind the scenes). I estimate
that they crash after half an hour or so.
The offending driver appears to be vioser.sys as shown by the very
limited information (a screenshot of the BSOD) I managed to capture:
*** STOP: 0x0000008E (0xC0000005, 0x8B98C037, 0x8A40BACC, 0x00000000)
*** vioser.sys - Address 8B98C037 base at 8B988000, Datestamp
50b73b6d
Please let me know if there is anything I can do to help.
Erik,
That may be a viable, although undesirable, workaround for disk IO,
but in my case the BSOD's appear to be caused by vioser.sys, i.e. the
serial driver. I believe this driver is used for communication between
the host and guest and an important part to make cut/paste work. There
really is no alternative.
My motivation for writing about this here is not so much to get a
workaround (although that would be very nice), but rather to make a
minuscule contribution to improving the project. So again, if there is
anything I can do to help debug this, please do not hesitate to ask.
Cheers,
Han
Hi Han,
CC'ed Gal & Yan, vioser windows driver developers.
Thanks,
Arnon
_______________________________________________
Spice-devel mailing list
Spice-devel@xxxxxxxxxxxxxxxxxxxxx
http://lists.freedesktop.org/mailman/listinfo/spice-devel