Xen ARM with Virtualization Extensions/OdroidXU: Difference between revisions
| Line 9: | Line 9: | ||
This will let XEN boot in hypervisor mode as well as set CNTFRQ through the trustzone. This is required for domUs to get the correct timer frequency. (dom0's optionally can pick it up from the device tree) |
This will let XEN boot in hypervisor mode as well as set CNTFRQ through the trustzone. This is required for domUs to get the correct timer frequency. (dom0's optionally can pick it up from the device tree) |
||
== Building XEN == |
|||
Follow [[Xen_ARMv7_with_Virtualization_Extensions#Building_Xen_on_ARM|Build Xen on ARM]] to build XEN. |
|||
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" xen-uImage |
|||
where ''$xen_src'' is the root directory of your xen git. |
|||
== Resources == |
== Resources == |
||
Revision as of 18:57, 6 January 2015
|
To Do:
Add page |
Preparing the board
The bootloader provided with the OdroidXU does not let Xen boot in hypervisor mode. In the Odroid forums for the XU, one is likely to see many U-Boot blobs (bl1/bl2/tzsw/u-boot) which could possibly be used to let Xen boot in hypervisor mode. To avoid multiple sources, currently a single source is provided which can be accessed from [1]
The sd_fusing.sh script found therein can be used to fuse the SD card or eMMC card with the required BL1/BL2/TZSW and U-Boot. Example: ./sd_fusing.sh /dev/mmcblk0
This will let XEN boot in hypervisor mode as well as set CNTFRQ through the trustzone. This is required for domUs to get the correct timer frequency. (dom0's optionally can pick it up from the device tree)
Building XEN
Follow Build Xen on ARM to build XEN. 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" xen-uImage
where $xen_src is the root directory of your xen git.
