From: "Wu, Jiaxin" <jiaxin.wu@intel.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: edk2-devel-01 <edk2-devel@lists.01.org>
Subject: OVMF OS boot
Date: Fri, 7 Jul 2017 03:40:23 +0000 [thread overview]
Message-ID: <895558F6EA4E3B41AC93A00D163B7274162E37E7@SHSMSX103.ccr.corp.intel.com> (raw)
Hi Laszlo,
I'm trying to PXE boot Windows 7 within OVMF. According the README under OvmfPkg, I should run the QEMU command with '-vga std' or '-vga qxl':
Current capabilities:
...
* UEFI Linux boots
* UEFI Windows 8 boots
* UEFI Windows 7 & Windows 2008 Server boot (see important notes below!)
...
* One of the '-vga std' and '-vga qxl' QEMU options should be used.
* Only one video mode, 1024x768x32, is supported at OS runtime.
* The '-vga qxl' QEMU option is recommended. After booting the installed
guest OS, select the video card in Device Manager, and upgrade its driver
to the QXL XDDM one. Download location:
<http://www.spice-space.org/download.html>, Guest | Windows binaries.
This enables further resolutions at OS runtime, and provides S3
(suspend/resume) capability.
But after PXE downloaded the install image and run into OS phase(So, it's not related to PXE), the QEMU screen is always black, never show anything (Both '-vga std' and '-vga qxl'). I also tried the PXE boot to windows 10, the bluescreen happened during OS phase (Even is not declared to boot win10 in README).
MyQEMU command is attached as below:
sudo qemu-system-x86_64 \
-vga std \
-machine q35 \
-m 8192 \
-hda /var/qemuDisk/vd1 \
-pflash OVMF.fd \
-global e1000.romfile=""\
\
-netdev tap,id=hostnet0,ifname=tap0,script=no,downscript=no \
-device e1000,netdev=hostnet0
Notes: vd1 is created by: dd if=/dev/zero of=/var/qemuDisk/vd1 seek=1M bs=20480 count=1
Do you know why?
Thanks and Best Regards!
Jiaxin
next reply other threads:[~2017-07-07 3:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-07 3:40 Wu, Jiaxin [this message]
2017-07-07 11:40 ` OVMF OS boot Laszlo Ersek
2017-07-11 3:18 ` Wu, Jiaxin
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-list 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=895558F6EA4E3B41AC93A00D163B7274162E37E7@SHSMSX103.ccr.corp.intel.com \
--to=devel@edk2.groups.io \
/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