From mboxrd@z Thu Jan 1 00:00:00 1970 From: George Dunlap Subject: Re: Xen 4.3 development update, and stock-taking Date: Thu, 17 Jan 2013 16:49:36 +0000 Message-ID: <50F82BA0.306@eu.citrix.com> References: <50F7CDBF02000078000B6A95@nat28.tlf.novell.com> <50F7DCA2.1070405@eu.citrix.com> <50F801F102000078000B6CEE@nat28.tlf.novell.com> <50F80378.4070105@eu.citrix.com> <50F815AC02000078000B6DC2@nat28.tlf.novell.com> <50F80B95.3010005@eu.citrix.com> <50F8270902000078000B6E48@nat28.tlf.novell.com> <50F81D33.9030200@eu.citrix.com> <50F8318C02000078000B6ED6@nat28.tlf.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <50F8318C02000078000B6ED6@nat28.tlf.novell.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: "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org On 17/01/13 16:14, Jan Beulich wrote: > And to be clear - unless someone manages to eliminate the > "conceptually wrong" argument above, I'm intending to veto any changes > that violate the model set by the specification. Jan Just for my information, could you describe what you think is "conceptually wrong" about leaving boot services for dom0? I would consider Xen+dom0 to be two halves of the "Xen system", and so leaving boot services on until dom0 gets a chance to fix up quirks doesn't seem to me any different than leaving it on when booting to Linux directly. If the spec doesn't explicitly say "hypervisor", then I would think "kernel" in a Xen system would conceptually include both Xen and dom0. -George (And sorry for responding 3 times to the same mail!)