cloudhypervisor: VM creation errors with "Address in use"

[icyphox]

Hey, apologies for the delay and Happy New Year! ✨ Here's the issue that I promised to create. Let me know if you need me to add any further info! Attaching relevant log files here:

cloudhypervisor-stderr.log
cloudhypervisor-stdout.log
cloudhypervisor.log

What happened:

Creating a VM using latest cloudhypervisor-static results in cloudhypervisor erroring out with (from /var/lib/flintlock/.../cloudhypervisor.stderr):

Failed to start the VMM thread: Error creation API server's socket Os { code: 98, kind: AddrInUse, message: "Address in use" }
Error booting VM: VmBoot(DeviceManager(CreateVirtioNet(OpenTap(TapOpen(ConfigureTap(Os { code: 16, kind: ResourceBusy, message: "Resource busy" }))))))

What did you expect to happen:

VM creation not to fail.

How to reproduce it:

I'm running flintlockd like so:

root@flintlock-test:/home/icy# ./flintlockd_amd64 run --cloudhypervisor-bin ./cloud-hypervisor-static --containerd-socket /run/containerd-dev/containerd.sock --bridge-name flbr-tenant1 --default-provider cloudhypervisor --insecure -v5

And sending the CreateMicroVM request using fl (built from main):

./fl microvm create --name "test-ch-1" --host localhost:9090 --network-interface eth1:tap --kernel-image ghcr.io/liquidmetal-dev/cloudhypervisor-kernel:6.2 --root-image ghcr.io/liquidmetal-dev/ubuntu:22.04 --kernel-filename vmlinux.bin

Environment:

• flintlock version: 0.7.0
• containerd version: 1.7.24
• OS (e.g. from /etc/os-release): Debian 11 (bullseye)
• Running on a GCP VM with nested virtualization enabled