This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-users] 32-bit OS images

What is your reason for wanting to do passthrough I/O?  The only really good reason I can think of for it is that you have an application that requires very high throughput and extremely low latency.  Otherwise the bridge should be fine, and I can think of several reasons why you don't want to use passthrough I/O.  One of which is the one you mentioned - migration will be worthless because your domUs will be hardware dependent.

So, if you're still insistent upon doing passthrough I/O, then, yes, you'll need one network card for every domU you have running.


>>> On Thu, Apr 24, 2008 at  2:39 PM, Asim <linkasim@xxxxxxxxx> wrote:

>  2) You don't want to do direct NIC access to a domU, you want to use a
> bridge.  By default XEN creates a bridge (can't remember what they're
> calling it these days) that bridges eth0 to all of your domUs.  This should
> allow you to use your single network card with as many domUs as you have on
> your system.

I want to do passthrough I/O for my specific needs and not use virbr0.
I believe
this will also disable migration if am not wrong? So, to do a direct NIC access
I think I should hide this PCI from Domain-0, so will need a second additional


This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR.

Xen-users mailing list
<Prev in Thread] Current Thread [Next in Thread>