Hi everybody, I''m trying to boot a domU and after some kernel messages I''m having the following message: XENBUS: Waiting for devices to initialise: 295s...290s...285s...280s...275s...270s...265s...260s...255s...250s...245s...240s...235s...230s...225s...220s...root@moon:~# Error: Device 0 (vif) could not be connected. Hotplug scripts not working. Does anybody know which "hotplug scripts" is not working? Where are those scripts on the file system? and how can I run them from a command line in order to find the problem? Thanks in advance ... Ronaldo _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> Hi everybody, > > I''m trying to boot a domU and after some kernel messages I''m having > the following message: > > XENBUS: Waiting for devices to initialise: >295s...290s...285s...280s...275s...270s...265s...260s...255s...250s...24 5s...2> 40s...235s...230s...225s...220s...root@moon:~# > Error: Device 0 (vif) could not be connected. Hotplug scripts not > working. > > Does anybody know which "hotplug scripts" is not working? Where are > those scripts on the file system? and how can I run them from a > command line in order to find the problem? >My best guess would be that you haven''t loaded the network backend module (''modprobe netbk'' or just add it to your ''/etc/modules'' file and reboot). If that''s the case, then you probably also want to load ''blkbk'' too and possibly a few others... James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi James, Actually I have the following drivers compiled as "built-in". Is there any way to "debug" the hotplug scripts? I mean, how can I see the hotplug executing on the fly (while the domU is booting)? Thanks []s Ronaldo On Sat, 2009-08-22 at 16:14 +1000, James Harper wrote:> > Hi everybody, > > > > I''m trying to boot a domU and after some kernel messages I''m having > > the following message: > > > > XENBUS: Waiting for devices to initialise: > > > 295s...290s...285s...280s...275s...270s...265s...260s...255s...250s...24 > 5s...2 > > 40s...235s...230s...225s...220s...root@moon:~# > > Error: Device 0 (vif) could not be connected. Hotplug scripts not > > working. > > > > Does anybody know which "hotplug scripts" is not working? Where are > > those scripts on the file system? and how can I run them from a > > command line in order to find the problem? > > > > My best guess would be that you haven''t loaded the network backend > module (''modprobe netbk'' or just add it to your ''/etc/modules'' file and > reboot). If that''s the case, then you probably also want to load ''blkbk'' > too and possibly a few others... > > James_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> Hi James, > > Actually I have the following drivers compiled as "built-in". > Is there any way to "debug" the hotplug scripts? > I mean, how can I see the hotplug executing on the fly (while the domU > is booting)? > Thanks >There could be but it would be a bit messy (turn on tracing in the shell and dump the output somewhere perhaps?) The setup process is approximately that the frontend driver (in domu or qemu) set the state to ''initialising'' in xenstore, then write an event channel number and a few grant ref numbers to xenstore, then set the state the ''connecting''. If the backend is happy with the setup it sets the state to ''connected'' and then so does the frontend (as I said, approximately, I may have the actual state transitions wrong). Can you post your kernel config, and also the output of ''xenstore-ls'' while the ''waiting for devices to initialise'' countdown is in progress James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Sun, Aug 23, 2009 at 6:57 AM, James Harper<james.harper@bendigoit.com.au> wrote:> Can you post your kernel config, and also the output of ''xenstore-ls'' > while the ''waiting for devices to initialise'' countdown is in progressI find that "Hotplug scripts not working." is usually a general error message. Sometimes the problem is just that : hotplug scripts not working, possibly because udev is dead, while other times it''s something harder to find out. So it would help to post: - domU config file (usually on /etc/xen, or from /var/lib/xend/domains) - the output of "brctl show" - /var/log/xen/xend.log (the relevant part only) -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi, The problem in my case was that the udev rules was not being copied to the /etc/udev/rules.d directory. I''m using Slackware and I did the installation this way: make tools make install-tools Well, now it''s working. Thanks. Ronaldo On Sun, 2009-08-23 at 21:22 +0700, Fajar A. Nugraha wrote:> On Sun, Aug 23, 2009 at 6:57 AM, James > Harper<james.harper@bendigoit.com.au> wrote: > > Can you post your kernel config, and also the output of ''xenstore-ls'' > > while the ''waiting for devices to initialise'' countdown is in progress > > I find that "Hotplug scripts not working." is usually a general error > message. Sometimes the problem is just that : hotplug scripts not > working, possibly because udev is dead, while other times it''s > something harder to find out. > > So it would help to post: > - domU config file (usually on /etc/xen, or from /var/lib/xend/domains) > - the output of "brctl show" > - /var/log/xen/xend.log (the relevant part only) >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users