WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] [PATCH] [RFC] Intercept some xm commands on HVM

To: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] [PATCH] [RFC] Intercept some xm commands on HVM
From: Stefan Berger <stefanb@xxxxxxxxxx>
Date: Fri, 20 Oct 2006 17:12:36 -0400
Delivery-date: Fri, 20 Oct 2006 14:13:04 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
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.

Signed-off-by: Stefan Berger <stefanb@xxxxxxxxxx>

Attachment: xm-block-commands-for-hvm.diff
Description: Text Data

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>