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/
Home Products Support Community News


Re: [Xen-users] PV networking issue in and 2.6.39-rc7 pvops dom

To: Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>
Subject: Re: [Xen-users] PV networking issue in and 2.6.39-rc7 pvops dom0 kernels
From: Mario <mario@xxxxxxxxxxxxxx>
Date: Mon, 16 May 2011 15:04:42 +0200
Cc: "todd.deshane@xxxxxxx" <todd.deshane@xxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "xen-users@xxxxxxxxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxxxxxxxx>, Pasi Kärkkäinen <pasik@xxxxxx>, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Delivery-date: Mon, 16 May 2011 06:09:51 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1305550841.20907.10.camel@xxxxxxxxxxxxxxxxxxxxxx>
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: <4DCFC8BB.9030201@xxxxxxxxxxxxxx> <20110515155322.GM32595@xxxxxxxxxxx> <4DCFF8FA.8020409@xxxxxxxxxxxxxx> <20110515161203.GN32595@xxxxxxxxxxx> <4DCFFE2B.4040302@xxxxxxxxxxxxxx> <20110515163444.GO32595@xxxxxxxxxxx> <4DD00235.1090207@xxxxxxxxxxxxxx> <20110515170345.GP32595@xxxxxxxxxxx> <20110515172030.GQ32595@xxxxxxxxxxx> <4DD00C66.7080100@xxxxxxxxxxxxxx> <20110516065141.GR32595@xxxxxxxxxxx> <1305532695.31488.168.camel@xxxxxxxxxxxxxxxxxxxxxx> <4DD0E6CE.4050004@xxxxxxxxxxxxxx> <1305536377.31488.213.camel@xxxxxxxxxxxxxxxxxxxxxx> <4DD0E85F.7070105@xxxxxxxxxxxxxx> <4DD104AB.8000401@xxxxxxxxxxxxxx> <1305550008.20907.8.camel@xxxxxxxxxxxxxxxxxxxxxx> <4DD11EF5.1050203@xxxxxxxxxxxxxx> <1305550841.20907.10.camel@xxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20110429 Thunderbird/3.1.10
On 05/16/2011 03:00 PM, Ian Campbell wrote:
On Mon, 2011-05-16 at 13:56 +0100, Mario wrote:
On 05/16/2011 02:46 PM, Ian Campbell wrote:
On Mon, 2011-05-16 at 12:04 +0100, Mario wrote:
On 05/16/2011 11:03 AM, Mario wrote:
On 05/16/2011 10:59 AM, Ian Campbell wrote:
On Mon, 2011-05-16 at 09:56 +0100, Mario wrote:
On 05/16/2011 09:58 AM, Ian Campbell wrote:
On Mon, 2011-05-16 at 07:51 +0100, Pasi Kärkkäinen wrote:

Ian: Any idea what could cause this error message (more info below):

"XENBUS: Timeout connecting to device: device/vif/0 (state 1)"

Is this from the domU or the dom0?

This is from the domU.

Do other devices work ok?

Yes, everything else seems to be working fine.

User says replacing 2.6.38/2.6.39 pvops dom0 kernel with xenlinux one
fixes the problem..

2.6.38 didn't have netback, only 2.6.39-rc1 did. Mario, please can you
supply the .config you used with the 2.6.39 kernel and the exact commit
id you are using. It would also be useful to see a complete log from
both dom0 and domU.

Pvops kernel configs are here:


This contains:



They are both based on default configs shipped with Slackware, with
minimal xen-only options enabled.

Too minimal ;-)

# xenstore-ls /local/domain/$(xl domid slackware)/devices/vif
xenstore-ls: xs_directory (/local/domain/1/devices/vif): No such file or

Should be "device" not "devices", I got this wrong in my original mail.

(I stopped reading here since I think it's all explained by the missing
config option).


Ehm, you are right, my bad, but what about ?

# grep XEN_NETDEV /tmp/linux-

I was under impression that userspace driver would kick in..?

I don't think so, that only happens for disks AFAIK.


So you are telling me that 2.6.38 does not have a working networking on PV guests, but HVM does?

Xen-users mailing list

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