From: Boris Derzhavets Subject: Re: Re: 2.6.30-rc3-tip kernel's backend network driver response when loading Xen 3.4 Dom0 on Ubuntu 9.04 Server (Ubuntu Desktop installed) Date: Tue, 12 May 2009 02:07:49 -0700 (PDT) Message-ID: <884147.15747.qm@web56105.mail.re3.yahoo.com> References: <4A08AC0F.5050001@goop.org> Reply-To: bderzhavets@yahoo.com Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2090450346==" Return-path: In-Reply-To: <4A08AC0F.5050001@goop.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jeremy Fitzhardinge Cc: xen-devel List-Id: xen-devel@lists.xenproject.org --===============2090450346== Content-Type: multipart/alternative; boundary="0-1390217167-1242119269=:15747" --0-1390217167-1242119269=:15747 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Jeremy, Backend support always gets compiled built-in either on Ubuntu 9.04 or Ubun= tu 8.10. But on 8.10 it works (gcc 4.3) on 9.04 it doesn't (gcc 4.4).=A0=20 In the last case hotplug scripts refuse to work. DomU paused at boot up and failed with messages:- **************************************************************** XENBUS: Timeout connecting to device: /device/vbd/51712 vif(0)=A0 could not be connected . Hotplug scripts not working. ***************************************************************** Please, advise how to try to load backend support modules manually. Boris --- On Mon, 5/11/09, Jeremy Fitzhardinge wrote: From: Jeremy Fitzhardinge Subject: [Xen-devel] Re: 2.6.30-rc3-tip kernel's backend network driver res= ponse when loading Xen 3.4 Dom0 on Ubuntu 9.04 Server (Ubuntu Desktop insta= lled) To: bderzhavets@yahoo.com Cc: "xen-devel" Date: Monday, May 11, 2009, 6:51 PM Boris Derzhavets wrote: > Last lines of dmesg report Xen 3.4 (2.6.30-rc3-tip) instance been built o= n Ubuntu 9.04 Server ( IP6v by default) >=20 > [ 29.214154] skge eth0: enabling interface > [ 29.218498] ADDRCONF(NETDEV_UP): eth0: link is not ready > [ 29.630012] eth1: no IPv6 routers present > [ 38.012544] sky2 eth1: disabling interface > [ 38.092791] sky2 peth1: enabling interface > [ 38.093450] ADDRCONF(NETDEV_UP): peth1: link is not ready > [ 39.776997] sky2 peth1: Link is up at 100 Mbps, full duplex, flow control both > [ 39.777643] ADDRCONF(NETDEV_CHANGE): peth1: link becomes ready > [ 40.145017] device peth1 entered promiscuous mode > [ 40.182778] eth1: topology change detected, propagating > [ 40.182783] eth1: port 1(peth1) entering forwarding state > [ 49.820430] xenbus_probe wake_waiting > [ 49.820491] xenbus_probe wake_waiting > [ 49.829859] XENBUS: Unable to read cpu state > [ 49.831443] XENBUS: Unable to read cpu state > [ 49.831633] XENBUS: Unable to read cpu state > [ 49.831851] XENBUS: Unable to read cpu state > [ 49.832132] xenbus_probe_devices backend > [ 49.832283] xenbus_probe_devices failed xenbus_directory > [ 49.832331] backend_probe_and_watch devices probed ok > [ 49.832494] backend_probe_and_watch watch add ok ok > [ 49.832541] backend_probe_and_watch all done > [ 49.832581] xenbus_probe_devices device > [ 49.832731] xenbus_probe_devices failed xenbus_directory > [ 49.832777] frontend_probe_and_watch devices probed ok > [ 49.832948] frontend_probe_and_watch watch add ok ok > [ 49.832995] frontend_probe_and_watch all done > [ 49.910018] peth1: no IPv6 routers present > [ 51.062517] eth1: no IPv6 routers present > [ 173.299352] vif1.0 (vif): not using net_device_ops yet >=20 > Last lines of dmesg report Xen 3.4 (2.6.30-rc3-tip) instance been built o= n Ubuntu 8.10 >=20 >=20 > [ 54.856147] sky2 peth0: enabling interface > [ 54.856810] ADDRCONF(NETDEV_UP): peth0: link is not ready > [ 55.777286] skge eth1: enabling interface > [ 55.781784] ADDRCONF(NETDEV_UP): eth1: link is not ready > [ 56.521131] sky2 peth0: Link is up at 100 Mbps, full duplex, flow control both > [ 56.521765] ADDRCONF(NETDEV_CHANGE): peth0: link becomes ready > [ 56.905093] device peth0 entered promiscuous mode > [ 56.917357] eth0: topology change detected, propagating > [ 56.917362] eth0: port 1(peth0) entering forwarding state > [ 64.531928] xenbus_probe wake_waiting > [ 64.531984] xenbus_probe wake_waiting > [ 64.542317] XENBUS: Unable to read cpu state > [ 64.542486] XENBUS: Unable to read cpu state > [ 64.542661] XENBUS: Unable to read cpu state > [ 64.542828] XENBUS: Unable to read cpu state > [ 64.543137] xenbus_probe_devices backend > [ 64.543313] xenbus_probe_devices failed xenbus_directory > [ 64.543356] backend_probe_and_watch devices probed ok > [ 64.543514] backend_probe_and_watch watch add ok ok > [ 64.543557] backend_probe_and_watch all done > [ 64.543599] xenbus_probe_devices device > [ 64.543776] xenbus_probe_devices failed xenbus_directory > [ 64.543818] frontend_probe_and_watch devices probed ok > [ 64.543972] frontend_probe_and_watch watch add ok ok > [ 64.544021] frontend_probe_and_watch all done > [ 67.040013] peth0: no IPv6 routers present > [ 67.890015] eth0: no IPv6 routers present > [ 118.012469] vif1.0 (vif): not using net_device_ops yet > [ 118.127252] device vif1.0 entered promiscuous mode > [ 118.130694] eth0: topology change detected, propagating > [ 118.130701] eth0: port 2(vif1.0) entering forwarding state > [ 122.657298] blkback: ring-ref 8, event-channel 9, protocol 1 (x86_64-abi) > [ 128.700025] vif1.0: no IPv6 routers present > [ 183.761252] eth0: port 2(vif1.0) entering disabled state > [ 183.800702] eth0: port 2(vif1.0) entering disabled state >=20 > Line:- >=20 > [ 122.657298] blkback: ring-ref 8, event-channel 9, protocol 1 (x86_64-abi) >=20 > is absent in first report. I believe it's a Dom0's kernel message from network > backend driver. Instances dual boot on the same box. >=20 I've seen similar things when building xenbus as modules; the backend modules don't get auto-loaded. Either compiling them non-modular or manually loading the modules works. If that doesn't work, I'm not sure what's going on. J _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel =0A=0A=0A --0-1390217167-1242119269=:15747 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable
Jeremy,

Backend support always gets co= mpiled built-in either on Ubuntu 9.04 or Ubuntu
8.10. But on 8.10 it wor= ks (gcc 4.3) on 9.04 it doesn't (gcc 4.4). 
In the last case hotpl= ug scripts refuse to work. DomU paused at boot up
and failed with messag= es:-
****************************************************************XENBUS: Timeout connecting to device: /device/vbd/51712
vif(0)  co= uld not be connected . Hotplug scripts not working.
********************= *********************************************
Please, advise how to try = to load backend support modules manually.

Boris

--- On Mon= , 5/11/09, Jeremy Fitzhardinge <jeremy@goop.org> wrote:
From: Jeremy Fitzhardinge <jeremy@goop.org>
Subject: [Xen-devel] Re: 2.6.30-rc3-tip kernel'= s backend network driver response when loading Xen 3.4 Dom0 on Ubuntu 9.04 = Server (Ubuntu Desktop installed)
To: bderzhavets@yahoo.com
Cc: "xen-= devel" <xen-devel@lists.xensource.com>
Date: Monday, May 11, 2009,= 6:51 PM

Boris Derzhavets wrote:
> Last lines of dmesg re= port Xen 3.4 (2.6.30-rc3-tip) instance been built on
Ubuntu 9.04 Server = ( IP6v by default)
>
> [ 29.214154] skge eth0: enabling inte= rface
> [ 29.218498] ADDRCONF(NETDEV_UP): eth0: link is not ready> [ 29.630012] eth1: no IPv6 routers present
> [ 38.012544] = sky2 eth1: disabling interface
> [ 38.092791] sky2 peth1: enabling = interface
> [ 38.093450] ADDRCONF(NETDEV_UP): peth1: link is not re= ady
> [ 39.776997] sky2 peth1: Link is up at 100 Mbps, full duplex,= flow
control both
> [ 39.777643] ADDRCONF(NETDEV_CHANGE): peth1: link becomes ready
> [ 40.145017] = device peth1 entered promiscuous mode
> [ 40.182778] eth1: topology= change detected, propagating
> [ 40.182783] eth1: port 1(peth1) en= tering forwarding state
> [ 49.820430] xenbus_probe wake_waiting> [ 49.820491] xenbus_probe wake_waiting
> [ 49.829859] XENBU= S: Unable to read cpu state
> [ 49.831443] XENBUS: Unable to read c= pu state
> [ 49.831633] XENBUS: Unable to read cpu state
> [ = 49.831851] XENBUS: Unable to read cpu state
> [ 49.832132] xenbus= _probe_devices backend
> [ 49.832283] xenbus_probe_devices failed x= enbus_directory
> [ 49.832331] backend_probe_and_watch devices prob= ed ok
> [ 49.832494] backend_probe_and_watch watch add ok ok
>= ; [ 49.832541] backend_probe_and_watch all done
> [ 49.832581] xe= nbus_probe_devices device
> [ 49.832731] xenbus_probe_devices failed xenbus_directory
> [ 49.832777] fronte= nd_probe_and_watch devices probed ok
> [ 49.832948] frontend_probe_= and_watch watch add ok ok
> [ 49.832995] frontend_probe_and_watch a= ll done
> [ 49.910018] peth1: no IPv6 routers present
> [ 5= 1.062517] eth1: no IPv6 routers present
> [ 173.299352] vif1.0 (vif)= : not using net_device_ops yet
>
> Last lines of dmesg report = Xen 3.4 (2.6.30-rc3-tip) instance been built on
Ubuntu 8.10
>
= >
> [ 54.856147] sky2 peth0: enabling interface
> [ 54.= 856810] ADDRCONF(NETDEV_UP): peth0: link is not ready
> [ 55.777286= ] skge eth1: enabling interface
> [ 55.781784] ADDRCONF(NETDEV_UP):= eth1: link is not ready
> [ 56.521131] sky2 peth0: Link is up at 1= 00 Mbps, full duplex, flow
control both
> [ 56.521765] ADDRCONF(= NETDEV_CHANGE): peth0: link becomes ready
> [ 56.905093] device peth0 entered promiscuous mode
> [ 56.917357] eth0: topolog= y change detected, propagating
> [ 56.917362] eth0: port 1(peth0) e= ntering forwarding state
> [ 64.531928] xenbus_probe wake_waiting> [ 64.531984] xenbus_probe wake_waiting
> [ 64.542317] XENB= US: Unable to read cpu state
> [ 64.542486] XENBUS: Unable to read = cpu state
> [ 64.542661] XENBUS: Unable to read cpu state
> [= 64.542828] XENBUS: Unable to read cpu state
> [ 64.543137] xenbu= s_probe_devices backend
> [ 64.543313] xenbus_probe_devices failed = xenbus_directory
> [ 64.543356] backend_probe_and_watch devices pro= bed ok
> [ 64.543514] backend_probe_and_watch watch add ok ok
&g= t; [ 64.543557] backend_probe_and_watch all done
> [ 64.543599] x= enbus_probe_devices device
> [ 64.543776] xenbus_probe_devices fail= ed xenbus_directory
> [ 64.543818] frontend_probe_and_watch devices probed ok
> [ 64.543972] frontend_probe_and_watch watch ad= d ok ok
> [ 64.544021] frontend_probe_and_watch all done
> [ = 67.040013] peth0: no IPv6 routers present
> [ 67.890015] eth0: no= IPv6 routers present
> [ 118.012469] vif1.0 (vif): not using net_de= vice_ops yet
> [ 118.127252] device vif1.0 entered promiscuous mode<= br>> [ 118.130694] eth0: topology change detected, propagating
> = [ 118.130701] eth0: port 2(vif1.0) entering forwarding state
> [ 12= 2.657298] blkback: ring-ref 8, event-channel 9, protocol 1
(x86_64-abi)<= br>> [ 128.700025] vif1.0: no IPv6 routers present
> [ 183.76125= 2] eth0: port 2(vif1.0) entering disabled state
> [ 183.800702] eth0= : port 2(vif1.0) entering disabled state
>
> Line:-
> > [ 122.657298] blkback: ring-ref 8, event-channel 9, protocol 1
(= x86_64-abi)
>
> is absent in first report. I believe it's a Dom0's kernel message
from network
> backend driver. Insta= nces dual boot on the same box.
>

I've seen similar things wh= en building xenbus as modules; the backend
modules don't get auto-loaded= . Either compiling them non-modular or
manually loading the modules wor= ks.

If that doesn't work, I'm not sure what's going on.

J<= br>
_______________________________________________
Xen-devel mailing= list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-de= vel

=0A=0A --0-1390217167-1242119269=:15747-- --===============2090450346== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============2090450346==--