search for: lockdown_m

...virt-manager. > >q35 doesn't help here. secureboot is in the EFI config menus (press ><ESC> or <DEL> in the guest while booting, go look at the boot >configuration, and you'll see secureboot options -- it's disabled by >default and not able to be enabled until LockDown_ms is applied). > Oh, so that's what I misunderstood, sorry for that. >What I don't understand is why this matters, since I was able to boot >with basically the generated command (see below) from a console, but >it's 100% reproducible. > >> >>>> Using qe...

On Mon, Aug 03, 2015 at 03:39:30PM -0700, Ryan Barry wrote: >On 08/03/2015 01:43 PM, Ryan Barry wrote: >> Using: >> >> edk2.git-0-20150803.b1141.ga0973dc.x86_64 >> edk2.git-ovmf-x64-0-20150802.b1139.gb234418.noarch >> >> On Fedora 22. >> >> Provisioning a i440FX system in virt-manager and attempting to boot >> results in successful EFI

...t anywhere in > virt-manager. q35 doesn't help here. secureboot is in the EFI config menus (press <ESC> or <DEL> in the guest while booting, go look at the boot configuration, and you'll see secureboot options -- it's disabled by default and not able to be enabled until LockDown_ms is applied). What I don't understand is why this matters, since I was able to boot with basically the generated command (see below) from a console, but it's 100% reproducible. > >>> Using qemu-kvm directly (qemu-kvm -bios >>> /usr/share/edk2.git/ovmf-x64/OVMF_CODE-...

...gt;> q35 doesn't help here. secureboot is in the EFI config menus >> (press <ESC> or <DEL> in the guest while booting, go look at the >> boot configuration, and you'll see secureboot options -- it's >> disabled by default and not able to be enabled until LockDown_ms >> is applied). >> > > Oh, so that's what I misunderstood, sorry for that. > >> What I don't understand is why this matters, since I was able to >> boot with basically the generated command (see below) from a >> console, but it's 100% reproduci...