All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Pasi Kärkkäinen" <pasik@iki.fi>
To: xen-devel@lists.xensource.com
Cc: Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Latest pvops dom0 kernel and missing /dev/xen/evtchn, xenstored and xend not starting
Date: Sat, 19 Jun 2010 15:32:36 +0300	[thread overview]
Message-ID: <20100619123236.GD17817@reaktio.net> (raw)

Hello,

I know there has been some discussion about this already, 
but I just noticed it myself when I upgraded my testbox.

So, I have Xen 4.0.0, and the latest xen/stable-2.6.32.x dom0 kernel, ie. 2.6.32.15.

On system startup I notice xenstored and xend fail to start.
I look around and notice /dev/xen/ is empty.

I do "rmmod xen-evtchn" and "modprobe xen-evtchn" and then I have:

# ls -la /dev/xen
total 0
drwxr-xr-x  2 root root     60 Jun 19 15:22 .
drwxr-xr-x 20 root root   4580 Jun 19 15:20 ..
crw-rw----  1 root root 10, 58 Jun 19 15:22 evtchn

Based on some earlier emails it has wrong major/minor? 

Also "modprobe xen-gntdev" gives this:

# ls -la /dev/xen
total 0
0 crw-rw---- 1 root root 10, 58 Jun 19 15:22 evtchn
0 crw-rw---- 1 root root 10, 57 Jun 19 15:25 gntdev

So what's the actual problem here? I guess something got changed in the kernel,
and now xen tools/scripts should create the devnodes with a different major/minor? 

Is the correct fix to upgrade Xen to 4.0.1-rcX ? 

I just want to get this correct so I can update the wiki pages.. 
it seems many people hit this problem.

Thanks!

-- Pasi

             reply	other threads:[~2010-06-19 12:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-19 12:32 Pasi Kärkkäinen [this message]
2010-06-19 12:44 ` Latest pvops dom0 kernel and missing /dev/xen/evtchn, xenstored and xend not starting Boris Derzhavets
2010-06-19 13:18   ` Pasi Kärkkäinen
2010-06-19 13:32     ` Boris Derzhavets
2010-06-19 13:37       ` Pasi Kärkkäinen
2010-06-19 15:21         ` Jeremy Fitzhardinge
2010-06-19 16:38           ` Pasi Kärkkäinen
2010-06-19 17:42             ` Jeremy Fitzhardinge
2010-06-19 18:04               ` Pasi Kärkkäinen

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=20100619123236.GD17817@reaktio.net \
    --to=pasik@iki.fi \
    --cc=jeremy@goop.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.