XEN + EFI = Unsupported device path component

English Virtualization
1

Greetings,

I’m a bit stuck and searching the web and this forum hasn’t been very helpful. I’ve got an HP Pavilion laptop (AMD A-10 platform) and am running OpenSuSE Leap 42.2. Thought I’d play with Xen and learn a little more about type 1 hypervisors so I set up a new install using the default LVM filesystem layout the installer gave me. I updated the system and then Installed the Xen server, Xen tools and libvirt LXC daemon via YaST. When I boot the system and select either of the Xen entries from the Grub menu it quickly displays an EFI Loader error message - I think it says Unsupported device path component. I’ll continue to scratch around. I’ve been off in Android the dev world for quite a while and using BBQLinux because the Android stuff is so tightly integrated in it. (I’m a lazy programmer) but OpenSuSE has been my favorite like forever. Wanted to check out the new stuffs and again, learn more about real virtualization. Any help for this ol’ man?

Many thanks

2

You’ll probably have to inspect the boot log, to inspect the previous boot entries in the system log,

journalctl -b -1

If you don’t understand or can’t find anything in your boot log, you can post it to a pastebin for others to inspect.

TSU

3

Thank you sir. Question though. If the bootloader can’t load the kernel will it even generate a boot log? Anyway, I took some time to get a little smarter about systemd, journald and journalctl. I’ll keep reading up on it since I’ve got lots to learn yet. But I used the exercise as an academic opportunity and did the following:

1: Capture current system time,

 echo `date` > rebootTime

2: Reboot the system and select the Hypervisor Grub menu entry.
3: After the EFI bootloader error flashes and returns me to the Grub menu, select the default entry and restart the vanilla kernel
4: Execute the date command to display the current time which says: **Fri Jun 30 21:32:08 CDT 2017
**5: Save the last boot log

 journalctl -b -1 > lastBoot.log

6: Cat the rebootTime file which says: **Fri Jun 30 21:29:58 CDT 2017

**
7: Trim the lastBoot.log file to something just before the rebootTime
8: Pastebin the file which can be seen here: https://pastebin.com/JCndVNyz

It doesn’t appear that it logs anything here during the time I attempt to boot the Xen kernel, which actually makes sense since the bootloader complains about an invalid (supported) device. The puzzle remains.