Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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:
virsh domfstrim will get uncorrelated error
Version-Release number of selected component (if applicable):
# rpm -qa libvirt qemu-kvm virt-manager kernel
kernel-3.7.0-0.36.el7.x86_64
virt-manager-0.9.4-4.el7.noarch
libvirt-1.0.3-1.el7.x86_64
qemu-kvm-1.4.0-1.el7.x86_64
Reproduce steps:
1. prepare a guest with qemu-guest-agent installed and start the qemu-guest-agent.service, guest xml should include:
<channel type='unix'>
<source mode='bind' path='/var/lib/libvirt/qemu/r7.agent'/>
<target type='virtio' name='org.qemu.guest_agent.0'/>
<alias name='channel0'/>
<address type='virtio-serial' controller='0' bus='0'
port='2'/>
</channel>
2. # virsh domfstrim r7
error: Failed to disconnect from the hypervisor, 1 leaked
reference(s)
# echo $?
0
From # virsh help domfstrim
...
SYNOPSIS
domfstrim <domain> [--minimum <number>] [<mountpoint>]
...
We can see those two options are both not requisite, and should have
default values if needed, furthermore the error info is indeed
uncorrelated and unnecessary.
And we can see from # man virsh
...
domfstrim domain [--minimum bytes] [--mountpoint mountPoint]
Issue a fstrim command on all mounted filesystems within a running domain. It discards blocks which are not in
use by the filesystem. If --minimum bytes is specified, it tells guest kernel length of contiguous free
range. Smaller than this may be ignored (this is a hint and the guest may not respect it). By increasing this
value, the fstrim operation will complete more quickly for filesystems with badly fragmented free space,
although not all blocks will be discarded. The default value is zero, meaning "discard every free block".
Moreover, a if user wants to trim only one mount point, it can be specified via optional --mountpoint ---there is a typeset error here "a if user"
parameter.
...
There is a default value zero for "--minimum" and if user wants to trim only one mount point, then can add --mountpoint.
Actual results:
As steps.
Expected results:
Step 2 should not get that uncorrelated error.
Additional info:
This request was resolved in Red Hat Enterprise Linux 7.0.
Contact your manager or support representative in case you have further questions about the request.
Description of problem: virsh domfstrim will get uncorrelated error Version-Release number of selected component (if applicable): # rpm -qa libvirt qemu-kvm virt-manager kernel kernel-3.7.0-0.36.el7.x86_64 virt-manager-0.9.4-4.el7.noarch libvirt-1.0.3-1.el7.x86_64 qemu-kvm-1.4.0-1.el7.x86_64 Reproduce steps: 1. prepare a guest with qemu-guest-agent installed and start the qemu-guest-agent.service, guest xml should include: <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/r7.agent'/> <target type='virtio' name='org.qemu.guest_agent.0'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='2'/> </channel> 2. # virsh domfstrim r7 error: Failed to disconnect from the hypervisor, 1 leaked reference(s) # echo $? 0 From # virsh help domfstrim ... SYNOPSIS domfstrim <domain> [--minimum <number>] [<mountpoint>] ... We can see those two options are both not requisite, and should have default values if needed, furthermore the error info is indeed uncorrelated and unnecessary. And we can see from # man virsh ... domfstrim domain [--minimum bytes] [--mountpoint mountPoint] Issue a fstrim command on all mounted filesystems within a running domain. It discards blocks which are not in use by the filesystem. If --minimum bytes is specified, it tells guest kernel length of contiguous free range. Smaller than this may be ignored (this is a hint and the guest may not respect it). By increasing this value, the fstrim operation will complete more quickly for filesystems with badly fragmented free space, although not all blocks will be discarded. The default value is zero, meaning "discard every free block". Moreover, a if user wants to trim only one mount point, it can be specified via optional --mountpoint ---there is a typeset error here "a if user" parameter. ... There is a default value zero for "--minimum" and if user wants to trim only one mount point, then can add --mountpoint. Actual results: As steps. Expected results: Step 2 should not get that uncorrelated error. Additional info: