From mboxrd@z Thu Jan 1 00:00:00 1970 From: Julien Grall Subject: Re: [PATCH 3/9] raisin: add QEMU upstream component Date: Thu, 16 Apr 2015 11:49:44 +0100 Message-ID: <552F93C8.2090309@citrix.com> References: <1429110900-8286-3-git-send-email-stefano.stabellini@eu.citrix.com> <552EB66F.7090105@citrix.com> <552F86EB.50803@eu.citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <552F86EB.50803@eu.citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: George Dunlap , Stefano Stabellini Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 16/04/2015 10:54, George Dunlap wrote: >>> Currently the QEMU built by Xen is installed in a Xen directory (IIRC >>> /usr/lib/xen/bin). Should not you use a similar path for raisin? Otherwise you >>> would override the QEMU installed via the distrib package >>> manager. >> >> This was done on purpose because the QEMU component built by Raisin >> should be generally usable, even without Xen. > > Do we want raisin to clobber / conflict with a system qemu by befault? > > I think if our goal is, "A Xen-focused configuration that Just Works", > putting it in /usr/lib/xen/bin is probably better. I agree, the system QEMU may use a different configuration that the user wants to use. Cheers, -- Julien Grall