Xen ARM with Virtualization Extensions/Salvator-X

From Xen

General information

This wiki describes how to run XEN on Renesas Salvator-X board with R-Car H3 SoC.

Due to the fact that Renesas provide their reference software in form of Yocto build instruction, it is provided additional steps in order to add XEN to the system being built. Those steps add meta-virtualization layer and a glue layer to the Yocto build.

XEN hypervisor is taken from a master branch of xen.git.

This wiki relies on Renesas Yocto version 2.19.0.

Known limitations

Due to different XEN specifics there is a list of system deviations from Renesas'es reference software:

  • ATF exits to bootloader in EL2 mode
  • TEE client is not functional
  • reserved memory is not supported
  • adsp, mmngr, mmngrbuf are dropped because they rely on reserved memory

Because of the fact that Renesas BSP u-boot uses cli-simple, adequate manual updating of fdt is not possible. So within the glue layer it is provided a device tree with changes required for XEN.

Please consider changes to dts and appropriate dtb load in case you want system configuration changes (i.e. nfs server ip, dom0 root option, xen command line, etc.)

System build

  • Follow the instruction to the system build step 10, including it.
  • Add meta-virtualization layer with its dependencies:
   git clone git://git.yoctoproject.org/meta-virtualization -b morty ../meta-virtualization
   bitbake-layers add-layer ../meta-virtualization
   git clone git://git.yoctoproject.org/meta-selinux -b jethro ../meta-selinux
   bitbake-layers add-layer ../meta-selinux
   bitbake-layers add-layer ../meta-openembedded/meta-networking
   bitbake-layers add-layer ../meta-openembedded/meta-python
  • Add the glue layer
   git clone https://github.com/xen-troops/meta-demo -b master ../meta-demo
   bitbake-layers add-layer ../meta-demo/meta-rcar-gen3-xen

BL2 & U-boot update procedure

It is crucial to update ATF on the board in order to get XEN start in EL2.

Please follow your board manual to find out ATF update procedure.

Running the system

Setup tftp and nfs as described in instruction.

Please consider that default expected nfs server setup is nfsroot=192.168.1.100:/srv/dom0.

For the system boot issue from u-boot cli:

   setenv bootargs #empties the bootargs added by u-boot
   tftp 0x48000000 Image-r8a7795-salvator-x-xen.dtb
   tftp 0x48080000 xen-salvator-x.uImage
   tftp 0x7a000000 Image
   bootm 0x48080000 - 0x48000000