1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
|
# ImageBuilder
Building an embedded virtualized system with anything more than one
Domain can be difficult, error prone and time consuming.
ImageBuilder, an Open Source collection of scripts (contributions
encouraged), changes all that.
ImageBuilder generates a U-Boot script that can be used to load all of
the binaries automatically and boot the full system fast. Given a
collection of binaries such as Xen, Dom0 and a number of Dom0-less
DomUs, ImageBuilder takes care of calculating all loading addresses,
editing device tree with the necessary information, and even
pre-configuring a disk image with kernels and rootfses.
ImageBuilder has been tested on Xilinx ZynqMP MPSoC boards. An
up-to-date wikipage is also available at
[wiki.xenproject.org](https://wiki.xenproject.org/index.php?title=ImageBuilder).
## scripts/uboot-script-gen
The ImageBuilder script that generates a u-boot script to load all your
binaries for a Xen Dom0-less setup is `scripts/uboot-script-gen`.
To use it, first write a config file like `config`:
```
MEMORY_START="0x0"
MEMORY_END="0x80000000"
DEVICE_TREE="mpsoc.dtb"
XEN="xen"
DOM0_KERNEL="Image-dom0"
DOM0_RAMDISK="dom0-ramdisk.cpio"
NUM_DOMUS=2
DOMU_KERNEL[0]="zynqmp-dom1/Image-domU"
DOMU_RAMDISK[0]="zynqmp-dom1/domU-ramdisk.cpio"
DOMU_PASSTHROUGH_DTB[0]="zynqmp-dom1/passthrough-example-part.dtb"
DOMU_KERNEL[1]="zynqmp-dom2/Image-domU"
DOMU_RAMDISK[1]="zynqmp-dom2/domU-ramdisk.cpio"
UBOOT_SOURCE="boot.source"
UBOOT_SCRIPT="boot.scr"
```
Where:
- MEMORY_START and MEMORY_END specify the start and end of RAM.
- DEVICE_TREE specifies the DTB file to load.
- XEN specifies the Xen hypervisor binary to load. Note that it has to
be a regular Xen binary, not a u-boot binary.
- DOM0_KERNEL specifies the Dom0 kernel file to load.
- DOM0_RAMDISK specifies the Dom0 ramdisk to use. Note that it should be
a regular ramdisk cpio.gz file, not a u-boot binary.
- NUM_DOMUS specifies how many Dom0-less DomUs to load
- DOMU_KERNEL[number] specifies the DomU kernel to use.
- DOMU_RAMDISK[number] specifies the DomU ramdisk to use.
- DOMU_PASSTHROUGH_DTB[number] specifies the device assignment
configuration, see xen.git:docs/misc/arm/passthrough.txt
- UBOOT_SOURCE and UBOOT_SCRIPT specify the output. They are optional
as you can pass -o FILENAME to uboot-script-gen as a command line
parameter
Then you can invoke uboot-script-gen as follows:
```
$ bash ./scripts/uboot-script-gen -c /path/to/config-file -d . -t tftp -o bootscript
```
Where:\
-c specifies the path to the config file to use\
-d specifies the "root" directory (paths in the config file are relative
to it), this is not a working directory (any output file locations
are specified in the config and any temporary files are in /tmp)\
-t specifies the u-boot command to load the binaries. "tftp" and "sd"
are shorthands for "tftpb" and "load scsi 0:1", but actually any
arbitrary command can be used, for instance -t "fatload" is valid.\
-o specifies the output filename for the uboot script and its source.\
## scripts/disk\_image
The ImageBuilder script that generates a disk image file to load on a
SD or SATA drive. This creates 2 partitions: boot partition where the
boot files from working directory (-c option) are, and the dom0 ramdisk
uncompressed into the root FS partition.
After you've generated the u-boot scripts using the uboot-script-gen
script, disk_image is run as follows:
```
$ sudo bash ./scripts/disk_image -c /path/to/config-file -d . \
-w /path/to/tmp/dir \
-o /path/to/output/disk.img
```
Where:\
-c specifies the path to the config file to use\
-d specifies the working directory (paths in the config file are relative
to it)\
-w specifies the temporary working directory that the script uses for
building the disk image, and if not set, one is created in /tmp\
-o specifies the output disk image file name\
|
