I am trying to fully automate the testing of an ISO installer.
The ISO is bootable via ISOLINUX and can automatically install Oracle Linux 6 via Kickstart.
I have several label
options in my isolinux.cfg
file, each appending a different Kickstart file as follows:
foo
kernel vmlinuz
append ks=cdrom://isolinux/oel6-foo-ks.cfg
bar
kernel vmlinuz
append ks=cdrom://isolinux/oel6-bar-ks.cfg
These labels help present the user with a boot menu, asking them what type of system to install (a foo or a bar).
Through VirtualBox command line, I can see how to create a VM with the ISO attached and power it on.
My problem is how to interact with the boot menu presented by the ISO?
In general, is there a way to automate the interaction with boot menus from the hypervisor command line?
If there is no proper way to interact with boot menus, could we perhaps bypass the boot menu and provide append ks
options by hand via something like this:
VBoxManage unattended install --extra-install-kernel-parameters=params
.
If possible, I would prefer to avoid changing the ISO (E.G. timeout-default to one menu option, or remove the menu entirely).