I assume this has been completely fixed in edk2, so I'm closing this
QEMU bug now.
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/17157
See also LP#1725560.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1715700
Title:
Windows 7 guest won't boot on qemu 2.10 (works on 2.9)
Status in QEMU:
Fix Committed
Bug description:
Qemu ve
edk2 commit range: b68c793144e8..947f3737abf6.
** Changed in: qemu
Status: New => Fix Committed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1715700
Title:
Windows 7 guest won't boot on qe
Posted:
[edk2] [PATCH 0/3] OvmfPkg/QemuVideoDxe/VbeShim: handle PAM1 register on
Q35 correctly
https://lists.01.org/pipermail/edk2-devel/2017-September/014898.html
I CC'd Aleksei on the series, but testing is welcome from anyone. (The
cover letter at the link contains a git fetch URL.)
--
You
On 09/19/17 14:38, Gerd Hoffmann wrote:
>> (2) Build the SeaBIOS CSM (CONFIG_CSM=y), and embed it into OVMF,
>> like described above. Then, boot Windows 7 in *UEFI Mode*.
>
>> Option #1 and option #2 no longer work because the CSM infrastructure
>> in edk2 needs to be able to write 0xc.
>
> W
Ahh, wait, now I remember something -- the PAM registers are at a
different location on Q35!!!
If that's what's wrong, then it is indeed an OVMF bug. Let me see if I
can write a patch.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
> (2) Build the SeaBIOS CSM (CONFIG_CSM=y), and embed it into OVMF,
> like described above. Then, boot Windows 7 in *UEFI Mode*.
> Option #1 and option #2 no longer work because the CSM infrastructure
> in edk2 needs to be able to write 0xc.
Well, option #2 works for me.
--
You received thi
On 09/19/17 13:49, Gerd Hoffmann wrote:
> ovmf seems to not touch pam configuration, so rom remains mapped.
I don't understand; the code that I quoted above -- and that LaunchPad
messed up -- explicitly changes the PAM registers:
//
// Put the shim in place first.
//
Pam1Address = PCI_LIB
Indeed the CSM platform support had the same error one and half years
ago, see:
https://github.com/tianocore/edk2/commit/db27e9f3d8f0
Thank you, Gerd, for the hint!
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launch
Re: comment 14, "is there a way to fix vbeshim instead of reverting RO
limitation that commit introduced?":
I don't think so; please see my earlier comments 15 and 17. To
elaborate:
If a user wants to boot Windows 7 on OVMF, they have *three* options:
(1) Build the SeaBIOS CSM (CONFIG_CSM=y), an
On Tue, 19 Sep 2017 10:59:51 -
"Laszlo Ersek \(Red Hat\)" wrote:
> Thanks, Gerd, for the CC -- I agree, this commit (208fa0e43645) almost
> certainly breaks the VBE Shim. Displaying the patch with a bit larger
> context,
>
> > diff --git a/hw/i386/pc.c b/hw/i386/pc.c
> > index 22e16031b03b..
ovmf seems to not touch pam configuration, so rom remains mapped.
seabios in contrast maps the address range to ram instead.
IIRC ovmf does that too in CSM mode.
So, yes, probably this is fixable in ovmf.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is s
What I mentioned earlier was not that SeaBIOS would break.
Instead, I said that building OVMF, with the SeaBIOS CSM (Compatibility
Support Module) embedded into it, would break, exactly the same way as
the VBE Shim.
Quoting the CSM Spec from Intel: "The CSM provides compatibility support
between
On Tue, 19 Sep 2017 10:39:00 -
Gerd Hoffmann <1715...@bugs.launchpad.net> wrote:
> could be this commit breaks vbeshim ...
>
Did a bit of testing: w7 iso boots to install screen with seabios but
stuck at win boot logo with ovmf.
I've heard (maybe wrongly) that seabios would also break in th
I'd also like to mention that, when we originally worked on the VBE
Shim, I tried to put it elsewhere. Obviously it has to be pointed-to by
a real mode interrupt vector, which limits quite a bit where it can go
at all; the point is that I tried to put it into low *RAM* (under
640KB).
It didn't wor
On Tue, 19 Sep 2017 10:39:00 -
Gerd Hoffmann <1715...@bugs.launchpad.net> wrote:
> could be this commit breaks vbeshim ...
>
is there a way to fix vbeshim instead of reverting RO limitation that
commit introduced?
--
You received this bug notification because you are a member of qemu-
deve
I'm not sure if I mentioned this before, but launchpad is an
*abomination*.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1715700
Title:
Windows 7 guest won't boot on qemu 2.10 (works on 2.9)
Stat
Thanks, Gerd, for the CC -- I agree, this commit (208fa0e43645) almost
certainly breaks the VBE Shim. Displaying the patch with a bit larger
context,
> diff --git a/hw/i386/pc.c b/hw/i386/pc.c
> index 22e16031b03b..59435390ba62 100644
> --- a/hw/i386/pc.c
> +++ b/hw/i386/pc.c
> @@ -1442,8 +1442,11
could be this commit breaks vbeshim ...
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1715700
Title:
Windows 7 guest won't boot on qemu 2.10 (works on 2.9)
Status in QEMU:
New
Bug description:
Igor asked to add Gerd.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1715700
Title:
Windows 7 guest won't boot on qemu 2.10 (works on 2.9)
Status in QEMU:
New
Bug description:
Qemu version:
Added Imammedo to this lp.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1715700
Title:
Windows 7 guest won't boot on qemu 2.10 (works on 2.9)
Status in QEMU:
New
Bug description:
Qemu versio
Just did a test to be sure: pulled latest git
(a9158a5cba955b79d580a252cc58ff44d154e370) - guest didn't launch.
Reverted 208fa0e43645edd0b0d8f838857dfc79daff40a8 - guest launched
successfully.
Can someone please take a look at this? I don't want to get stuck at
2.9.0 :)
--
You received this bug
Bisected. Good thing Igor is already here :)
208fa0e43645edd0b0d8f838857dfc79daff40a8 is the first bad commit
commit 208fa0e43645edd0b0d8f838857dfc79daff40a8
Author: Igor Mammedov
Date: Fri Jul 28 11:09:05 2017 +0200
pc: make 'pc.rom' readonly when machine has PCI enabled
--
You received
The newer GCC compilers are more fussy - just add '--disable-werror'
when running 'configure' to make it ignore the warning
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1715700
Title:
Windows 7 gu
* Aleksei Kovura (alex3...@zoho.com) wrote:
> Ok, so I cloned from github and am bisecting like this (it's been a while,
> correct me if I'm wrong):
> $ git bisect start
> $ git bisect bad 1ab5eb4efb91a3d4569b0df6e824cc08ab4bd8ec # 2.10.0 stable
> commit
> $ git bisect good 359c41abe32638adad503e
Ok, so I cloned from github and am bisecting like this (it's been a while,
correct me if I'm wrong):
$ git bisect start
$ git bisect bad 1ab5eb4efb91a3d4569b0df6e824cc08ab4bd8ec # 2.10.0 stable commit
$ git bisect good 359c41abe32638adad503e386969fa428cecff52 # 2.9.0 stable commit
Bisecting: 1426
On Thu, 07 Sep 2017 19:34:37 -
Aleksei Kovura wrote:
> Compiled latest OVMF from git (ea21f1d), used it in "-bios" line - same
> result. What else can I try?
Bisecting 2.9 -> 2.10 might point out offending commit
Compiled latest OVMF from git (ea21f1d), used it in "-bios" line - same
result. What else can I try?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1715700
Title:
Windows 7 guest won't boot on qemu
Hi,
There's a good chance this is the same as lp 1714331 - fixed by a newer OVMF.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1715700
Title:
Windows 7 guest won't boot on qemu 2.10 (works on 2.
29 matches
Mail list logo
