diff --git a/source/linux/Foundational_Components/Hypervisor/Jailhouse.rst b/source/linux/Foundational_Components/Hypervisor/Jailhouse.rst index 60ca9bfc2..5758516d1 100644 --- a/source/linux/Foundational_Components/Hypervisor/Jailhouse.rst +++ b/source/linux/Foundational_Components/Hypervisor/Jailhouse.rst @@ -50,9 +50,9 @@ cell configuration file. The open source Jailhouse project from https://github.com/siemens/jailhouse is integrated in Yocto build environment. -- Yocto recipe (Scarthgap) for Jailhouse can be found here: `meta-ti `__. +- Yocto recipe (master) for Jailhouse can be found here: `meta-ti `__. -- Jailhouse kernel patches are integrated with TI Linux Kernel (v6.12) and hosted here `Linux git.ti `__. This repository includes Jailhouse module, +- Jailhouse kernel patches are integrated with TI Linux Kernel (v6.18) and hosted here `Linux git.ti `__. This repository includes Jailhouse module, uio_ivshmem module for shared-memory and device tree changes for Jailhouse. - U-Boot port for Jailhouse can be found here `U-Boot git.ti `__. This repository contains the fix for error @@ -264,7 +264,7 @@ on the EVM then power on the board, the following logs can be observed on the te am62lxx-evm login: -.. note:: +.. note:: Jailhouse module is not autoloaded during boot-up. To load the jailhouse module after boot, run following commands: @@ -927,7 +927,7 @@ Run ivshmem-demo on both root and inmate cell ^C You can see interrupts will be received in both inmate and root cell. Also, check -the values using +the values using .. code-block:: console @@ -981,32 +981,40 @@ Running Ethernet Demo ===================== This application demonstrates how to use IVSHMEM Ethernet to communicate with another -linux inmate cell in the Jailhouse hypervisor. Configure the eth1 in root cell and eth0 in +linux inmate cell in the Jailhouse hypervisor. Configure the eth2 in root cell and eth0 in inmate cell and ping. - In inmate cell .. code-block:: console - root@: ifconfig enp0s1 192.168.0.2 + root@: ip addr add 192.168.0.3 dev eth0 + root@: ip link set eth0 up - In root cell .. code-block:: console - root@: ifconfig enP1p0s1 192.168.0.3 + root@: ip addr add 192.168.0.2 dev eth2 + root@: ip link set eth2 up -Ping enp0s1 using enP1p0s1 #ping 192.168.0.2 in root cell or ping enP1p0s1 using enp0s1 +Ping eth0 using eth2 #ping 192.168.0.2 in root cell or ping eth2 using eth0 ping 192.168.0.3 in inmate cell. Ex. ping to inmate cell from root cell .. code-block:: console - root@: ping 192.168.0.2 - PING 192.168.0.2 (192.168.0.2): 56 data bytes - 64 bytes from 192.168.0.2: seq=0 ttl=64 time=0.707 ms - 64 bytes from 192.168.0.2: seq=1 ttl=64 time=0.373 ms + root@:~# ping -c 4 192.168.0.3 + PING 192.168.0.3 (192.168.0.3) 56(84) bytes of data. + 64 bytes from 192.168.0.3: icmp_seq=1 ttl=64 time=0.780 ms + 64 bytes from 192.168.0.3: icmp_seq=2 ttl=64 time=0.413 ms + 64 bytes from 192.168.0.3: icmp_seq=3 ttl=64 time=0.407 ms + 64 bytes from 192.168.0.3: icmp_seq=4 ttl=64 time=0.415 ms + + --- 192.168.0.3 ping statistics --- + 4 packets transmitted, 4 received, 0% packet loss, time 3057ms + rtt min/avg/max/mdev = 0.407/0.503/0.780/0.159 ms Running Baremetal Demos =======================