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

Re: [Xen-devel] [PATCH] fix vmx configuration after nics=n option is rem

To: "Ling, Xiaofeng" <xiaofeng.ling@xxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] fix vmx configuration after nics=n option is removed.
From: Ewan Mellor <ewan@xxxxxxxxxxxxx>
Date: Tue, 13 Dec 2005 10:59:38 +0000
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 13 Dec 2005 11:01:12 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <439E92FE.40606@xxxxxxxxx>
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>
References: <439E92FE.40606@xxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
On Tue, Dec 13, 2005 at 05:23:10PM +0800, Ling, Xiaofeng wrote:

> # HG changeset patch
> # User Xiaofeng Ling <xiaofeng.ling@xxxxxxxxx>
> # Node ID 6c201a2164c232cf07983f3b47a963e8ce7f5736
> # Parent  7f2ccea5a4ec96af72e83c13ee25845e5d2cbb61
> change the NIC configuration accordingly after remove "nics=n"
> otherwise, nics=-1 will be passed to device model and cause device
> model exiting.
> 
> Signed-off-by: Xiaofeng Ling <xiaofeng.ling@xxxxxxxxx>

Applied, thank you.

I deliberately didn't touch the nics part of the VMX configuration, so that I
didn't break anything ;-(  It might be worth coming up with a way to test
Xend's VMX path without having the appropriate hardware available, so that we
could try and reduce the risk of doing this again.

Ewan.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

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