(In reply to Claudio Fontana from comment #1) > # virsh pool-list --all > > # virt-install --print-xml --dry-run --noautoconsole --check all=off > --virt-type kvm --machine pc --os-variant detect=on,require=off --name > ubuntu20 --metadata title=ubuntu20 --memory 4096 --cpu > host-passthrough,check=none,migratable=on --vcpus > 4,sockets=4,cores=1,threads=1 --iothreads 4 --watchdog i6300esb,action=none > --graphics vnc --video model.type=cirrus --events on_crash=restart --disk > device=disk,path=/vm_testboot/ubuntu20/ubuntu20.qcow2,target.bus=virtio, > driver.cache=none,type=file --network network=default,model=virtio-net > --controller type=virtio-serial,model=virtio --channel > unix,mode=bind,target_type=virtio,name=org.qemu.guest_agent.0 --channel > qemu-vdagent,source.clipboard.copypaste=on,target.type=virtio --rng > /dev/urandom --memballoon none > > # virsh pool-list --all > > Name State Autostart > -------------------------------- > ubuntu20 active yes same problem happens with virt-xml (which calls virt-install in the background). We should find a way to at the very least optionally disable this pernicious behavior.