ARM64 instance deletion leaves nvram files

[rohityadavcloud]

problem

When expunging KVM arm64 instances, it leaves nvram/fd files which are not removed. This isn't an issue as the file are generally small in size, but it would be great if CloudStack cleans them up.

versions

ACS 4.20.0, on RPi5/ARM64 hosts

The steps to reproduce the bug

1. Create a ARM64 instances and destroy it (note its internal instance name, such as i-2-970-VM)
2. Go to the host where the instance was running, and check /var/lib/libvirt/qemu/nvram/ for the the instance by internal name (i.e. i-2-970-VM)

What to do about it?

ARM64 destroy/expunge should properly cleanup all additional files and configs - such as the nvram fd