| olofl | |
| Sep 7 2017, 9:51 PM |
| F28504: autoboot.png | |
| Dec 1 2017, 6:21 PM |
When I run the VyOS beta image (vyos-999.201709062137-amd64.iso) in VirtualBox, I actively have to click start either live or live failsafe mode.
How can I come around this behavior so it boots automatically after X seconds? /etc/default/grub shows GRUB_TIMEOUT=5
I ran update-grub and copied file to /boot/grub/ after I installed the image on disk, but it hasn't changed anything.
This is a pretty annoying issue, since I suspect this is whats keeping GNS3 to not load the image properly.
I guess that you are referring to the installation of VyOS, as a proper installed system will automatically boot up. At least last nights build does.
Yes that's correct, I was referring to an uninstalled VyOS. Once the "install image" command was done it would boot through GRUB without interaction.
For my particular problem regarding GNS3, I was able to interact with the machine if I connected with VNC instead of serial. Installed image and then back to serial connection, successful workaround :)
@syncer @dmbaturin @UnicronNL is there any reason to not implement this? I think this should be doable in less then two hours.
we actually need clean up grup config a bit
as it have 2 timers for 5 seconds and it's kind of annoying
cpo@AC1:~$ cat /boot/grub/grub.cfg | grep timeout set timeout=5
There is just one 5 seconds timeout. The timeout mentioned by @olofl is inside the isolinux bootloader part which is used for the installation media. @olofl thought that it would be GRUB related but infact its isolinux related.
vyos-build/data/live-build-config/includes.binary/isolinux/menu.cfg
From http://www.syslinux.org/wiki/index.php?title=Config#TIMEOUT
TIMEOUT timeout
If more than one label entry is available, this directive indicates how long to wait at the "boot:" prompt until booting automatically, in units of 1/10 s.
The timeout is cancelled as soon as the user types anything on the keyboard; the assumption being that the user will complete the command line already begun.
The timer is reset to timeout upon return from an unsuccessful attempt to boot or from a module. A timeout of zero (the default) will disable the timeout completely.
