WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

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

To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] Report Xen-3.1.1-rc1 make install does not install /etc/hotplug
From: "Teck Choon Giam" <giamteckchoon@xxxxxxxxx>
Date: Wed, 26 Sep 2007 15:04:10 +0800
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 26 Sep 2007 00:04:51 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=dA9Gr6JjrmVwa2e90beghOqYFNiuOuGMrMQTDk772yM=; b=femFEp4EMqH/dKc/OPtp7/2+W2QlFvmSg1h6oD7Dl/M+31HkbqU7NF8jEouzxw/IZ3EIeuap99l614qONm7Vj7mx6+NNPETzR2tNxru8nHmK98uVAyBGU9f7DmYfPf0IOz++Pn+Gpvj+Rb+F3Ayj5YeK81Z38CPh3/xCtk4ZbC4=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=nv/QKSrRrH4DaTgLsfwC2ojFNhL9zds5qknMUdYfQupdateXN6wf92uXnMNKYAqc39yY8aynq8nJplg6VzzTJJcVycCZp1D72gZ0TCRovgHxeybPNrX0a5lzeYswJYUfb2NajX1z/OjjEpIsaBxjvbah/SMW7UFW8qt85AjApJM=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C31F392F.E070%Keir.Fraser@xxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <9b5c9bb30709251127n56b086a0if24315928bc7b4e8@xxxxxxxxxxxxxx> <C31F392F.E070%Keir.Fraser@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
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