[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] EFI boot unsuccessful with Ubuntu 18.04 dom0

I am having the very same kind of problem using Gentoo.  About two years ago, I was able to build a xen kernel in Gentoo and start a Dom0 instance by using UEFI command line.  At that time, GRUB2 did not support UEFI.  For the sake of brevity, I am having the very same problem now as depicted by Mr. Baixauli as I upgraded the kernel (to 4.19.23-gentoo) and wanted to get the system to boot up without my manual intervention.  I've built a kernel which successfully boots for a regular Gentoo session using Grub2, but when I try to launch the Dom0 version, I'm cut off at the initial posting with no record and having to push the reset button.  I did make progress because I hard-wired the location of the root drive into the kernel using the Partition ID - see https://wiki.gentoo.org/wiki/EFI_stub_kernel

And I made some progress, the boot up gets past the "Cannot find FS...", but then it hangs thereafter.

My current solution is: I've ordered a serial to USB connector so I can monitor and capture the boot postings to help further identify the problem.  I'll then be staging the emerge builds, the kernel configuration, the kernel build log, and the boot posting with appropriate questions either here and/or the Gentoo Forum seeking help so all the information will be available to one considering my question. I'm certain the problem I'm having concerns the file system differences.

I wanted to respond here just to you let you know you are not alone and I'm hopeful once I capture the boot postings, I'll be closer to identifying the problem and obtaining help.  I'm hoping that in the next week I'll have a nice package to present for a plea of help.

On 2/25/2019 10:16 AM, Enrique Sainz Baixauli wrote:

I am very new to Xen, trying to set up my laptop with Xen using the EFI image that comes with Ubuntu package xen-hypervisor-4.9-amd64.

I have managed to boot the image by modifying efibootmgr options and adding a new entry there. However, when trying to boot that entry, it first prints out how it loads xen hypervisor, its config file, the Linux kernel and the initramfs, and two more lines with hex digits that I can't read because they disappear too fast. And then it goes blank. It stays blank for a few seconds and finally a white blinking cursor shows up in the top left corner of the screen. Then I have to Ctrl+Alt+Del to reboot, as I get nothing else.

What I have done:
  1. Install Ubuntu package xen-hypervisor-4.9-amd64.
  2. Create a new directory "xen" under /boot/efi/EFI with the following files:
    1. xen-4.9-amd.efi
    2. vmlinuz-4.15.0-45-generic
    3. initrd.img-4.15.0-45-generic
    4. xen.cfg, with the following content:
    options=console=vga,com1 com1=115200,8n1 iommu=verbose ucode=scan flask=disabled conring_size=2097152  loglvl=all
    kernel=vmlinuz-4.15.0-45-generic root=UUID=24bd5658-bf88-41ae-85e7-11ea902a3c50= ro vt.handoff=7 console=hvc0
  3. Added the new entry with the command efibootmgr -c -d /dev/nvme0n1 -L Xen -l "\EFI\xen\xen-4.9-amd64.efi"
All of this following the UEFI guide at Xen wiki: https://wiki.xenproject.org/wiki/Xen_EFI

My guess is that the config in xen.cfg is not adequate for booting Ubuntu. But the list of options (https://xenbits.xen.org/docs/unstable/man/xl.cfg.5.html) is so long I have no idea how to write a proper config file.

Can anyone shed some light on this? Or some way to get any debug information from the boot process inside Xen? I am totally clueless here.


Xen-users mailing list

John Laurence Poole
Salem OR 97301-4241
707-812-1323 office

Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.