Arch Linux

ryanbarillos

Member

Registered: 2023-11-29

Posts: 51

[virt-manager] How to share my host Arch kernel to my guest Arch VM?

To save space on my Arch VM (I only gave it 10GB of space + with KDE & a dedicated browser), I wanna remove the Linux kernel of my guest Arch VM and just boot the VM using my host's kernel.

Currently using the linux-zen kernel. And I wanna share that.

I tried doing this by navigating here:

Arch VM >> Virtual Hardware Details >> Boot Options >> Direct kernel boot

And after giving my kernel & initrd paths it boots, but then I jump straight into the emergency shell with the following errors:

:: running early hook [udev]
Starting systemd-udevd version 259.3-1-arch
[    1.715855] NVRM: No NVIDIA GPU found.
[    1.957803] NVRM: No NVIDIA GPU found.
[    2.177464] NVRM: No NVIDIA GPU found.
[    2.405095] NVRM: No NVIDIA GPU found.
:: running hook [udev]
:: Triggering uevents...
:: running hook [keymap]
:: Loading keymap...done.
:: running hook [resume]
No resume device found, exiting.
ERROR: device '' not found. Skipping fsck.
:: mounting '' on real root
mount: /new_root: wrong fs type, bad option, bad superblock on , missing codepage or helper program, or other error.
       dmesg(1) may have more information after failed mount system call.
ERROR: Failed to mount '' on real root
You are now being dropped into an emergency shell.
sh: can't access tty; job control turned off
[rootfs ]#

Well that sucks. I don't know what's wrong.
I know my host machine has NVIDIA graphics card & in my mkinitcpio.conf I added in some NVIDIA modules to be built-in when regenerating the initramfs. And my Arch VM doesn't have and GPU passthrough in it (not even my only NVIDIA card).

Any ideas on where I'm hitting this problem wrong?

Lone_Wolf

Administrator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 14,901

Re: [virt-manager] How to share my host Arch kernel to my guest Arch VM?

You will probably need to create a separate initramfs for the guest and definitely change boot command parameters.

Using a chroot or Linux Container may be a better option .

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky