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
Describe the bug
Describe what your problem is.
After successfully creating and running an instance using Multipass, the instance initially starts as expected. However, after stopping the instance and attempting to start it again, the instance immediately transitions to an "unknown" state instead of the expected "running" state. This issue occurs consistently and makes the instance inaccessible despite multiple start attempts.
To Reproduce
How, and what happened?
multipass ...
Expected behavior
What did you expect to happen?
Logs
Please provide logs from the daemon, see accessing logs on where to find them on your platform.
Additional info
OS: [e.g. macOS 10.15]
multipass version
multipass 1.15.0+mac
multipassd 1.15.0+mac
multipass info
multipass get local.driver
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Hi @manishNeupane13 , did you upgrade or do a fresh install? What hardware are you on (e.g. M1, M3, ...) and which version of macOS are you currently running? (e.g. Sequoia 15.2)
Describe the bug
Describe what your problem is.
After successfully creating and running an instance using Multipass, the instance initially starts as expected. However, after stopping the instance and attempting to start it again, the instance immediately transitions to an "unknown" state instead of the expected "running" state. This issue occurs consistently and makes the instance inaccessible despite multiple start attempts.
To Reproduce
How, and what happened?
multipass ...
Expected behavior
What did you expect to happen?
Logs
Please provide logs from the daemon, see accessing logs on where to find them on your platform.
Additional info
multipass version
multipass info
multipass get local.driver
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: