Time out and unknown state

**Describe the bug**
Cannot connect to VM, 'Open Shell' and ssh times out. Logs indicate network is being reset regularly. Logs say VM is in an unknown state as well as 'multipass ls'.

**To Reproduce**
How, and what happened?
1. Rebooted my laptop (2022 M1 Max MBP Ventura 13.2.1)
2. Tried ssh'ing into my ubuntu 20.04 VM

**Expected behavior**
What did you expect to happen?
To have ssh access to my VM

**Logs**
Please provide logs from the daemon, see [accessing logs](https://multipass.run/docs/accessing-logs) on where to find them on your platform.
Ill attach logs to the issue

**Additional info**
- OS: MacOS 13.2.1
-
- `% multipass version
multipass 1.11.1+mac
multipassd 1.11.1+mac`

- `multipass info --all`
```brendanscherer@Brendans-MacBook-Pro ~ % multipass info --all
Name: primary
State: Stopped
IPv4: --
Release: --
Image hash: f6b5b3a980f2 (Ubuntu 22.04 LTS)
CPU(s): --
Load: --
Disk usage: --
Memory usage: --
Mounts: /Users/brendanscherer => Home
UID map: 501:default
GID map: 20:default

Name: brendan-vm
State: Unknown
IPv4: --
Release: --
Image hash: 0f1a20bcda28 (Ubuntu 20.04 LTS)
CPU(s): --
Load: --
Disk usage: --
Memory usage: --
Mounts: --
```

- multipass get local.driver
qemu

[multipassd.log](https://github.com/canonical/multipass/files/10935433/multipassd.log)

**Additional context**
In the logs there are references to qemu crashing

Start with the linked multipassd.log and the references to QEMU crashes, then reproduce the failure using `multipass info --all`, `multipass ls`, and `multipass get local.driver`. Trace why the `brendan-vm` instance reaches an unknown state and why SSH and Open Shell time out. Done means the affected VM reports a usable state and SSH access works after the laptop reboot scenario.

Written by the indexing model from the issue text.