WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Problems "upgrading" 3.1 to 3.2?

To: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Problems "upgrading" 3.1 to 3.2?
From: "Dan Magenheimer" <dan.magenheimer@xxxxxxxxxx>
Date: Tue, 18 Dec 2007 12:03:11 -0700
Delivery-date: Tue, 18 Dec 2007 11:03:48 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Organization: Oracle Corporation
Reply-to: "dan.magenheimer@xxxxxxxxxx" <dan.magenheimer@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AchBqJ/xSn0dIBlDT5epCJJJq4cdAw==
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
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>