I am able to start the primary but not my instance. I restarted the Multipass, but the result is the same.
How can I fix this?
After 1 hour, it is still starting.
I am able to start the primary but not my instance. I restarted the Multipass, but the result is the same.
How can I fix this?
After 1 hour, it is still starting.
Hmm, something went amiss in there. Is that hyperkit on macOS? Does restarting the multipass daemon help (sudo pkill multipassd
)? Is bootp still running? Have a look at this troubleshooting section to see if it helps. Otherwise, please report an issue here, filling in the details. Thank you.
@ricab Thank you for your help.
I restarted my mac and it is working.
I now remember that It happened before.
Thanks again, ricab.
The reboot worked for me as well. Thanks!
Hello. What is the process to troubleshoot instances that cannot start?
My host is mbp M1 12.7.2. Today I started having issues with an instance not being able to push and pull from git. I tried to stop and start the instance, but that did not work. I was able to shell into the instance and set it to powerdown. I tried then to upgrade multipass, but no luck. Now the instance is stuck as Unknown after trying to start it several times:
Name State IPv4 Image
ubuntu Unknown -- Ubuntu 22.04 LTS
Unfortunately, this was before the nice update with snapshots, so I don’t have any snapshot of this instance (thought everything on it is git, so no work was lost).
How can I go about poking this instance to see what could be wrong?
Hey, @fraguada! Could you please provide some more details, like logs, perhaps by opening an issue here? If you try to create a new instance, does it work properly? Have you tried restarting the daemon, as mentioned above (sudo pkill multipassd
)?
Here are some logs:
[2024-01-23T14:55:33.198] [debug] [update] Latest Multipass release available is version 1.13.0
[2024-01-23T14:55:33.320] [debug] [blueprint provider] Loading "anbox-cloud-appliance" v1
[2024-01-23T14:55:33.322] [debug] [blueprint provider] Loading "charm-dev" v1
[2024-01-23T14:55:33.323] [debug] [blueprint provider] Loading "docker" v1
[2024-01-23T14:55:33.323] [debug] [blueprint provider] Loading "jellyfin" v1
[2024-01-23T14:55:33.324] [debug] [blueprint provider] Loading "minikube" v1
[2024-01-23T14:55:33.324] [debug] [blueprint provider] Loading "ros-noetic" v1
[2024-01-23T14:55:33.325] [debug] [blueprint provider] Loading "ros2-humble" v1
[2024-01-23T14:55:33.350] [info] [rpc] gRPC listening on unix:/var/run/multipass_socket
[2024-01-23T14:55:33.350] [debug] [async task] fetch manifest periodically
[2024-01-23T14:55:33.383] [debug] [qemu-img] [13137] started: qemu-img snapshot -l /var/root/Library/Application Support/multipassd/qemu/vault/instances/ubuntu/ubuntu-22.04-server-cloudimg-arm64.img
[2024-01-23T14:55:33.409] [info] [VMImageHost] Did not find any supported products in "appliance"
[2024-01-23T14:55:35.042] [debug] [qemu-img] [13639] started: qemu-img amend -o compat=1.1 /var/root/Library/Application Support/multipassd/qemu/vault/instances/ubuntu/ubuntu-22.04-server-cloudimg-arm64.img
[2024-01-23T14:55:35.062] [info] [daemon] Starting Multipass 1.13.0+mac
[2024-01-23T14:55:35.062] [info] [daemon] Daemon arguments: /Library/Application Support/com.canonical.multipass/bin/multipassd --verbosity debug
[2024-01-23T14:56:38.278] [debug] [ubuntu] process working dir ''
[2024-01-23T14:56:38.278] [info] [ubuntu] process program 'qemu-system-aarch64'
[2024-01-23T14:56:38.278] [info] [ubuntu] process arguments '-machine, virt,gic-version=3, -accel, hvf, -drive, file=/Library/Application Support/com.canonical.multipass/bin/../Resources/qemu/edk2-aarch64-code.fd,if=pflash,format=raw,readonly=on, -cpu, host, -nic, vmnet-shared,model=virtio-net-pci,mac=52:54:00:98:b5:83, -device, virtio-scsi-pci,id=scsi0, -drive, file=/var/root/Library/Application Support/multipassd/qemu/vault/instances/ubuntu/ubuntu-22.04-server-cloudimg-arm64.img,if=none,format=qcow2,discard=unmap,id=hda, -device, scsi-hd,drive=hda,bus=scsi0.0, -smp, 4, -m, 8192M, -qmp, stdio, -chardev, null,id=char0, -serial, chardev:char0, -nographic, -cdrom, /var/root/Library/Application Support/multipassd/qemu/vault/instances/ubuntu/cloud-init-config.iso'
[2024-01-23T14:56:38.301] [debug] [qemu-system-aarch64] [32890] started: qemu-system-aarch64 -machine virt,gic-version=3 -nographic -dump-vmstate /private/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/multipassd.KslaIv
[2024-01-23T14:56:39.913] [info] [ubuntu] process state changed to Starting
[2024-01-23T14:56:39.916] [info] [ubuntu] process state changed to Running
[2024-01-23T14:56:39.916] [debug] [qemu-system-aarch64] [33370] started: qemu-system-aarch64 -machine virt,gic-version=3 -accel hvf -drive file=/Library/Application Support/com.canonical.multipass/bin/../Resources/qemu/edk2-aarch64-code.fd,if=pflash,format=raw,readonly=on -cpu host -nic vmnet-shared,model=virtio-net-pci,mac=52:54:00:98:b5:83 -device virtio-scsi-pci,id=scsi0 -drive file=/var/root/Library/Application Support/multipassd/qemu/vault/instances/ubuntu/ubuntu-22.04-server-cloudimg-arm64.img,if=none,format=qcow2,discard=unmap,id=hda -device scsi-hd,drive=hda,bus=scsi0.0 -smp 4 -m 8192M -qmp stdio -chardev null,id=char0 -serial chardev:char0 -nographic -cdrom /var/root/Library/Application Support/multipassd/qemu/vault/instances/ubuntu/cloud-init-config.iso
[2024-01-23T14:56:39.916] [info] [ubuntu] process started
[2024-01-23T14:56:39.927] [debug] [ubuntu] Waiting for SSH to be up
[2024-01-23T14:56:39.972] [debug] [ubuntu] QMP: {"QMP": {"version": {"qemu": {"micro": 0, "minor": 0, "major": 8}, "package": ""}, "capabilities": ["oob"]}}
[2024-01-23T14:56:40.011] [debug] [ubuntu] QMP: {"return": {}}
[2024-01-23T15:06:20.814] [info] [daemon] Cannot open ssh session on "ubuntu" shutdown: ssh connection failed: 'Timeout connecting to 192.168.64.6'
[2024-01-23T15:06:20.816] [debug] [ubuntu] QMP: {"return": {}}
{"timestamp": {"seconds": 1706018780, "microseconds": 816315}, "event": "POWERDOWN"}
yes it does
I did that, but not sure how to restart it.