You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
if you don't use multipass stop, then it's really hard for multipassd to know the state of a VM. That said, we could probably be better at detecting instance states that are modified outside of Multipass when using the LXD driver.
@townsend2010 are you aware that multipass stop --all is not enough to prevent instances from auto-booting the next time the host boots?
Example:
An instance is powered off internally, using a command like poweroff
multipass stop --all is run on the host machine.
Host machine is rebooted, and the instance (unfortunately!) auto-boots, despite both above attempts to prevent that :/
(This should be easily fixable, no?)
PS This is separate from the question as to whether or not Multipass will one day act like a modern BIOS:
there really should be a Multipass/LXD option (rather like in a PC's BIOS/firmware) allowing you to toggle between either of these 2 choices:
Auto-boot VM's/instances after power failure / glitch / etc.
Do NOT auto-boot VM's/instances after power failure / glitch / etc.
The text was updated successfully, but these errors were encountered:
townsend2010
changed the title
[lxd] Multipass not reacting correctly with internally shutdown instances
[lxd] Multipass not reacting correctly with internally shut down instances
Jul 19, 2022
2684: Fix LXD not updating state r=andrei-toterman a=sharder996
LXD instances do not update instance state within multipass when they are externally shutdown (ie. `sudo poweroff` within the instance) and so will reboot them when the daemon restarts. To fix this, we force multipass to update the state of LXD instances before shutting down to ensure that they are put into the correct state when multipass reboots.
Fixes#2672
Co-authored-by: sharder996 <[email protected]>
borsbot
added a commit
that referenced
this issue
Aug 9, 2022
2684: Fix LXD not updating state r=andrei-toterman a=sharder996
LXD instances do not update instance state within multipass when they are externally shutdown (ie. `sudo poweroff` within the instance) and so will reboot them when the daemon restarts. To fix this, we force multipass to update the state of LXD instances before shutting down to ensure that they are put into the correct state when multipass reboots.
Fixes#2672
Co-authored-by: sharder996 <[email protected]>
borsbot
added a commit
that referenced
this issue
Aug 9, 2022
2684: Fix LXD not updating state r=andrei-toterman a=sharder996
LXD instances do not update instance state within multipass when they are externally shutdown (ie. `sudo poweroff` within the instance) and so will reboot them when the daemon restarts. To fix this, we force multipass to update the state of LXD instances before shutting down to ensure that they are put into the correct state when multipass reboots.
Fixes#2672
Co-authored-by: sharder996 <[email protected]>
@townsend2010 are you aware that
multipass stop --all
is not enough to prevent instances from auto-booting the next time the host boots?Example:
poweroff
multipass stop --all
is run on the host machine.(This should be easily fixable, no?)
PS This is separate from the question as to whether or not Multipass will one day act like a modern BIOS:
Originally posted by @holta in #2610 (comment)
The text was updated successfully, but these errors were encountered: