search for: pflash

This is only lightly tested. In particularly I only tested that the non-secure-boot path still works. I didn't test it on RHEL 7.3 yet because I haven't got enough free disk space for these giant source *.ova files :-( Will try to give that a go later. Rich.

Hello World, We were hit by the "internal snapshots of a VM with pflash based firmware are not supported" problem. Is there a workaround for it (for which revert works)? Another format perhaps? Our use case: We have an image (Win10, UEFI) with some software installed. This image is used by Jenkins to execute some tests. After the tests, the image should be re...

Greetings Andrea, > Sent: Monday, January 06, 2020 at 11:37 AM > From: "Andrea Bolognani" <abologna@redhat.com> > To: daggs <daggs@gmx.com>, libvirt-users@redhat.com > Subject: Re: [libvirt-users] aarch64 vm doesn't boots > > On Thu, 2019-12-26 at 09:00 +0100, daggs wrote: > > Greetings, > > > > I'm trying to bring up a alpine rpi

...contains_files (const char *dir, ...) * * XXX See also v2v/utils.ml:find_uefi_firmware */ -#ifdef __aarch64__ - -static const char *uefi_firmware[] = { - "/usr/share/AAVMF/AAVMF_CODE.fd", - "/usr/share/AAVMF/AAVMF_VARS.fd", - - "/usr/share/edk2.git/aarch64/QEMU_EFI-pflash.raw", - "/usr/share/edk2.git/aarch64/vars-template-pflash.raw", - - NULL -}; - -#else - -static const char *uefi_firmware[] = { NULL }; - -#endif - int guestfs_int_get_uefi (guestfs_h *g, char **code, char **vars) { +#ifdef __aarch64__ size_t i; - for (i = 0; uefi_firmware...

https://bugzilla.redhat.com/show_bug.cgi?id=1338083 Now that UEFI is fully open source the UEFI firmware can be included in Fedora. The location will be slightly different. These patches do a bit of code rearrangement and add the new paths. Rich.

...rt python binding UEFI: Shell> ver UEFI Interactive Shell v2.1 EDK II UEFI v2.50 (EDK II, 0x00010000) for this host....my nvram setting look like <os> <type arch='x86_64' machine='pc-i440fx-2.5'>hvm</type> <loader readonly='yes' type='pflash'>/home/xyz/OVMF.fd</loader> <nvram template='/usr/share/OVMF/OVMF_VARS.fd'>/var/lib/libvirt/qemu/nvram/X_VARS.fd</nvram> <boot dev='hd'/> </os>

...d I used: $ virt-install \ --cpu cortex-a53 \ --name alpine-aarch64 \ --cdrom ~/Downloads/alpine-virt-3.11.2-aarch64.iso \ --disk size=8 \ --vcpus 4 \ --memory 2048 \ --os-variant alpinelinux3.8 \ --arch aarch64 \ --boot loader=/usr/share/edk2/aarch64/QEMU_EFI-pflash.raw,loader.readonly=yes,loader.type=pflash,nvram.template=/usr/share/edk2/aarch64/vars-template-pflash.raw,loader_secure=no The '--boot ...' part is only necessary because of an issue in current libvirt that's already being worked on. Here's the full XML: <domain type='q...

First version was posted here: https://www.redhat.com/archives/libguestfs/2016-August/thread.html#00100 This is semantically the same as the first version. However I've split the patch up into two parts. In the first part, I factor out the UEFI paths so now they are created by the generator and written in the library and v2v/ directory directly, instead of the complex business of having a C

...DK II > > UEFI v2.50 (EDK II, 0x00010000) > > > > > > for this host....my nvram setting look like > > <os> > > <type arch='x86_64' machine='pc-i440fx-2.5'>hvm</type> > > <loader readonly='yes' type='pflash'>/home/xyz/OVMF.fd</loader> > > <nvram > > > template='/usr/share/OVMF/OVMF_VARS.fd'>/var/lib/libvirt/qemu/nvram/X_VARS.fd</nvram> > > <boot dev='hd'/> > > </os> > > Your domain XML is wrong. You can use...

...f using firmware=“efi” on libvirt 5.4.0 I am running Ubuntu eoan 19.10, I am wondering how did it happen. Detailed error Error starting domain: internal error: process exited while connecting to monitor: 2020-05-15T14:19:06.033267Z qemu-system-x86_64: -drive file=/usr/share/OVMF/OVMF_CODE.fd,if=pflash,format=raw,unit=0,readonly=on: Failed to lock byte 100 Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 75, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/asyncjob.py", line 111,...

...EFI Interactive Shell v2.1 > EDK II > UEFI v2.50 (EDK II, 0x00010000) > > > for this host....my nvram setting look like > <os> > <type arch='x86_64' machine='pc-i440fx-2.5'>hvm</type> > <loader readonly='yes' type='pflash'>/home/xyz/OVMF.fd</loader> > <nvram > template='/usr/share/OVMF/OVMF_VARS.fd'>/var/lib/libvirt/qemu/nvram/X_VARS.fd</nvram> > <boot dev='hd'/> > </os> Your domain XML is wrong. You can use OVMF with libvirt in three setups...

...and that guest differs from all other guest by: > > > > > > ? <os> > > > ??? <type arch='x86_64' machine='pc-q35-rhel9.0.0'>hvm</type> > > > ??? <loader readonly='yes' secure='yes' > > > type='pflash'>/usr/share/edk2/ovmf/OVMF_CODE.secboot.fd</loader> > > > <nvram>/var/lib/libvirt/qemu/nvram/ubusrv1_VARS.fd</nvram> > > > ??? <boot dev='hd'/> > > > ??? <bootmenu enable='yes'/> > > > ? </os> > &gt...

...t-manager. >> Using qemu-kvm directly (qemu-kvm -bios >> /usr/share/edk2.git/ovmf-x64/OVMF_CODE-pure-efi.fd -m 1G -cdrom >> ~rbarry/Downloads/Fedora-Server-netinst-x86_64-22.iso) boots and loads >> successfully. > We don't use '-bios' but '-drive file,if=pflash' and that's done once for the OVMF code and second time for the efivars storage. What's the guest XML and full command line of qemu being started? >Just to update -- > >This appears to be related to secureboot. Using a VM which has secure >boot enabled is successful > &...

...er error > > Hey, > > I'll paste the interesting part of domain XML here so that it doesn't > get lost: > > <os> > <type arch='x86_64' machine='pc-q35-5.0'>hvm</type> > <loader readonly='yes' > type='pflash'>/usr/share/edk2-ovmf/OVMF_CODE.fd</loader> > <nvram>/var/lib/libvirt/qemu/nvram/vm1_VARS.fd</nvram> > <boot dev='hd'/> > </os> > > And then in qemu.conf you define the pair: > > nvram = [ > "/usr/share/edk2-ovm...

...! I'm working currently on integration of UEFI/SecureBoot support into oVirt. And I have several questions about UEFI/SecureBoot support in libvirt. Can you please help me with them? For UEFI I add the following to the XML: <loader readonly="yes" secure="no" type="pflash"> /usr/share/OVMF/OVMF_CODE.secboot.fd </loader> <nvram template="/usr/share/OVMF/OVMF_VARS.fd"> /var/lib/libvirt/qemu/nvram/VM_UUID.fd </nvram> 1. Are all paths mandatory or there are some defaults? 2. If nvram image file is absent, libvirt creates it? 3. Is nv...

...u-kvm -bios >>>> /usr/share/edk2.git/ovmf-x64/OVMF_CODE-pure-efi.fd -m 1G -cdrom >>>> ~rbarry/Downloads/Fedora-Server-netinst-x86_64-22.iso) boots >>>> and loads successfully. >>> >> >> We don't use '-bios' but '-drive file,if=pflash' and that's done >> once for the OVMF code and second time for the efivars storage. >> What's the guest XML and full command line of qemu being started? > >I was able to boot with this (once I removed -S, -spice, and -netdev). >After installing with -netdev user...,...

...wrote: > Hi guys. > > I've have a guest and that guest differs from all other guest by: > > ? <os> > ??? <type arch='x86_64' machine='pc-q35-rhel9.0.0'>hvm</type> > ??? <loader readonly='yes' secure='yes' > type='pflash'>/usr/share/edk2/ovmf/OVMF_CODE.secboot.fd</loader> > <nvram>/var/lib/libvirt/qemu/nvram/ubusrv1_VARS.fd</nvram> > ??? <boot dev='hd'/> > ??? <bootmenu enable='yes'/> > ? </os> > > whereas everything else has: > >...

...>> I've have a guest and that guest differs from all other guest by: >> >> ? <os> >> ??? <type arch='x86_64' machine='pc-q35-rhel9.0.0'>hvm</type> >> ??? <loader readonly='yes' secure='yes' >> type='pflash'>/usr/share/edk2/ovmf/OVMF_CODE.secboot.fd</loader> >> <nvram>/var/lib/libvirt/qemu/nvram/ubusrv1_VARS.fd</nvram> >> ??? <boot dev='hd'/> >> ??? <bootmenu enable='yes'/> >> ? </os> >> >> whereas everyt...

...r *arg) ADD_CMDLINE ("kvm-pit.lost_tick_policy=discard"); } + /* UEFI (firmware) if required. */ + if (guestfs___get_uefi (g, &uefi_code, &uefi_vars) == -1) + goto cleanup0; + if (uefi_code) { + ADD_CMDLINE ("-drive"); + ADD_CMDLINE_PRINTF ("if=pflash,format=raw,file=%s,readonly", uefi_code); + if (uefi_vars) { + ADD_CMDLINE ("-drive"); + ADD_CMDLINE_PRINTF ("if=pflash,format=raw,file=%s", uefi_vars); + } + } + + /* Kernel, DTB and initrd. */ ADD_CMDLINE ("-kernel"); ADD_CMDLINE (kernel)...

...emu-kvm directly (qemu-kvm -bios >>> /usr/share/edk2.git/ovmf-x64/OVMF_CODE-pure-efi.fd -m 1G -cdrom >>> ~rbarry/Downloads/Fedora-Server-netinst-x86_64-22.iso) boots >>> and loads successfully. >> > > We don't use '-bios' but '-drive file,if=pflash' and that's done > once for the OVMF code and second time for the efivars storage. > What's the guest XML and full command line of qemu being started? I was able to boot with this (once I removed -S, -spice, and -netdev). After installing with -netdev user..., and applying Lock...