From: Boris Derzhavets Subject: 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: Sat, 9 May 2009 12:41:47 -0700 (PDT) Message-ID: <757214.78953.qm@web56107.mail.re3.yahoo.com> References: <347626.33558.qm@web56105.mail.re3.yahoo.com> Reply-To: bderzhavets@yahoo.com Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1744388051==" Return-path: In-Reply-To: <347626.33558.qm@web56105.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: Jeremy Fitzhardinge Cc: xen-devel List-Id: xen-devel@lists.xenproject.org --===============1744388051== Content-Type: multipart/alternative; boundary="0-440771607-1241898107=:78953" --0-440771607-1241898107=:78953 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Last lines of dmesg report Xen 3.4 (2.6.30-rc3-tip) instance been built on = Ubuntu 9.04 Server ( IP6v by default) [=A0=A0 29.214154] skge eth0: enabling interface [=A0=A0 29.218498] ADDRCONF(NETDEV_UP): eth0: link is not ready [=A0=A0 29.630012] eth1: no IPv6 routers present [=A0=A0 38.012544] sky2 eth1: disabling interface [=A0=A0 38.092791] sky2 peth1: enabling interface [=A0=A0 38.093450] ADDRCONF(NETDEV_UP): peth1: link is not ready [=A0=A0 39.776997] sky2 peth1: Link is up at 100 Mbps, full duplex, flow co= ntrol both [=A0=A0 39.777643] ADDRCONF(NETDEV_CHANGE): peth1: link becomes ready [=A0=A0 40.145017] device peth1 entered promiscuous mode [=A0=A0 40.182778] eth1: topology change detected, propagating [=A0=A0 40.182783] eth1: port 1(peth1) entering forwarding state [=A0=A0 49.820430] xenbus_probe wake_waiting [=A0=A0 49.820491] xenbus_probe wake_waiting [=A0=A0 49.829859] XENBUS: Unable to read cpu state [=A0=A0 49.831443] XENBUS: Unable to read cpu state [=A0=A0 49.831633] XENBUS: Unable to read cpu state [=A0=A0 49.831851] XENBUS: Unable to read cpu state [=A0=A0 49.832132] xenbus_probe_devices backend [=A0=A0 49.832283] xenbus_probe_devices failed xenbus_directory [=A0=A0 49.832331] backend_probe_and_watch devices probed ok [=A0=A0 49.832494] backend_probe_and_watch watch add ok ok [=A0=A0 49.832541] backend_probe_and_watch all done [=A0=A0 49.832581] xenbus_probe_devices device [=A0=A0 49.832731] xenbus_probe_devices failed xenbus_directory [=A0=A0 49.832777] frontend_probe_and_watch devices probed ok [=A0=A0 49.832948] frontend_probe_and_watch watch add ok ok [=A0=A0 49.832995] frontend_probe_and_watch all done [=A0=A0 49.910018] peth1: no IPv6 routers present [=A0=A0 51.062517] eth1: no IPv6 routers present [=A0 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 [=A0=A0 54.856147] sky2 peth0: enabling interface [=A0=A0 54.856810] ADDRCONF(NETDEV_UP): peth0: link is not ready [=A0=A0 55.777286] skge eth1: enabling interface [=A0=A0 55.781784] ADDRCONF(NETDEV_UP): eth1: link is not ready [=A0=A0 56.521131] sky2 peth0: Link is up at 100 Mbps, full duplex, flow co= ntrol both [=A0=A0 56.521765] ADDRCONF(NETDEV_CHANGE): peth0: link becomes ready [=A0=A0 56.905093] device peth0 entered promiscuous mode [=A0=A0 56.917357] eth0: topology change detected, propagating [=A0=A0 56.917362] eth0: port 1(peth0) entering forwarding state [=A0=A0 64.531928] xenbus_probe wake_waiting [=A0=A0 64.531984] xenbus_probe wake_waiting [=A0=A0 64.542317] XENBUS: Unable to read cpu state [=A0=A0 64.542486] XENBUS: Unable to read cpu state [=A0=A0 64.542661] XENBUS: Unable to read cpu state [=A0=A0 64.542828] XENBUS: Unable to read cpu state [=A0=A0 64.543137] xenbus_probe_devices backend [=A0=A0 64.543313] xenbus_probe_devices failed xenbus_directory [=A0=A0 64.543356] backend_probe_and_watch devices probed ok [=A0=A0 64.543514] backend_probe_and_watch watch add ok ok [=A0=A0 64.543557] backend_probe_and_watch all done [=A0=A0 64.543599] xenbus_probe_devices device [=A0=A0 64.543776] xenbus_probe_devices failed xenbus_directory [=A0=A0 64.543818] frontend_probe_and_watch devices probed ok [=A0=A0 64.543972] frontend_probe_and_watch watch add ok ok [=A0=A0 64.544021] frontend_probe_and_watch all done [=A0=A0 67.040013] peth0: no IPv6 routers present [=A0=A0 67.890015] eth0: no IPv6 routers present [=A0 118.012469] vif1.0 (vif): not using net_device_ops yet [=A0 118.127252] device vif1.0 entered promiscuous mode [=A0 118.130694] eth0: topology change detected, propagating [=A0 118.130701] eth0: port 2(vif1.0) entering forwarding state [=A0 122.657298] blkback: ring-ref 8, event-channel 9, protocol 1 (x86_64-a= bi) [=A0 128.700025] vif1.0: no IPv6 routers present [=A0 183.761252] eth0: port 2(vif1.0) entering disabled state [=A0 183.800702] eth0: port 2(vif1.0) entering disabled state Line:- [=A0 122.657298] blkback: ring-ref 8, event-channel 9, protocol 1 (x86_64-a= bi) is absent in first report. I believe it's a Dom0's kernel message from netw= ork backend driver. Instances dual boot on the same box. Boris. =0A=0A=0A --0-440771607-1241898107=:78953 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable
Last lines of dmesg report Xen 3.4 (2.6.30-rc= 3-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.63= 0012] eth1: no IPv6 routers present
[   38.012544] sky2 eth1: = disabling interface
[   38.092791] sky2 peth1: enabling interf= ace
[   38.093450] ADDRCONF(NETDEV_UP): peth1: link is not rea= dy
[   39.776997] sky2 peth1: Link is up at 100 Mbps, full dup= lex, flow control both
[   39.777643] ADDRCONF(NETDEV_CHANGE):= peth1: link becomes ready
[   40.145017] device peth1 entered= promiscuous mode
[   40.182778] eth1: topology change detecte= d, propagating
[   40.182783] eth1: port 1(peth1) entering forwarding state
[   49.820430] xenbus_probe wake_waiting
= [   49.820491] xenbus_probe wake_waiting
[   49.8298= 59] XENBUS: Unable to read cpu state
[   49.831443] XENBUS: Un= able to read cpu state
[   49.831633] XENBUS: Unable to read c= pu state
[   49.831851] XENBUS: Unable to read cpu state
[&= nbsp;  49.832132] xenbus_probe_devices backend
[   49.832= 283] xenbus_probe_devices failed xenbus_directory
[   49.83233= 1] backend_probe_and_watch devices probed ok
[   49.832494] ba= ckend_probe_and_watch watch add ok ok
[   49.832541] backend_p= robe_and_watch all done
[   49.832581] xenbus_probe_devices de= vice
[   49.832731] xenbus_probe_devices failed xenbus_directo= ry
[   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.06251= 7] eth1: no IPv6 routers present
[  173.299352] vif1.0 (vif): not u= sing net_device_ops yet

Last lines of dmesg report Xen 3.4 (2.6.30-r= c3-tip) instance been built on Ubuntu 8.10


[   54.8561= 47] sky2 peth0: enabling interface
[   54.856810] ADDRCONF(NET= DEV_UP): peth0: link is not ready
[   55.777286] skge eth1: en= abling interface
[   55.781784] ADDRCONF(NETDEV_UP): eth1: lin= k is not ready
[   56.521131] sky2 peth0: Link is up at 100 Mb= ps, full duplex, flow control both
[   56.521765] ADDRCONF(NET= DEV_CHANGE): peth0: link becomes ready
[   56.905093] device p= eth0 entered promiscuous mode
[   56.917357] eth0: topology ch= ange detected, propagating
[   56.917362] eth0: port 1(peth0) entering forwarding state
[   64.531928] xenbus_prob= e wake_waiting
[   64.531984] xenbus_probe wake_waiting
[&n= bsp;  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 re= ad cpu state
[   64.543137] xenbus_probe_devices backend
[&= nbsp;  64.543313] xenbus_probe_devices failed xenbus_directory
[&nb= sp;  64.543356] backend_probe_and_watch devices probed ok
[ &n= bsp; 64.543514] backend_probe_and_watch watch add ok ok
[   64= .543557] backend_probe_and_watch all done
[   64.543599] xenbu= s_probe_devices device
[   64.543776] xenbus_probe_devices fai= led xenbus_directory
[   64.543818] frontend_probe_and_watch d= evices probed ok
[   64.543972] frontend_probe_and_watch watch add ok ok
[   64.544021] front= end_probe_and_watch all done
[   67.040013] peth0: no IPv6 rou= ters present
[   67.890015] eth0: no IPv6 routers present
[=   118.012469] vif1.0 (vif): not using net_device_ops yet
[  11= 8.127252] device vif1.0 entered promiscuous mode
[  118.130694] eth= 0: topology change detected, propagating
[  118.130701] eth0: port = 2(vif1.0) entering forwarding state
[  122.657298] blkback: ring-re= f 8, event-channel 9, protocol 1 (x86_64-abi)
[  128.700025] vif1.0= : no IPv6 routers present
[  183.761252] eth0: port 2(vif1.0) enter= ing disabled state
[  183.800702] eth0: port 2(vif1.0) entering dis= abled state

Line:-

[  122.657298] blkback: ring-ref 8, e= vent-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.

Boris.


=0A=0A --0-440771607-1241898107=:78953-- --===============1744388051== 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 --===============1744388051==--