[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 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?

Do other devices work ok?

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

Do the vif entries appear in XenStore? Using:
        xenstore-ls /local/domain/$(xl domid <name>)/devices/vif
you should see some entries and those entries should reference a backend
path which should also contains entries, please post both.

Ian.

> 
> -- Pasi
> 
> On Sun, May 15, 2011 at 07:24:54PM +0200, Mario wrote:
> >
> >
> > On 05/15/2011 07:20 PM, Pasi KÃrkkÃinen wrote:
> >> On Sun, May 15, 2011 at 08:03:45PM +0300, Pasi KÃrkkÃinen wrote:
> >>> On Sun, May 15, 2011 at 06:41:25PM +0200, Mario wrote:
> >>>> On 05/15/2011 06:34 PM, Pasi KÃrkkÃinen wrote:
> >>>>> On Sun, May 15, 2011 at 06:24:11PM +0200, Mario wrote:
> >>>>>>
> >>>>>>
> >>>>>> On 05/15/2011 06:12 PM, Pasi KÃrkkÃinen wrote:
> >>>>>>> On Sun, May 15, 2011 at 06:02:02PM +0200, Mario wrote:
> >>>>>>>> On 05/15/2011 05:53 PM, Pasi KÃrkkÃinen wrote:
> >>>>>>>>> On Sun, May 15, 2011 at 02:36:11PM +0200, Mario wrote:
> >>>>>>>>>> Hey everyone,
> >>>>>>>>>>
> >>>>>>>>>> I have been trying to make Xen-4.1.0 work on kernels mentioned in 
> >>>>>>>>>> the
> >>>>>>>>>> subject, without much sucess. HVM guests are not affected, only PV.
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> Below you mention gentoo xenlinux patches..
> >>>>>>>>>
> >>>>>>>>> So please be more specific about which kernel was vanilla (pvops),
> >>>>>>>>> and which kernels had some external patches applied..
> >>>>>>>>>
> >>>>>>>>> -- Pasi
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>> Sorry, both kernels in subject were vanilla from kernel.org, with xen
> >>>>>>>> options selected for dom0 usage.
> >>>>>>>> I only wanted to point out that networking works if i use kernel 
> >>>>>>>> patched
> >>>>>>>> with rebased gentoo patches.
> >>>>>>>> I am talking only about dom0 kernel here, domU kernel does not seem 
> >>>>>>>> to
> >>>>>>>> be the source of the problem.
> >>>>>>>>
> >>>>>>>
> >>>>>>> OK. What kernel is the PV domU running? What Xen version are you 
> >>>>>>> using? 4.1 ?
> >>>>>>>
> >>>>>>> -- Pasi
> >>>>>>>
> >>>>>>
> >>>>>> Well, i have tried following kernels in domU:
> >>>>>>
> >>>>>> 2.6.31.6 (i got this one from stacklet)
> >>>>>> 2.6.37.6-domU
> >>>>>> 2.6.33.4-domU
> >>>>>
> >>>>> Are these pvops/vanilla or with some patches?
> >>>>
> >>>> Those are pvops/vanilla, no patches.
> >>>>
> >>>>
> >>>>>
> >>>>>> 2.6.38.6-xen (dom0 kernel)
> >>>>>> 2.6.34.7-xen (dom0 kernel)
> >>>>>> 2.6.39-rc7-xen (dom0 kernel)
> >>>>>>
> >>>>>> None of them made any difference, they were all complaining about vif.
> >>>>>> Yeah, I am running Xen 4.1
> >>>>>>
> >>>>>
> >>>>> Are you using xm/xend or xl/libxl toolstack?
> >>>>
> >>>> I am using xl/libxl with Xen 4.1
> >>>>
> >>>
> >>> Ok. Have you tried Jeremy's xen.git xen/stable-2.6.32.x as a dom0 kernel?
> >>> It would be interesting to know if that works for you or not.
> >>>
> >>
> >> Btw. Did you realize upstream 2.6.38 / 2.6.39 does not yet have
> >> xen-blkback driver included? also blktap2 driver is missing.
> >>
> >> So you you can only use the phy: or file: backends, assuming Xen 4.1,
> >> which has the (slow) fallback qemu-based userspace blkback implementation.
> >>
> >> -- Pasi
> >>
> >>
> >>
> >
> > Yes i have, but seeing that HVM networking works, i wanted to report the  
> > PV one that doesn't.
> >
> >
> > m.
> >
> >
> >>>>>
> >>>>>>
> >>>>>>>>
> >>>>>>>>>> Error that i see in dmesg on the domU:
> >>>>>>>>>> XENBUS: Timeout connecting to device: device/vif/0 (state 1)
> >>>>>>>>>>
> >>>>>>>>>> ifconfig -a on domU shows MAC address: 00:00:00:00:00:00
> >>>>>>>>>>
> >>>>>>>>>> dom0 doesn't have any vif/tap interfaces assigned to domU when i do
> >>>>>>>>>> brctl show or ifconfig -a
> >>>>>>>>>>
> >>>>>>>>>> I don't see any errors worth mentioning in /var/log/xen, except 
> >>>>>>>>>> mybe
> >>>>>>>>>> these two:
> >>>>>>>>>>
> >>>>>>>>>> /tmp/SBo/xen-4.1.0/tools/ioemu-qemu-xen/hw/xen_blktap.c:628: Init 
> >>>>>>>>>> blktap
> >>>>>>>>>> pipes
> >>>>>>>>>> Could not open /var/run/tap/qemu-read-2
> >>>>>>>>>>
> >>>>>>>>>> Problem goes away when i boot 2.6.34.7 (it is the last kernel that 
> >>>>>>>>>> i
> >>>>>>>>>> have built with gentoo rebased patches).
> >>>>>>>>>>
> >>>>>>>>>> If there is something i can do to help debug this please do let me 
> >>>>>>>>>> know.
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> Best regards,
> >>>>>>>>>> mario
> >>>>>>>>>>
> >>>>>>>>>> _______________________________________________
> >>>>>>>>>> Xen-users mailing list
> >>>>>>>>>> Xen-users@xxxxxxxxxxxxxxxxxxx
> >>>>>>>>>> http://lists.xensource.com/xen-users
> >>>>>>>>>
> >>>>>>>>> _______________________________________________
> >>>>>>>>> Xen-users mailing list
> >>>>>>>>> Xen-users@xxxxxxxxxxxxxxxxxxx
> >>>>>>>>> http://lists.xensource.com/xen-users
> >>>>>>>
> >>>>>>> _______________________________________________
> >>>>>>> Xen-users mailing list
> >>>>>>> Xen-users@xxxxxxxxxxxxxxxxxxx
> >>>>>>> http://lists.xensource.com/xen-users
> >>>>>
> >>>>> _______________________________________________
> >>>>> Xen-users mailing list
> >>>>> Xen-users@xxxxxxxxxxxxxxxxxxx
> >>>>> http://lists.xensource.com/xen-users
> >>>
> >>> _______________________________________________
> >>> Xen-users mailing list
> >>> Xen-users@xxxxxxxxxxxxxxxxxxx
> >>> http://lists.xensource.com/xen-users



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