On 02/02/2012 12:24 PM, Marc-André Lureau wrote:
Hi,
On Sun, Jan 8, 2012 at 5:55 PM, Daniel P. Berrange <berrange(a)redhat.com> wrote:
> On Fri, Jan 06, 2012 at 02:27:42PM -0700, Eric Blake wrote:
>> I hit a VERY weird testsuite failure on rawhide, which included
>> _binary_ output to stderr, followed by a hang waiting for me
>> to type something! (Here, using ^@ for NUL):
>>
>> $ ./commandtest
>> TEST: commandtest
>> WARNING: gnome-keyring:: couldn't send data: Bad file descriptor
>> .WARNING: gnome-keyring:: couldn't send data: Bad file descriptor
>> .WARNING: gnome-keyring:: couldn't send data: Bad file descriptor
>> WARNING: gnome-keyring:: couldn't send data: Bad file descriptor
This was a bug in the testsuite,
I failed to create a kvm domain using qemu:///session because qemu-kvm
fails with this error when executed. I tried to track it down, but
it's quite hard to follow it in gdb. I saw bind() failing too, so I
turned off selinux and everything worked again.
But you are describing what sounds like a bug in either libvirt itself,
or more likely, in the SELinux policy for forbidding something that
libvirt needs for qemu:///session to work correctly. Alas,
qemu:///session doesn't get much good testing; so I haven't hit this if
only because I haven't tried using it lately. Can you file a bugzilla
report with the actual AVC created when running SELinux in permissive mode?
--
Eric Blake eblake(a)redhat.com +1-919-301-3266
Libvirt virtualization library
http://libvirt.org