This bug was fixed in the package edk2 - 0~20170911.5dfba97c-1ubuntu0.1
---
edk2 (0~20170911.5dfba97c-1ubuntu0.1) artful; urgency=medium
* d/p/MdeModulePkg-AtaAtapiPassThru-disable-only-BM-DMA-at.patch:
Fix Win10 guests booting from IDE drives. LP: #1725560.
-- dann frazier
@Max: most important is to isolate the component whose upgrade causes
the regression for you. OVMF, QEMU, libvirt (possibly, but unlikely),
and host kernel (=KVM). Once isolated, the component should be
bisectable. See also LP#1723731 -- the issue you are seeing might be a
duplicate. (I haven't
@Max: Can you file a new bug? The fix here was in the IDE subsystem and,
since you're not using IDE, you're bug is unlikely related.
Note that if you want to try the fix for this issue, be aware that there
are *two* "9/11" debs:
Yeah I've installed the 9/11 and 10/27 debs as well as several of the
bisected OVMF_CODE.fd files you marked as working, no luck. I am
currently trying a bunch of different fresh windows VM installs to see
if I can narrow down a specific set of options that causes the problem.
Or it's entirely
Did you try installing this as described above?:
https://launchpad.net/ubuntu/+archive/primary/+files/ovmf_0~20170911
.5dfba97c-1ubuntu0.1_all.deb
The tianocore logo change doesn't really matter as they talked about
above, it is an expected change.
Sounds like what I have been experiencing.
--
I think I'm also getting hit with this bug, or else something very
similar. I migrated this VM from a 17.04 install to a fresh 17.10
install. Since then I haven't been able to boot Windows successfully. It
seems to be booting fine (I see the spinning white circle) but then I
just get a black
Oh okay, didn't know the -1ubuntu0.1 made a difference, sorry. I tested
0~20170911.5dfba97c-1ubuntu0.1 and can confirm it is working correctly.
Again, sorry for the confusion and thanks for the help.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
To be clear, 0~20170911.5dfba97c-1ubuntu0.1 is the artful-proposed version.
0~20170911.5dfba97c-1 is the artful release version:
See: http://launchpad.net/ubuntu/+source/edk2
The one with "the ubuntu0.1" suffix is the one with the fix.
Can you (re-?)confirm that you tested with
I tested it in the comment above. I guess what I was trying to show is
that I expected version 0~20170911.5dfba97c-1 to be in the proposed
repository, but by the time I got to test it, it came from the main
repository. I verified that version 0~20170911.5dfba97c-1 does not work
and have gone back
Ah, OK. I've moved this back to verification-needed.
Note that the version in artful-proposed is: 0~20170911.5dfba97c-
1ubuntu0.1. It doesn't appear that you have tested that one yet.
** Tags removed: verification-done verification-done-artful
** Tags added: verification-needed
I just wanted to clarify that the Artful proposed and main package
version 0~20170911.5dfba97c-1 are not working. I wrote the above
response in a strange order and I apologize.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags removed: verification-needed verification-needed-artful
** Tags added: verification-done verification-done-artful
--
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
Alright, here is what I did. I used the default Artful sources. I
started with the updated upstream ovmf version 0~20171027.76fd5a66-1.
apt-get update
apt-get remove ovmf
apt-get install ovmf
dpkg -l ovmf | cat
ovmf 0~20170911.5dfba97c-1 all UEFI firmware for 64-bit x86
Hello Krupp, or anyone else affected,
Accepted edk2 into artful-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/edk2/0~20170911
.5dfba97c-1ubuntu0.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
On Mon, Oct 30, 2017 at 8:36 PM, Krupp <1725...@bugs.launchpad.net> wrote:
> I installed the new upstream release 0~20171027.76fd5a66-1 and
> everything is working great. Thanks for all the help and finding a
> solution so quickly!
For my part, you're welcome. Note that I have also uploaded a
I installed the new upstream release 0~20171027.76fd5a66-1 and
everything is working great. Thanks for all the help and finding a
solution so quickly!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: edk2 (Ubuntu Artful)
Status: New => In Progress
** Description changed:
- lsb_release -rd
- Description:Ubuntu 17.10
- Release:17.10
- Kernel Version: 4.13.0-16.19
+ [Impact]
+ Windows 10 guests using IDE storage fail to boot (or boot *really* slowly)
- After
This bug was fixed in the package edk2 - 0~20171027.76fd5a66-1
---
edk2 (0~20171027.76fd5a66-1) unstable; urgency=medium
* New upstream release.
- Fix Win10 guests booting from IDE drives. LP: #1725560.
-- dann frazier Fri, 27 Oct 2017 16:10:29 -0600
**
** Also affects: edk2 (Ubuntu Artful)
Importance: Undecided
Status: New
--
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 to not boot after
** Summary changed:
- OVMF UEFI firmware causes Windows 10 w/ GPU passthrough to not boot after
upgrade
+ OVMF UEFI firmware causes Windows 10 to not boot after upgrade
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
20 matches
Mail list logo