[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] can't start domU
Ewan Mellor <ewan@xxxxxxxxxxxxx> wrote on 11/16/2005 12:45:39 PM: > On Wed, Nov 16, 2005 at 11:19:12AM -0600, Steve Dobbelstein wrote: > > > I'm not sure how to tell if /sbin/udevsend binary gets run. > > mv /sbin/udevsend{,.real} > cat >/sbin/udevsend > #!/bin/sh > echo "udevsend running" >>/var/log/udev.log > exec /sbin/udevsend.real > ^D > > ought to do it. Of course. My duh. I have been scratching my head over this and scrambling it with python code that I forgot the obvious. > I think that it's clear that the whole hotplug > subsystem isn't > running in your case, so I wouldn't worry about it. /var/log/udesend.log says: -------- Wed Nov 16 16:54:21 CST 2005 udevsend net Wed Nov 16 16:57:22 CST 2005 udevsend xen-backend Wed Nov 16 16:57:22 CST 2005 udevsend xen-backend -------- Looks like hotplug is initiated, but perhaps not for the vif stuff. > > [root@gir scripts]# PYTHONPATH=/usr/lib/python python > > /usr/lib/python/xen/util/diagnose.py 4 > > Domain ID is 4. > > Domain name is dom1. > > Found 1 device classes in use. > > Found 2 vbd devices. > > Found device vbd, 2049. > > Backend is in state Connected. > > Frontend is in state Connected. > > Device vbd, 2049 hotplugging has completed successfully, and is connected > > to physical device 0xfd01. > > Found device vbd, 2050. > > Backend is in state Connected. > > Frontend is in state Connected. > > Device vbd, 2050 hotplugging has completed successfully, and is connected > > to physical device 0xfd00. > > This suggests that the tools have not even got as far as trying to create a > vif for you. Are you getting the "Device 0 (vif) could not be connected. > Hotplug scripts not working." message, same as Charles Coffing? That really > would be very curious. In any case, your config file ought to be causing Xend > to at least try to create a vif. I will need to see your /var/log/xend.log to > pin this down, and if you can get a xenstore trace, that will be useful too. I had seen the "Device 0 (vif) could not be connected. Hotplug scripts not working." message on occasion in the past. It's not doing it now. Here are some helpful debug files. (See attached file: xend.log)(See attached file: xend.trace.gz)(See attached file: xend-debug.log)(See attached file: xenstored-trace.log.gz) I'm afraid this is going to end up being some user error because something got changed elsewhere on the system, but I can't figure out what. The machine used to not exhibit the problem with build 7713. I upgraded the machine to a later build (can't remember which offhand) and saw the problem. I then backed down to 7713 but still saw the problem. It has been doing it on every build since then. I have tried cleaning everything out (make uninstall, rm -rf /etc/xen, etc.) and rebuilding and reinstalling. I am beginning to suspect something outside of Xen is causing it to trip up. Thanks a lot for your help. Steve D. Attachment:
xend.log Attachment:
xend.trace.gz Attachment:
xend-debug.log Attachment:
xenstored-trace.log.gz _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |