On Wed, May 13, 2009 at 08:47:55PM +0100, Iain J. Watson wrote:
> On Sun, Apr 19, 2009 at 3:31 PM, Eric Lenio <
eric@xxxxxxxxx> wrote:
> > Hello list. My server:
> >
> > Gentoo 2.6.21-xen dom0
> > xen-tools 3.2.1
> > lvm 2.02.28-r2
> > udev-115-r1
> >
> >
> > Symptoms: normally I run 4 domUs. About once a week I have a need to
> > restart a domU. Sometimes it works just fine, but other times it does not
> > and I'll get a message back saying "Error: Device 0 (vif) could not be
> > connected. Hotplug scripts not working". The domU config file has not been
> > changed so I'm fairly certain it is configured properly. I think it comes
> > down to the domU not being able to "talk" with udevd. I know udevd is
> > still running and is responsive (if I run udevmonitor and mount/umount a
> > disk I see normal output). When I attempt to start my domU I normally see
> > udevmonitor output like this:
> >
> > UEVENT[1240149226.992189] add /devices/xen-backend/vbd-9-2048 (xen-backend)
> > UDEV [1240149226.993163] add /devices/xen-backend/vbd-9-2048 (xen-backend)
> > UEVENT[1240149227.012202] add /devices/xen-backend/vbd-9-2064 (xen-backend)
> > UDEV [1240149227.013301] add /devices/xen-backend/vbd-9-2064 (xen-backend)
> > UEVENT[1240149227.045410] add /devices/xen-backend/vif-9-0 (xen-backend)
> > UDEV [1240149227.048638] add /devices/xen-backend/vif-9-0 (xen-backend)
> > UEVENT[1240149227.051320] add /devices/virtual/net/vif9.0 (net)
> > UEVENT[1240149227.051805] online /devices/xen-backend/vif-9-0 (xen-backend)
> > UDEV [1240149227.054369] online /devices/xen-backend/vif-9-0 (xen-backend)
> > UDEV [1240149227.062738] add /devices/virtual/net/vif9.0 (net)
> > UEVENT[1240149227.108918] add /devices/xen-backend/console-9-0 (xen-backend)
> > UDEV [1240149227.110112] add /devices/xen-backend/console-9-0 (xen-backend)
> >
> >
> > But when the issue happens I see no udevmonitor output. Restarting udevd
> > did not help. The problem does not seem specific to any particular domU --
> > once the condition happens, none of the domUs will restart. My only
> > solution so far has been to restart dom0. Suggestions?
> >
>
> I am having a similar problem. I don't know about the complete lack of udevd
> activity as I didn't know about that command but I'll be checking tomorrow.
>
> Did you have any luck chasing this problem down?
>
> Regards,
> Iain Watson