From: Jeremy Fitzhardinge Subject: 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: Mon, 11 May 2009 15:51:59 -0700 Message-ID: <4A08AC0F.5050001@goop.org> References: <757214.78953.qm@web56107.mail.re3.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <757214.78953.qm@web56107.mail.re3.yahoo.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: bderzhavets@yahoo.com Cc: xen-devel List-Id: xen-devel@lists.xenproject.org Boris Derzhavets wrote: > Last lines of dmesg report Xen 3.4 (2.6.30-rc3-tip) instance been > built on Ubuntu 9.04 Server ( IP6v by default) > > [ 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 > > 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 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 > > 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. Instances dual boot on the same box. > 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