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/
Home Products Support Community News


[Xen-devel] [PATCH] [Xm-test] Fixes for some test cases that migrate or

To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] [PATCH] [Xm-test] Fixes for some test cases that migrate or suspend/resume VMs
From: Stefan Berger <stefanb@xxxxxxxxxx>
Date: Tue, 08 May 2007 09:47:48 -0400
Cc: Ewan Mellor <ewan@xxxxxxxxxxxxx>
Delivery-date: Tue, 08 May 2007 06:07:20 -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
Some test cases where a VM is suspended/resumed or migrated do not
properly delete the VM configuration using 'xm delete' when 'xm' is run
in Xen-API mode. It seems that 'xm destroy' is necessary since these
operations lead VMs to become 'xend - managed'. Adding them to the list
of managed domains before executing those operations will call 'xm
destroy' when the test finishes and keep the domain list clean.

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

Attachment: xend-xspolicy-xapi-xmtest-fixes.diff
Description: Text Data

Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] [PATCH] [Xm-test] Fixes for some test cases that migrate or suspend/resume VMs, Stefan Berger <=