>>> On 26.03.15 at 08:17, <[email protected]> wrote: > I've installed an openSUSE 13.2 server. > > The server's built on a modern Supermicro motherboard with full UEFI > support. > > openSUSE boots ok via GRUB2+UEFI to kernel-default. > > uname -r > 3.19.2-3.gd8856ce-default > > I'm working on the switch to a Xen Dom0 > > I installed > > efibootmgr-0.6.0-3.2.2.x86_64 > grub2-x86_64-efi-2.02~beta2-20.5.1.x86_64 > grub2-x86_64-xen-2.02~beta2-20.5.1.x86_64 > kernel-xen-3.19.2-3.1.gd8856ce.x86_64 > xen-4.5.0_03-359.6.x86_64 > xen-libs-4.5.0_03-359.6.x86_64 > xen-tools-4.5.0_03-359.6.x86_64 > > When I boot/select the Xen option it stalls at > > WARNING: no console will be available to os > ... > loading initramd ... > > There's no console output. > > A search on the message led me to > > > http://lists.xenproject.org/archives/html/xen-users/2014-03/msg00142.html > > It is not possible to boot EFI Xen via grub. You should instead > boot it > direct from the EFI shell. > > http://xenbits.xen.org/docs/unstable/misc/efi.html has some > documentation for the config file which Xen expects when > booting in this > mode. > > Daniel Kiper is working with grub upstream to make a version of > multiboot which is compatible with EFI for use when booting Xen > via grub > on such systems. AFAIK it is not complete. > > and > > http://xenbits.xen.org/docs/unstable/misc/efi.html > > When booted as an EFI application, Xen requires a configuration > file as > described below unless a bootloader, such as GRUB, has loaded > the modules > and describes them in the device tree provided to Xen. If a > bootloader > provides > a device tree containing modules then any configuration files > are ignored, > and the bootloader is responsible for populating all relevant > device tree > nodes. > > I'm not sure if those are relevant to this case.
It is, in a way. > Does opensuse Xen Dom0 boot from GRUB2+UEFI? I suppose so, but using the chainloader command, not the "normal" mechanism to invoke a multiboot aware OS. I would have thought that you even get respective entries created when installing Xen, which you could then at least use as reference. The chainloader mechanism of course requires using xen.efi, not xen.gz. (To be precise, booting xen.gz to "normal" way is possible on some systems - the main prerequisite is that despite there being UEFI the firmware also exposes ACPI tables such that they can be found without using EFI mechanisms.) > What/where do I need to edit to fix the 'no console' error? No idea. Jan -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
