WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] Problem with delegated hardware (Realtek Network driver

To: Luciano Coutinho Barcellos <luciano@xxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-users] Problem with delegated hardware (Realtek Network driver 8139too)
From: Edson Marquezani Filho <edsonmarquezani@xxxxxxxxx>
Date: Mon, 1 Mar 2010 08:01:06 -0300
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 01 Mar 2010 03:02:54 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=iydZEXJqtYTJJfGvkaC7lEnQHBuraafO//ppIXA7WAQ=; b=J7mscLpPP1aKPygcdpbVdzyfjbDEiuLpZImelZXcI/80LeQLngt1H4e10+f4Xz+RxI ulQYvW7dXrMzCaHMnkFPLBAJP7YvNhfBLhSdh6ZU27GyyDdxzHnOQ1ZOwPvaF1F8F3Bt Y9iTYdAyQe2nl9a5Ctr02D4pptpXK0dXX9cWQ=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=GxdfOxJywEq7VZw8J7I9C6GCKoRfDt4Y4ERe3s0/502az86yaz+cG+nouCb0b3nd6R 4Ww3NiBKZUvcA5yncGqqWQ+Xdb3MjO7eM1w5SAq5G40QJzduLrukFoe/81zv1dFzk8Yh gbaq1guDr9upQ3FI7fhd9U8DrY/qukAXfJIjU=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4B89855A.4050806@xxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <4B89855A.4050806@xxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On Sat, Feb 27, 2010 at 17:49, Luciano Coutinho Barcellos
<luciano@xxxxxxxxxxxxxxxxx> wrote:
> Dear friends,
>
>  I've googled a lot before giving up and come here to ask for some help. All
> I've found about my problem was a pretty old single message with no reply
> since it was post on Jul 19th, 2007.
>  I hope to have better luck and find some light to solve the problem. I want
> to configure a domU, with 3 nics (identified as having the Realtek 8139D
> chip) delegated to it. Everything works almost great except for the message
> shown when I try to ifconfig any card:
>
>       SIOCSIFFLAGS: Cannot allocate memory.
>
>  Considering the following:
>
>      - The cards work fine on dom0;
>      - Delegating a card with chipset Via works on domU;
>      - Everything is fine with passthrough, card detection and module
> loading in domU.
>
>   What could be the problem?
>   I've read something about an old b44 driver which suffered from a
> limitation about memory allocation. It needed memory from the first physical
> 16MB. Could it be a similar problem?
>   My configuration is the folowing:
>
>      - dom0 kernel command line includes:
>  pciback.hide=(00:08.0)(00:09.0)(00:0a.0)
>      - domU configuration file has: pci = [ '00:08.0', '00:09.0', '00:0a.0'
> ]
>      - xen hypervisor: 3.2.1-i386 from Debian Lenny repositories
>      - linux kernel for both dom0 and domU: 2.6.26-2-xen-686 from Debian
> Lenny repositories
>      - kernel module used for the nics: 8139too
>
>   Hope to get some help.
>

I see you are using Debian. Are you aware of what Debian Wiki says
about pci passthrough on Lenny [1]? In few words, it says that it's
possible only if you run kernel 2.6.18 (Etch's one) for both dom0 and
domU.
Actualy, I didn't tested it but I assumed it as being true and didn't
even try to configure pci passthroug with kernel 2.6.26.

Anyway, you say it has worked for you and I do believe. =) But, there
may be some issue related to the kernel you are using. I would try
some more "traditional" Xen kernel. =)

Just a clue. I hope this can help you a little bit. =)

[1] http://wiki.debian.org/Xen#Installationonlenny

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

<Prev in Thread] Current Thread [Next in Thread>