Claudia:
Claudia:
# tar -C / -cvzf ~/boot-backup.tar.gz boot/
# qubes-dom0-update grub2-efi
# chmod ugo+x /etc/grub.d/10_linux
# echo GRUB_CMDLINE_LINUX=\"$(cat /boot/efi/EFI/qubes/xen.cfg | grep
kernel | cut -d ' ' -f 4- | head -n 1)\" >> /etc/default/grub
# grub2-mkconfig -o
Claudia:
# tar -C / -cvzf ~/boot-backup.tar.gz boot/
# qubes-dom0-update grub2-efi
# chmod ugo+x /etc/grub.d/10_linux
# echo GRUB_CMDLINE_LINUX=\"$(cat /boot/efi/EFI/qubes/xen.cfg | grep
kernel | cut -d ' ' -f 4- | head -n 1)\" >> /etc/default/grub
# grub2-mkconfig -o
'awokd' via qubes-users:
Claudia:
So I was wondering, is it possible to run the Qubes dom0 kernel directly
on the hardware instead of under Xen? How might one go about this? And
how much work would it involve?
I've had similar troubleshooting needs. Closest I found was to download
Fedora 25
Claudia:
> So I was wondering, is it possible to run the Qubes dom0 kernel directly
> on the hardware instead of under Xen? How might one go about this? And
> how much work would it involve?
I've had similar troubleshooting needs. Closest I found was to download
Fedora 25 and test under that.
I've recently run into some hardware problems in Qubes which are not
present in the equivalent Fedora version (F25). I have a feeling Xen may
be a likely culprit, just simply because of how Xen controls the use of
certain hardware for security reasons (VT-d, and such).
If it were possible to
