[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] calling vif-script


  • To: xen-devel@xxxxxxxxxxxxxxxxxxxxx
  • From: Kero-Chan <kerochan2@xxxxxxxxx>
  • Date: Wed, 19 Jan 2005 03:11:42 +0100
  • Delivery-date: Wed, 19 Jan 2005 02:30:21 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=HFrhbOGGUn+1Ma7KURV5CxOeb8jprAqCR16RB3oTRpmW8nt16gEf7WYy7REY0kGhUBRyQFZR7+xlkca3r40fmdAZvJiPEov4Ig050d9LaFgskcY0foP1KwCcDPytujymy0Ne6TPKed2T2Ixzg/nAeVDEKxtEMbMsz9AqLxY6pJ8=
  • List-id: List for Xen developers <xen-devel.lists.sourceforge.net>

On Wed, 19 Jan 2005 02:12:18 +0100, Kero-Chan <kerochan2@xxxxxxxxx> wrote:
> vif-route does not currently work. It's OK for a single domU, but if I
> start more domains, all the vifs get the same IP! Each vif would need
> a separate IP for routing to work.
> vif-route doesn't set up the route either.
> So what would be a good scheme? 169.254.X.Y for vifX.Y?
> A domain may get different vifs at different times, and a different IP
> for the vif would interfere with using NFS root from dom0 (nfs_server
> would be always different).
> What about a vif_ip or similar option in the domain configuration file?

OK sorry. I realised my previous post is plain wrong.

-- 
/Varga Péter/


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.