Yes, but in 2.0 you also have to hide that PCI device from domain0,
and give the parameter 'physdev_dom0_hide=(xx:xx.x)' to the xen command
line when it boots.
Xen 3.0 does not know the parameter physdev_dom0_hide any more,
because PCI enumeration was moved from xen to dom0.
Ron
Himanshu Raj wrote:

I am not sure about this. I think you can allocate pci devices to other domains using pci = ... in domain config file, no? Of course it has to be a privileged domain.

-Himanshu
Ron Arts wrote:

Ted Kaczmarek wrote:

On Sun, 2005年09月25日 at 11:32 +0200, Ron Arts wrote:

I personally bumped into the 3.0 limitation that you can't
allocate PCI devices to other domains, so I had to go back
to 2.0.
Is there a list somewhere that gives detailed differences
between 2.0 and 3.0?
Ron

Is their a bug open on this?

Uhm, I didn't create one, because there is a mail from
Ian Pratt where he basically said: um, yeah we are aware
of that, but nobody has had the time to fix it yet.
Apparently an API needs to be create to let domains
communicate with dom0 to request PCI devices, and
dom0 needs to have some way to prevent his own drivers
from loading.
Ron

Regards,
Ted

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

--
Netland Internet Services
bedrijfsmatige internetoplossingen
http://www.netland.nl Kruislaan 419 1098 VA Amsterdam
info: 020-5628282 servicedesk: 020-5628280 fax: 020-5628281
Op dit bericht is de volgende disclaimer van toepassing:
http://www.netland.nl/maildisclaimer
The world will end in 5 minutes. Please log out.

Attachment: ron.arts.vcf
Description: Vcard

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

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