|
|
|
|
|
|
|
|
|
|
xen-users
Re: [Xen-users] physdev_dom0_hide in xen 3.0.2
Frank DiRocco wrote:
pciback.hide=(00:11.0) and pci=['00:11:0']
when I lspci in dom0 i still see the device and when i lspci in the
domu i still see the device with 0000: in front of it.
I am passing two vifs to it with
vif = ['mac=aa:cc:00:00:00:02, bridge=xenbr0','mac=aa:cc:00:00:00:03,
bridge=xenbr1']
the machine is only able to bring up eth0 and eth1, eth2 fails.
any ideas?
On 4/23/06, *Frank DiRocco* <ofanged1@xxxxxxxxx
<mailto:ofanged1@xxxxxxxxx>> wrote:
thanks! I have seen that option before but couldn't find it and
forgot exactly where I saw it last.
On 4/23/06, *Q3aiml* < q3aiml@xxxxxxxxxx
<mailto:q3aiml@xxxxxxxxxx>> wrote:
Frank DiRocco wrote:
> Does physdev_dom0_hide work in 3.0.2? If no, is there an
alternative,
> or somthing other than using a bridge?
>
Yeah, the replacement is pciback. To hide devices you now pass
pciback.hide to the kernel. Example:
title Xen 3.0 / XenLinux 2.6
kernel /boot/xen-3.0.gz console=vga dom0_mem=256M
module /boot/vmlinuz-2.6-xen root=/dev/md0 ro quiet splash
console=tty0 pciback.hide=(06:08.0)(06:09.0)
module /boot/initrd.img- 2.6.16-xen
Then to use them in a domain the syntax is unchanged:
pci = ['06,08,00','06,09,00']
Hope that helps,
Andy Clayton
--
Thank you,
Frank Di Rocco
if (!try()) { while (!$caught) { cheat(); } lie(); exit; } -
anonymous
Due to the nature of the new pciback, you will see the device both in
dom0 and the assigned domU. If lspci shows the device and it shows up
under ifconfig, then to me that sounds like a problem localized to the
domU. Can you provide more details/logs regarding how it fails? I seem
to remember some talk in xen-devel about certain cards needing a
permissive setting to work. I believe that setting is integrated into
3.0.2 so it is worth a try, but I cannot say for sure off the top of my
head. If you want to check into it just search the -devel archives for
something about pciback and permissive. Either that or maybe someone
involved with that patch can say more specifically.
- Andy Clayton
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
|
|