[Xen-devel] Re: [Xen-users] PV networking issue in 2.6.38.6 and 2.6.39-rc7 pvops dom0 kernels

[Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>]

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:
> >>>>>>> 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..?

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

Ian.


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