Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #257598 > unrolled thread
| Started by | Valentin Caracalla <vorubergehend@tutanota.com> |
|---|---|
| First post | 2023-04-25 17:40 +0200 |
| Last post | 2023-04-25 19:50 +0200 |
| Articles | 5 — 3 participants |
Back to article view | Back to linux.debian.user
Re: Re: Debian installation using debootstrap and grub-install - no entry in ESC boot menu Valentin Caracalla <vorubergehend@tutanota.com> - 2023-04-25 17:40 +0200
Re: Debian installation using debootstrap and grub-install - no entry in ESC boot menu Steve McIntyre <steve@einval.com> - 2023-04-25 17:50 +0200
Boot an EFI system with QEMU Valentin Caracalla <vorubergehend@tutanota.com> - 2023-04-25 19:20 +0200
Re: Boot an EFI system with QEMU Nicolas George <george@nsup.org> - 2023-04-25 19:30 +0200
Re: Boot an EFI system with QEMU Steve McIntyre <steve@einval.com> - 2023-04-25 19:50 +0200
| From | Valentin Caracalla <vorubergehend@tutanota.com> |
|---|---|
| Date | 2023-04-25 17:40 +0200 |
| Subject | Re: Re: Debian installation using debootstrap and grub-install - no entry in ESC boot menu |
| Message-ID | <GosVP-4rVa-3@gated-at.bofh.it> |
By the way: The disadvantage of using EFI is that it doesn't work in QEMU, i.e. the following will not show a GRUB command line: sudo qemu-system-x86_64 -accel kvm -smp 2 -m 2G /dev/sda The same thing works for the BIOS boot interface, however (as in my original recipe).
[toc] | [next] | [standalone]
| From | Steve McIntyre <steve@einval.com> |
|---|---|
| Date | 2023-04-25 17:50 +0200 |
| Message-ID | <Got5v-4rYA-3@gated-at.bofh.it> |
| In reply to | #257598 |
vorubergehend@tutanota.com wrote:
>By the way:
>
>The disadvantage of using EFI is that it doesn't work in QEMU, i.e. the following will not show a GRUB command line:
>
>sudo qemu-system-x86_64 -accel kvm -smp 2 -m 2G /dev/sda
>
>The same thing works for the BIOS boot interface, however (as in my original recipe).
That's just qemu-system-x86_64 defaulting to using SeaBIOS for
firmware. I boot VMs in UEFI mode all the time, using the EDK2 binary
builds in the ovmf package.
--
Steve McIntyre, Cambridge, UK. steve@einval.com
< sladen> I actually stayed in a hotel and arrived to find a post-it
note stuck to the mini-bar saying "Paul: This fridge and
fittings are the correct way around and do not need altering"
[toc] | [prev] | [next] | [standalone]
| From | Valentin Caracalla <vorubergehend@tutanota.com> |
|---|---|
| Date | 2023-04-25 19:20 +0200 |
| Subject | Boot an EFI system with QEMU |
| Message-ID | <GouuB-4sXp-1@gated-at.bofh.it> |
| In reply to | #257599 |
Hello Steve,
thanks a lot for the tip! However, I'm a complete novice when it comes to running custom firmware in QEMU. I just tried the following:
1.: Download the latest EDK2 release from Github:
https://github.com/tianocore/edk2/archive/refs/tags/edk2-stable202302.tar.gz
2.: Extract the OVMF firmware file:
tar xz edk2-edk2-stable202302/OvmfPkg/OvmfPkgX64.fdf <Downloads/edk2-edk2-stable202302.tar.gz
3.: Try to run it with QEMU:
sudo qemu-system-x86_64 -accel kvm -bios edk2-edk2-stable202302/OvmfPkg/OvmfPkgX64.fdf -smp 2 -m 2G /dev/sda
This will just give me a QEMU error message ("could not load PC BIOS"). Is it possible to boot an EFI system with QEMU without downloading a custom firmware file, i.e. is there a Debian package providing this functionality?
Kind regards,
Valentin Caracalla
[toc] | [prev] | [next] | [standalone]
| From | Nicolas George <george@nsup.org> |
|---|---|
| Date | 2023-04-25 19:30 +0200 |
| Subject | Re: Boot an EFI system with QEMU |
| Message-ID | <GouEh-4t0v-3@gated-at.bofh.it> |
| In reply to | #257604 |
[Multipart message — attachments visible in raw view] — view raw
Valentin Caracalla (12023-04-25): > thanks a lot for the tip! However, I'm a complete novice when it comes to running custom firmware in QEMU. I just tried the following: > > 1.: Download the latest EDK2 release from Github: I could boot a VM with a UEFI bootloader using only files packaged by the host operating system, an old Ubuntu LTS, 18 IIRC. I do not have my notes near at hand, but I found the procedure easily either on some stackoverflow question or possibly in the answers of an AI search engine, as I am frequently toying with them these days. HtH Regards, -- Nicolas George
[toc] | [prev] | [next] | [standalone]
| From | Steve McIntyre <steve@einval.com> |
|---|---|
| Date | 2023-04-25 19:50 +0200 |
| Subject | Re: Boot an EFI system with QEMU |
| Message-ID | <GouXD-4t76-15@gated-at.bofh.it> |
| In reply to | #257604 |
On Tue, Apr 25, 2023 at 07:00:21PM +0200, Valentin Caracalla wrote:
>Hello Steve,
>
>thanks a lot for the tip! However, I'm a complete novice when it comes to running custom firmware in QEMU. I just tried the following:
>
>1.: Download the latest EDK2 release from Github:
>
>https://github.com/tianocore/edk2/archive/refs/tags/edk2-stable202302.tar.gz
>
>2.: Extract the OVMF firmware file:
>
>tar xz edk2-edk2-stable202302/OvmfPkg/OvmfPkgX64.fdf <Downloads/edk2-edk2-stable202302.tar.gz
>3.: Try to run it with QEMU:
>
>sudo qemu-system-x86_64 -accel kvm -bios edk2-edk2-stable202302/OvmfPkg/OvmfPkgX64.fdf -smp 2 -m 2G /dev/sda
>This will just give me a QEMU error message ("could not load PC BIOS"). Is it possible to boot an EFI system with QEMU without downloading a custom firmware file, i.e. is there a Debian package providing this functionality?
My local test scripts for UEFI boot do other things too, but I add the
following:
-pflash <OVMF image> -pflash <vars image>
where I copy matching images from /usr/share/OVMF in the ovmf
package. See the file /usr/share/doc/ovmf/README.Debian for what the
different files offer (secure boot, etc.).
--
Steve McIntyre, Cambridge, UK. steve@einval.com
"Yes, of course duct tape works in a near-vacuum. Duct tape works
anywhere. Duct tape is magic and should be worshipped."
-― Andy Weir, "The Martian"
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.user
csiph-web