Failed to restart a stopped VM caused by a handled signal

[innobead]

When a VM stopped by a handled signal, ignite-spawn will update the VM running status to false but it does not handle the VM networking correctly to cause the VM unable to start due to duplicated IP allocation error.

Steps to reproduce:

• ignite run starts a VM
• kill -2 <ignite spawn/VM PID>
• ignite stop <VM ID> failed to forcibly stop the VM

➜  ignite stop b5d26a20c03fc678
FATA[0000] VM "b5d26a20c03fc678" is not running 

• ignite start <VM ID> failed with duplicated IP allocation error

➜  ignite start b5d26a20c03fc678
ERRO[0000] failed to setup network for namespace "ignite-b5d26a20c03fc678": failed to allocate for range 0: 10.61.0.42 has been allocated to ignite-b5d26a20c03fc678, duplicate allocation is not allowed 
FATA[0000] failed to allocate for range 0: 10.61.0.42 has been allocated to ignite-b5d26a20c03fc678, duplicate allocation is not allowed