3 novaboot - A tool for booting various operating systems on various hardware or in qemu
9 __novaboot__ \[option\]... \[--\] script...
11 __./script__ \[option\]...
15 This program makes booting of an operating system (e.g. NOVA or Linux)
16 as simple as running a local program. It facilitates booting on local
17 or remote hosts or in emulators such as qemu. Novaboot operation is
18 controlled by command line options and by a so called novaboot script,
19 which can be thought as a generalization of bootloader configuration
20 files. Based on this input, novaboot setups everything for the target
21 host to boot the desired configuration, i.e. it generates the
22 bootloader configuration file in the proper format, deploy the
23 binaries and other needed files to required locations, perhaps on a
24 remote boot server and reset the target host. Finally, target host's
25 serial output is redirected to standard output if that is possible.
27 Typical way of using novaboot is to make the novaboot script
28 executable and set its first line to _\#!/usr/bin/env novaboot_. Then,
29 booting a particular OS configuration becomes the same as executing a
30 local program - the novaboot script.
32 For example, with `novaboot` you can:
34 1. Run an OS in Qemu. This is the default action when no other action is
35 specified by command line switches. Thus running `novaboot ./script`
36 (or `./script` as described above) will run Qemu and make it boot the
37 configuration specified in the `script`.
38 2. Create a bootloader configuration file (currently supported
39 bootloaders are GRUB, GRUB2, Pulsar and U-Boot) and copy it with all
40 other files needed for booting to a remote boot server.
42 ./script --server=192.168.1.1:/tftp --iprelay=192.168.1.2
44 This command copies files to the TFTP server and uses
45 TCP/IP-controlled relay to reset the target host and receive its
48 3. Run DHCP and TFTP server on developer's machine to PXE-boot the target
53 When a PXE-bootable machine is connected via Ethernet to developer's
54 machine, it will boot the configuration described in _script_.
56 4. Create bootable ISO images. E.g.
58 novaboot --iso -- script1 script2
60 The created ISO image will have GRUB bootloader installed on it and
61 the boot menu will allow selecting between _script1_ and _script2_
64 Note that the options needed for a specific target can be stored in a
65 ["CONFIGURATION FILE"](#configuration-file). Then it is sufficient to use only the __\-t__
66 option to specify the name of the target.
70 Novaboot performs its work in several phases. Each phase can be
71 influenced by several options, certain phases can be skipped. The list
72 of phases (in the execution order) and the corresponding options
75 ## Configuration reading phase
77 After starting, novaboot reads configuration files. By default, it
78 searches for files named `.novaboot` starting from the directory of
79 the novaboot script (or working directory, see bellow) and continuing
80 upwards up to the root directory. The configuration files are read in
81 order from the root directory downwards with latter files overriding
82 settings from the former ones.
84 In certain cases, the location of the novaboot script cannot be
85 determined in this early phase. This happens either when the script is
86 read from the standard input or when novaboot is invoked explicitly
87 and options precede the script name, as in the example ["4."](#4) above.
88 In this case the current working directory is used as a starting point
89 for configuration file search.
91 - \-c, --config=_filename_
93 Use the specified configuration file instead of the default one(s).
95 ## Command line processing phase
99 Dump the current configuration to stdout end exits. Useful as an
100 initial template for a configuration file.
104 Print short (__\-h__) or long (__\--help__) help.
106 - \-t, --target=_target_
108 This option serves as a user configurable shortcut for other novaboot
109 options. The effect of this option is the same as the options stored
110 in the `%targets` configuration variable under key _target_. See
111 also ["CONFIGURATION FILE"](#configuration-file).
113 ## Script preprocessing phase
115 This phases allows to modify the parsed novaboot script before it is
116 used in the later phases.
118 - \-a, --append=_parameters_
120 Append a string to the first `load` line in the novaboot script. This
121 can be used to append parameters to the kernel's or root task's
122 command line. Can appear multiple times.
126 Use `bender` chainloader. Bender scans the PCI bus for PCI serial
127 ports and stores the information about them in the BIOS data area for
130 - \--chainloader=_chainloader_
132 Chainloader that is loaded before the kernel and other files specified
133 in the novaboot script. E.g. 'bin/boot/bender promisc'.
137 Print the modules to boot and their parameters after this phase
138 finishes. Then exit. This is useful for seeing the effect of other
139 options in this section.
141 - \-k, --kernel=`file`
143 Replace the first word on the first `load` line in the novaboot
146 - \--scriptmod=_perl expression_
148 When novaboot script is read, _perl expression_ is executed for every
149 line (in $\_ variable). For example, `novaboot
150 --scriptmod=s/sigma0/omega6/g` replaces every occurrence of _sigma0_
151 in the script with _omega6_.
153 When this option is present, it overrides _$script\_modifier_ variable
154 from the configuration file, which has the same effect. If this option
155 is given multiple times all expressions are evaluated in the command
158 ## File generation phase
160 In this phase, files needed for booting are generated in a so called
161 _build directory_ (see ["--build-dir"](#build-dir)). In most cases configuration
162 for a bootloader is generated automatically by novaboot. It is also
163 possible to generate other files using _heredoc_ or _"<"_ syntax in
164 novaboot scripts. Finally, binaries can be generated in this phases by
165 running `scons` or `make`.
167 - \--build-dir=_directory_
169 Overrides the default build directory location.
171 The default build directory location is determined as follows: If the
172 configuration file defines the `$builddir` variable, its value is
173 used. Otherwise, it is the directory that contains the first processed
176 See also ["BUILDDIR"](#builddir) variable.
178 - \-g, --grub\[=_filename_\]
180 Generates grub bootloader menu file. If the _filename_ is not
181 specified, `menu.lst` is used. The _filename_ is relative to the
182 build directory (see __\--build-dir__).
184 - \--grub-preamble=_prefix_
186 Specifies the _preable_ that is at the beginning of the generated
187 GRUB or GRUB2 config files. This is useful for specifying GRUB's
190 - \--grub-prefix=_prefix_
192 Specifies _prefix_ that is put in front of every file name in GRUB's
193 `menu.lst`. The default value is the absolute path to the build directory.
195 If the _prefix_ contains string $NAME, it will be replaced with the
196 name of the novaboot script (see also __\--name__).
198 - \--grub2\[=_filename_\]
200 Generate GRUB2 menuentry in _filename_. If _filename_ is not
201 specified `grub.cfg` is used. The content of the menuentry can be
202 customized with __\--grub-preable__, __\--grub2-prolog__ or
203 __\--grub\_prefix__ options.
205 In order to use the the generated menuentry on your development
206 machine that uses GRUB2, append the following snippet to
207 `/etc/grub.d/40_custom` file and regenerate your grub configuration,
208 i.e. run update-grub on Debian/Ubuntu.
210 if [ -f /path/to/nul/build/grub.cfg ]; then
211 source /path/to/nul/build/grub.cfg
214 - \--grub2-prolog=_prolog_
216 Specifies text _preable_ that is put at the beginning of the entry
219 - \-m, --make\[=make command\]
221 Runs `make` to build files that are not generated by novaboot itself.
225 Use the name _string_ instead of the name of the novaboot script.
226 This name is used for things like a title of grub menu or for the
227 server directory where the boot files are copied to.
231 Do not generate files on the fly (i.e. "<" syntax) except for the
232 files generated via "<<WORD" syntax.
234 - \-p, --pulsar\[=mac\]
236 Generates pulsar bootloader configuration file named `config-_mac_`
237 The _mac_ string is typically a MAC address and defaults to
240 - \--scons\[=scons command\]
242 Runs `scons` to build files that are not generated by novaboot
247 Strip _rom://_ prefix from command lines and generated config files.
248 The _rom://_ prefix is used by NUL. For NRE, it has to be stripped.
252 Exit novaboot after file generation phase.
254 ## Target connection check
256 If supported by the target, the connection to it is made and it is
257 checked whether the target is not occupied by another novaboot
260 - \--iprelay=_addr\[:port\]_
262 Use TCP/IP relay and serial port to access the target's serial port
263 and powercycle it. The IP address of the relay is given by _addr_
264 parameter. If _port_ is not specified, it default to 23.
266 Note: This option is supposed to work with HWG-ER02a IP relays.
268 - \-s, --serial\[=device\]
270 Target's serial line is connected to host's serial line (device). The
271 default value for device is `/dev/ttyUSB0`.
273 The value of this option is exported in NB\_NOVABOOT environment
274 variable to all subprocesses run by `novaboot`.
278 Specifies settings passed to `stty` invoked on the serial line
279 specified with __\--serial__ option. If this option is not given,
280 `stty` is called with `raw -crtscts -onlcr 115200` settings.
282 - \--remote-cmd=_cmd_
284 Command that mediates connection to the target's serial line. For
285 example `ssh server 'cu -l /dev/ttyS0'`.
287 - \--remote-expect=_string_
289 Wait for reception of _string_ after establishing the the remote
290 connection before continuing.
292 ## File deployment phase
294 In some setups, it is necessary to copy the files needed for booting
295 to a particular location, e.g. to a TFTP boot server or to the
300 Turns your workstation into a DHCP and TFTP server so that the OS can
301 be booted via PXE BIOS (or similar mechanism) on the test machine
302 directly connected by a plain Ethernet cable to your workstation.
304 The DHCP and TFTP servers require root privileges and `novaboot`
305 uses `sudo` command to obtain those. You can put the following to
306 _/etc/sudoers_ to allow running the necessary commands without
309 Cmnd_Alias NOVABOOT = /bin/ip a add 10.23.23.1/24 dev eth0, /bin/ip l set dev eth0 up, /usr/sbin/dhcpd -d -cf dhcpd.conf -lf dhcpd.leases -pf dhcpd.pid, /usr/sbin/in.tftpd --foreground --secure -v -v -v --pidfile tftpd.pid *, /usr/bin/touch dhcpd.leases, /usr/bin/pkill --pidfile=dhcpd.pid, /usr/bin/pkill --pidfile=tftpd.pid
310 your_login ALL=NOPASSWD: NOVABOOT
312 - \--iso\[=filename\]
314 Generates the ISO image that boots NOVA system via GRUB. If no filename
315 is given, the image is stored under _NAME_.iso, where _NAME_ is the name
316 of the novaboot script (see also __\--name__).
318 - \--server\[=\[\[user@\]server:\]path\]
320 Copy all files needed for booting to another location (implies __\-g__
321 unless __\--grub2__ is given). The files will be copied (by __rsync__
322 tool) to the directory _path_. If the _path_ contains string $NAME,
323 it will be replaced with the name of the novaboot script (see also
328 If __\--server__ is used and its value ends with $NAME, then after
329 copying the files, a new bootloader configuration file (e.g. menu.lst)
330 is created at _path-wo-name_, i.e. the path specified by __\--server__
331 with $NAME part removed. The content of the file is created by
332 concatenating all files of the same name from all subdirectories of
333 _path-wo-name_ found on the "server".
335 - \--rsync-flags=_flags_
337 Specifies which _flags_ are appended to `rsync` command line when
338 copying files as a result of _\--server_ option.
340 ## Target power-on and reset phase
344 Switch on/off the target machine. Currently works only with
347 - \-Q, --qemu\[=_qemu-binary_\]
349 Boot the configuration in qemu. Optionally, the name of qemu binary
350 can be specified as a parameter.
352 - \--qemu-append=_flags_
354 Append _flags_ to the default qemu flags (QEMU\_FLAGS variable or
355 `-cpu coreduo -smp 2`).
357 - \-q, --qemu-flags=_flags_
359 Replace the default qemu flags (QEMU\_FLAGS variable or `-cpu coreduo
360 -smp 2`) with _flags_ specified here.
364 Command that resets the target.
366 ## Interaction with the bootloader on the target
370 Interact with uBoot bootloader to boot the thing described in the
371 novaboot script. Implementation of this option is currently tied to a
372 particular board that we use. It may be subject to changes in the
377 Command(s) to send the U-Boot bootloader before loading the images and
380 ## Target interaction phase
382 In this phase, target's serial output is redirected to stdout and if
383 stdin is a TTY, it is redirected to the target's serial input allowing
384 interactive work with the target.
388 When _string_ is sent by the target, novaboot exits. This option can
389 be specified multiple times.
391 If _string_ is `-re`, then the next __\--exiton__'s _string_ is
392 treated as regular expression. For example:
394 --exiton -re --exiton 'error:.*failed'
398 Setup things for interactive use of target. Your terminal will be
399 switched to raw mode. In raw mode, your system does not process input
400 in any way (no echoing of entered characters, no interpretation
401 special characters). This, among others, means that Ctrl-C is passed
402 to the target and does no longer interrupt novaboot. Use "~~."
403 sequence to exit novaboot.
407 When _string_ is received from the target, send the string specified
408 with the subsequent __\--send\*__ option to the target.
410 - \--expect-re=_regex_
412 When target's output matches regular expression _regex_, send the
413 string specified with the subsequent __\--send\*__ option to the target.
415 - \--expect-raw=_perl-code_
417 Provides direct control over Perl's Expect module.
421 Send _string_ to the target after the previously specified
422 __\--expect\*__ was matched in the target's output. The _string_ may
423 contain escape sequences such as "\\n".
425 Note that _string_ is actually interpreted by Perl, so it can contain
426 much more that escape sequences. This behavior may change in the
429 Example: `--expect='login: ' --send='root\n'`
431 - \--sendcont=_string_
433 Similar to __\--send__ but continue expecting more input.
435 Example: `--expect='Continue?' --sendcont='yes\n'`
437 # NOVABOOT SCRIPT SYNTAX
439 The syntax tries to mimic POSIX shell syntax. The syntax is defined
440 with the following rules.
442 Lines starting with "\#" and empty lines are ignored.
444 Lines that end with "\\" are concatenated with the following line after
445 removal of the final "\\" and leading whitespace of the following line.
447 Lines of the form _VARIABLE=..._ (i.e. matching '^\[A-Z\_\]+=' regular
448 expression) assign values to internal variables. See ["VARIABLES"](#variables)
451 Lines starting with `load` keyword represent modules to boot. The
452 word after `load` is a file name (relative to the build directory
453 (see __\--build-dir__) of the module to load and the remaining words are
454 passed to it as the command line parameters.
456 When the `load` line ends with "<<WORD" then the subsequent lines
457 until the line containing solely WORD are copied literally to the file
458 named on that line. This is similar to shell's heredoc feature.
460 When the `load` line ends with "< CMD" then command CMD is executed
461 with `/bin/sh` and its standard output is stored in the file named on
462 that line. The SRCDIR variable in CMD's environment is set to the
463 absolute path of the directory containing the interpreted novaboot
467 \#!/usr/bin/env novaboot
468 WVDESC=Example program
469 load bin/apps/sigma0.nul S0\_DEFAULT script\_start:1,1 \\
470 verbose hostkeyb:0,0x60,1,12,2
471 load bin/apps/hello.nul
472 load hello.nulconfig <<EOF
473 sigma0::mem:16 name::/s0/log name::/s0/timer name::/s0/fs/rom ||
474 rom://bin/apps/hello.nul
477 This example will load three modules: `sigma0.nul`, `hello.nul` and
478 `hello.nulconfig`. sigma0 receives some command line parameters and
479 `hello.nulconfig` file is generated on the fly from the lines between
484 The following variables are interpreted in the novaboot script:
488 Novaboot chdir()s to this directory before file generation phase. The
489 directory name specified here is relative to the build directory
490 specified by other means (see ["--build-dir"](#build-dir)).
494 Assigning this variable has the same effect as specifying ["--exiton"](#exiton)
499 Parameters passed to hypervisor. The default value is "serial", unless
500 overridden in configuration file.
504 The kernel to use instead of the hypervisor specified in the
505 configuration file with the `$hypervisor` variable. The value should
506 contain the name of the kernel image as well as its command line
507 parameters. If this variable is defined and non-empty, the variable
508 HYPERVISOR\_PARAMS is not used.
512 Use a specific qemu binary (can be overridden with __\-Q__) and flags
513 when booting this script under qemu. If QEMU\_FLAGS variable is also
514 specified flags specified in QEMU variable are replaced by those in
519 Use specific qemu flags (can be overridden with __\-q__).
523 Description of the wvtest-compliant program.
527 The timeout in seconds for WvTest harness. If no complete line appears
528 in the test output within the time specified here, the test fails. It
529 is necessary to specify this for long running tests that produce no
534 Novaboot can read its configuration from one or more files. By
535 default, novaboot looks for files named `.novaboot` as described in
536 ["Configuration reading phase"](#configuration-reading-phase). Alternatively, its location can be
537 specified with the __\-c__ switch or with the NOVABOOT\_CONFIG
538 environment variable. The configuration file has perl syntax and
539 should set values of certain Perl variables. The current configuration
540 can be dumped with the __\--dump-config__ switch. Some configuration
541 variables can be overridden by environment variables (see below) or by
542 command line switches.
544 Supported configuration variables include:
548 Build directory location relative to the location of the configuration
553 Default target (see below) to use when no target is explicitly
554 specified on command line with the __\--target__ option.
558 Hash of shortcuts to be used with the __\--target__ option. If the hash
559 contains, for instance, the following pair of values
561 'mybox' => '--server=boot:/tftproot --serial=/dev/ttyUSB0 --grub',
563 then the following two commands are equivalent:
565 ./script --server=boot:/tftproot --serial=/dev/ttyUSB0 --grub
568 # ENVIRONMENT VARIABLES
570 Some options can be specified not only via config file or command line
571 but also through environment variables. Environment variables override
572 the values from configuration file and command line parameters
573 override the environment variables.
577 Name of the novaboot configuration file to use instead of the default
582 Defining this variable has the same meaning as __\--bender__ option.
586 Michal Sojka <sojka@os.inf.tu-dresden.de>