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 15:04:42 +0200 Message-ID: <4DD120EA.4060204@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> <4DD0E6CE.4050004@slackverse.org> <1305536377.31488.213.camel@zakaz.uk.xensource.com> <4DD0E85F.7070105@slackverse.org> <4DD104AB.8000401@slackverse.org> <1305550008.20907.8.camel@zakaz.uk.xensource.com> <4DD11EF5.1050203@slackverse.org> <1305550841.20907.10.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: <1305550841.20907.10.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 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=C3=A4rkk=C3=A4inen wro= te: >>>>>>>>> Hello, >>>>>>>>> >>>>>>>>> Ian: Any idea what could cause this error message (more info be= low): >>>>>>>>> >>>>>>>>> "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 xenlin= ux one >>>>>>>>> fixes the problem.. >>>>>>>> >>>>>>>> 2.6.38 didn't have netback, only 2.6.39-rc1 did. Mario, please c= an 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 fil= e or >>>> directory >>> >>> Should be "device" not "devices", I got this wrong in my original mai= l. >>> Sorry. >>> >>> (I stopped reading here since I think it's all explained by the missi= ng >>> 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=3Dy >> >> I was under impression that userspace driver would kick in..? > > I don't think so, that only happens for disks AFAIK. > > Ian. > So you are telling me that 2.6.38 does not have a working networking on=20 PV guests, but HVM does?