#Linux community, I have been trying to find documentation how to use #hyperv on Linux, and I mean as the #Dom0 and the guy and girls at #microsoft who has provided the hyper-v host code don't bother to reply on inquiries.

Anyone who know how or seen documentation?

At least there is a big proof it works as #Azure is up and running...

#LinuxHacks

@MsDropbear42 the type-1/type-2 terminology should probably be retired at this point. #kvm exhibits a lot of type-2 behaviour (e.g. guests are processes to the kernel) although being #Linux it accesses the hardware directly. #Xen looks more like a typical type-1 layered #hypervisor although a lot of #hardware management is delegated to the #dom0 guest. And that's before you look at the architectural differences between for example #x86 and #arm (with and without #vhe).

So I finally got around to experimenting with Qubes and in the process, uncovered yet one more reason to despise #systemd

There is a unit / service, rc-local, that has the sole job of executing /etc/rc.d/rc.local should it exist and be marked executable.

I like to use the console, and I like to be able to read the font. I like to remap my caps lock key to be control.

So I dumped the loadkeys and setfont commands in /etc/rc.d/rc.local and rebooted.

Only to find out that rc-local had aborted, because... In graphical mode, it has been decided, by someone, that there should be no need to 'setfont'.

Someone decided, in their infinite wisdom, that in graphical mode, nobody would /ever/ use CTRL-ALT-F2 to switch to a virtual terminal.

I threw my hands up with #Qubes, and ran into some other issue that I since resolved -- dom0 has no network, therefore I can't clone my configs to it, but realized I could create a vdisk that would be accessible by one of my users in a separate VM.

The issue with #Fedora 40 and systemd being a part of dom0 was ultimately the deal-breaker, which has lead me down the path of figuring out how to more or less re-implement the Qubes approach on Slackware.

To my great joy, someone has compiled an excellent guide for how to install and configure #Slackware to be a #dom0 for #Xen.

My plan for #Slubes is coming together better than I'd hoped.

https://pub.nethence.com/xen/slackware

Slackware Linux as a XEN host

#TIL: A #Xen #Dom0 running #Debian 12 Bookworm or #Gentoo may crash xenconsoled or xenstored upon #DomU boot if the Dom0 initially has too much RAM:

kernel BUG at arch/x86/xen/p2m.c:542!

In my case it happened with #DebianBookworm's kernel 6.1.0-21-amd64 and in the case of https://bugs.gentoo.org/920747 (via https://lists.xenproject.org/archives/html/xen-users/2023-12/msg00005.html) it was Gentoo's 6.1.67-gentoo-x86_64, both with 64 GB.

Fix:

/etc/default/grub += GRUB_CMDLINE_XEN_DEFAULT="dom0_mem=1024M,max:1024M"

/etc/xen/xl.conf += autoballoon=0

920747 – app-emulation/xen-4.16.6_pre1-kernel bug - xen/p2m.c: 542: invalid opcode: 0000 [#1] PREEMPT SMP NOPTI

And thanks to #KDE, #Dom0 is looking quite good.