From mboxrd@z Thu Jan 1 00:00:00 1970 Subject: Re: [edk2-devel] [PATCH v2 03/11] OvmfPkg: PlatformBootManagerLibGrub: Allow executing kernel via fw_cfg To: Dov Murik ,devel@edk2.groups.io From: "Christoph Willing" X-Originating-Location: Brisbane, Queensland, AU (49.197.242.5) X-Originating-Platform: Linux Firefox 90 User-Agent: GROUPS.IO Web Poster MIME-Version: 1.0 Date: Mon, 19 Jul 2021 05:56:02 -0700 References: In-Reply-To: Message-ID: <23418.1626699362007911011@groups.io> Content-Type: multipart/alternative; boundary="MLtdosYDuWXnr6TYIPjN" --MLtdosYDuWXnr6TYIPjN Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Thanks for the clarification Dov. I've been trying with just "normal" VMs, not SEV. I did already find and t= ry the confidential-containers-demo sev-hashes-v2 branch but it didn't help= - not surprising if it's not relevant to normal VMs. Do you know whether this functionality (-kernel, -initrd, -append options)= is actually supposed to work in normal VMs at the moment? The only conditi= ons under which it works here with qemu-6.0.0 is with vUDK2017 & 2018 and a= n old ovmf binary package from kraxel.og dated 2017. Anything built from th= e edk2 master branch has failed when using those qemu options, although all= the same builds work perfectly using the VMs' internal kernels & initrds. = I've also extracted OVMF files from the current kraxel.org package as well = as Ubuntu's (hirsute) package and these also fail the same way i.e. kernel = boots and initrd works (loads modules) but then the VM filesystem doesn't s= eem to be found (no /dev/sdX exists to mount the filesystem root). I guess this could be a qemu problem but since it works with some (old) ud= k/edk2 versions, I thought I'd look here first. Thanks for any help or pointers, chris --MLtdosYDuWXnr6TYIPjN Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Thanks for the clarification Dov.

I've been trying with just "no= rmal" VMs, not SEV. I did already find and try the confidential-containers-= demo sev-hashes-v2 branch but it didn't help - not surprising if it's not r= elevant to normal VMs.

Do you know whether this functionality (-= kernel, -initrd, -append options) is actually supposed to work in normal VM= s at the moment? The only conditions under which it works here with qemu-6.= 0.0 is with vUDK2017 & 2018 and an old ovmf binary package from kraxel.= og dated 2017. Anything built from the edk2 master branch has failed when u= sing those qemu options, although all the same builds work perfectly using = the VMs' internal kernels & initrds. I've also extracted OVMF files fro= m the current kraxel.org package as well as Ubuntu's (hirsute) package and = these also fail the same way i.e. kernel boots and initrd works (loads modu= les) but then the VM filesystem doesn't seem to be found (no /dev/sdX exist= s to mount the filesystem root).

I guess this could be a qemu pr= oblem but since it works with some (old) udk/edk2 versions, I thought I'd l= ook here first.

Thanks for any help or pointers,
chris --MLtdosYDuWXnr6TYIPjN--