Git-Mirrors/qubes-doc
1
0
Fork 0
mirror of https://github.com/QubesOS/qubes-doc.git synced 2024-10-01 01:25:40 -04:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'master' of github.com:QubesOS/qubes-doc

Browse Source
This commit is contained in:
Andrew David Wong 2019-02-16 20:53:16 -06:00
commit bdbe42a83a
No known key found for this signature in database
GPG Key ID: 8CE137352A019A17
2 changed files with 22 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
configuration/managing-vm-kernel.md
View File

@ -207,6 +207,18 @@ mke2fs 1.42.12 (29-Aug-2014)
--> Done. --> Done.
~~~ ~~~
Kernel files structure
-----------------------
Kernel for a VM is stored in `/var/lib/qubes/vm-kernels/KERNEL_VERSION` directory (`KERNEL_VERSION` replaced with actual version). Qubes supports the following files there:
- `vmlinuz` - kernel binary (may not be a Linux kernel)
- `initramfs` - initramfs for the kernel to load
- `modules.img` - ext4 filesystem image containing Linux kernel modules (to be mounted at `/lib/modules`); additionally it should contain a copy of `vmlinuz` and `initramfs` in its root directory (for loading by qemu inside stubdomain)
- `default-kernelopts.txt` - default kernel options, in addition to those specified with `kernelopts` VM property
All the files besides `vmlinuz` are optional.
Using kernel installed in the VM (R4.0) Using kernel installed in the VM (R4.0)
-------------------------------- --------------------------------

10
troubleshooting/uefi-troubleshooting.md
View File

@ -225,3 +225,13 @@ If that's not an option there, or legacy mode does not work either, you can try
7. Continue with setting up default templates and logging in to Qubes. 7. Continue with setting up default templates and logging in to Qubes.
Whenever there is a kernel or Xen update for Qubes, you will need to follow these [other steps above](/doc/uefi-troubleshooting/#boot-device-not-recognized-after-installing) because your system is using the fallback UEFI bootloader in `[...]/EFI/BOOT` instead of directly booting to the Qubes entry under `[...]/EFI/qubes`. Whenever there is a kernel or Xen update for Qubes, you will need to follow these [other steps above](/doc/uefi-troubleshooting/#boot-device-not-recognized-after-installing) because your system is using the fallback UEFI bootloader in `[...]/EFI/BOOT` instead of directly booting to the Qubes entry under `[...]/EFI/qubes`.
Accessing installer Rescue mode on UEFI
---------------------------------------
In UEFI mode installer do not have boot menu, but starts directly the installation wizard. To get into Rescue mode, you need to switch to tty2 (Ctrl+Alt+F2) and then execute:
~~~
pkill -9 anaconda
anaconda --rescue
~~~