[Android Software Development] richaardvark:
Same problem for me :(

This didn't work for me unfortunately :( I'd really love to run 14 over 11 if possible since the former has so many improvements and bug fixes/is newer. But perhaps it's just not possible at the moment... :-/

Edit 1: Also - I don't know if this is maybe related to the above problem but I had trouble installing Bliss from the ISO to the virtual hard disk ("/dev/sda1") created in my VM. I normally just use the "Advanced Options --> Auto-Installation - Auto Install to specified harddisk" setting from the GRUB menu and normally have no issues but with this .ISO file (I'm using "BlissOS-14.3-x86_64-202106181339_k-google-5.4.112-lts-ax86_m-r_emugapps_cros-hd_gearlock.iso") when I try the Auto-Installation option it fails and says "Cannot mount /dev/sda1 - Do you want to format it?" but the formatting fails. I was able to get around this by instead using the normal installation menu option. There are also errors at first as well when using the regular installation option when creating the partitions on my virtual drive but I was able to create the correct partition structure by first creating the wrong partition type (ext2) and then the system asked me if I wanted to update the partition to ext3 and automatically reformatted it to ext3 and then successfully installed Bliss 14.3 and GRUB onto the newly created partition. However, upon first boot the gearlock startup script/feature runs and increases the size of the system image but then I also briefly see the "Failed to extend system.img, you system.img is broken now..." message for just a split second and then there is just a black screen with a blinking underscore (typical "not going to boot" Linux screen, lol). I tried running various debug and nomodeset options, also edited the boot command and added "NOSC=0" but it still won't boot.

I tried this a number of times on various VM platforms / with different virtual disk image formats (all 30GB):

using QEMU and a "raw" .img disk type

using QEMU and a "qcow2" disk type

using VMWare Workstation Player and a vmdk disk type

using Oracle VirtualBox and a vdi disk type

Strangely enough I experienced the exact same issues with every one of these different VM platforms and disk types. I also tried both BIOS and UEFI partition formats and installations but same problem every time. I think this ISO release just isn't yet capable of being installed in a VM :-/

Here is the final error screen from my last attempt (using VirtualBox/.vdi disk image type/UEFI boot):

Also, just before this screen appeared I also saw the "rusty-magisk: root(/) is not writable, failed to initialize" error described by @Nequite in post #866 above.

But I guess that's why this is a beta/developer build - it just isn't quite ready yet it seems... 😬

Edit 2: I tried again, but this time used the "BlissOS-14.3-x86_64-202106261907_k-android12-5.10.46-ax86_m-21.1.3_r-x86_emugapps_cros-hd" file instead of the gearlock version. Same exact errors! Was able to capture a better screenshot of the "rusty-magisk" error - it definitely seems like something is wrong with the way file permissions are being setup/the installation disk is being mounted:

Edit 3: I Googled around a bit to see if anyone else had ever dealt with this specific problem and the only real result I found was on some other tech forum and ironically is also from people trying to install an older release of Bliss OS in a virtual machine, back in 2019. See the last half of all comments at the bottom of this installation how-to guide/article... it seems a good number of other users have historically been frustrated and have experienced this same exact drive/partition file permission issue. Really seems like this is an issue that needs to be taken seriously, investigated, and resolved by the Bliss OS developer team. I hope @electrikjesus sees this response and information I have shared here. Please let me know if there is anything I can do to help with finding a solution.