multipass icon indicating copy to clipboard operation
multipass copied to clipboard

Published 20 hours ago • verified publisher icon canonical

Installing version 1.15.1 on 1.15.0 causes errors

Open ssg3d opened this issue 8 months ago • 3 comments

Describe the bug Installing version 1.15.1 on 1.15.0 causes errors

To Reproduce Have an instance running on multipass 1.15.0 Install multipass 1.15.1 Reboot the mac Do a multipass list. We get all sorts of errors.

Expected behavior Should work!

Logs Different errors when one does multipass list at different points of time:

<error 1> list failed: qemu-system-aarch64: -drive file=/var/root/Library/Application Support/multipassd/qemu/vault/instances/dev/ubuntu-24.04-server-cloudimg-arm64.img,if=none,format=qcow2,discard=unmap,id=hda: qcow2: Image is corrupt; cannot be opened read/write : shutdown called while starting

<error 2> list failed: cannot connect to the multipass socket

<error 3??> Name State IPv4 Image Unknown -- Ubuntu 24.04 LTS

Additional info

  • macOS 15.3.2
  • Apple M2
  • 1.15.,1
  • multipass info
  • info failed: qemu-system-aarch64: -drive file=/var/root/Library/Application Support/multipassd/qemu/vault/instances/dev/ubuntu-24.04-server-cloudimg-arm64.img,if=none,format=qcow2,discard=unmap,id=hda: qcow2: Image is corrupt; cannot be opened read/write dev: shutdown called while starting
  • qemu

ssg3d avatar Apr 10 '25 23:04 ssg3d

Hi @ssg3d,

Thank you for reporting this issue! Can you share your logs from the Multipass daemon as well please? (see how to access them)

Sploder12 avatar Apr 11 '25 13:04 Sploder12

Hi @Sploder12 sorry for the late response and for my inability to provide the information you requested. Since I had some mission critical stuff to resume, I couldn't wait for your response and uninstalled multipass from my mac (as per the documentation) and cleaned up stuff with multipass and reinstalled it and it worked. Of course, I lost my instance so I had to go through setting it up again. But this was a bit of a deja vu as I vaguely remember encountering a similar-ish issue a year or so back when I upgraded the version without shutting down my instances.

ssg3d avatar Apr 20 '25 14:04 ssg3d

No worries @ssg3d, I'm glad you were able to get it to work, although it's unfortunate the instance had to be recreated.

when I upgraded the version without shutting down my instances

This seems like a good clue as to what could've caused the issue, thank you for sharing!

Sploder12 avatar Apr 21 '25 14:04 Sploder12

This no longer appears to occur.

ricab avatar Sep 12 '25 18:09 ricab