[Bug 1228384] New: virt-install generates unwanted libvirt storage pools when running with --dry-run --print-xml
https://bugzilla.suse.com/show_bug.cgi?id=1228384 Bug ID: 1228384 Summary: virt-install generates unwanted libvirt storage pools when running with --dry-run --print-xml Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Tools Assignee: virt-bugs@suse.de Reporter: claudio.fontana@suse.com QA Contact: qa-bugs@suse.de Target Milestone: --- Found By: --- Blocker: --- For virtx/vmx2xml we need to run virt-install _just_ to generate the xml. All other features of virt-install are useless for this use case. Therefore we run virt-install with --print-xml --dry-run Still virt-install insists in creating a storage pool for the disks referenced in the domain xml. It should not, as it makes no sense under those command line options. This slows down the rest of the stack (cockpit...) as 100s of unused storage pools are loaded. The workarounds create their own problems. This needs to be addressed upstream. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1228384 Claudio Fontana <claudio.fontana@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jfehlig@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1228384 Claudio Fontana <claudio.fontana@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1228384 https://bugzilla.suse.com/show_bug.cgi?id=1228384#c1 --- Comment #1 from Claudio Fontana <claudio.fontana@suse.com> --- # 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 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1228384 https://bugzilla.suse.com/show_bug.cgi?id=1228384#c2 --- Comment #2 from Claudio Fontana <claudio.fontana@suse.com> --- (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. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1228384 https://bugzilla.suse.com/show_bug.cgi?id=1228384#c3 Charles Arnold <carnold@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|virt-bugs@suse.de |carnold@suse.com --- Comment #3 from Charles Arnold <carnold@suse.com> --- According to the man page, using --print-xml does create storage and therefore storage pools are also created. To disable this, you must use --dry-run. I have created a patch that keys off the --dry-run option and if used, will not create the storage pools. Currently in the Virtualization repo. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1228384 https://bugzilla.suse.com/show_bug.cgi?id=1228384#c5 Charles Arnold <carnold@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #5 from Charles Arnold <carnold@suse.com> --- The fix should show up in Tumbleweed soon. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com