From: Mario <mario@slackverse.org>
To: Ian Campbell <Ian.Campbell@eu.citrix.com>
Cc: "todd.deshane@xen.org" <todd.deshane@xen.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"xen-users@lists.xensource.com" <xen-users@lists.xensource.com>,
"Pasi Kärkkäinen" <pasik@iki.fi>,
"Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>
Subject: Re: PV networking issue in 2.6.38.6 and 2.6.39-rc7 pvops dom0 kernels
Date: Mon, 16 May 2011 14:56:21 +0200 [thread overview]
Message-ID: <4DD11EF5.1050203@slackverse.org> (raw)
In-Reply-To: <1305550008.20907.8.camel@zakaz.uk.xensource.com>
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:
>>>>>>> Hello,
>>>>>>>
>>>>>>> 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:
>>
>> http://dev.slackverse.org/tmp/config-2.6.39-rc7-xen
>
> This contains:
>
> # CONFIG_XEN_NETDEV_BACKEND is not set
>
>> http://dev.slackverse.org/tmp/config-2.6.37.6-xenU
>>
>> 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
>> directory
>
> Should be "device" not "devices", I got this wrong in my original mail.
> Sorry.
>
> (I stopped reading here since I think it's all explained by the missing
> config option).
>
> Ian.
>
>
Ehm, you are right, my bad, but what about 2.6.38.6 ?
# grep XEN_NETDEV /tmp/linux-2.6.38.6-xen/.config
CONFIG_XEN_NETDEV_FRONTEND=y
I was under impression that userspace driver would kick in..?
m.
next prev parent reply other threads:[~2011-05-16 12:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4DCFC8BB.9030201@slackverse.org>
[not found] ` <20110515155322.GM32595@reaktio.net>
[not found] ` <4DCFF8FA.8020409@slackverse.org>
[not found] ` <20110515161203.GN32595@reaktio.net>
[not found] ` <4DCFFE2B.4040302@slackverse.org>
[not found] ` <20110515163444.GO32595@reaktio.net>
[not found] ` <4DD00235.1090207@slackverse.org>
[not found] ` <20110515170345.GP32595@reaktio.net>
[not found] ` <20110515172030.GQ32595@reaktio.net>
[not found] ` <4DD00C66.7080100@slackverse.org>
2011-05-16 6:51 ` PV networking issue in 2.6.38.6 and 2.6.39-rc7 pvops dom0 kernels Pasi Kärkkäinen
2011-05-16 7:58 ` [Xen-users] " Ian Campbell
2011-05-16 8:56 ` Mario
2011-05-16 8:59 ` Ian Campbell
2011-05-16 9:03 ` Mario
2011-05-16 11:04 ` Mario
2011-05-16 12:46 ` [Xen-users] " Ian Campbell
2011-05-16 12:56 ` Mario [this message]
2011-05-16 13:00 ` Ian Campbell
2011-05-16 13:04 ` Mario
2011-05-16 13:06 ` Ian Campbell
2011-05-16 13:09 ` Mario
2011-05-16 13:15 ` Mario
2011-05-16 13:22 ` Pasi Kärkkäinen
2011-05-17 10:49 ` Mario
2011-05-17 11:04 ` Pasi Kärkkäinen
2011-05-17 11:20 ` Mario
2011-05-17 12:09 ` Pasi Kärkkäinen
2011-05-17 12:14 ` Ian Campbell
2011-05-17 14:23 ` Konrad Rzeszutek Wilk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DD11EF5.1050203@slackverse.org \
--to=mario@slackverse.org \
--cc=Ian.Campbell@eu.citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=pasik@iki.fi \
--cc=todd.deshane@xen.org \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.