Hi, Thanks for you reply. I already tried the mentioned commands before, but it did not see the hint up until now: Vagrant-libvirt plugin removed box only from you LOCAL ~/.vagrant/boxes directory >From libvirt storage pool you have to delete image manually(virsh, virt-manager or by any other tool)
I also had the vagrant virtualbox image debian/buster64 version 10.3.0 in use, after deleting volume /var/lib/libvirt/images/debian-VAGRANTSLASH-buster64_vagrant_box_image_10.3.0.img from the default pool as hinted above everything seems to work, it was like the vagrant with libvirt provider was trying to start the virtualbox image somehow. Don't know how this happened I thought vagrant had native support for virtualbox and not through libvirt, but I see that I can't have both started at the same time (there are in different directories ~/lv-buster and ~/vb-buster), get this error in lv-buster when vb-buster is already started: Call to virDomainCreateWithFlags failed: internal error: process exited while connecting to monitor: ioctl(KVM_CREATE_VM) failed: 16 Device or resource busy 2020-04-22T19:06:13.421798Z qemu-system-x86_64: failed to initialize KVM: Device or resource busy And this fatal error in vb-buster when lv-buster is already started: The guest machine entered an invalid state while waiting for it to boot. Valid states are 'starting, running'. The machine is in the 'gurumeditation' state. But this is probably a bug in vagrant itself? I'm new to vagrant my apologies for the incorrect bug report. Kind regards, Pascal
