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


Re: [Xen-devel] [PATCH 07/14]: libxenlight, destroy device-model only fo

To: Andres Lagar-Cavilla <andres@xxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH 07/14]: libxenlight, destroy device-model only for hvm domains
From: Vincent Hanquez <vincent.hanquez@xxxxxxxxxxxxx>
Date: Tue, 1 Dec 2009 06:14:42 +0000
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Stefano Stabellini <Stefano.Stabellini@xxxxxxxxxxxxx>
Delivery-date: Mon, 30 Nov 2009 22:06:22 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4B14196D.8010603@xxxxxxxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4B14196D.8010603@xxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.20 (2009-06-14)
On Mon, Nov 30, 2009 at 07:13:49PM +0000, Andres Lagar-Cavilla wrote:
> Destroy device-model only for hvm domains.
> Signed-off-by: Andres Lagar-Cavilla <andres@xxxxxxxxxxxxxxxx>

> # HG changeset patch
> # User Andres Lagar-Cavilla <andres@xxxxxxxxxxxxxxxx>
> # Date 1259253630 18000
> # Node ID 05e2dad9b117e80c8daf55a30cb7eeda3fda4764
> # Parent  a19e1cef7b72a90b3cc9c8c38dadf06aaf413155
> Destroy device-model only for hvm domains.

no, we need to destroy the device-model if it is present,
and beeing PV doesn't means you don't have a device-model.


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>