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:
On one of our testing machine , always failed to save a running guest . Tried both "setenforce 0" and "setenforce 1" will always fail to save the guest , and encounter selinux warning in /var/log/messages log 

Version-Release number of selected component (if applicable):
libvirt-0.8.7-16.el6.x86_64
qemu-kvm-0.12.1.2-2.153.el6.x86_64
kernel-2.6.32-125.el6.x86_64

How reproducible:
an occasional situation to meet this problem 

Steps to Reproduce:
1. # setenforce 1
2. # virsh start guest 
3. # virsh save guest /tmp/guest.save
4. # virsh destroy guest
5. # getenforce 0
6. # virsh start guest
7. # virsh save guest /tmp/guest.save
  
Actual results:
error: Failed to save domain local to /tmp/local.save
error: operation failed: domain save job: unexpectedly failed


Expected results:


Additional info:
# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/mpathap5   97G   51G   41G  56% /
tmpfs                 990M  376K  990M   1% /dev/shm

Created attachment 491137 [details]
/var/log/messages and LIBVIRT_DEBUG=1 LIBVIRT_LOG_FILTERS="1:util 1:libvirt 1:qemu 1:remote"  debug info

Since RHEL 6.1 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.

there is no AVC audit errors , and it is not a high reproducible bug to all of the machines , so it is not a Testblocker . QA suggest fix it on 6.2

I don't see any errors in the log related to selinux. The only error I see is this:

qemuDomainWaitForMigrationComplete:4662 : operation failed: domain save job: unexpectedly failed

It's possible there is a more revealing message in the domain's qemu log file (/var/log/libvirt/qemu/domainname.log). Can you attach that file?

Also, unless there really is an error log in /var/log/messages that mentions selinux, we should change the summary to be more appropriate.

Created attachment 493089 [details]
/var/log/libvirt/qemu/guest.log

It's still unclear exactly what the problem is here.