From: Ryan Harper <ryanh@us.ibm.com>
To: Henry Pepper <henrypepr@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: Any suggestions on where I can find description of how the network bridging work
Date: Mon, 4 Oct 2010 21:11:06 -0500 [thread overview]
Message-ID: <20101005021106.GO30086@us.ibm.com> (raw)
In-Reply-To: <AANLkTinTWAMZwvvr8hnUddmemA3hnKMhKL=vED-2cYG5@mail.gmail.com>
* Henry Pepper <henrypepr@gmail.com> [2010-10-04 16:15]:
> Hi
>
> I'm trying to figure out how the network bridging work, focusing on:
> - How to create a network where the DomU can get a dhcp address from
> the central network.
> - How to setup the domain network so that the DomU eth0 and eth1 goes
> to the coresponding physical nics, without any chance of crosstalk
> between eth0 and eth1
> - Is it possible to do a routing network in KVM as can be done in Xen?
>
> I appreciate any hint on documentation or insights.
http://www.linux-kvm.org/page/Networking
--
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
ryanh@us.ibm.com
prev parent reply other threads:[~2010-10-05 2:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-04 21:14 Any suggestions on where I can find description of how the network bridging work Henry Pepper
2010-10-05 2:11 ` Ryan Harper [this message]
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=20101005021106.GO30086@us.ibm.com \
--to=ryanh@us.ibm.com \
--cc=henrypepr@gmail.com \
--cc=kvm@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox