From: Olaf Hering <olaf@aepfle.de>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: vif backend configuration times out
Date: Fri, 10 Aug 2012 09:41:59 +0200 [thread overview]
Message-ID: <20120810074159.GA11792@aepfle.de> (raw)
In-Reply-To: <20120809143406.GA9317@aepfle.de>
On Thu, Aug 09, Olaf Hering wrote:
> Indeed, netback_probe is appearently never called in my case. I will
> check why that happens.
What I have seen so far is that in 4.2+xl the vif driver is not
registered, while in 4.1+xm there is a vif driver registered. Thats so
far the difference I could spot.
I will post more results why that happens later.
Olaf
root@satriani:~ # grep xen-backend xl-dmesg-3.0.34-sles11sp2_olh-xen.txt
[ 0.149879] bus: 'xen-backend': registered
[ 0.149879] device: 'xen-backend': device_add
[ 0.149879] PM: Adding info for No Bus:xen-backend
[ 90.055240] bus: 'xen-backend': add device qdisk-1-768
[ 90.055252] PM: Adding info for xen-backend:qdisk-1-768
[ 90.064575] bus: 'xen-backend': add device qdisk-1-5632
[ 90.064584] PM: Adding info for xen-backend:qdisk-1-5632
[ 90.073196] bus: 'xen-backend': add device console-1-0
[ 90.073205] PM: Adding info for xen-backend:console-1-0
[ 90.081771] bus: 'xen-backend': add device vkbd-1-0
[ 90.081776] PM: Adding info for xen-backend:vkbd-1-0
[ 90.378494] bus: 'xen-backend': add device vif-1-0
[ 90.378504] PM: Adding info for xen-backend:vif-1-0
[ 100.401586] PM: Removing info for xen-backend:console-1-0
[ 100.401596] bus: 'xen-backend': remove device console-1-0
[ 102.400202] PM: Removing info for xen-backend:qdisk-1-768
[ 102.400212] bus: 'xen-backend': remove device qdisk-1-768
[ 102.406016] PM: Removing info for xen-backend:qdisk-1-5632
[ 102.406025] bus: 'xen-backend': remove device qdisk-1-5632
[ 102.411464] PM: Removing info for xen-backend:vkbd-1-0
[ 102.411473] bus: 'xen-backend': remove device vkbd-1-0
[ 110.410600] PM: Removing info for xen-backend:vif-1-0
[ 110.410610] bus: 'xen-backend': remove device vif-1-0
root@satriani:~ # grep xen-backend xm-dmesg-3.0.34-sles11sp2_olh-xen.txt
[ 0.150119] bus: 'xen-backend': registered
[ 0.150119] device: 'xen-backend': device_add
[ 0.150119] PM: Adding info for No Bus:xen-backend
[ 44.319441] bus: 'xen-backend': add driver tap
[ 44.338383] bus: 'xen-backend': add driver vbd
[ 44.367501] bus: 'xen-backend': add driver vif
[ 44.378095] bus: 'xen-backend': add driver vusb
[ 204.002506] bus: 'xen-backend': add device vfb-1-0
[ 204.002514] PM: Adding info for xen-backend:vfb-1-0
[ 204.017641] bus: 'xen-backend': add device vbd-1-768
[ 204.017650] PM: Adding info for xen-backend:vbd-1-768
[ 204.017663] bus: 'xen-backend': driver_probe_device: matched device vbd-1-768 with driver vbd
[ 204.017667] bus: 'xen-backend': really_probe: probing driver vbd with device vbd-1-768
[ 204.018903] bus: 'xen-backend': really_probe: bound device vbd-1-768 to driver vbd
[ 204.032488] bus: 'xen-backend': add device vbd-1-5632
[ 204.032494] PM: Adding info for xen-backend:vbd-1-5632
[ 204.032502] bus: 'xen-backend': driver_probe_device: matched device vbd-1-5632 with driver vbd
[ 204.032504] bus: 'xen-backend': really_probe: probing driver vbd with device vbd-1-5632
[ 204.033534] bus: 'xen-backend': really_probe: bound device vbd-1-5632 to driver vbd
[ 204.043973] bus: 'xen-backend': add device vif-1-0
[ 204.043980] PM: Adding info for xen-backend:vif-1-0
[ 204.043988] bus: 'xen-backend': driver_probe_device: matched device vif-1-0 with driver vif
[ 204.043990] bus: 'xen-backend': really_probe: probing driver vif with device vif-1-0
[ 204.049398] bus: 'xen-backend': really_probe: bound device vif-1-0 to driver vif
[ 204.739981] bus: 'xen-backend': add device console-1-0
[ 204.739993] PM: Adding info for xen-backend:console-1-0
[ 340.548887] PM: Removing info for xen-backend:console-1-0
[ 340.548902] bus: 'xen-backend': remove device console-1-0
[ 340.570464] PM: Removing info for xen-backend:vfb-1-0
[ 340.570470] bus: 'xen-backend': remove device vfb-1-0
[ 340.577394] PM: Removing info for xen-backend:vbd-1-768
[ 340.577403] bus: 'xen-backend': remove device vbd-1-768
[ 340.578784] PM: Removing info for xen-backend:vbd-1-5632
[ 340.578791] bus: 'xen-backend': remove device vbd-1-5632
[ 340.581006] PM: Removing info for xen-backend:vif-1-0
[ 340.581014] bus: 'xen-backend': remove device vif-1-0
next prev parent reply other threads:[~2012-08-10 7:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-06 17:39 vif backend configuration times out Olaf Hering
2012-08-07 5:42 ` Ian Campbell
2012-08-07 15:25 ` Olaf Hering
2012-08-07 15:33 ` Ian Campbell
2012-08-08 17:28 ` Olaf Hering
2012-08-09 8:32 ` Ian Campbell
2012-08-09 14:34 ` Olaf Hering
2012-08-10 7:41 ` Olaf Hering [this message]
2012-08-10 12:59 ` Olaf Hering
2012-08-14 10:18 ` Ian Campbell
2012-08-14 11:30 ` Olaf Hering
2012-08-14 13:04 ` Ian Campbell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120810074159.GA11792@aepfle.de \
--to=olaf@aepfle.de \
--cc=Ian.Campbell@citrix.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).