[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] Multiple I/O domains?


  • To: "Rob Gardner" <rob.gardner@xxxxxx>
  • From: "Neugebauer, Rolf" <rolf.neugebauer@xxxxxxxxx>
  • Date: Wed, 31 Aug 2005 23:13:35 +0100
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Wed, 31 Aug 2005 22:11:46 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcWudraytftV7vtpQ7CR/UGzNMCQRgAAgQNQ
  • Thread-topic: [Xen-devel] Multiple I/O domains?

Multiple IO domains are currently not supported in 3.x. this is mainly
due to the moving of the PCI into dom0 (out of Xen). There was a
discussion on this a month back on the mailing list on how to re-enable
this, but I don't know if anyone is actively working on this at the
moment.

If you want multiple io domains you'd have to use 2.x for now. There is
a xen command option allowing you to hide pci devices from dom0 and then
the config file for a VM has an option to assign a PCI device to another
VM. AFAIK there is no cookbook for this

rolf

> -----Original Message-----
> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-devel-
> bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Rob Gardner
> Sent: 31 August 2005 22:54
> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: [Xen-devel] Multiple I/O domains?
> 
> I'd like to set up a xen system with mutliple I/O domains.
> 
> A few questions:
> 
> Is this known to work?
> 
> Should I use xen 2.0x or xen 3.x to start with. Which has better
support
> for multiple I/O domains?
> 
> Is there a cookbook someplace for doing this? A quick search didn't
> reveal anything. A few people have already given us some hints, but
the
> information is a little too sparse.
> 
> Finally, are there some requirements that aren't obvious? For
instance,
> I've got a machine with with one disk and one nic. Is that sufficient,
> or do I need additional interfaces? I'd like to be able to have just
two
> domains, one controlling the nic, the other disk. Is this possible? It
> seems like dom0 must be the driver domain for its own boot device.
> 
> Rob Gardner
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.