Bug 695180 - virsh save guest meet unexpected failed and selinux warning for cannot lookup default selinux label for the save file
Summary: virsh save guest meet unexpected failed and selinux warning for cannot lookup...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libvirt
Version: 6.1
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Laine Stump
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-11 03:44 UTC by Vivian Bian
Modified: 2011-06-21 03:28 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-21 03:28:53 UTC
Target Upstream Version:


Attachments (Terms of Use)
/var/log/messages and LIBVIRT_DEBUG=1 LIBVIRT_LOG_FILTERS="1:util 1:libvirt 1:qemu 1:remote" debug info (19.34 KB, text/plain)
2011-04-11 03:45 UTC, Vivian Bian
no flags Details
/var/log/libvirt/qemu/guest.log (8.43 KB, text/plain)
2011-04-19 06:08 UTC, Vivian Bian
no flags Details

Description Vivian Bian 2011-04-11 03:44:23 UTC
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

Comment 1 Vivian Bian 2011-04-11 03:45:05 UTC
Created attachment 491137 [details]
/var/log/messages and LIBVIRT_DEBUG=1 LIBVIRT_LOG_FILTERS="1:util 1:libvirt 1:qemu 1:remote"  debug info

Comment 3 RHEL Program Management 2011-04-11 06:00:25 UTC
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.

Comment 4 Vivian Bian 2011-04-11 07:34:01 UTC
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

Comment 5 Laine Stump 2011-04-18 20:41:43 UTC
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.

Comment 6 Vivian Bian 2011-04-19 06:08:13 UTC
Created attachment 493089 [details]
/var/log/libvirt/qemu/guest.log

Comment 7 Laine Stump 2011-06-03 21:10:33 UTC
It's still unclear exactly what the problem is here.


Note You need to log in before you can comment on or make changes to this bug.