Problems "upgrading" 3.1 to 3.2?

Problems "upgrading" 3.1 to 3.2?

[Dan Magenheimer]

[-- 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

Re: Problems "upgrading" 3.1 to 3.2?

[Mark Williamson]

Hi Dan,

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

Yeah, it'll be some kind of "residue" problem.  Unfortunately there's not a 
particularly clean way to uninstall Xen.

You could try removing /usr/lib/libxen* and /usr/lib/python/xen and then 
reinstalling the tools.  Does that help?

Otherwise, I'm afraid you're going to need to keep hunting down Xen-installed 
binaries until the problem goes away :-(

Cheers,
Mark

-- 
Dave: Just a question. What use is a unicyle with no seat?  And no pedals!
Mark: To answer a question with a question: What use is a skateboard?
Dave: Skateboards have wheels.
Mark: My wheel has a wheel!

Re: Problems "upgrading" 3.1 to 3.2?

[Keir Fraser]

On 19/12/07 05:24, "Mark Williamson" <mark.williamson@cl.cam.ac.uk> wrote:

> Yeah, it'll be some kind of "residue" problem.  Unfortunately there's not a
> particularly clean way to uninstall Xen.

'make uninstall' from the root of a Xen repository should do it. If it's not
comprehensive then I'd like patches.

 -- Keir

RE: Problems "upgrading" 3.1 to 3.2?

[Dan Magenheimer]

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

Snakes in the grass, alas!

I had two different python directories and the old one was being used.

Removing of /usr/lib/xen may also have been necessary... I did that earlier.

Thanks for the help!
Dan

> -----Original Message-----
> From: M.A. Williamson [mailto:maw48@hermes.cam.ac.uk]On Behalf Of Mark
> Williamson
> Sent: Tuesday, December 18, 2007 10:25 PM
> To: xen-devel@lists.xensource.com; dan.magenheimer@oracle.com
> Subject: Re: [Xen-devel] Problems "upgrading" 3.1 to 3.2?
> 
> 
> Hi Dan,
> 
> > 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.
> 
> Yeah, it'll be some kind of "residue" problem.  Unfortunately 
> there's not a
> particularly clean way to uninstall Xen.
> 
> You could try removing /usr/lib/libxen* and 
> /usr/lib/python/xen and then
> reinstalling the tools.  Does that help?
> 
> Otherwise, I'm afraid you're going to need to keep hunting 
> down Xen-installed
> binaries until the problem goes away :-(
> 
> Cheers,
> Mark
> 
> --
> Dave: Just a question. What use is a unicyle with no seat?  
> And no pedals!
> Mark: To answer a question with a question: What use is a skateboard?
> Dave: Skateboards have wheels.
> Mark: My wheel has a wheel!
> 
> 

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

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

Re: Problems "upgrading" 3.1 to 3.2?

[Mark Williamson]

> > Yeah, it'll be some kind of "residue" problem.  Unfortunately there's not
> > a particularly clean way to uninstall Xen.
>
> 'make uninstall' from the root of a Xen repository should do it. If it's
> not comprehensive then I'd like patches.

Well, I have a number of problems in mind: it's not necessarily so simple if 
you're mixing installs from different versions or if you don't have the 
original repository around.  Obviously, recreating the original repository is 
always doable and ought to work.  But it seemed worth mentioning in case one 
of these was tripping things up.

The other problem wrt uninstalls is that I'm not sure the binary tarball has 
an uninstall option (?) because it omits the makefile.  If that's the case 
then that is probably something that does merit a patch.

Cheers,
Mark

-- 
Dave: Just a question. What use is a unicyle with no seat?  And no pedals!
Mark: To answer a question with a question: What use is a skateboard?
Dave: Skateboards have wheels.
Mark: My wheel has a wheel!

Re: Problems "upgrading" 3.1 to 3.2?

[Daniel P. Berrange]

On Wed, Dec 19, 2007 at 03:43:47PM +0000, Mark Williamson wrote:
> > > Yeah, it'll be some kind of "residue" problem.  Unfortunately there's not
> > > a particularly clean way to uninstall Xen.
> >
> > 'make uninstall' from the root of a Xen repository should do it. If it's
> > not comprehensive then I'd like patches.
> 
> Well, I have a number of problems in mind: it's not necessarily so simple if 
> you're mixing installs from different versions or if you don't have the 
> original repository around.  Obviously, recreating the original repository is 
> always doable and ought to work.  But it seemed worth mentioning in case one 
> of these was tripping things up.
> 
> The other problem wrt uninstalls is that I'm not sure the binary tarball has 
> an uninstall option (?) because it omits the makefile.  If that's the case 
> then that is probably something that does merit a patch.

If you really care about cleanly un-installing Xen then this is what packaging
tools are for - RPM / Dpkg. Its very easy to update Fedora Xen RPMs to new
Xen-unstable snapshots - just drop in a new tar.gz and update the changeset 
number in the spec.

Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=|