> Should this be opened as a bug on the `ovmf` Ubuntu package
(xenial/zesty/artful)? I'm very familiar with the Ubuntu version
policies.
I've just noticed that I intended to write "I'm *not* very familiar with
the Ubuntu version policies".
--
You received this bug notification because you are a
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/1714331
Title:
Virtual machines not working anymore on 2.10
Status in QEMU:
New
Bug description:
Using 2.10, my virtual
Building the OVMF from the `edk2` current master (89796c69d9) fixes both
(non/vfio) issues.
Should this be opened as a bug on the `ovmf` Ubuntu package
(xenial/zesty/artful)? I'm very familiar with the Ubuntu version
policies.
--
You received this bug notification because you are a member of
I was using a version of OVMF from about a year ago which works fine
with QEMU 2.8 and 2.9 but doesn't work with 2.10. I just updated to the
latest OVMF from master and everything's working now with QEMU 2.10 and
WIndows 10 64 bit, so the old OVMF was the issue.
Thanks for your help,
Chris
--
I'm using the Ubuntu artful version (0~20161202.7bbe0b3e-1), so I'll
need to build a recent OVMF package to verify the solution.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1714331
Title:
Hi Stefan,
What version of OVMF are you using? There were a bunch of bugs related to
FADT in OVMF which were fixed back in March. Specifically, commits
072060a, 78807f6, and 198a46d. If your version of OVMF doesn't include
these fixes, that's a likely source for your problems.
Hope that helps.
On Tue, Sep 05, 2017 at 06:42:06PM -, Chris Unsworth wrote:
> I think my issue looks like the same. Sometimes I just get spinning
> dots, and sometimes there is the message about doing an automatic repair
> below the spinning dots before it stops and uses 100% cpu. I just did a
> git bisect:
I think my issue looks like the same. Sometimes I just get spinning
dots, and sometimes there is the message about doing an automatic repair
below the spinning dots before it stops and uses 100% cpu. I just did a
git bisect:
# git bisect log
# bad: [1ab5eb4efb91a3d4569b0df6e824cc08ab4bd8ec]
OK, I'll do that. It will take me a bit of time - I'll timeframe a week.
Note that I can't know if both VFIO and non-VFIO context suffer the same
bug. For simplicity, I'll peform the bisect using the non-VFIO version,
then, once we have more information, we can decide how to proceed.
--
You
Mary: If you have time to run a git bisect that would be very helpful,
thanks!
$ git bisect v2.10.0 v2.9.0
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1714331
Title:
Virtual machines not
I am also unable to boot Windows 10 64 bit since updating to 2.10.0. I
was previously using 2.8.0 which worked perfectly. Windows gets stuck
at the big Windows logo with the spinning dots underneath and QEMU uses
100% CPU of 1 core. I am using kernel 4.11.9 and the following command
line:
> Please try: -machine pc-q35-2.9,accel=kvm,mem-merge=off
I've tried the first configuration (windowed) with the change you
proposed, and I get the same behavior (windows recovery); I didnt' try
the second configuration (VFIO).
> Did you build QEMU 2.9 from source with the same ./configure
Please try: -machine pc-q35-2.9,accel=kvm,mem-merge=off
I'm not sure if it will make a difference in this case but it presents
exactly the same onboard hardware as QEMU 2.9. The onboard hardware
configuration may change unless you specify a precise version in the
machine type, so I suggest using
13 matches
Mail list logo
