[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Problems with xen and linux 2.26.32 kernels for dom0


  • To: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
  • From: Jia Rao <rickenrao@xxxxxxxxx>
  • Date: Fri, 18 Jun 2010 11:24:41 -0400
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Fri, 18 Jun 2010 08:25:26 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=U66fLNcBH1Dxsg4QWSAHeaEXw6FHpivb/bOGxU+j7+TRTaLaAqvWR3z83Dae6Xfea5 uGp6+AOcNzXQjsEfoHmgdf+J1MZQ6rUsTOHEmuIp8X2LdH5/2m0Au3UFQ1PDPzCBwAN0 ik0g8VspQ/5I1ehs+pNeOx6HUnMDriGxtFFCg=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

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@xxxxxxxxxx> 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).

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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.