[prev in list] [next in list] [prev in thread] [next in thread] 

List:       fedora-xen
Subject:    [Fedora-xen] SElinux causes kernel bug on F7(?)
From:       Felix Schwarz <felix.schwarz () web ! de>
Date:       2007-07-26 10:12:42
Message-ID: 46A8739A.6060500 () web ! de
[Download RAW message or body]

Hi,

after upgrading my SElinux on Fedora 7 (x86_64) to selinux-policy-2.6.4-28.fc7 
and selinux-policy-targeted-2.6.4-28.fc7, I can't start Xen guests anymore. 
Every time I do 'xm create xenguest' I get a message "invalid opcode: 0000 [2] 
SMP" on all consoles together with some long call traces in syslog [1].

Immediately before I updated SElinux, the guest creation failed due to losetup 
policy restrictions. After the update, I get "invalid opcode" messages. If I put 
SElinux into permissive mode, I can at least start the xen guest. I think it is 
the same problem as in bug 248834 [2].

So my question is:
* Is it really SElinux which causes the problem?
* Are there other Xen users out there which can reproduce this problem?
* Is this the right list to ask this question or should I ask on the SElinux
   list?
* How can I help to fix this problem?

Thank you very much
fs

[1] https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=159998
[2] https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=248834

--
Fedora-xen mailing list
Fedora-xen@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-xen
[prev in list] [next in list] [prev in thread] [next in thread]