5. Part D - Hypervisor Host Configuration
Hint
This guide focuses on the RTOS-32 example guest. Initially, the Hypervisor Host does not provide any example guest folders. To switch to the RTOS-32 guest example, you need to perform the appropriate initialization. For instructions on initializing the examples, please see the RTOS Guests chapter in the Hypervisor Manual.
hv_open_example rtos32
hv_sync_example rtos32
cd /hv/guests/guestrtos32
Adjust the guest configuration setting to prepare starting the RTOS-32 Debug Monitor:
cd /hv/guests/guestrtos32
mousepad usr_guest_config.sh
and add the following line:
export osImage=$HV_ROOT/guests/guestrtos32/Monvmf.bin
Start the RTOS-32 Debug Monitor:
cd /hv/guests/guestrtos32
hv_guest_start -view
The output of the RTOS-32 Debug Monitor should be similar to:
RTTarget-32 Debug Monitor 6.29 Evaluation Version
Copyright (c) 1996,2022 On Time Informatik GmbH
Monitor Header at: 04037A3C, Current CPL: 0
Ethernet: RTOS32Win VNet, MAC: AA-BB-CC-DD-EE-03, IP: 172.17.10.5
Open a new terminal window (right click on desktop and select ‘Open Terminal here’ or press CRTL + ALT + T)
Configure a bridge which connects the external network (where the Development PC is located) with the virtual network (where RTOS-32 is connected to).
See section Bridge virtual and physical network in the Hypervisor manual for details.
Create bridged network connection:
sudo hv_brvnetset
Output of successful bridge creation:
rtv@rtv-TEST:/hv/guests/guestrtos32$ sudo hv_brvnetset
[sudo] password for rtv:
load vnet bridge configuration
add enp2s0 and vnet0 to bridge vnetbr
bridge name bridge id STP enabled interfaces
vnetbr 8000.0060c8000000 no enp2s0
vnet0
ifconfig vnetbr 172.17.10.53 netmask 255.255.0.0
ip route add default via 172.17.5.2
RTNETLINK answers: No such process
Important
Remove the bridged network connection after debugging!
sudo hv_brvnetclr
Hint
See chapter “Bridge virtual and physical network” in the Hypervisor Manual for details how to configure the bridge.