From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ewan Mellor Subject: Re: No network device problem in -testing Date: Fri, 3 Feb 2006 14:00:11 -0800 Message-ID: <20060203220011.GB3075@localhost.localdomain> References: <5d7aca950602022143m1f9b9e75y178228dcac53fbc7@mail.gmail.com> <5d7aca950602030551w3c2184afvbc90c0a8cfc289c7@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <5d7aca950602030551w3c2184afvbc90c0a8cfc289c7@mail.gmail.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: NAHieu Cc: Xen-devel List-Id: xen-devel@lists.xenproject.org On Fri, Feb 03, 2006 at 10:51:32PM +0900, NAHieu wrote: > On 2/3/06, Christopher Clark wrote: > > try adding this to your config: > > > > vif = [ '' ] > > > > Thanks, Christopher. That works, but it surprises me: it seems that > previously I didnt need to specify this parameter. Something changes > recently in xend? > > Probably it is better to leave this parameter "on" by default, so the > virtual domain always has NIC, by default. This change was made on Dec 13. Previously, the nics= option and the vif option interacted in unexpected ways (nics=0 did not necessarily mean 0 vifs, for example). This way vif and vbd configuration behaves the same, and there are no concealed defaults to confuse people. Ewan.