[19:32] <on3pk> is there a way to increase the timeout when starting multipass instances?  I'm having an issue wher multipass is reporting that starting an instance is timing out.  Eventually the instance starts and it's possible to SSH into the instance using it's IP, but not multipass shell because multipass doesn't know it's running
[19:32] <on3pk> (or rather, it's in an unknown state when checked with multipass list)
[19:34] <ChrisTownsend> on3pk: Hi on3pk, there is a `--timeout` option you can pass to `start`.  See `multipass start --help`.
[19:37] <on3pk> thanks.  when it's in an unknown state, is killing the qemu process a worthwhile thing to do?
[19:40] <ChrisTownsend> Well, killing the process out from underneath multipass will probably get multipass confused.  When you say you are about the SSH directly into the instance, how are you getting the IP address?
[19:42] <on3pk> I was using journalctl to see what happens when I try to start an instance
[19:44] <ChrisTownsend> Ok, what's weird is that multipass is not discovering the IP address from the dnsmasq.leases file.  What host are you using?
[19:45] <on3pk> ubuntu
[19:45] <on3pk> 22.04 I think
[19:46] <ChrisTownsend> Ok, that's fine.  Does this only happen for this particular instance or any instance you start/launch?
[19:51] <on3pk> this is the only instance on the machine.  I'm trying to launch a new instance now
[20:08] <on3pk> ok, so it timed out for the initialization to complete, too
[20:09] <ChrisTownsend> Oh, initialization, do you have a custom cloud-init that is doing quite a bit of stuff?
[20:11] <on3pk> not that I'm aware of.  Everything is default
[20:12] <ChrisTownsend> You are seeing the message "timed out waiting for initialization to complete", correct?
[20:14] <on3pk> [2023-01-13T19:51:21.884] [error] [qemu factory] Qemu failed to start: program: qemu-system-x86_64; error: Process operation timed out
[20:14] <on3pk> timed out waiting for initialization to complete
[20:20] <ChrisTownsend> That error message is strange as that message comes when probing the qemu version.  And the "timed out waiting for initialization to complete" means that multipass is able to communicate with the instance, but `cloud-init` is failing or not completing in time.  There is definitely something going on here that is not normal.  Would it possible for you to provide the logs: https://multipass.run/docs/accessing-logs#heading--linux
[22:30] <on3pk> I tried to launch the instance with a timeout of 900 seconds and it still failed :|
[23:31] <on3pk> well I think I might have found one of the problems
[23:32] <on3pk> disk i/o is on the order of "really, really bad".  Read       | 162.00 KB/s Write      | 243.00 KB/s