It is not a destroy. With some hardware changes you require the host to
shutdown down and then start. The shutdown down is manually given either
via some acpi request or from within the guest.
When the guest is down, the 'host' recognizes this guest requires a one
time start, and starts it.
This should 'solve' that if you change hardware you have to wait for the
guest to shutdown and then start the guest manually.
I would not know what level this can best be implemented.
-----Original Message-----
From: brent s. [mailto:bts@square-r00t.net]
Sent: maandag 22 juni 2020 1:54
To: libvirt-users@redhat.com
Subject: Re: Feature request? Auto start vm upon next shutdown
On 6/21/20 13:20, Marc Roos wrote:>
> Sometimes when you change the configuration, this configuration change
> will only be available after a shutdown. Not to have to monitor when
> the vm shuts down, to start it again. It could be nice to have libvirt
> start it one time. Something like:
>
> 1. change the network interface of a running guest 2. at the prompt of
> the virt-manager "Some changes may require a guest shutdown to take
> effect"
> introduce check box 'Auto start vm upon next shutdown'
> 3. shutdown the guest
> 4. after the guest completed shutdown, libvirt is automatically
> starting it again.
>
This took me a while because at first I thought you were talking about
the vm automatically starting on libvirt invocation (autostart), but
instead it sounds like you want a function to allow the user upon making
a change to initiate a hypervisor-level restart (i.e. destroy then
start). Correct?
--
brent saner
https://square-r00t.net/
GPG info: https://square-r00t.net/gpg-info
