qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <1715700@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 1715700] Re: Windows 7 guest won't boot on qemu 2.10 (works on 2.9)
Date: Tue, 19 Sep 2017 12:38:15 -0000	[thread overview]
Message-ID: <1505824695.12708.7.camel@redhat.com> (raw)
In-Reply-To: 150582231000.13645.13271569408662777261.malone@gac.canonical.com

> (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 0xc0000.

Well, option #2 works for me.

-- 
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: 2.10 stable.
  Guest: Windows 7 SP1 x64, virtio drivers are already installed in the guest.
  Command line:
  qemu-system-x86_64 \
      -nodefaults \
      -nodefconfig \
      -machine type=q35,accel=kvm \
      -enable-kvm \
      -cpu host \
      -m 2048 \
      -vga virtio \
      -boot menu=on \
      -smbios file=/path/dmidecode_BIOS.bin \
      -acpitable file=/path/acpi_slic.bin \
      -bios /path/OVMF_CODE.fd \
      -net none \
      -drive if=virtio,media=disk,file=/media/win7.qcow2 \
      -device pcie-root-port \
      -device ich9-usb-ehci1 \
      -device ich9-usb-uhci1 \
      -device ich9-usb-uhci2 \
      -device ich9-usb-uhci3

  Windows hangs at boot with waving flag screen (flag doesn't freeze,
  keeps waving indefinitely). Same command line boots fine with Qemu
  2.9. I tried changing machine type to pc-q35-2.9 - same result.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1715700/+subscriptions

  reply	other threads:[~2017-09-19 12:51 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-07 16:31 [Qemu-devel] [Bug 1715700] [NEW] Windows 7 guest won't boot on qemu 2.10 (works on 2.9) Aleksei Kovura
2017-09-07 16:48 ` [Qemu-devel] [Bug 1715700] " Dr. David Alan Gilbert
2017-09-07 19:34 ` Aleksei Kovura
2017-09-11 11:41   ` Igor Mammedov
2017-09-11 16:15 ` Aleksei Kovura
2017-09-11 16:36   ` Dr. David Alan Gilbert
2017-09-11 16:36 ` Daniel Berrange
2017-09-11 20:43 ` Aleksei Kovura
2017-09-18 19:12 ` Aleksei Kovura
2017-09-19  9:27 ` Dr. David Alan Gilbert
2017-09-19 10:01 ` Dr. David Alan Gilbert
2017-09-19 10:39 ` Gerd Hoffmann
2017-09-19 11:01   ` Igor
2017-09-19 11:10   ` Igor
2017-09-19 10:59 ` Laszlo Ersek (Red Hat)
2017-09-19 11:46   ` Igor
2017-09-19 11:00 ` Laszlo Ersek (Red Hat)
2017-09-19 11:10 ` Laszlo Ersek (Red Hat)
2017-09-19 11:44 ` Laszlo Ersek (Red Hat)
2017-09-19 11:49 ` Gerd Hoffmann
2017-09-19 12:33   ` Laszlo Ersek (Red Hat)
2017-09-19 11:58 ` Laszlo Ersek (Red Hat)
2017-09-19 12:38   ` Gerd Hoffmann [this message]
2017-09-19 13:05     ` Laszlo Ersek (Red Hat)
2017-09-19 12:35 ` Laszlo Ersek (Red Hat)
2017-09-19 12:38 ` Laszlo Ersek (Red Hat)
2017-09-19 19:20 ` Laszlo Ersek (Red Hat)
2017-09-20 18:29 ` Laszlo Ersek (Red Hat)
2017-10-23 18:57 ` Laszlo Ersek (Red Hat)
2018-04-26 10:08 ` Thomas Huth

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1505824695.12708.7.camel@redhat.com \
    --to=1715700@bugs.launchpad.net \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).