Update documentation

1 files changed, 15 insertions, 14 deletions

diff --git a/README.md b/README.md
index 3b550ee..305f1c8 100644
--- a/README.md
+++ b/README.md
@@ -12,33 +12,34 @@ This also means that as people come up with potentially new combinations of thin
 
 The section that follows is about a VM configured more for work and can be thought of as a template or starting point to define your own host, mostly with the same packages potentially, and with whatever personal touches you want for your own standard user account.
 
-## richese
+## kaitain/richese
 
-This host is currently assumed to be a VirtualBox VM.  The VirtualBox VM should be configured with the following:
+Both of these hosts are Virtalbox VM's.  Currently, kaitain is configured as a more modern EFI based system while richese is still configured as an older BIOS based system.  This means that richese needs an extra BIOS boot partition defined in its disko configuration and uses GRUB instead of systemd-boot.
 
-* CPU
+Beyond that, you'll probably want to enable bidirectional clipboard support under General -> Advanced.
 
-As many physical (non-SMT) cores as your CPU has ideally, since NixOS does need to build things occasionally.
+Both systems are configured with 12288 MB of RAM currently so they can be run concurrently on a 32GB laptop.
 
-* RAM
+kaitain is using the newer ICH9 chpiset whereas richese is configured using the older PIIX3 chipset.  I/O APIC is enabled on both as well as hardware clock being in UTC.
 
-8GB is probably a good starting point.  If the installer hangs, you probably need to increase this from the presumably lower value you have set.
+Both use 8 CPU cores with PAE/NX enabled along with nested paging.
 
-* Display
+Both use VMSVGA with 3D acceleration enabled and the default 16MB of video memory.
 
-The NixOS configuration assumes VMSVGA.
+Both use a virtio-scsi storage controller with host I/O cache enabled.
 
-* Storage
+Both use Intel HD audio.
 
-The installer assumes you've selected the AHCI SATA controller using a dynamically allocated VDI of 100GB.  This might need to be bigger, given how disk intensive NixOS can be.
+Both use the virtio-net adapter.  richese is currently configured to use NAT for networking and kaitain uses a bridged adapter using the wireless adapter.  This is necessary to bypass the security theater, but might not always work depending on the exact hardware in the laptop.
 
-* Network
+Both use an automounted shared folder pointing at my host user's Downloads directory with full read/write access.
 
-The NIC was configured in VirtualBox to use NAT and virtio-net.
+Most importantly, depending on the host configuration, you might end up with the green frog icon in the status bar in the bottom right when starting your Virtualbox VM, instead of the preferred blue V which indicates CPU virtualization support is working as intended.  If this is due to the broken ass host OS being Windows and forcing Hyper-V to be enabled, there are a number of features which might need to be turned off in Windows to keep Hyper-V at bay.  Notably, these two links should provide some more information on how to disable everything:
 
-* Other
+https://forums.virtualbox.org/viewtopic.php?f=25&t=99390
+https://learn.microsoft.com/en-us/troubleshoot/windows-client/application-management/virtualization-apps-not-work-with-hyper-v
 
-This configuration works best if you also enable the bidirectional shared clipboard functionality under General -> Advanced.
+I also had to disable full memory encryption in the BIOS.  Other steps might also be necessary, depending on how broken Windows has become when you're reading this.
 
 ### Installation