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

Re: [Xen-devel] BUG: [?] host-only networking under HVM is broken with custom script

  • To: "Keir Fraser" <keir.fraser@xxxxxxxxxxxxx>
  • From: "Ray Barnes" <tical.net@xxxxxxxxx>
  • Date: Mon, 2 Jun 2008 05:12:49 -0400
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Mon, 02 Jun 2008 02:13:11 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=t/kyaJoHTGFPe40PjsdbMdwr0bVkhrT2uNobxPuovB6kaAQqm7S+wzYqAgr451WoPn2DasHkgC5gR+fanVxcXA9Vk2nMT2sftnskuAmirnmX8i4vFSNlRmjYKIUWokREy7MpBi1Vatrc4HyZBzP7Rt7Lb6WieRJFoClaFv9kdf8=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

On Mon, Jun 2, 2008 at 4:08 AM, Keir Fraser <keir.fraser@xxxxxxxxxxxxx> wrote:

> Couldn't you route directly to the vif, and get rid of the bridges entirely?

I could - but it would be a worse hack (IMO).  I just ran a few tests
and surprisingly, routed vifs work, however the IP for the VIF must be
set in qemu-ifup and not in the custom vif script.  Forgive my
ignorance of what goes on "behind the curtain" but it seems to me that
not being able to override qemu-ifup (i.e. specifying a script to be
run instead of qemu-ifup) is the hangup here.  So the only way I could
use straight VIFs with no bridge is if I put a bunch of 'case'
statements for each vif/IP in qemu-ifup which will break my
provisioning model a bit; it would be easier to use bridges with the
aforementioned hack.  Should this be revisited in development or am I
way off base here?


Xen-devel mailing list



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