This is done by the boot paramer in vm.cfg.
The switches are:
* floppy (a)
* hard disk (c)
* Network (n)
* CD-ROM (d)
If you use
boot = ‘n’
it will be stuck at PXE boot even if there is no dhcp lease and guest will not attempt boot from the Virtual Disk.
To be able to have an order, you need to concatenate the switches. e.g. if you need to have a boot order like
1. network (n)
2. harddisk (c)
3. cdrom (d)
you need to have
boot=”ncd”
in vm.cfg.
Moreover,
If somehow the TFTP server is not accessible or misconfigured, that will fail
over to “c” aka. disk..
But if the DHCP server is not available, the boot will be stuck in a loop of “No
IP address”. Actually this is not much different from a normal BIOS.. A couple
of Dell systems with IBA (Intel Boot Agent) behaves similarly, but only
providing keystroke options.
I’ll also check the behaviour model of pypxeboot too ..
