I've been experimenting with both encrypted /boot partitions and booting from a hidden encrypted volume inside an outer encrypted volume, and have been successful with Debian based systems. I'd like to get it working with Qubes, but I've run into some issues.
The implementation requires decrypting the volumes from grub, then a manual boot of the kernal and initram, then some pre-boot scripts added to the initramfs are needed to properly decrypt and mount the volumes and then re-scan and activate LVM volume groups during the handover between grub, initram and the final boot. However, the Qubes Mananger is non-functional after boot. I notice when booting from a normal install, Grub briefly displays something like: Loading Xen-4.6.1 Loading vmlinuz-4*** Loading intramfs-4*** In what way does the Xen image get loaded? I think this is what's missing from my boot sequence. If I'm going through the boot sequence manually, or loading the components from a bash script in initram, what needs to be done with the /boot/xen-4.6.1 file? Any help would be greatly appreciated. -- You received this message because you are subscribed to the Google Groups "qubes-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-devel+unsubscr...@googlegroups.com. To post to this group, send email to qubes-devel@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-devel/87b8837f3bb3c425492634f4b1490f7b.webmail%40localhost. For more options, visit https://groups.google.com/d/optout.
