Re: [Xen-devel] Report Xen-3.1.1-rc1 make install does not install /etc/hotplug

["Teck Choon Giam" <giamteckchoon@xxxxxxxxx>]

On 9/26/07, Keir Fraser <Keir.Fraser@xxxxxxxxxxxx> wrote:
> On 25/9/07 19:27, "Teck Choon Giam" <giamteckchoon@xxxxxxxxx> wrote:
>
> > 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?
>
> The question is really why your system doesn't pick up the udev config files
> we install, and work properly with those. I wouldn't really expect it to
> need the hotplug config file.

Maybe this is something to do with this bug?
http://bugs.centos.org/view.php?id=2141

It is uncommon to see error related to fd or cdrom especially if
compare CentOS 4 and CentOS 5.  In CentOS 4 using the exact same
hardware and specs/configuration of the kernel I don't see the
following errors:

# dmesg|grep -i error
hdd: packet command error: status=0x51 { DriveReady SeekComplete Error }
hdd: packet command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
hdd: packet command error: status=0x51 { DriveReady SeekComplete Error }
hdd: packet command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
hdd: packet command error: status=0x51 { DriveReady SeekComplete Error }
hdd: packet command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }

But in CentOS 5, the above errors are shown :/

Even doing yum update and updating kernels will see the above errors
and even fd related error in one of my system... ...

I will try to append different boot option such as pci=noacpi etc
and/or disable fd and/or cdrom the next time to the data center to see
whether
xen-backend.rules in /etc/udev/rules.d/ works or not... ...

# ls -al /etc/udev/rules.d/
total 100
drwxr-xr-x 2 root root  4096 Sep 26 05:28 .
drwxr-xr-x 4 root root  4096 Sep 26 05:28 ..
-rw-r--r-- 1 root root   515 Mar 15  2007 05-udev-early.rules
-rw-r--r-- 1 root root 14344 Mar 15  2007 50-udev.rules
-rw-r--r-- 1 root root   471 Mar 15  2007 51-hotplug.rules
-rw-r--r-- 1 root root   143 Apr 11  2006 60-net.rules
-rw-r--r-- 1 root root  1088 Jan  7  2007 60-pcmcia.rules
-rw-r--r-- 1 root root   452 Mar 15  2007 60-raw.rules
-rw-r--r-- 1 root root    82 Mar 15  2007 90-hal.rules
-rw-r--r-- 1 root root   107 Mar 15  2007 95-pam-console.rules
-rw-r--r-- 1 root root  2319 Mar 28 13:48 bluetooth.rules
lrwxrwxrwx 1 root root    20 Sep 26 05:28 xen-backend.rules ->
../xen-backend.rules

Thanks Keir for the tip ;)

Kindest regards,
Giam Teck Choon

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel