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.
Bug 2109460 - unexpected error and warning in the libvirt log when destroy vm
Summary: unexpected error and warning in the libvirt log when destroy vm
Keywords:
Status: CLOSED DUPLICATE of bug 2121141
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: libvirt
Version: 9.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Michal Privoznik
QA Contact: zhentang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-07-21 10:11 UTC by yalzhang@redhat.com
Modified: 2022-08-25 10:01 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-08-25 10:01:17 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-128600 0 None None None 2022-07-21 10:16:07 UTC

Description yalzhang@redhat.com 2022-07-21 10:11:08 UTC 
Description of problem:
unexpected error and warning in the libvirt log when destroy vm

Version-Release number of selected component (if applicable):
libvirt-8.5.0-2.el9.x86_64
qemu-kvm-7.0.0-9.el9.x86_64
kernel-5.14.0-127.el9.x86_64

How reproducible:
100%

Steps to Reproduce:
1. enable virtqemud's log;
2. start a vm and destroy it, then check the log, there are several errors:
# grep error /var/log/libvirt/libvirtd.log
2022-07-21 05:02:40.507+0000: 81110: error : virProcessRunInFork:1361 : internal error: child reported (status=125): Kernel does not provide mount namespace: No such file or directory
2022-07-21 05:02:40.507+0000: 81110: error : virProcessRunInFork:1365 : Kernel does not provide mount namespace: No such file or directory
2022-07-21 05:02:40.510+0000: 81110: error : virProcessRunInFork:1361 : internal error: child reported (status=125): Kernel does not provide mount namespace: No such file or directory
2022-07-21 05:02:40.510+0000: 81110: error : virProcessRunInFork:1365 : Kernel does not provide mount namespace: No such file or directory

# grep warning /var/log/libvirt/libvirtd.log
2022-07-21 03:35:41.906+0000: 7200: warning : qemuBlockRemoveImageMetadata:2969 : Unable to remove disk metadata on vm avocado-vt-vm1 from /var/lib/libvirt/images/RHEL-9.1.0-20220520.0-x86_64-ovmf.qcow2 (disk target sda)


Actual results:
unexpected error and warning in the libvirt log when destroy vm

Expected results:
should be no such error or warning

Additional info:
Comment 1 Jaroslav Suchanek 2022-08-02 07:56:07 UTC 
Michal, have a look please.
Comment 2 yalzhang@redhat.com 2022-08-25 08:38:45 UTC 
Hi Michal， is this the duplicate bug as bug 2121141?
Comment 3 Michal Privoznik 2022-08-25 08:52:20 UTC 
Yes, I believe so. Huh, I haven't realized this bug exists, sorry. I could have backported the patch earlier.
Comment 4 yalzhang@redhat.com 2022-08-25 10:01:17 UTC 
(In reply to Michal Privoznik from comment #3)
> Yes, I believe so. Huh, I haven't realized this bug exists, sorry. I could
> have backported the patch earlier.

Never mind, I will close this bug as duplicate. Thank you for confirmation.
And I have tested the scratch build, there is no error messages any more like in comment 0.

*** This bug has been marked as a duplicate of bug 2121141 ***
Note You need to log in before you can comment on or make changes to this bug.