Feature #187
Reload VM config after install or rescue is launched
| Status: | New | Start: | 2020-06-03 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assigned to: | - | % Done: | 0% |
|
| Category: | - | |||
| Target version: | - | |||
| Votes: | 0 |
Description
The "install" and "rescue" commands work by generating an alternate VM config that loads the operating system installer or rescue images respectively. If a reboot happens from within those environments then the VM itself is not destroyed but simply restarted. This results in the same image loading again (installer or rescue) rather than the VM's expected kernel.
It may be possible to update the VM's running config back to what it normally would be, after the installer or rescue has launched. That would cause a reboot to behave normally.
This would particularly help for the Debian (and Ubuntu) installers as these normally do a reboot at the end of the install process. At present these are configured to actually shut down instead of doing a reboot in order to avoid this issue but the text of the installer still says it's going to do a reboot, which can be confusing.