When quickly looking at the recent modifications, I noticed 290b9b0 reduced the timeout in case of crash.
To deal with that, in our CI scripts for MPTCP, we add CONFIG_PANIC_TIMEOUT=-1 in the kernel config. To avoid the VM to reboot and mess-up with automation, we launch virtme with --qemu-opts -no-reboot, but I don't know what's the equivalent with virtme-ng.
While at it, we also enabled CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC and CONFIG_BOOTPARAM_HUNG_TASK_PANIC.
Maybe it would be easier to maintain a ci.config file in the selftests? Or always set that in lib/vm.py?
When quickly looking at the recent modifications, I noticed 290b9b0 reduced the timeout in case of crash.
To deal with that, in our CI scripts for MPTCP, we add
CONFIG_PANIC_TIMEOUT=-1in the kernel config. To avoid the VM to reboot and mess-up with automation, we launchvirtmewith--qemu-opts -no-reboot, but I don't know what's the equivalent withvirtme-ng.While at it, we also enabled
CONFIG_BOOTPARAM_SOFTLOCKUP_PANICandCONFIG_BOOTPARAM_HUNG_TASK_PANIC.Maybe it would be easier to maintain a
ci.configfile in the selftests? Or always set that inlib/vm.py?