When people follow the "Kali Inside Vagrant" doc (https://www.kali.org/docs/virtualization/install-vagrant-guest-vm/) they'll likely encounter this issue.

So I was thinking, the folks who maintain the Vagrant Kali boxes might want to know about this.

The issue seems to have appeared with 2022.3.1 (the first box version that has libvirt support)

This should be fixed now according to this GitLab issue: https://gitlab.com/kalilinux/build-scripts/kali-vagrant/-/issues/6

You'll probably have to do something like vagrant box remove kalilinux/rolling to remove the old version and then you could do a vagrant up again.

Yup -- this issue is fixed now (with kalilinux/rolling 2022.3.2).

To apply the fix, I did the following:
1) vagrant destroy -f
2) Remove the version-pin line from the Vagrantfile
3) vagrant box remove kalilinux/rolling --all (clear Vagrant's cached box versions)
4) vagrant up

This issue can be closed/resolved now.