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 927620 - Destroy guest with --gracefull get unknown error
Summary: Destroy guest with --gracefull get unknown error
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libvirt
Version: 7.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Jiri Denemark
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-26 11:02 UTC by Luwen Su
Modified: 2014-06-18 00:46 UTC (History)
7 users (show)

Fixed In Version: libvirt-1.0.6-1.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-13 11:44:28 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Luwen Su 2013-03-26 11:02:58 UTC 
Description of problem:
start a guest , then #kill -STOP `pidof qemu-kvm` ; virsh destroy $guest --graceful
will get "An error occurred, but the cause is unknown" ,
not "operation failed: failed to kill qemu process with SIGTERM" in rhel6

Version-Release number of selected component (if applicable):
libvirt-1.0.3-1.el7.x86_64
qemu-kvm-1.4.0-1.el7.x86_64
kernel-3.7.0-0.36.el7.x86_64

How reproducible:
100%

1.Prepare a running guest , then
#kill -STOP `pidof qemu-kvm`
#virsh destroy $guest --graceful
error: Failed to destroy domain rhel6
error: An error occurred, but the cause is unknown

2.Then
#virsh destroy $guest
libvirtd.log get
Mar 22 14:10:07 localhost.localdomain libvirtd[26280]: End of file while reading data: Input/output error
Mar 22 14:10:11 localhost.localdomain libvirtd[26280]: internal error End of file from monitor


Actual result:
Get unknown error

Expected result:
Should be clear like rhel6:
error: Failed to destroy domain test
error: operation failed: failed to kill qemu process with SIGTERM
Comment 2 Gunannan Ren 2013-05-17 09:30:48 UTC 
proposed patch sent
https://www.redhat.com/archives/libvir-list/2013-May/msg01299.html
Comment 3 Gunannan Ren 2013-05-20 09:40:43 UTC 
commit 6459af6a434e8b363c0b15d8bc0f9be535bd278f upstream fixed this bug.

With --graceful, SIGTERM always is emitted to kill driver
process, but it won't success till burning out waiting time
in case of process being stopped.
But domain destroy without --graceful can work, SIGKILL will
be emitted to the stopped process after 10 secs which always
kills a process even one that is currently stopped.
Comment 4 Gunannan Ren 2013-05-22 13:06:30 UTC 
Jiri, I am going to set this bug to POST based on comment 3.
Comment 5 Hu Jianwei 2013-06-05 03:20:35 UTC 
Can reproduce the bug in below version:
libvirt-1.0.5-2.el7.x86_64
qemu-kvm-1.5.0-2.el7.x86_64
kernel-3.9.0-0.55.el7.x86_64

But can not reproduce in below version:
libvirt-1.0.6-1.el7.x86_64
qemu-kvm-1.5.0-2.el7.x86_64
kernel-3.9.0-0.55.el7.x86_64


1.[root@hujianweitest ~]# virsh start rhel7
Domain rhel7 started

2.[root@hujianweitest ~]# virsh list --all
 Id    Name                           State
----------------------------------------------------
 5     rhel7                          running
 -     r7_m                           shut off
 -     rhel6_local                    shut off

3. Kill the process
[root@hujianweitest ~]# 
[root@hujianweitest ~]# kill -STOP `pidof qemu-kvm`
[root@hujianweitest ~]# 

4.Destroy the domain
[root@hujianweitest ~]# virsh destroy rhel7 --graceful
error: Failed to destroy domain rhel7
error: Failed to terminate process 11063 with SIGTERM: Device or resource busy

We can get expected results, setting to verified.
Comment 6 Ludek Smid 2014-06-13 11:44:28 UTC 
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.
Note You need to log in before you can comment on or make changes to this bug.