ignite hangs when starting/running firecracker vm's using a CNI which is misconfigured/unhealthy

[fire-ant]

Issue description

whilst testing ignite using the weave CNI I came across an issue which may be of interest.

It appears that ignite is dependent on a functioning CNI but has no way to inform the end user as to whether the status of the CNI is known in the event that it is not functioning correctly. This leads to any attempt to start a VM silently hanging whilst ignite attempts to connect/interact for an indefinite period of time.

Steps to reproduce the issue

1. configure two vm's, both with ignite. configure one vm to peer with the other using the weave CNI but purposely avoid successful peering
2. start weave-net using a weave launch or similar command
3. attempt to use ignite run | start on a created vm, which should hang the console

What's the expected result?

A running VM

What's the actual result?

A hung cmd line

Additional details /

Ignite version: 0.8.0 Weave version: 2.7.0