All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Rhett Aultman <jaultman@cise.ufl.edu>
To: xen-devel@lists.xensource.com
Subject: VIFs
Date: Sat, 03 Dec 2005 14:21:40 -0500	[thread overview]
Message-ID: <4391F044.2010404@cise.ufl.edu> (raw)

Hello again, gang.

I've been working with Xen on and off through this past semester and I'm
narrowed down to a few more, final questions.

First off, when a new domU is created, how/where are the dom0 vifs that
bridge to that domU getting created?
Secondly, I want to tweak the dom0 VIF associated with a given domU.  I
want the dom0 VIF to stay live and do something basic like log when
packets arrive to it.  Where is the code for these VIFs?

Finally, I want to make sure I actually understand what's going on in
Xen network virtualization.  It looks like the default behavior can be
summed up as follows:

- New domU is created.  A VIF for it in dom0 is created.  The dom0 VIF
is placed in the xen-br0 bridge.
- When a packet arrives on the actual physical network hardware, the
packet is bridged to all the dom0 VIFs on the bridge
- When a VIF associated with a domU receives a packet, it transfers the
packet via the Xenbus to the hardware driver in the domU, making the
packet's arrival transparent.

If I'm off-base, I really would like to be corrected.  I've been
wrestling with Xen, bridging, routing, iptables, etc for a while now and
I'm really trying to get the hang of Xen's networking.

--
Rhett.

                 reply	other threads:[~2005-12-03 19:21 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4391F044.2010404@cise.ufl.edu \
    --to=jaultman@cise.ufl.edu \
    --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.