[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] Xen 4.12.0 Dom0=pvh mode EFI variables 'not supported' after boot
Adding the Linux Xen maintainers, in case they can provide some insight. On Mon, Apr 15, 2019 at 03:27:43PM -0700, PGNet Dev wrote: > ref: from chat in #xen > > [08:53] <royger> pgnd: would be good to send an email so we can keep > track of this in a more formal way. > > I've got Xen PV Dom0 booted on a Linux UEFI box > > dmesg | grep -i "xen version" > [ 1.185996] Xen version: 4.12.0_09-lp150.640 (preserve-AD) > > uname -rm > 5.0.7-lp150.5.g012b5f1-default x86_64 > > lsb_release -rd > Description: openSUSE Leap 15.0 > Release: 15.0 > > rpm -qa | grep -i qemu | egrep "seabios|u-3" > qemu-seabios-1.12.0-lp150.513.13.noarch > qemu-3.1.0-lp150.513.13.x86_64 > > rpm -qa | grep -i ovmf > ovmf-tools-2019+git1552059899.89910a39dcfd-lp150.100.3.x86_64 > > qemu-ovmf-x86_64-2019+git1552059899.89910a39dcfd-lp150.100.3.noarch > ovmf-2019+git1552059899.89910a39dcfd-lp150.100.3.x86_64 > > rpm -qa | grep grub2 |egrep "xen|efi" > grub2-x86_64-efi-2.02-lp150.64.10.noarch > grub2-x86_64-xen-2.02-lp150.64.10.noarch > & > > rpm -qa | grep -i efi | grep git | sort > efibootmgr-999.git.20190306.438ba96-lp150.7.22.x86_64 > efivar-devel-999.git.20190305.836461e-lp150.6.21.x86_64 > libefivar1-999.git.20190305.836461e-lp150.6.21.x86_64 > > note these^^ EFI* tools -- src from efi master branch, pkgs available here, > > https://build.opensuse.org/package/show/home:pgnd:Kernel:stable/efivar > > https://build.opensuse.org/package/show/home:pgnd:Kernel:stable/efibootmgr > > -- were needed, as distro packaged versions' were old/problematic ... > > With this^^ config, all's well > > serial boot log > ... > [ 0.000000] efi: EFI v2.31 by American Megatrends > [ 0.000000] efi: ESRT=0x9ef8d998 ACPI 2.0=0x9e819000 > ACPI=0x9e819000 SMBIOS=0xf04c0 MPS=0xfd490 > [ 0.000000] SMBIOS 2.7 present. > [ 0.000000] Hypervisor detected: Xen PV > [ 0.000000] Xen version 4.12. > ... > > at shell prompt, > > xl list > Name ID Mem VCPUs > State Time(s) > Domain-0 0 4016 4 > r----- 5949.6 > Xenstore 1 31 1 > -b---- 0.2 > > efibootmgr -v > BootCurrent: 0000 > Timeout: 1 seconds > BootOrder: 0000 > Boot0000* openSUSE-pgnXEN > HD(2,GPT,98026223-f11d-3c68-8d30-3f9856c8c21e,0x1000,0x96000)/File(\EFI\opensuse\grubx64.efi) > dp: 04 01 2a ... 04 00 > > enabling PVH Dom0, adding to grub configs, > > GRUB_CMDLINE_LINUX_XEN_REPLACE="... intel_iommu=on ..." > GRUB_CMDLINE_XEN="... dom0=pvh dom0-iommu=map-reserved ..." > > then mkinitrd & grub reconfig, > > serial boot log > Xen 4.12.0_09-lp150.640 (c/s ) EFI loader > ... > (XEN) [00000027dcded44e] Bootloader: EFI > ... > Using configuration file 'xen-4.12.0_09-lp150.640.cfg' > ... > [ 0.000000] BIOS-e820: [mem > 0x0000000100000000-0x000000016a2acfff] usable > [ 0.000000] BIOS-e820: [mem > 0x000000016a2ad000-0x000000085dffffff] unusable > [ 0.000000] NX (Execute Disable) protection: active > [ 0.000000] SMBIOS 2.7 present. > [ 0.000000] Hypervisor detected: Xen HVM > [ 0.000000] Xen version 4.12. > ... > > Note, there is NO "efi: ..." log content, as in the prior, PV mode example. > > at shell prompt, > > xl list > Name ID Mem VCPUs > State Time(s) > Domain-0 0 4015 4 > r----- 563.0 > Xenstore 1 31 1 > -b---- 0.0 > > but, in this Dom0=pvh mode, > > efibootmgr -v > EFI variables are not supported on this system. So boot works as expected, it's just interaction with the EFI firmware by dom0 that seems to be broken. I'm currently setting up a Linux EFI box to test this, thanks for the report. Roger. _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/mailman/listinfo/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |