Closed amitchahalgits closed 3 days ago
Hi @amitchahalgits
Can you please provide the output of the following commands:
sudo /Library/Application\ Support/com.canonical.multipass/bin/qemu-img info /var/root/Library/Application Support/multipassd/qemu/vault/instances/consul/ubuntu-22.04-server-cloudimg-amd64.img
sudo /Library/Application\ Support/com.canonical.multipass/bin/qemu-img check /var/root/Library/Application Support/multipassd/qemu/vault/instances/consul/ubuntu-22.04-server-cloudimg-amd64.img
Also, could you provide the contents of your cloud init file?
Happens to me aswell, I recently udpated to 14.5 too. I had previously installed a regular ubuntu 22.04 server instance. Now it doesn't start, I've tried purging the image and launching another one, but after waiting a lot of time:
$ multipass launch docker
launch failed: The following errors occurred:
docker: timed out waiting for response
$ multipass list
Name State IPv4 Image
docker Unknown -- Ubuntu 22.04 LTS
Same results
` matt@matts-MBP ~ % multipass --version multipass 1.13.1+mac multipassd 1.13.1+mac matt@matts-MBP ~ % multipass start launch failed: The following errors occurred: primary: timed out waiting for response [2024-05-23T15:43:38.268] [info] [daemon] Daemon arguments: /Library/Application Support/com.canonical. |
ReplyForwardAdd reaction |
---|
Happens to me aswell, I recently udpated to 14.5 too. I had previously installed a regular ubuntu 22.04 server instance. Now it doesn't start, I've tried purging the image and launching another one, but after waiting a lot of time:
$ multipass launch docker launch failed: The following errors occurred: docker: timed out waiting for response $ multipass list Name State IPv4 Image docker Unknown -- Ubuntu 22.04 LTS
I've tried reinstalling multipass and it didn't initially work, but after rebooting (I don't really know if that solved it) it works again.
EDIT: I've figured out what was wrong. I'm using a VPN connection, when it's connected I can't use multipass
@mdfranz The likely cause of the Unknown
state is probably because Multipass can't connect to the instance. This can happen if you're using a VPN or have your firewall turned on. If the issue still persists for you, can you post the logs of launching an instance?
Are there additional logs you are looking for besides what I posted above starting with
Correct me if I'm wrong but if it couldn't connect it couldn't start or purge?
[2024-05-23T15:43:38.268] [info] [daemon] Daemon arguments: /Library/Application Support/com.canonical.multipass/bin/multipassd --verbosity debug
[2024-05-23T15:43:38.314] [debug] [update] Latest Multipass release available is version 1.13.1
[2024-05-23T15:44:01.558] [debug] [daemon] Deleting instance: primary
[2024-05-23T15:44:01.558] [debug] [daemon] Instance deleted: primary
[2024-05-23T15:44:12.016] [debug] [daemon] Instance purged: primary
[2024-05-23T15:44:16.024] [debug] [qemu-system-aarch64] [9815] started: qemu-system-aarch64 --version
[2024-05-23T15:44:16.721] [debug] [qemu-img] [9816] started: qemu-img info /var/root/Library/Caches/multipassd/qemu/vault/images/noble-20240423/ubuntu-24.04-server-cloudimg-arm64.img
[2024-05-23T15:44:16.739] [debug] [qemu-img] [9817] started: qemu-img resize /var/root/Library/Application Support/multipassd/qemu/vault/instances/primary/ubuntu-24.04-server-cloudimg-arm64.img 5368709120
[2024-05-23T15:44:16.758] [debug] [qemu-img] [9818] started: qemu-img snapshot -l /var/root/Library/Application Support/multipassd/qemu/vault/instances/primary/ubuntu-24.04-server-cloudimg-arm64.img
[2024-05-23T15:44:16.771] [debug] [qemu-img] [9819] started: qemu-img amend -o compat=1.1 /var/root/Library/Application Support/multipassd/qemu/vault/instances/primary/ubuntu-24.04-server-cloudimg-arm64.img
Sorry, I thought those were from another user. The NIC_RX_FILTER_CHANGED
in the logs suggests that the instance has successfully started up and initialized the network interface, just that Multipass cannot connect to it. Can you confirm that you don't have anything else running that could affect the network (VPN, macOS firewall, etc). You may have to reboot the machine to any changes take effect.
Turns out my M3 had bad memory. 😬
@amitchahalgits Can you confirm whether the issue has been solved for you or not? If not, would you be able to provide me the information from the commands I gave in my previous comments to you? Otherwise, if there is no longer an issue, I will close this issue.
Thanks!
Closing then. Please reopen if needed.
Describe the bug multipass 1.13.1 doesnt run VMs and state shows "unknown" Multipass version 1.13.1 MacOS version : Sonoma 14.5(ARM64)
To Reproduce How, and what happened?
mp launch jammy -n consul --cloud-init consul-server-cloud-init.yaml
multipass get local.driver
qemuExpected behavior With all things in place, ot should be able to spin VMs as expected.
Logs
Additional info
mp info consul
Additional context NA