-
Notifications
You must be signed in to change notification settings - Fork 651
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[daemon] need to kill misbehaving instances on stop
#1167
Comments
This is easily reproduced by issuing |
I will say too, that this can lead to the daemon being in a bad state since it thinks the instance is running and has a valid IP address where in fact, the instance is not really running. |
Is there a workaround to kill an instance in this state? [Edit] I killed qemu and that at least allowed me to start Multipass and the instance again. |
@jbosse ultimate hammer is always |
This particularly needs fixing now that instance modification is possible and it's possible to overcommit resources to an instance, making it unbootable yet unstoppable. |
When an instance doesn't stop, a
multipass stop
command happily exits, when the instance actually continues to run.We need to apply a timeout, after which we let the user know that the instance didn't stop, and maybe add a
--force
option tomultipass stop
so that it gets killed instead after the timeout.This is at least the case on QEMU.
The text was updated successfully, but these errors were encountered: