Bug #181
"arch" command does not take effect until shutdown then boot
| Status: | Closed | Start: | 2019-07-22 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assigned to: | - | % Done: | 0% |
|
| Category: | - | |||
| Target version: | - | |||
| Votes: | 0 |
Description
The "arch" command alters the bootloader defined in the guest config, but guests don't see config updates until their next creation. Rebooting a guest does not create a new VM, it just re-uses the existing one. The result is that an architecture change won't take effect until the guest is shutdown and booted again.
This can be fixed by making the "arch" command do a config update as well.
