Skip to content

contest: stop the VM after a crash? #8

@matttbe

Description

@matttbe

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions