I have a leap 42.1 vm in virtual box on a windows 10 host (I know, I know but no choice) on a laptop amd fx8800p with 16GB ram and 2TB HD. The VM has a dynamically allocated 750GB .vdi, with 8GB ram and 2 cpu’s. This applies to both virtualbox 5.1 and 5.0.24. The system is up and running with secure boot enabled in grub2 and the vm is set up for efi and VT-X/AMD-V/Nested Paging/KVM - virtualization is enabled in the laptop UEFI bios. So when I enabvle encryption in VirtualBox and the .vdi is encrypted Leap 42.1 only boots into emergency mode. Grub2 appears then the green splash screen then no leap. This happens when secure boot is eabled in grub or not. Any ideas or suggestions on how to use VirtualBox encryption with Leap? Thanks,
I’m pretty sure VBox disk image encryption (I assume this is what you are talking about) is completely separate from any software issues within the VM, although a close read of the VBox documentation emphasizes that passwords are set and need to be decrypted on a disk by disk basis (How many disk images is your VM using, and how are you decrypting?)
The relevant VBox documentation is 9.31, with special attention to the sections on starting up a VM and possibly decrypting.
Well when I start the leap vm it asks for the decryption password which I supply, then grub2 starts normally, after grub the green splash screen starts, after that I get the leap emergency rescue kernel and a command prompt – no desktop. This only happens with disk encryption enabled in VirtualBox. The password is correct or grub2 would not start. Section 9.31 of vb docs sheds no light. This cannot be a virtualbox issue alone. It has to be the way Leap interacts with Virtualbox. It happens with vb ver 5.024 and 5.1. There is a single virtual hard disk, a dynamically allocated 500GB .vdi which was partitioned by the leap installer. efi boot is enabled for the vm in VirtualBox. Something is going on with Leap here.
I am unable to replicate your problem,
You might try building another vm to see if your problem is something unique to your current vm.
Have built 2 new LEAP vms, one with disk encryption configured prior to the LEAP install, and the other encrypting the disks after the install.
Both do <not> have KVM interface configured, I revisited this within the past month, and the current status is that it doesn’t work. I did get it to work earlier, but only because I had “KVM on Windows” installed which is an old, no longer maintained but apparently still working technology… Without KVM installed on the HostOS, the VBox KVM interface does not work, and it’s documented and discussed recently in the VBox forums(The KVM interface is not supposed to work this way, it’s supposed to provide direct access to hardware CPU extensions).
Since I don’t have a non-VBox interface configured, “nested paging” is not a working option.
Although you can’t ever say 100%, I highly doubt that the above should have anything to do with your problem, but in any case I recommend you modify your vm settings accordingly.