From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Xen 4.5 Development Update (RC4) Date: Wed, 17 Dec 2014 14:41:50 -0500 Message-ID: <20141217194150.GD29130@laptop.dumpdata.com> References: <20141216161352.504FA124EF2@laptop.dumpdata.com> <20141216163451.GA18976@aepfle.de> <20141216204601.GA11551@konrad-lan.dumpdata.com> <20141217075510.GA678@aepfle.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Y1KTv-0000ZL-Ql for xen-devel@lists.xenproject.org; Wed, 17 Dec 2014 19:41:59 +0000 Content-Disposition: inline In-Reply-To: <20141217075510.GA678@aepfle.de> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Olaf Hering Cc: xen-devel@lists.xenproject.org List-Id: xen-devel@lists.xenproject.org On Wed, Dec 17, 2014 at 08:55:10AM +0100, Olaf Hering wrote: > On Tue, Dec 16, Konrad Rzeszutek Wilk wrote: > > > On Tue, Dec 16, 2014 at 05:34:51PM +0100, Olaf Hering wrote: > > > On Tue, Dec 16, konrad.wilk@oracle.com wrote: > > > > > > > In terms of bugs, we have: > > > > > > ... systemd SELinux, but its not listed. > > > > > > > > Whats your plan with the failures you see? Should I continue to be > > > concerned about that, or will all the be postponed to 4.6? > > > > I was under the impression you had some patches which would solve a > > majority of the issues? And after the discussion with Ian Jackson the > > way to exec was solved? > > No. What I did was to handle XENSTORED_TRACE which is just a bool to > pass "-T /log/file" to xenstored. I think xenstored can not access the > sockets if it was launched with a shell script as it is done now. > No idea how to solve that. Maybe "/usr/bin/env $XENSTORED" could be a > workaround for the SELinux socket access issue. But perhaps launching it > via env or sh fails either way. > > > And for the other - the SELinux context and how to figure this out - > > I thought (I will have to double-check it tomorrow) that I mentioned it might > > make sense to talk to the SELinux maintainers to see if they have any > > recommendation? > > For xen-4.5 the easy way would be to remove the context= option and let > people who build from source and who want to use SELinux put the > required options into /etc/fstab. This would also resolve the issue > Anthony is seeing, his mount or kernel does not understand context= at > all. No idea how he got into that state in his Arch Linux installation. And also remove the EnvionmentFile and such. Anyhow I've taken for spin these patches: tools/hotplug: add wrapper to start xenstored tools/hotplug: remove EnvironmentFile from xen-qemu-dom0-disk-backend.service tools/hotplug: use XENCONSOLED_TRACE in xenconsoled.service tools/hotplug: use xencommons as EnvironmentFile in xenconsoled.service tools/hotplug: xendomains.service depends on network tools/hotplug: remove XENSTORED_ROOTDIR from xenstored.service tools/hotplug: remove SELinux options from var-lib-xenstored.mount from you https://github.com/olafhering/xen.git staging-for-4.5.0 and they fixed the issues I saw. That is I can boot Fedora Core 21 with the sources being built out (plus said patches above) > > Olaf