All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Theurer <habanero@us.ibm.com>
To: Felipe Alfaro Solana <lkml@mac.com>
Cc: xen-devel@lists.sourceforge.net, bjoern.sessler@web.de
Subject: Re: allocating virtual nic to domain0
Date: Thu, 20 Jan 2005 10:28:16 -0600	[thread overview]
Message-ID: <41EFDC20.90402@us.ibm.com> (raw)
In-Reply-To: <AA5D54AC-6AFB-11D9-9A48-000D9352858E@mac.com>

Felipe Alfaro Solana wrote:

> On 20 Jan 2005, at 15:02, Andrew Theurer wrote:
>
>> Björn Sessler wrote:
>>
>>> Hi Andrew,
>>>
>>> i have a setup with 2 bridges, one on ethertap tap0 serving internal 
>>> services like nfs for xenU domains and one on separate bridge eth0 
>>> for outside communication. so xen0/xenU internal traffic won't 
>>> effect the bridge on eth0 and performance is much better... you need 
>>> to define the mac in config-file, because with dynamic configuration 
>>> both eth-devices in xenU will have same mac.
>>>
>> Actually, what I wanted to do was assign a xen virtual front-end 
>> ethernet to domain0, in a similar manner that one would assign one to 
>> another domain (nics = 1 in config file).  I can't seem to do that 
>> for domain0.  It seems like the options for domain0 ae a bit limited.
>
>
> Sorry, I don't understand what you mean. Are you saying no network 
> interfaces are available in domain0? domain0 has access to all 
> physical interfaces installed on your machine. For example, I have a 
> 3c59x and a RTL8139 which are both accessible from domain0 as eth0 and 
> eth1, respectively.
>
I would like to have one device per domain: domain0 has scsi 
controller1, domin2 has network adapter 1, etc.  In order to do this, 
domain0 still needs network access.

-Andrew


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl

  reply	other threads:[~2005-01-20 16:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-20  9:49 allocating virtual nic to domain0 Björn Sessler
2005-01-20 14:02 ` Andrew Theurer
2005-01-20 15:55   ` Felipe Alfaro Solana
2005-01-20 16:28     ` Andrew Theurer [this message]
2005-01-20 16:32       ` Mark Williamson
  -- strict thread matches above, loose matches on Subject: below --
2005-01-19 21:59 Ian Pratt
2005-01-19 21:23 Andrew Theurer
2005-01-19 21:51 ` Felipe Alfaro Solana

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=41EFDC20.90402@us.ibm.com \
    --to=habanero@us.ibm.com \
    --cc=bjoern.sessler@web.de \
    --cc=lkml@mac.com \
    --cc=xen-devel@lists.sourceforge.net \
    /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.