Better stress testing on behavior of Qubes OS after an illegal shutdown

[logoerthiner1]

How to file a helpful issue

The problem you're addressing (if any)

Qubes OS gets unstable when illegally shutdown. Since Qubes OS may not support certain hardware very well, sometimes the computer dies and immediately reboot, or user is forced to illegally shutdown the machine and then reboot. In both cases Qubes OS is under an unstable internal state, which can cause various problems. Possible causes of illegal shutdowns can be caused, for example, when #7340 happens.

The solution you'd like

For example, monkey testing of Qubes OS when a monkey cuts off the power of the computer at a random time spot when Qubes OS is busy doing various tasks (for example playing with creating vm, starting vm, pausing vm(suspension involves pausing them, right?), destroying vm, running lvm cleanup, commiting lvm image, attaching devices and detaching devices, flushing usb devices, , or even updating xen or linux kernels) and then boot the system again to check whether the system gets unstable, whether the boot time become longer or maybe even get into softlock or permanent destroyal.

The value to a user, and who that user might be

User of devices that Qubes OS sometimes dies. As many deaths of Qubes OS gets unsolved for a long time, the alternate ways that make deaths of computer less painful become more and more important.

[logoerthiner1]

oops sorry for the repetition, I do not have a stable internet connection