RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. # for i in {1..1000}; do virt-sandbox-service create -C -u httpd.service apache$i; done
2. # for i in {1..100}; do virt-sandbox-service start apache$i & done
3. # time virt-sandbox-service list -r |wc -l

Actual results:

# time virt-sandbox-service list|wc -l
1000

real	0m0.877s
user	0m0.847s
sys	0m0.026s


# time virsh -c lxc:/// list |wc -l
74

real	0m0.196s
user	0m0.018s
sys	0m0.009s

Notes, need to minus 2 title line nd 1 end line , so total containers are 74-2-1=71.

# time virt-sandbox-service list -r |wc -l
73

real	3m20.606s
user	0m11.730s
sys	0m1.394s

Notes, it's more slow than 'virsh list', in addition, the result is inconsistent with above, in other words, the result(73 running containers) is incorrect.


# ps -ef|grep virt-sandbox-service-util|grep -v grep|wc -l
71

Notes, it indeed has 71 running containers not 73.

Expected results:
To improve performance for listing running sandbox containers, and make sure the result is correct.

Additional info:

(In reply to Alex Jia from comment #0)
> Description of problem:
> 
To create 1000 containers then start some containers, and executing 'virt-sandbox-service list -r' to check running container number, you will need to wait more than 1m, and running number is inconsistent with real case.


> Version-Release number of selected component (if applicable):
# rpm -q selinux-policy libvirt-sandbox libvirt systemd
selinux-policy-3.12.1-56.el7.noarch
libvirt-sandbox-0.2.0-1.el7.x86_64
libvirt-1.1.0-1.el7.x86_64
systemd-204-9.el7.1.x86_64
> 
> How reproducible:
awlays

> Additional info:

In libvirt-sandbox >= 0.5.0, the 'virt-sandbox-service list' command has been deleted. Now that configurations are loaded into libvirt, a regular 'virsh list' will show them. If there are any problems with performance of virsh, please file a bug against libvirt.