From: Ewan Mellor Subject: Re: [PATCH] [RFC] Intercept some xm commands on HVM Date: Fri, 20 Oct 2006 22:47:33 +0100 Message-ID: <20061020214733.GC21591@leeni.uk.xensource.com> References: <1161378756.17852.12.camel@lt2.watson.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <1161378756.17852.12.camel@lt2.watson.ibm.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Stefan Berger Cc: Xen-devel List-Id: xen-devel@lists.xenproject.org On Fri, Oct 20, 2006 at 05:12:36PM -0400, Stefan Berger wrote: > Hello! > > I find some of the xm commands when applied to an HVM domain > misleading: > > xm shutdown - behaves like 'xm destroy' unlike the > paravirtualized case that gracefully > shuts down a domain; use 'destroy' instead > for HVM > xm migrate / save - returns > Error: /usr/lib/xen/bin/xc-save ... failed > > The attached patch intercepts only those commands now and returns a > 'better' message. These commands aren't necessarily unsupported for HVM domains -- they need PV driver support, but that's not a fundamental limitation. We need a decent mechanism for guest capability interrogation, that's for sure, so that we can give better diagnostics; I'd like to see this mechanism in Xen 3.0.4. For now, I don't think we can reject these commands unconditionally. Ewan.