Network cleanup fails when VMM process is already dead

[goyalpalak18]

Description

There is a resource leak where network interfaces (TAP devices) and Traffic Control (TC) rules are left behind if a VMM crashes or is killed externally.

Issue

The Kill() function currently returns an error immediately if vmm.Stop() fails (e.g. if the process is already dead/ESRCH). This skips the critical network.Cleanup() step.

Impact

This causes tap devices (e.g., tap0_urunc) to pile up in the namespace during crash loops, potentially exhausting resources.

[cmainas]

Hello @goyalpalak18 ,

thank you for opening this issue. Have you encountered such case? The kernel will clean up the network namespace (and all interfaces) as soon as all process in the namespace exit.