On 9/26/07, Keir Fraser <Keir.Fraser@xxxxxxxxxxxx> wrote:
> 'make install' probably decided that your system uses udev rather than
> hotplug. This will be because 'udevinfo -V' on your system indicates a
> version greater than or equal to 059.
Hi Keir,
Thanks for your information about udevinfo. Yes, you are right as
this is the output shown in my test CentOS 5.0:
# udevinfo -V
udevinfo, version 095
and in CentOS 4.5 it is:
# udevinfo -V
udevinfo, version 039
So would this means that for any udevinfo version greater than 059, I
have to manually create /etc/hotplug folder and copy xen-backend.agent
into it manually for future releases for Xen i.e. version 3.1.1?
>
> -- Keir
Thanks Keir for your prompt reply :)
Kindest regards,
Giam Teck Choon
>
> On 25/9/07 19:09, "Teck Choon Giam" <giamteckchoon@xxxxxxxxx> wrote:
>
> > Hi,
> >
> > This is my testing in a fresh CentOS 5.0 system. I downloaded the
> > xen-3.1.1-rc1 aka xen-3.1-testing.hg and do my normal make world and
> > make install.
> >
> > # ls -al /etc/hotplug/xen-backend.agent
> > ls: /etc/hotplug/xen-backend.agent: No such file or directory
> >
> > # ls -al /usr/src/xen-3.1.1-rc1-src/dist/install/etc/hotplug/
> > total 12
> > drwxr-xr-x 2 root root 4096 Sep 25 12:44 .
> > drwxr-xr-x 7 root root 4096 Sep 25 12:44 ..
> > -rwxr-xr-x 1 root root 513 Sep 2 08:31 xen-backend.agent
> >
> > I just did the mkdir /etc/hotplug and copy the xen-backend.agent to it
> > or else domainU can't be started and will show you error such as:
> >
> > Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
> > Error: Device 2049 (vbd) could not be connected. Hotplug scripts not 
> > working.
> >
> > Thanks.
> >
> > Kindest regards,
> > Giam Teck Choon
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-devel 
>
>
>
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel