XenevaOS

Setting up Virtual Machine for Xeneva

Notice

Xeneva is well tested only on VMware Workstation and Virtual Box with vmdk file that maps PhysicalDisk (The USB Flash drive containing all required binaries). Refer to Setting up USB Flash Drive for more information. Every thing should be set up as mentioned in this document. You can skip to Virtual Machine Creation if you have downloaded the release vhd file.

Creating the .vmdk file

In Virtual Box’s VMs we will use .vmdk file in AHCI Controllers Port 1. To Create vmdk we will use Virtual Box VBoxManage.exe tool present in location C:\Program Files\Oracle\VirtualBox. You can add this location to Windows Environment Variable PATH for accessing the tool from any location inside your local Machine.

Disabling VBS(Virtualization Based Security) on Windows (~Important)

Before running XenevaOS on Windows Machine, we need to temporarily disable VBS feature of Windows. Xeneva fails to access virtualized hardware memory regions on VBS enabled Windows machine for which the OS cannot continue the boot process. VBS completely occupies all hardware resource to create an isolated region of memory. To turn off VBS, please follow the steps

- Turn off Memory integrity :

- Turn off hypervisorlaunchtype

Creating the Virtual Machine in Virtual Box

Using Xeneva Terminal (only for v1.0)

When the OS boots up it automatically starts the Window Manager and launches Xeneva Terminal application. Desktop should be started manually. Follow the steps to start the desktop

Starting play application to play audio

XenevaOS has builtin play application which can play audio files of 48kHZ - 16bit format .wav files

Conclusion

Currently components of Xeneva should be started separately, automatic starting of components is not supported.You can attach a serial terminal to print Xeneva’s internal messages which helps debugging the system on various crashes. See How to setup a serial Terminal for Xeneva for more information