From mboxrd@z Thu Jan 1 00:00:00 1970 From: Juergen Gross Subject: Re: [PATCH v3 01/15] xen: add xenstore domain flag to hypervisor Date: Fri, 8 Jan 2016 15:22:07 +0100 Message-ID: <568FC60F.4090605@suse.com> References: <1452258526-4797-1-git-send-email-jgross@suse.com> <1452258526-4797-2-git-send-email-jgross@suse.com> <568FD0B902000078000C4E8F@suse.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <568FD0B902000078000C4E8F@suse.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: Jan Beulich Cc: Tim Deegan , wei.liu2@citrix.com, Ian.Campbell@citrix.com, stefano.stabellini@eu.citrix.com, Andrew Cooper , ian.jackson@eu.citrix.com, xen-devel@lists.xen.org, David Vrabel , Keir Fraser , dgdegra@tycho.nsa.gov List-Id: xen-devel@lists.xenproject.org On 08/01/16 15:07, Jan Beulich wrote: >>>> On 08.01.16 at 14:08, wrote: >> --- a/xen/common/domain.c >> +++ b/xen/common/domain.c >> @@ -318,6 +318,12 @@ struct domain *domain_create(domid_t domid, unsigned int domcr_flags, >> hardware_domain = d; >> } >> >> + if ( domcr_flags & DOMCRF_xs_domain ) >> + { >> + d->is_xenstore = 1; >> + d->disable_migrate = 1; >> + } > > It only occurred to me now: Wouldn't it be worth denying the domain > creation request if there already is a xenstore domain? Hmm, the only cases where this would make sense would be: - some bug in dom0 resulting in parallel calls of init-xenstore-domain - an out-of-tree tool in dom0 (or another domain capable of creating domains) creating a domain with the xenstore flag set I'm really not sure what would be best here. Should the hypervisor really be responsible for this decision? In case it is desired, I can modify the patch accordingly (the modification would be trivial). Juergen