From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mario Subject: Re: PV networking issue in 2.6.38.6 and 2.6.39-rc7 pvops dom0 kernels Date: Mon, 16 May 2011 10:56:46 +0200 Message-ID: <4DD0E6CE.4050004@slackverse.org> References: <4DCFC8BB.9030201@slackverse.org> <20110515155322.GM32595@reaktio.net> <4DCFF8FA.8020409@slackverse.org> <20110515161203.GN32595@reaktio.net> <4DCFFE2B.4040302@slackverse.org> <20110515163444.GO32595@reaktio.net> <4DD00235.1090207@slackverse.org> <20110515170345.GP32595@reaktio.net> <20110515172030.GQ32595@reaktio.net> <4DD00C66.7080100@slackverse.org> <20110516065141.GR32595@reaktio.net> <1305532695.31488.168.camel@zakaz.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <1305532695.31488.168.camel@zakaz.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-users-bounces@lists.xensource.com Errors-To: xen-users-bounces@lists.xensource.com To: Ian Campbell Cc: "todd.deshane@xen.org" , "xen-devel@lists.xensource.com" , "xen-users@lists.xensource.com" , =?UTF-8?B?UGFzaSBLw6Rya2vDpGluZW4=?= , Konrad Rzeszutek Wilk List-Id: xen-devel@lists.xenproject.org On 05/16/2011 09:58 AM, Ian Campbell wrote: > On Mon, 2011-05-16 at 07:51 +0100, Pasi K=C3=A4rkk=C3=A4inen 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. > Well, when i saw that 2.6.39-rc7 did not work, and i did not expect=20 anyone to care, i simply wiped all of the pvops stuff that i was=20 testing, and replaced it with a gentoo patched kernel wich works. If it will not be in vain, i will compile it again and give you more=20 details. > Do the vif entries appear in XenStore? Using: > xenstore-ls /local/domain/$(xl domid)/devices/vif > you should see some entries and those entries should reference a backen= d > path which should also contains entries, please post both. > Well, from what i remember, only vhd was being shown, but i will try and=20 get you exact info today. > Ian. > >> >> -- Pasi >> >> On Sun, May 15, 2011 at 07:24:54PM +0200, Mario wrote: >>> >>> >>> On 05/15/2011 07:20 PM, Pasi K=C3=A4rkk=C3=A4inen wrote: >>>> On Sun, May 15, 2011 at 08:03:45PM +0300, Pasi K=C3=A4rkk=C3=A4inen = wrote: >>>>> On Sun, May 15, 2011 at 06:41:25PM +0200, Mario wrote: >>>>>> On 05/15/2011 06:34 PM, Pasi K=C3=A4rkk=C3=A4inen wrote: >>>>>>> On Sun, May 15, 2011 at 06:24:11PM +0200, Mario wrote: >>>>>>>> >>>>>>>> >>>>>>>> On 05/15/2011 06:12 PM, Pasi K=C3=A4rkk=C3=A4inen wrote: >>>>>>>>> On Sun, May 15, 2011 at 06:02:02PM +0200, Mario wrote: >>>>>>>>>> On 05/15/2011 05:53 PM, Pasi K=C3=A4rkk=C3=A4inen 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 mention= ed in the >>>>>>>>>>>> subject, without much sucess. HVM guests are not affected, o= nly PV. >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Below you mention gentoo xenlinux patches.. >>>>>>>>>>> >>>>>>>>>>> So please be more specific about which kernel was vanilla (pv= ops), >>>>>>>>>>> and which kernels had some external patches applied.. >>>>>>>>>>> >>>>>>>>>>> -- Pasi >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Sorry, both kernels in subject were vanilla from kernel.org, w= ith xen >>>>>>>>>> options selected for dom0 usage. >>>>>>>>>> I only wanted to point out that networking works if i use kern= el 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 yo= u 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 abou= t 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 k= ernel? >>>>> 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 implement= ation. >>>> >>>> -- 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 wh= en i do >>>>>>>>>>>> brctl show or ifconfig -a >>>>>>>>>>>> >>>>>>>>>>>> I don't see any errors worth mentioning in /var/log/xen, exc= ept 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 kerne= l 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@lists.xensource.com >>>>>>>>>>>> http://lists.xensource.com/xen-users >>>>>>>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> Xen-users mailing list >>>>>>>>>>> Xen-users@lists.xensource.com >>>>>>>>>>> http://lists.xensource.com/xen-users >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> Xen-users mailing list >>>>>>>>> Xen-users@lists.xensource.com >>>>>>>>> http://lists.xensource.com/xen-users >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Xen-users mailing list >>>>>>> Xen-users@lists.xensource.com >>>>>>> http://lists.xensource.com/xen-users >>>>> >>>>> _______________________________________________ >>>>> Xen-users mailing list >>>>> Xen-users@lists.xensource.com >>>>> http://lists.xensource.com/xen-users > >