From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mike Wray Subject: Re: Xend vnet support to be removed Date: Mon, 12 Dec 2005 08:45:00 +0000 Message-ID: <439D388C.3030404@hp.com> References: <20051209161009.GI9336@leeni.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20051209161009.GI9336@leeni.uk.xensource.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: Ewan Mellor Cc: Xen-devel List-Id: xen-devel@lists.xenproject.org Ewan Mellor wrote: > Unless someone speaks up, Xend vnet support will be removed. It is broken, > unused, and unloved (as far as I know). This is the xm vnet-list, > vnet-create, and vnet-delete commands, as well as all the Xend support behind > that (XendVnet.py, SrvVnetDir.py, plus plumbing in xm/main.py and > XendClient.py). > > Cheers, > > Ewan. As the developer of the vnet count I'm speaking up for this code. As far as I am aware it is neither broken nor unused, and I have recently submitted patches to this list updating the code. The code is in active development and I will be continuing to maintain it. So please don't remove it. Mike