I have found a solution in the past (and am still using) another way of loading the (AMD) microcode in Xen.
In essence:
- Create a symlink from /lib/firmware/amd-ucode/microcode_amd_fam15h.bin -> /boot/microcode_amd_fam15h.bin
- Edit the /etc/xen/grub.conf and add " ucode=-1"
-
Manually update the file /etc/grub.d/09_xen by adding the following two lines (note that these lines differ a little bit from the forum post
echo 'Loading AMD Microcode' module2 ${REAL_DIR}/microcode_amd_fam15h.bin
-
rebuild grub conf file: grub-mkconfig -o /boot/grub/grub.cfg
- reboot
I have described it more accurately in this forum post, where you have to replace the word module (outdated) with module2.
https://bbs.archlinux.org/viewtopic.php?id=191828
So, no kernel panic while loading multiple ramdisks.
Does this help you to find a persistent solution?
Pinned Comments
Refutationalist commented on 2024-05-22 22:08 (UTC) (edited on 2024-05-23 00:07 (UTC) by Refutationalist)
As of now (2024-22-05) Xen with stubdom doesn't build because of a problem in the imported code. Been this way for about two weeks. Anyone else seeing this behavior?
Also, there is a lot of work happening on Xen in my development repo, thanks to @Serus. Check it out at: https://github.com/refutationalist/saur