Description of problem: (from bug 2075736) After being hammered for a day virsh (virtqemud) gets slower and slower. For instance, undefining a VM goes from fractions of a second to seconds. Version-Release number of selected component (if applicable): libvirt-daemon-driver-qemu-8.1.0-2.fc36.x86_64 How reproducible: 100% Steps to Reproduce: 1. Set up virtqemud so it doesn't restart (workaround to bug 2075736, but reasonable) 2. Spend a day creating and deleting the same VMs and networks (the total doesn't grow). Actual results: By end of day, virsh is taking a second or more to do each operation. Expected results: Should be a consistent sub-second response to virsh commands. Additional info: Suggestions for how to grab virtqemud's state when this happens welcome (tricky as it is all over in a second).
Created attachment 1909268 [details] Possible backtrace of problem I'm finding virt-install is slow enough, below is the command and attached is the backtrace: sudo qemu-img create -f qcow2 -F qcow2 -b /home/pool/m.fedora-upgrade.qcow2 /home/pool/m.fedora.qcow2 Formatting '/home/pool/m.fedora.qcow2', fmt=qcow2 cluster_size=65536 extended_l2=off compression_type=zlib size=10737418240 backing_file=/home/pool/m.fedora-upgrade.qcow2 backing_fmt=qcow2 lazy_refcounts=off refcount_bits=16 sudo virt-install \ --connect=qemu:///system --check=path_in_use=off --graphics=none --virt-type=kvm --noreboot --console=pty,target_type=serial --vcpus=4 --memory=5120 --cpu=host-passthrough --network=network:swandefault,model=virtio --rng=type=random,device=/dev/random --security=type=static,model=dac,label='1000:107',relabel=yes --filesystem=target=pool,type=mount,accessmode=squash,source=/home/pool \ --filesystem=target=source,type=mount,accessmode=squash,source=/home/libreswan/wip-misc \ --filesystem=target=testing,type=mount,accessmode=squash,source=/home/libreswan/wip-misc/testing \ --name=m.fedora \ --os-variant=fedora36 \ --disk=cache=writeback,path=/home/pool/m.fedora.qcow2 \ --import \ --noautoconsole
This message is a reminder that Fedora Linux 36 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '36'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 36 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16. Fedora Linux 36 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.