Alright, I checked both of those from upstream:
http://people.canonical.com/~dannf/lp1725560/OVMF_CODE.fd.5dfba97c4
This one works correctly, no issues.
http://people.canonical.com/~dannf/lp1725560/OVMF_CODE.fd.7bbe0b3ef
This one does not work, meaning that Windows appears to be trying to boot (h
Yea, you are right, I seemed to have flipped them.
http://people.canonical.com/~dannf/lp1725560/OVMF_CODE.fd.7bbe0b3ef
This one works.
http://people.canonical.com/~dannf/lp1725560/OVMF_CODE.fd.5dfba97c4
This one does not work.
Sorry for the confusion.
--
You received this bug notification beca
Alright, I gave that last one a test:
http://people.canonical.com/~dannf/lp1725560/OVMF_CODE.fd.8693aa6a1
This version works, however there is a small difference. During booting
of OVMF_CODE.fd.8693aa6a1, it shows the white dot ring when booting
windows as described above, but also shows the "Tian
Public bug reported:
lsb_release -rd
Description:Ubuntu 17.10
Release:17.10
Kernel Version: 4.13.0-16.19
After a full system upgrade from Zesty to Artful, Windows 10 virtual
machine was no longer able to boot.
I am currently using an ACS patched kernel in order to support GPU
passthr
