Bug 1820493

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.

I think the bug is getting better on RHEL9:
Packages:
cockpit-machines-269-1.el9.noarch
cockpit-269-1.el9.x86_64
libvirt-8.4.0-1.el9.x86_64
libvirt-dbus-1.4.1-5.el9.x86_64

1. Login the cockpit web console with root, prepare 25 VMs.
 Use follow script to create multiple VMs
#!/bin/bash
time=$(date "+%Y-%-m-%-d")
a='B'
while [ $a != '_' ];do
vmName="fedora33-$time-$a"
diskPath="/var/lib/libvirt/images/$vmName.qcow2"
touch $diskPath
virt-install --name $vmName --os-variant fedora33 --memory 1 --wait -1 --disk $diskPath --print-xml=1 > /tmp/xml && virsh define /tmp/xml && virsh start $vmName
a=`echo $a | tr B-Z C-Z_`
done	

2.  Create user sysadmin and add it to libvirt and libvirtdbus groups:
# useradd -G libvirt,libvirtdbus sysadmin
	
3. Login the cockpit web console use sysadmin, can see and manage the VM (Pause).
	
4. Change configuration in libvirt.conf:
on RHEL9:
# vi /etc/libvirt/virtqemud.conf
access_drivers = [ "polkit" ]	

5. On RHEL9, restart virtqemud:
# systemctl restart virtqemud	

6. Refresh the cockpit page	
There will be no vm listed

7. Add rules:
# cat /usr/share/polkit-1/rules.d/libvirt-dbus.rules
// Allow libvirt-dbus running in dedicated account to use libvirt

polkit.addRule(function(action, subject) {
    if ((action.id == "org.libvirt.unix.manage" || action.id.indexOf("org.libvirt.api.") == 0) &&
        subject.user == "libvirtdbus") {
        return polkit.Result.YES;
    }
});

6. Refresh the cockpit page, vms can be listed now, and it took several seconds to see the VMs on the page which is acceptable
Try to manage the vm, it can be managed .
I tried 2 env, one need about 5s to start to list vms, and totally 10s to see all the vms.
The other one need about 8s to start to list vms, and totally 15s to see all the vms.	

7. Clear the vms:
# for arg in `virsh list --all| grep -i fedora33 |awk -F" " '{print $2}' `; do virsh destroy $arg ; done

Pavel, please triage this one. Thanks.