Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Win10 1709: qxldod.sys crash #1

Open
magist3r opened this issue Mar 21, 2018 · 10 comments
Open

Win10 1709: qxldod.sys crash #1

magist3r opened this issue Mar 21, 2018 · 10 comments

Comments

@magist3r
Copy link

Hi!
Windows 10 guest crashes in qxldod.sys with blue screen.
Steps to reproduce:

  1. Save windows 10 guest state
  2. Reboot host system
  3. Restore windows 10 guest -> crash

QxlDod 0.18 from latest spice-quest-tools 0.141.
This is a relatively new issue, and I think it is caused by some of win10 updates.

Minidump generated by windows.

@ybendito
Copy link
Contributor

Thank you for the report. It looks like the device memory is not restored correctly on vm load, so seems like problem of qemu. We will take care on it.

@ybendito
Copy link
Contributor

Which spice server version you have on host side? If you run qemu from command line with '-monitor stdio' you can see it by "info spice", or can just 'dnf info spice-server' or similar, Thanks

@magist3r
Copy link
Author

@ybendito spice server v. 0.12.8. I can update it if needed.

@ybendito
Copy link
Contributor

ybendito commented Apr 1, 2018

Please do not update it if you do not have strong reason to do that. According to current investigation there is similar problem with 0.14 which should not happen with 0.12.8. I'm checking a possibility to issue custom build of the driver to investigate the problem.

@magist3r
Copy link
Author

magist3r commented Apr 2, 2018

Hmm, looks like I have installed 0.14 version before (with manual update). Now with 0.12.8 I don't have any problems, you are right.

@magist3r
Copy link
Author

After upgrading to Leap 15.0 I see this issue again because of lib version 0.14. Unfortunately I can't downgrade. Is there any workarounds for this issue?

@ybendito
Copy link
Contributor

ybendito commented Jun 3, 2018

There is no simple workaround unfortunately.
Related BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1540919
It contains possible fix for QEMU that should solve the problem:
https://bugzilla.redhat.com/attachment.cgi?id=1412225
Does build of qemu seem suitable workaround for you?
What is your host system?

@pedrocr
Copy link

pedrocr commented Jan 20, 2019

I have the same thing on Ubuntu 18.04 using a Windows 10 host with the latest versions. I'll see if a downgrade is possible. Meanwhile if you'd like to test anything let me know.

@ybendito
Copy link
Contributor

ybendito commented Jan 21, 2019 via email

@pedrocr
Copy link

pedrocr commented Jan 25, 2019

The qemu version currently shipped in Ubuntu is 2.11+dfsg-1ubuntu7.9 and spice server is 0.14.0-1ubuntu2.2 so it may very well be fixed in qemu 3.0 or spice-server 0.14.1. Right now it seems Ubuntu has only packaged qemu 2.12 and spice-server is still at 0.14.0 in all Ubuntu versions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants