All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dan Magenheimer" <dan.magenheimer@oracle.com>
To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Problems "upgrading" 3.1 to 3.2?
Date: Tue, 18 Dec 2007 12:03:11 -0700	[thread overview]
Message-ID: <20071218120311250.00000002296@djm-pc> (raw)

[-- Attachment #1: Type: text/plain, Size: 1047 bytes --]

I have a 3.1-based system (OracleVM actually) and am trying to build/run xen-unstable on it (c/s 16618). From xen-unstable.hg, I am doing a "make distclean", then building and installing normally (plus normal depmod, mkinitrd, cp initrd, and grub.conf changes).  However when I reboot, xend won't run.  /var/log/xen/xend-debug.log says:

  sysctl operation failed -- need to rebuild the user-space tool set?
  Exception starting xend: (13, 'Permission denied')

Another "make install" and reboot still doesn't fix the problem.

I can build and run xen-unstable on another system with a fresh install with no xen, so I don't think it's pilot error.

Anybody else try "upgrading" and run into similar probs?  My xend is definitely the new one from xen-unstable, so I'm thinking there must be some leftover 3.1 residue messing things up.

IIRC from years ago, there was some trick to resolve a similar problem, e.g. removing /var/lib/xen* and rebooting but that doesn't work here.

Thanks for any help or debugging ideas.

Thanks,
Dan

[-- 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:[~2007-12-18 19:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-18 19:03 Dan Magenheimer [this message]
2007-12-19  5:24 ` Problems "upgrading" 3.1 to 3.2? Mark Williamson
2007-12-19 10:40   ` Keir Fraser
2007-12-19 15:43     ` Mark Williamson
2007-12-19 15:48       ` Daniel P. Berrange
2007-12-19 15:37   ` Dan Magenheimer

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=20071218120311250.00000002296@djm-pc \
    --to=dan.magenheimer@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 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.