All of lore.kernel.org
 help / color / mirror / Atom feed
From: John McCullough <jmccullo@cs.ucsd.edu>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Problems with network-route/vif-route scripts
Date: Sun, 29 Oct 2006 18:08:52 -0800	[thread overview]
Message-ID: <20061030020852.GA609@cs.ucsd.edu> (raw)
In-Reply-To: <20061026161750.GB28762@redhat.com>

On Thu, Oct 26, 2006 at 05:17:50PM +0100, Daniel P. Berrange wrote:
> I've been attempting to get the network-route/vif-route scripts running
> instead of using the traditional bridging setup, but running into some
> puzzelling issues.

Are you using an hvm or pv guest?

Routing under hvm requires a bit of hacking.  Qemu uses /dev/tap*
devices rather than the vif*.* devices and is by default invoked in a
bridging mode (the default /etc/xen/qemu-ifup script that is invoked by
qemu-dm on launch simply adds the tap device to the bridge xenbr0).

I've found that turning the vif script executed by xend into a no-op,
changing the qemu-ifup script to invoke a vif-like script with the
correct vif and XENBUS_PATH defined, and modifying image.py to invoke
qemu-dm without the bridging.

There is a patch for image.py in
http://lists.xensource.com/archives/html/xen-users/2006-09/msg00976.html

To the list -- is there a chance that the qemu-dm network device
interaction will follow the pv naming scheme anytime soon?

-John McCullough

  reply	other threads:[~2006-10-30  2:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-26 16:17 Problems with network-route/vif-route scripts Daniel P. Berrange
2006-10-30  2:08 ` John McCullough [this message]
2006-10-30  3:22   ` Daniel P. Berrange
2006-10-30 10:22   ` Ian Pratt
2006-11-15  2:48 ` Daniel P. Berrange

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20061030020852.GA609@cs.ucsd.edu \
    --to=jmccullo@cs.ucsd.edu \
    --cc=berrange@redhat.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.