Hi Jarod,
Is this guest paravirtualized or fully virtualized?
I can however see the bnx2 and e1000 modules in my Dom0.
Because with my guest I am running the following kernel:-
kernel-xenU-2.6.9-55.0.2.EL
This guest kernel does not have the e1000 and bnx2 modules (or any others for that matter).
In relation to passing through the pci device in my /etc/xen/{xen instance} config file I am using the following directive:-
pci = ['0000:0e:00.0']
Cheers
[EMAIL PROTECTED] wrote: -----
Is this guest paravirtualized or fully virtualized?
I can however see the bnx2 and e1000 modules in my Dom0.
Because with my guest I am running the following kernel:-
kernel-xenU-2.6.9-55.0.2.EL
This guest kernel does not have the e1000 and bnx2 modules (or any others for that matter).
In relation to passing through the pci device in my /etc/xen/{xen instance} config file I am using the following directive:-
pci = ['0000:0e:00.0']
Cheers
To: "Red Hat Enterprise Linux 5 (Tikanga) discussion mailing-list" <[email protected]>
From: Jarod Wilson <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
Date: 06/29/2007 06:56AM
Subject: Re: [rhelv5-list] Xen Guest Kernel Modules
Stephen John Smoogen wrote:
> On 6/28/07, Clayton Rogers <[EMAIL PROTECTED]> wrote:
>> I understand this part. I am passing the pci card through to the
>> paravirtualized instance.
>>
>> Shouldn't you be able to compile and use additional devices you pass
>> through?
>>
>> Regards
>>
>>
>
> As far as I have run into.. and I am very certain I am probably wrong,
> the answer is no. Certain devices are 'special' due to other layers of
> the kernel and can not be handled in such a manner. In most cases if
> you are needing the speed/performance of a direct connection you will
> need to use a pure hardware solution. [My information is rather old
> and dealt with someone wanting to make xen snort boxes on gigabit
> networks...]
Can't say that I have any clue about passing through pci devices myself,
but something else just dawned on me... The e1000 and bnx2 modules *are*
built for kernel-xen, since its used for both dom0 and domU. This here's
from a xen guest I've got up and running:
# modinfo e1000
filename:
/lib/modules/2.6.18-32.el5xen/kernel/drivers/net/e1000/e1000.ko
version: 7.3.20-k2-NAPI
license: GPL
description: Intel(R) PRO/1000 Network Driver
author: Intel Corporation, <[EMAIL PROTECTED]>
srcversion: ADCAB2C9F5C9C78F9962FC8
[...snip...]
# modinfo bnx2
filename: /lib/modules/2.6.18-32.el5xen/kernel/drivers/net/bnx2.ko
version: 1.5.11
license: GPL
description: Broadcom NetXtreme II BCM5706/5708 Driver
author: Michael Chan <[EMAIL PROTECTED]>
srcversion: 33BED7A4FFB2AF8571C55C3
[...snip...]
--
Jarod Wilson
[EMAIL PROTECTED]
_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list
signature.asc
Description: Binary data
_______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
