xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Jia Rao <rickenrao@gmail.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Problems with xen and linux 2.26.32 kernels for dom0
Date: Fri, 18 Jun 2010 11:24:41 -0400	[thread overview]
Message-ID: <AANLkTil7Fg0uI5xJ-7zObZsLJVXEfIVu2AxqP95WFFwo@mail.gmail.com> (raw)
In-Reply-To: <20100617130857.GA3474@phenom.dumpdata.com>


[-- Attachment #1.1: Type: text/plain, Size: 1946 bytes --]

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

[-- Attachment #1.2: Type: text/html, Size: 2576 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

      reply	other threads:[~2010-06-18 15:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-16 19:00 Problems with xen and linux 2.26.32 kernels for dom0 Jia Rao
2010-06-16 19:43 ` Konrad Rzeszutek Wilk
2010-06-16 21:06   ` Jia Rao
2010-06-17 13:08     ` Konrad Rzeszutek Wilk
2010-06-18 15:24       ` Jia Rao [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AANLkTil7Fg0uI5xJ-7zObZsLJVXEfIVu2AxqP95WFFwo@mail.gmail.com \
    --to=rickenrao@gmail.com \
    --cc=konrad.wilk@oracle.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).