On Wed, Jan 07, Konrad Rzeszutek Wilk wrote: > On Wed, Jan 07, 2015 at 10:53:06AM +0100, Olaf Hering wrote: > > Its my understanding that the reported SELinux failure is not only > > related to the context= mount option, but also to the socket passing > > from systemd. > > I couldn't spot any errors in SELinux for this. Perhaps I had misconfigured?
Last year you said xenstored did not start, even with patch #1 applied. I dont know if you added the required fstab changes. So if current staging works fine with SELinux enabled we could go with this change for the service file, instead of the wrapper: ExecStart=/usr/bin/env $XENSTORED --no-fork $XENSTORED_ARGS Does that work for you? If yes, lets get rid of the XENSTORED_TRACE= boolean and use a new XENSTORED_ARGS= variable instead. That would make patch #7 alot simpler. Olaf _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
