From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jia Rao Subject: Re: Problems with xen and linux 2.26.32 kernels for dom0 Date: Fri, 18 Jun 2010 11:24:41 -0400 Message-ID: References: <20100616194310.GB8413@phenom.dumpdata.com> <20100617130857.GA3474@phenom.dumpdata.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0630746411==" Return-path: In-Reply-To: <20100617130857.GA3474@phenom.dumpdata.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Konrad Rzeszutek Wilk Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org --===============0630746411== Content-Type: multipart/alternative; boundary=0015174789dccde81b04894f8d7b --0015174789dccde81b04894f8d7b Content-Type: text/plain; charset=ISO-8859-1 Finally the 2.6.32 pvops dom0 booted with xen 4.0. However the xend can not start. I believe that is something related to the *evtchn*. I compile the CONFIG_XEN_DEV_EVTCHN=y in kernel, so i donot need to load it. When the dom0 booted, I can see there is a entry for evtchn in /dev/xen along with gntdev. But when xend starts, the evtchn in /dev/xen disappeared. and xend is not properly started. The error log in /var/log/xen/xend.log is the following: [2010-06-18 10:51:35 4685] INFO (SrvDaemon:332) Xend Daemon started [2010-06-18 10:51:35 4685] INFO (SrvDaemon:336) Xend changeset: unavailable. [2010-06-18 10:51:35 4685] ERROR (SrvDaemon:349) Exception starting xend ((111, 'Connection refused')) I am using a centos 5, which has an old udev. I tried to modified the udev rules in /etc/udev/rules.d/xen-backend.rules and changed evtchn to xen-evtchn. No luck. Any ideas? Thanks. On Thu, Jun 17, 2010 at 9:08 AM, Konrad Rzeszutek Wilk < konrad.wilk@oracle.com> wrote: > > > > generated initrd, dom0 can not boot. I got the error: *unable to > locate > > > > IOAPIC for GSIx and mount: could not find filesystem: /dev/root*. > > > > I enabled : CONFIG_SYSFS_DEPRECATED=y, CONFIG_SYSFS_DEPRECATED_V2=y > and > > > > tried to use root=/dev/sdax or root=LABEL=/. No luck. > > > > > > You did follow the the Wiki: > > > http://wiki.xensource.com/xenwiki/2.6.18-to-2.6.31-and-higher > > > > > > and made sure you had the right SATA drivers compiled in? They changed > > > their names from .18 to .31-and-higher > > > > > > > > > > > I tried the script with the pvops, the dom0 still cannt boot. How can I > > check if other modules have changed the name besides ata_piix ? > > > find /sys/class/scsi_host/host*/proc_name | xargs cat > > If the name of the module exists in 2.6.32, OK, otherwise use Google. > > You did also use the 'new-kernel-package' to insert your new kernel > and/or ran 'mkinitrd' (pre FC12) or 'dracut' (past FC12). > --0015174789dccde81b04894f8d7b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Finally the 2.6.32 pvops dom0 booted with xen 4.0. However the xend can not= start.
I believe that is something related to the evtchn.
I = compile the CONFIG_XEN_DEV_EVTCHN=3Dy in kernel, so i donot need to load it= . When the dom0 booted, I can see there is a entry for evtchn in /dev/xen a= long with gntdev.

But when xend starts, the evtchn in /dev/xen disappeared. and xend is n= ot properly started.
The error log in /var/log/xen/xend.log is the follo= wing:

[2010-06-18 10:51:35 4685] INFO (SrvDaemon:332) Xend Daemon st= arted
[2010-06-18 10:51:35 4685] INFO (SrvDaemon:336) Xend changeset: unavailable= .
[2010-06-18 10:51:35 4685] ERROR (SrvDaemon:349) Exception starting xe= nd ((111, 'Connection refused'))

I am using a centos 5, whic= h has an old udev. I tried to modified the udev rules in /etc/udev/rules.d/= xen-backend.rules and changed evtchn to xen-evtchn. No luck.

Any ideas?

Thanks.

On Thu, Jun= 17, 2010 at 9:08 AM, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wr= ote:
> > > generated initrd, dom0 can not boot. I got the error: *unab= le to locate
> > > IOAPIC for GSIx and mount: could not find filesystem: /dev/r= oot*.
> > > I enabled : CONFIG_SYSFS_DEPRECATED=3Dy, =A0CONFIG_SYSFS_DEP= RECATED_V2=3Dy and
> > > tried to use root=3D/dev/sdax or root=3DLABEL=3D/. No luck.<= br> > >
> > You did follow the the Wiki:
> > http://wiki.xensource.com/xenwiki/2.6.18-to-2.6.= 31-and-higher
> >
> > and made sure you had the right SATA drivers compiled in? They ch= anged
> > their names from .18 to .31-and-higher
> > >
> >
>
> I tried the script with the pvops, the dom0 still cannt boot. How can = I
> check if other modules have changed the name besides ata_piix ?


find /sys/class/scsi_host/host*/proc_name | xargs cat

If the name of the module exists in 2.6.32, OK, otherwise use Google.

You did also use the 'new-kernel-package' to insert your new kernel=
and/or ran 'mkinitrd' (pre FC12) or 'dracut' (past FC12).

--0015174789dccde81b04894f8d7b-- --===============0630746411== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============0630746411==--