Thanks everyone for the help; I pushed the patch in comment #40 as edk2
commit 76fd5a660d70.
** Changed in: edk2 (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
I'll test it in the next few days.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1725560
Title:
OVMF UEFI firmware causes Windows 10 w/ GPU passthrough to not boot
after upgrade
To manage notific
Posted:
[edk2] [PATCH] MdeModulePkg/AtaAtapiPassThru: disable only BM-DMA at
ExitBootServices()
http://mid.mail-archive.com/20171026154819.20865-1-lersek@redhat.com
https://lists.01.org/pipermail/edk2-devel/2017-October/016535.html
I CC'd a few people for feedback -- please send yo
Re: comment 32:
> BTW, I've also noticed that a large chunk of the delay, with i440fx, is
> not even spent loading data from the IDE CD-ROM. IDE emulation means host
> CPU load, but in this case, Windows just sits there with the empty
> purplish/bluish screen, and there is zero host CPU load -- no
(
Aleksei: no, mail-archive.com is a public mailing list archive, it does
not require subscription.
After the demise of GMANE, I started using references to mail-
archive.com because similarly to GMANE, it also provides lookup by
Message-Id -- regardless of the specific mailing list(s) that the
m
> OK, given that the edk2 commit in question is correct, I asked specifically
> for bug-compat ideas on > edk2-devel:
> http://mid.mail-archive.com/5bf829cb-4517-a579-ba7c-745c4ee89147@redhat.com
I'm getting 404 on this link, is this only for redhat subscribers or
something?
--
You received thi
On Wed, Oct 25, 2017 at 9:32 AM, Laszlo Ersek (Red Hat)
wrote:
> OK, given that the edk2 commit in question is correct, I asked
> specifically for bug-compat ideas on edk2-devel:
>
> http://mid.mail-archive.com/5bf829cb-4517-a579-ba7c-
> 745c4ee89...@redhat.com
>
> I'll also try to ask IDE and Win
OK, given that the edk2 commit in question is correct, I asked
specifically for bug-compat ideas on edk2-devel:
http://mid.mail-archive.com/5bf829cb-4517-a579-ba7c-
745c4ee89...@redhat.com
I'll also try to ask IDE and Windows experts for help with figuring out
what Windows is waiting for, when it
** Attachment added: "undamaged table from comment#32"
https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1725560/+attachment/4994611/+files/lp-1725560-c-32-table.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
Using the script from comment#30:
QEMU machine OVMF time from launch to
typefirst install screen
--- -
v2.8.1.1 pc 704b71d7e11f 117
In other news, LaunchPad is an abomination. Way to screw up my nicely
laid out table in comment#32.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1725560
Title:
OVMF UEFI firmware causes Windows 10
Hold on, the machine type could have an impact. I switched my script in
comment#30 from q35 to pc, and the IDE CD-ROM boot slowed to a crawl.
I've always assumed that this difference was simply due to q35 having
AHCI/SATA and pc having only plain IDE, but maybe there is a perf
regression specific t
Thanks everyone for the investigation thus far.
I cannot reproduce the issue (using an IDE CD-ROM):
* QEMU: tested both the v2.10.1 release, and current upstream master
(3d7196d43bfe, "Merge remote-tracking branch
'remotes/kraxel/tags/usb-20171023-pull-request' into staging", 2017-10-24)
* O
Would you like me to continue with the bisects or do anything else?
I've attached my XML configuration in case anyone is still interested.
** Attachment added: "windows.xml"
https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1725560/+attachment/4993329/+files/windows.xml
--
You received t
** Changed in: edk2 (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1725560
Title:
OVMF UEFI firmware causes Windows 10 w/ GPU passthrough to not boot
after up
I'm also hitting freakishly long IDE boots with latest edk2/ovmf, QEMU 2.10.1
and win7 x64 guest.
A workaround for me was to to boot the VM with win7 iso, virtio iso and drive
image all on ahci bus; then assign C: to windows partition and inject drivers
into it from virtio cd with "dism /image:c
fwiw, I'm able to reproduce the slow-to-boot-ISO issue by using IDE.
With that as a symptom, I completed the bisect and hit:
6fb8ddd36bde MdeModulePkg/AtaAtapiPassThru: disable the device at
ExitBootServices()
Prior to this commit, it took 34s for me to go from EFI shell to first install
screen.
Next one in the bisect:
http://people.canonical.com/~dannf/lp1725560/OVMF_CODE.fd.3281ebb4a
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1725560
Title:
OVMF UEFI firmware causes Windows 10 w/ GPU
I won't be able to work on it until quite a bit later today, but I can
confirm that I am using IDE as the virtual hard drive. I will post the
xml later tonight. Thanks for the help.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
On Tue, Oct 24, 2017 at 5:37 AM, Laszlo Ersek (Red Hat)
wrote:
> In comment #1 Dann stated he could *not* reproduce the issue. Was that
> perhaps because Krupp used IDE but Dann used virtio?
I am in fact using virtio.
--
You received this bug notification because you are a member of Ubuntu
Bugs
In comment 17, Krupp confirmed that even current-ish upstream
(d8e36289cef7, "EmbeddedPkg: add driver to set graphical/serial console
preference", 2017-10-20) was broken for them; so I was definitely off
with my LP#1715700 parallel. Sorry about that.
The bisection thus far has narrowed down the in
Re Laszlo's comment #8 - it feels the opposite way around to lp 1715700
- in that I don't think downgrading OVMF helped; so perhaps something
else is going on?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
This one works correctly:
http://people.canonical.com/~dannf/lp1725560/OVMF_CODE.fd.c50596a70
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1725560
Title:
OVMF UEFI firmware causes Windows 10 w/ GPU
OK, next one:
http://people.canonical.com/~dannf/lp1725560/OVMF_CODE.fd.c50596a70
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1725560
Title:
OVMF UEFI firmware causes Windows 10 w/ GPU passthrou
This one works correctly:
http://people.canonical.com/~dannf/lp1725560/OVMF_CODE.fd.9a04dcffb
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1725560
Title:
OVMF UEFI firmware causes Windows 10 w/ GPU
No worries, you're testing has been very helpful. Here's the next build -
estimated 4 more left to test:
http://people.canonical.com/~dannf/lp1725560/OVMF_CODE.fd.9a04dcffb
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
Okay, I checked both of them twice and neither are working:
Bisect:
http://people.canonical.com/~dannf/lp1725560/OVMF_CODE.fd.5659ec3fa
Upstream:
http://people.canonical.com/~dannf/lp1725560/OVMF_CODE.fd.d8e36289c
Sorry I can't help more, I'm looking into how to bisect in git and maybe
in the futu
Thank you. Here's the next one:
http://people.canonical.com/~dannf/lp1725560/OVMF_CODE.fd.5659ec3fa
Also, probably worth checking to see if latest upstream is still affected:
http://people.canonical.com/~dannf/lp1725560/OVMF_CODE.fd.d8e36289c
--
You received this bug notification because you
This one works correctly:
http://people.canonical.com/~dannf/lp1725560/OVMF_CODE.fd.ae66c6f12
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1725560
Title:
OVMF UEFI firmware causes Windows 10 w/ GPU
On Mon, Oct 23, 2017 at 3:13 PM, Krupp <1725...@bugs.launchpad.net> wrote:
> This one works correctly:
> http://people.canonical.com/~dannf/lp1725560/OVMF_CODE.fd.821f24b12
Thanks. Next one:
http://people.canonical.com/~dannf/lp1725560/OVMF_CODE.fd.ae66c6f12
-dann
--
You received this bug
This one works correctly:
http://people.canonical.com/~dannf/lp1725560/OVMF_CODE.fd.821f24b12
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1725560
Title:
OVMF UEFI firmware causes Windows 10 w/ GPU
On Mon, Oct 23, 2017 at 2:50 PM, Krupp <1725...@bugs.launchpad.net> wrote:
> Sure thing!
>
> http://people.canonical.com/~dannf/lp1725560/OVMF_CODE.fd.5dfba97c4+lp1715700
> The patched version still does not work.
:(
> http://people.canonical.com/~dannf/lp1725560/OVMF_CODE.fd.e5251fecb
> The bise
Sure thing!
http://people.canonical.com/~dannf/lp1725560/OVMF_CODE.fd.5dfba97c4+lp1715700
The patched version still does not work.
http://people.canonical.com/~dannf/lp1725560/OVMF_CODE.fd.e5251fecb
The bisect works.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Thanks Laszlo! artful has the patches you mention as related to LP:
#1714331, but not the patches you mention as related to LP: #1715700.
@Krupp: Can you test this build to see if the patches for LP: #1715700 fix it
for you?
http://people.canonical.com/~dannf/lp1725560/OVMF_CODE.fd.5dfba97c4+lp
Okay, thanks Laszlo Ersek, good to know that behavior is expected then.
I tried out:
http://people.canonical.com/~dannf/lp1725560/OVMF_CODE.fd.401d1343c
This one works correctly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
You are probably hitting one of LP#1715700 and LP#1714331. (Upgrading
from "Zesty" (17.04) to "Artful" (17.10) seems to imply a QEMU upgrade
from 2.8 to 2.10.)
LP#1715700 was fixed in edk2 commit range b68c793144e8..947f3737abf6:
ba1d245f1d3d OvmfPkg/CsmSupportLib: move PAM register addresses to
Ok, thanks. Here's the next one (note that the estimate for this bisect is 9
tests):
http://people.canonical.com/~dannf/lp1725560/OVMF_CODE.fd.401d1343c
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
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
Ah, great! Then we have a path forward. I'll prepare you a series of builds of
bisect source to try and identify the change that broke it. Here's the first
one:
http://people.canonical.com/~dannf/lp1725560/OVMF_CODE.fd.8693aa6a1
--
You received this bug notification because you are a member o
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
Thanks for testing! The results are confounding though. It appears that,
while the zesty package worked for you, the upstream base (7bbe0b3ef)
for the zesty version did not. And, while the artful version fails for
you, the upstream base (5dfba97c) for the artful version *did* work. Can
you double-c
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
Thanks for the report! I attempted to reproduce w/ a straight Win10
install, but I didn't have any problems. I suspect (as you imply) this
maybe related to the GPU passthrough. Unfortunately, I don't have a way
to reproduce that myself so, if you're willing, I could use some
assistance running some
** Summary changed:
- OVMF UEFI firmware causes Windows 10 to not boot after upgrade
+ OVMF UEFI firmware causes Windows 10 w/ GPU passthrough to not boot after
upgrade
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
44 matches
Mail list logo
