Chris Townsend

Hey @rlewkowicz, We are a small team and have had other things going on before we can triage this bug (and sometimes things just get missed until a later time)....

I believe this is actually fixed by https://github.com/canonical/multipass/pull/2535. I'm closing this, but please reopen if this is not the case.

Hey @abitrolly, I commented at https://github.com/canonical/multipass/issues/2564#issuecomment-1125994537 about the challenges of automatically making Multipass work with `firewalld`. Thanks!

Upon some debugging and digging, I've found that this is caused by a Qt bug: https://bugreports.qt.io/browse/QTBUG-81318 There is a proposed fix since August 2020, but it remains unmerged: https://codereview.qt-project.org/c/qt/qtbase/+/296092 Seeing...

Hi @UchihaYuki, Yeah, it's a Qt bug. You need to remove, `C:\ProgramData\Multipass\cache\network-cache` and restart the Multipass service and that should clear it up.

Hi @holta Ah, you are using the LXD driver. So what I suspect is happening is that the lxd daemon is not ready or at least not reporting the instances...

Hi @holta, Could you please provide [logs](https://multipass.run/docs/accessing-logs#heading--linux) and I will scan through them to see if I can glean anything from them.

Hey @holta, Ok, just quickly scanning through this log, `multipassd` is unable to reach the internet and then throws and unexpected exception and bails. This is a known issue and...

I'm guessing Multipass gets started before networking is fully up and ready.

Hi @holta, Are you asking if this issue should be fixed in `edge` version of Multipass? > (Possibly this erroneous and over-eager launching of VM's is a result of these...