How to file a helpful issue
The problem you're addressing (if any)
R4.2
The solution you'd like
Make executing reboot from within a VM actually restart such VM. This requires qubesd to handle the restarting all the relevant daemons (qrexec, qubesdb etc). That's also the time to reload VM configuration (maxmem, color etc). Due to that, libvirt should likely remain configured to <on_reboot>destroy</on_reboot>, but qubesd should react on shutdown reason in the libvirt event.
This may be opt-in feature (enabled with qvm-features or qvm-prefs).
The value to a user, and who that user might be
Currently when executing "reboot" within a VM, it is actually shut down. This is especially annoying for Windows VMs which do perform reboot from time to time (some updates, etc).
How to file a helpful issue
The problem you're addressing (if any)
R4.2
The solution you'd like
Make executing reboot from within a VM actually restart such VM. This requires qubesd to handle the restarting all the relevant daemons (qrexec, qubesdb etc). That's also the time to reload VM configuration (maxmem, color etc). Due to that, libvirt should likely remain configured to
<on_reboot>destroy</on_reboot>, but qubesd should react on shutdown reason in the libvirt event.This may be opt-in feature (enabled with qvm-features or qvm-prefs).
The value to a user, and who that user might be
Currently when executing "reboot" within a VM, it is actually shut down. This is especially annoying for Windows VMs which do perform reboot from time to time (some updates, etc).