Thank you, that's it!
virsh vol-list storage
VM1 /dev/storage/VM1.img
VM2 /dev/storage/VM2.img
VM3 /dev/storage/VM3.img [dead]
VM4 /dev/storage/VM4.img [dead]
A last stupid question (I don't want to make a big mistake ...): Is
virsh vol-delete VM3
virsh vol-delete VM4
the right command to get rid of the offending ones?
Am 14.05.2020 um 19:10 schrieb Alvin Starr:
virsh pool-list
you will get something like:
Name State Autostart
-----------------------------------------------
default active yes
gnome-boxes active no
windows-openstack-image active yes
then run virsh vol-list <your volume name>
and you should be able to see the volumes that are still defined.
On 5/14/20 1:01 PM, Lothar Schilling wrote:
> virsh list --all
>
> 15 VM1 running
> 16 VM2 running
>
> ps ax | grep virt
>
> 14281 ? Sl 1170:30 /usr/libexec/qemu-kvm -name VM1 [...]
> 14384 ? Sl 376:45 /usr/libexec/qemu-kvm -name VM2 [...]
>
> Am 14.05.2020 um 17:45 schrieb Alvin Starr:
>
>> List your storage pool to insure that they have been deleted from
>> the pool.
>> If they are not there anymore then check to make sure nothing is
>> running that would have the VM images open.
>>
>> On 5/14/20 11:01 AM, Lothar Schilling wrote:
>>> Hi everybody,
>>>
>>> we have a Centos 6 host with libvirtd 0.10.2. It's holding a
>>> storage pool of about 3.5 TB with 4 VMs. I decided to rearrange
>>> them, so I destroyed and undefined two of them. But now I am not
>>> able to install a new one because virsh gives me an "not enough
>>> space left". Those two undefined VMs still linger around somehow
>>> occupying a lot of that storage. How can I get rid of them?
>>>
>>> Name: storage
>>> UUID: 8b25e085-38d8-5a09-f80f-a29150f25d42
>>> Status: laufend
>>> Persistent: yes
>>> Automatischer Start: yes
>>> Kapazität: 3,54 TiB
>>> Zuordnung: 3,39 TiB
>>> Verfügbar: 155,27 GiB
>>>
>>> Thank you very much
>>>
>>> Lothar Schilling
>
>