libvirt users - May 2022 - something (qemu?) is leaking

Hi guys.

I do a simple thing which should be easy to reproduce.

-> $ virt-install -n rum1 --virt-type kvm --os-variant 
centos8 --memory $((4*1024)) 
--disk=/VMs3/rum1.qcow2,device=disk,bus=virtio --network 
network=10_3_1,model=virtio --graphics=listen=0.0.0.0 --cpu 
EPYC-Rome --vcpus 3 --cdrom 
/VMs3/CentOS-Stream-9-latest-x86_64-dvd1.iso

During manual setup in the VM I set 'hostname' to something 
and when installation begins and disk config stage takes 
place I can see - and later when VM(c9s) is ready can 
confirm - that VG name is taken from another VM 
defined/running on the host.

Host is c9s with:
qemu-kvm-7.0.0-1.el9.x86_64
libvirt-daemon-8.2.0-1.el9.x86_64
5.14.0-86.el9.x86_64

Does anybody see this/similar?
many thanks, L.

On 5/23/22 11:19, lejeczek wrote:
> Hi guys.
> 
> I do a simple thing which should be easy to reproduce.
> 
> -> $ virt-install -n rum1 --virt-type kvm --os-variant centos8 --memory
> $((4*1024)) --disk=/VMs3/rum1.qcow2,device=disk,bus=virtio --network
> network=10_3_1,model=virtio --graphics=listen=0.0.0.0 --cpu EPYC-Rome
> --vcpus 3 --cdrom /VMs3/CentOS-Stream-9-latest-x86_64-dvd1.iso
> 
> During manual setup in the VM I set 'hostname' to something and
when
> installation begins and disk config stage takes place I can see - and
> later when VM(c9s) is ready can confirm - that VG name is taken from
> another VM defined/running on the host.
I'm no LVM expert, but I always thought that installer has some defaults
built in and thus it's kind of expected if you went with defaults.

But I'm kind of failing why is this a problem since all you're giving to
the guest is a single qcow2 disk which is not shared between two
domains. Maybe I'm misunderstanding something?

Michal