2. Installation and basic configuration¶
The hypervisor has to be installed onto an empty installation media. It is directly booted from the BIOS. Side-by-side installation with an existing Windows or Linux is not recommended, but possible. If an existing Windows or Linux system shall be used, assure a free partition for booting the hypervisor is required. The minimum required size for the installation media is 10 GByte.
2.1. USB stick boot medium creation¶
We simply recommend the Rufus tool to create the boot medium stick.
2.2. Installation¶
Currently, a light-weight Ubuntu derivate (Xubuntu) is used for hypervisor installation. Select Install Xubuntu
to install the Hypervisor, other options are not supported.
A user account must be created while installing the hypervisor.
Note
A password MUST be defined!
After the installation has finished, you have to reboot the system;
Follow the installation instructions.
After reboot the default entry Ubuntu
is selected, keep this and do not boot the Hypervisor
entry. This entry will be activated automatically after the first-time configuration.
2.3. For your convenience¶
It’s recommended to access the hypervisor system through xrdp
, if a Windows development PC is used. It’s easier to copy-paste the successive shell commands through (x)RDP.
The following steps must be done in case of xrdp
:
Open shell (right click on desktop and select ‘Open Terminal here’ or press CRTL + ALT + T)
sudo apt-get update
sudo apt-get upgrade
sudo apt-get install xrdp
sudo adduser xrdp ssl-cert
sudo systemctl restart xrdp
sudo ufw allow 3389
sudo apt-get install xorgxrdp-hwe-18.04
2.4. Basic system configuration¶
Open shell (right click on desktop and select ‘Open Terminal here’ or press CRTL + ALT + T)
Change to configuration directory:
cd /hv/config
Next step we need the memory assignment (rtos-depend!) through the autoconf
script:
RTOS-32:
sudo ./autoconf.sh 64 8
LxWin:
sudo ./autoconf.sh 368 8
The first parameter of the autoconf.sh
describes the amount of assigned memory of the Rtos and the second one the shared memory pool size in MB
.
Caution
If you get the message WARNING: CPU frequency not stable…
through the execution of the autoconf.sh
script, you did not properly disable power settings in the BIOS.
Please follow the respective instructions above (Prerequisites).
A second run of the autoconf script may help in that case after! a reboot.
To get the changes effective, a reboot is required:
sudo reboot
2.5. Verification¶
Last step: validate, if our basic settings could run our realtimedemo
:
RTOS-32:
cd /hv/rtos-32
sudo ./realtimedemo.sh
LxWin:
cd /hv/lx
sudo ./lx.sh
./dbgcon.sh
vmf login: root
password: root
./RealtimeDemo
Stop output and return to console: CTRL + C
Stop RTOS:
RTOS-32:
sudo /hv/rtos-32/stopall.sh
LxWin:
sudo /hv/lx/stopall.sh
Caution
Always call stop before start again!