Unix sockets from `virtio-vsock` devices not cleaned up

[unsuman]

Thanks for working on #79

When a krunkit VM is started with virtio-vsock devices configured, the Unix socket files created by krunkit on the host are not cleaned up when the VM is stopped. This causes subsequent stop/start cycles to fail because the socket files still exist.

1. Krunkit creates Unix socket files for each virtio-vsock device
2. On VM stop, krunkit does not remove these socket files
3. On the next VM start, krunkit attempts to create the same socket files again, but they still exist from the previous run
4. This causes the VM to fail to start or hang

[jakecorrenti]

Thank you for reporting this @unsuman. I don't have the cycles at the moment to fix this, but I will get to it as soon as I can.

In the meantime if you'd like to work on this yourself, just assign yourself this issue.

[unsuman]

You're welcome! Yes I can give it a try