Xen ARM with Virtualization Extensions/Arndale

From Xen
Revision as of 13:20, 24 April 2013 by Julieng (talk | contribs) (Update version tag for xen repository)

The work for Xen on the Arndale Development board is on his way. So don't expect to have a usable dom0 yet.

Preparing the board

The bootloader provided with the Arndale does not let Xen boot in hypervisor mode, so we will use the u-boot provided by Linaro.

Follow the step on the Linaro wiki, to build and install u-boot.

Building Xen and Linux Dom0

First, we will build Linux for dom0 to have a device tree to provide to Xen.

You can get a tree from xenbits which is built on top of Linaro's tree [1].

Use this config file and add anything you need.

 git clone -b arndale git://xenbits.xen.org/people/julieng/linux-arm.git linux
 cd linux
 make xen_dom0_arndale_defconfig
 make zImage
 make dtbs

Use arch/arm/boot/exynos5250-arndale.dtb as a device tree provided to Xen at compile time.

To Build, get the source tree from the repo, which contain branches with patches to get serial and other device working on the board (last tag is arndale-130424).

 git clone --branch arndale git://xenbits.xen.org/people/julieng/xen-unstable.git

Then, Build Xen on ARM, with CONFIG_DTB_FILE=$linux_tree/arch/arm/boot/exynos5250-arndale.dtb passed to make.

For the moment, xen doesn't build uImage for U-Boot. You can create the image with:

 mkimage -A arm -T kernel -a 0x80200000 -e 0x80200000 -C none -d "$xen_src/xen/xen.bin" xen-uImage 

where $xen_src is the root directory of your xen git.

Building linux DomU

To build linux for Domu, get the source tree from the repo, which contains arndale-domU-3.9 branch (last tag is arndale-domU-3.9-130405).

 git clone -b arndale-domU-3.9 http://xenbits.xen.org/gitweb/?p=people/julieng/linux-arm.git linux-domU
 cd linux-domU
 make xen_domU_arndale_defconfig
 make zImage
 make dts

Booting Xen and Dom0

To boot Xen and Dom0, you can use:

  • PXE: it's easier for development but you need a computer which act as a server;
  • copy binary on the SD card: when you don't have network on your board.

Once you have chosen the boot method, you can start to follow steps in the next sections. When you have finished to configure your board, you can:

  • Save the U-Boot configuration with saveenv command. The next time you want to reboot your board, you won't have to reconfigure U-Boot.
  • Boot with boot command.

Booting via PXE

  • Setup the PXE Server
  • Copy xen-uImage and the zImage (rename in linux-zImage) in /tftpboot/
  • At U-Boot prompt, on your board, you need to set the following variable:
 setenv ipaddr 10.y.y.y
 setenv ipconfig 10.y.y.y
 setenv kernel_addr_r 0x60000000
 setenv serverip 10.x.x.x
 setenv tftp_path '10.x.x.x:'
 setenv usbethaddr 00:40:5c:26:0a:5b
 setenv ethaddr 00:40:5c:26:0a:5b
 setenv xen_addr_r 0x50000000
 setenv bootcmd_load_linux 'tftpboot $kernel_addr_r $tftp_path/linux-zImage'
 setenv boot_xen 'run bootcmd_load_linux; tftpboot $xen_addr_r $tftp_path/xen-uImage; bootm $xen_addr_r -'
 setenv bootcmd 'run boot_xen'

with 10.y.y.y the ip addr of the board and 10.x.x.x the ip of a tftp server (or PXE server).

Booting directly on the SD card

  • Copy xen-uImage and the zImage the root directory of you SD card.
  • At U-Boot prompt, on your board, you need to set the following variable:
 setenv kernel_addr_r 0x60000000
 setenv xen_addr_r 0x50000000
 setenv bootcmd_load_linux_mmc 'ext2load mmc 1:0 $kernel_addr_r /zImage'
 setenv boot_xen_mmc 'run bootcmd_load_linux_mmc; ext2load mmc 1:0 $xen_addr_r /xen-uImage; bootm $xen_addr_r -'
 setenv bootcmd 'run boot_xen_mmc'

We assume the SD card has only 1 partition with ext2 filesystem.

  • execute the boot command with the following command: