RE: [Xen-devel] Re: [Xen-users] pci passthrough and Xenserver

[Matej Zary <zary@xxxxxxxxx>]

Hi, Etch (old stable) xen kernel should be still in repositories AFAIK.

http://packages.debian.org/search?keywords=xen-linux-system&searchon=names&suite=oldstable&section=all
 

Just add line into /etc/apt/sources with Etch repositories.
Set bigger priority for Lenny with apt-pinning. 
(http://jaqque.sbih.org/kplug/apt-pinning.html)
Install the 2.6.18xen kernel with aptitude (aptitude update; aptitude install 
xen-linux-system-2.6.18-4-xen-amd64/oldstable)

Haven't tried yet, but should work eventually. :)

Regards

Matej



________________________________________
From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx 
[xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Ritu kaur 
[ritu.kaur.us@xxxxxxxxx]
Sent: 12 March 2010 16:18
To: Ian Campbell
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] Re: [Xen-users] pci passthrough and Xenserver

what version of Debian Lenny should I be using for domU? I see below snippets 
in wiki.debian.org/Xen

The default Lenny kernel is the newer paravirt_ops version (2.6.26), which does 
not function as a dom0 (except for the -xen variants, which have dom0 support 
but also some issues running as domU (please clarify?). It will also not 
support PCI passthrough in a domU. For PCI passthrough, you have to run the 
2.6.18 etch kernel as both dom0 and domU.

Can you please point me to a domU kernel binary with PV drivers compiled in it 
and works with XCP 0.1.1 pci passthrough?

Thanks

On Thu, Mar 11, 2010 at 11:32 PM, Ian Campbell 
<Ian.Campbell@xxxxxxxxxx<mailto:Ian.Campbell@xxxxxxxxxx>> wrote:
On Fri, 2010-03-12 at 03:04 +0000, Ritu kaur wrote:
>
> 4. after domU is up,
>
> a. lspci in domU shows nothing
> b. ifconfig/ifconfig -a shows no interface
> c. driver doesn't seem to load during boot(lsmod doesn't list it, did
> modprobe again)

You seem to be using Lenny as your domU. I don't think the kernel used
in Lenny has pcifront support. You could try installing a more up to
date pvops kernel in your domU.

> 5. lspci in dom0 still lists the pci device.

That is normal. The driver which is bound to the device is in domain 0
should be pciback not something else.

Ian.



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