Xen users - Mar 2007 - FAQ request: hide pci device

Currently the FAQ at:
http://wiki.xensource.com/xenwiki/XenFaq

only has any documentation for Xen2.x in:

2.2. How do I hide a pci device from dom0?


I''ve tried finding documentation on this for Xen3.x elsewhere with no
luck. Well, nothing useful anyway.

Can someone please provide some documentation, update the wiki or direct
me to a URL which can help?

Thanks!

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

On 3/18/07, Steve Wray <steve.wray@cwa.co.nz>
wrote:
> Can someone please provide some documentation, update the wiki or direct
> me to a URL which can help?
http://wiki.xensource.com/xenwiki/Assign_hardware_to_DomU_with_PCIBack_as_module
has helped me...

jerry

-- 
"Oh joy! Rapture! I''ve got a brain"
-Scarecrow

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

Jerry Amundson wrote:
> On 3/18/07, Steve Wray <steve.wray@cwa.co.nz> wrote:
>> Can someone please provide some documentation, update the wiki or
direct
>> me to a URL which can help?
> 
>
http://wiki.xensource.com/xenwiki/Assign_hardware_to_DomU_with_PCIBack_as_module
> 
> has helped me...
Thanks, thats one of the ones I found too... but it didn''t help me
much.

Its better than nothing but what I''d really like to see is something
along the lines of:

"So you have a xen2 box which hides PCI devices using physdev_dom0_hide
etc? Heres how to upgrade this existing, known-good configuration to xen3".



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

I''ve been doing some testing of the pci device hiding; its a lot easier
in Debian than it is in Suse as Debian doesn''t mess around with having
it as a module...

Anyhow, I''m finding a bizarre issue:

I have a domU which uses a ''hidden'' PCI network card, this
works just
fine. In other words I do have the ''pci ='' directive and the
''pciback.hide='' directives correct as I can access the pci
network card
from the domU and there are no problems with the dom0 prior to shutting
the domU down.

However, when I shut that domU down the dom0 starts having issues with
the IRQs for its IDE controllers, has DMA errors on all of its drives
and crashes. It doesn''t kernel panic, it just goes into an endless
cycle
of DMA-errors on its hard drives and becomes unusable.

Seems odd that shutting down a domU (with a ''pci ='' directive)
should so
hose the dom0... are these actually likely to be connected or is there
something else going on here?

Thanks!


Steve Wray wrote:
> Jerry Amundson wrote:
>> On 3/18/07, Steve Wray <steve.wray@cwa.co.nz> wrote:
>>> Can someone please provide some documentation, update the wiki or
direct
>>> me to a URL which can help?
>>
http://wiki.xensource.com/xenwiki/Assign_hardware_to_DomU_with_PCIBack_as_module
>>
>> has helped me...
> 
> Thanks, thats one of the ones I found too... but it didn''t help me
much.
> 
> Its better than nothing but what I''d really like to see is
something
> along the lines of:
> 
> "So you have a xen2 box which hides PCI devices using
physdev_dom0_hide
> etc? Heres how to upgrade this existing, known-good configuration to
xen3".
> 
> 
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users

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

hi,

i have similar issue with an usb 2.0 controller: rebooting the domU
kills the oboard sata controller. the usb 1.1 controllers don''t kill
the
domU (but refuse to work if no 2.0 controller is present, which is odd:
the remaining usb 1.1 controller in the dom0 works just fine without
it). a nic in an other domU is no problem what so ever.
if anybody cares to look at it i''ll happily throw debugging information
in your direction.

setup: debian etch (xen , linux-2.6.18 from debian).
pciback.permissive is set

/rupi
-- 
 http://rantanplan.org/~rupi/ || encrypt email || use free software
 fingerprint = 9639 0ABC AD2F 155F C96C  FC78 3CFE 82C0 0AF9 AE3A


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

rupi wrote:
> hi,
> 
> i have similar issue with an usb 2.0 controller: rebooting the domU
> kills the oboard sata controller. the usb 1.1 controllers don''t
kill the
> domU (but refuse to work if no 2.0 controller is present, which is odd:
> the remaining usb 1.1 controller in the dom0 works just fine without
> it). a nic in an other domU is no problem what so ever.
> if anybody cares to look at it i''ll happily throw debugging
information
> in your direction.
I had 3 hidden NICs in the server in question, only one in use by a domU
at the time of the problems.

I''ve found that if I take this down to 2 hidden NICS then I have no
problems. Yet.

I''d like to get some idea from others on the list -- hopefuly some
people who know more about pciback.hide -- if this feature is actually
considered ''production ready'' or if its still
''beta''.

Thanks
> setup: debian etch (xen , linux-2.6.18 from debian).
> pciback.permissive is set
> 
> /rupi
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users

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