-
Notifications
You must be signed in to change notification settings - Fork 386
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
cannot boot windows 7 with qxl drivers #244
Comments
Hi @muelli , In order to debug this efficiently can you please provide me with the following information:
I want to try and reproduce this, |
Hi @muelli , Thanks for all of this info, I just need one more thing. Can you please share the dump file with us and the driver package that you used. you can configure windows to save dumps this way: and then grab the dump file from where it usually resides in c:\Windows\memory.dmp Thanks! |
Hi @muelli , Can you also please indicate from what directory you are installing the driver? Thanks, |
The 100MB memory dump is here: https://send.firefox.com/download/6b8e1e1989/#MCuJ8hlDPNMF-t38i8zOqQ first click first serve... If you have a suggestion as to where to place that file, I'm happy to upload it there.
I don't understand. I selected "search my local computer" and then "D:" for the CD-ROM drive. I only ever had it install drivers off the CD-ROM drive. |
Looks like by misunderstanding you try to use qxldod driver for Win10/W8. |
hm. Again: I haven't manually selected any driver in particular. I've only ever given it "d:" as a path. I don't know how to test this now, because I can only boot when the QXL adapter is not present. Then, however, I don't know how to update the QXL driver, because I have nowhere to click "update driver". I could start over with a fresh machine, but maybe we need the current machine still. I'd consider it a bug if it's selecting the wrong driver, anyway. Maybe it's a Microsoft bug, though. |
You can uninstall the qxldod driver: boot the machine without qxl, then open device manager, select 'show hidden devices', find the QXL adapter and select 'Uninstall' and check 'Remove driver'. On next boot with qxl it will be installed with standard MSFT driver, then you can install proper driver for it. |
On Mon, Jan 29, 2018 at 2:35 PM, muelli ***@***.***> wrote:
Looks like by misunderstanding you try to use qxldod driver for Win10.
hm. Again: I haven't manually selected any driver in particular. I've only
ever given it "d:" as a path.
You should select the correct driver for the correct platform.
I don't know how to test this now, because I can only boot when the QXL
adapter is not present. Then, however, I don't know how to update the QXL
driver, because I have nowhere to click "update driver". I could start over
with a fresh machine, but maybe we need the current machine still.
Remove the driver using device manager or other tool.
I'd consider it a bug if it's selecting the wrong driver, anyway. Maybe
it's a Microsoft bug, though.
This is a way that Windows selects the INFs. It will get the first one it
will found.
… —
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#244 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABDkWDE2G_iSSDTDFvEXR7Qcfm5T5J9pks5tPbsQgaJpZM4Rvy2M>
.
|
I cannot find such a device.
Is it not possible to ship multiple drivers on the CD-ROM and have Windows select the most appropriate one? |
With 'show hidden devices' you should see two devices under 'display adapters' - one existing, one not existing, not existing is the one you need to uninstall together with the driver. |
ah, with "scan for hardware changes" it detected a standard VGA adapter. Sorry, my Windows-fu isn't very strong. I appreciate that manually selecting the driver makes this a non-issue. But it's hard for me to tell whether it installs the correct driver. |
Glad to hear it worked out for you.
In any case, while other drivers might function (for example if you install
Windows XP driver on Windows 7 for network adapter) - they might not
function in an optimal way.
Best regards,
Yan.
…On Mon, Jan 29, 2018 at 9:08 PM, muelli ***@***.***> wrote:
ah, with "scan for hardware changes" it detected a standard VGA adapter.
Sorry, my Windows-fu isn't very strong.
I uninstalled that new device and try to reboot, but it showed the
"Shutting down" screen forever. I forced the machine off and rebooted with
a QXL adapter instead of virtio and it booted successfully. It still had a
standard VGA compatible adapter and I selected to to update the driver from
"D:\QXL\W7".
I then updated the driver and it successfully rebooted.
I appreciate that manually selecting the driver makes this a non-issue.
But it's hard for me to tell whether it installs the correct driver.
My life would be a tiny bit happier if I didn't have to manually select
this particular driver while all the others seem to install fine when
Windows is pointed to the root of the CD-ROM.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#244 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABDkWKg6JqRUzqSRB8V-N13i7Q8LOlqXks5tPhdDgaJpZM4Rvy2M>
.
|
What's the rationale for closing? I still think that the experience could be better and maybe investigating the shipping of multiple drivers on the CD-ROM and have Windows select the most appropriate one is one option to make it better. Another might be to include the .exe from https://www.spice-space.org/download.html on the CD-ROM. |
I have opened a bug report in the following link: This is not the right place to track this issue, I will update once the bug is resolved. |
@muelli Hi I have tried to reproduce the issue but I could not, even when selecting the qxldod folder instead of the parent folder which has both qxl and qxldod. Windows doesnt select a driver from the qxldod. Can you please try and point to d:\qxldod and try and install the driver? Does this succeeds? |
This is 100% reproducible for me. I've visited https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/ and selected IE11 on Win7 for Vagrant. The download link is https://az792536.vo.msecnd.net/vms/VMBuild_20150916/Vagrant/IE11/IE11.Win7.Vagrant.zip and my sha256sum is
Then I booted and Windows wanted to reboot. After that, I opened the device manager and updated drivers off the root folder of the CD-ROM. First it installed this driver: but that didn't seem to have worked: After installing the other drivers off the root directory of the CD-ROM, I tried again to update the VGA graphics adapter driver. This time it selected this driver: Instead of rebooting as it requested I opened the driver details: After a reboot, the machine crashed: I hope that this allows you to reproduce this issue. |
Hi @muelli, |
Update: |
The commit that fixes the issue is now in upstream, so this issue should be fixed in the next release. I am closing the issue, please reopen in case you think the issue is not fully resolved. |
I have a vanilla windows 7 from modern.ie (apparently "version 20150916") and once I install the QXL driver from virtio-win-0.1.141.iso
(43aefa812c37342cfefc48ec0dd7f1e56a930fcd) the machine doesn't boot anymore. The situation doesn't change if I install all the available Windows updates.
STOP 0x0000007F (0x0000000D, 0x0, 0x0, 0x0)
According to https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x7f--unexpected-kernel-mode-trap it indicates a "Bug Check 0x7F: UNEXPECTED_KERNEL_MODE_TRAP" with "0x0000000D -- An exception not covered by some other exception; a protection fault that pertains to access violations for applications".
Once I change the video mode from QXL to, say, virtio, I can boot.
I thus suspect the QXL driver to be the cuprit.
Interestingly, using the "Windows guest tools - spice-guest-tools" from https://www.spice-space.org/download.html seems to work better. But it's unfortunate to download the stuff from there, because it requires a network connection. And Windows does not have virtio network drivers by default.
The text was updated successfully, but these errors were encountered: