On Sun, Sep 22, 2013 at 09:59:08AM +0800, bigclouds wrote:
> i find a bug fixed 1 year ago.
> type=VIRT_CONTROL msg=audit(1379813127.359:42015): user pid=1637 uid=0
> auid=4294967295 ses=4294967295 subj=system_u:system_r:virtd_t:s0-s0:c0.c1023
> msg='virt=kvm op=start reason=booted vm="testname-1"
> uuid=24f7e975-9aa5-4a14-b0f0-590add14c8b5 vm-pid=-1 exe="/usr/sbin/libvirtd"
> hostname=? addr=? terminal=? res=failed'
> but in my case, i have 'setenforce 0',
If there's an SELinux-related regression, we should understand it, not
hide it with `setenforce 0` ;-)
Which is the version of your selinux-policy rpm?
> i had not noticed both of you online on irc channel. how could you review my
> code and talk about it.
Sorry, we have plenty of holidays this time of year.
You are most welcome to post the code on-list, or to vdsm's gerrit (if
you would like to contribute it to vdsm_hooks).
vdsm-devel mailing list