|
xen-users
RE: [Xen-users] Upgrade Proceedure
Ok thanks for that - ill give it a shot.
On another note remember the problem with the missing interrupt on
intel? Well since ive changed to AMD ive not had this problem so
obviously something doesn't like the Intel side of things.
Thanks for your help :)
Ian
-----Original Message-----
From: Petersson, Mats [mailto:Mats.Petersson@xxxxxxx]
Sent: 14 May 2007 10:46
To: Ian Tobin; xen-users@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-users] Upgrade Proceedure
> -----Original Message-----
> From: Ian Tobin [mailto:itobin@xxxxxxxxxxxxx]
> Sent: 14 May 2007 10:40
> To: Petersson, Mats; xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: RE: [Xen-users] Upgrade Proceedure
>
> What happens if you don't have an initrd :)
>
> The reason i say that is ive compiled everything into the
> kernel not as
> modules
Then you don't need this step, dist/install.sh will copy the kernel
image to /boot.
Depending on how you've set your grub.conf up, you may also need to
modify/add the Xen boot entry to match the new version.
--
Mats
>
> -----Original Message-----
> From: Petersson, Mats [mailto:Mats.Petersson@xxxxxxx]
> Sent: 14 May 2007 10:31
> To: Ian Tobin; xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: RE: [Xen-users] Upgrade Proceedure
>
>
>
> > -----Original Message-----
> > From: Ian Tobin [mailto:itobin@xxxxxxxxxxxxx]
> > Sent: 14 May 2007 10:27
> > To: Petersson, Mats; xen-users@xxxxxxxxxxxxxxxxxxx
> > Subject: RE: [Xen-users] Upgrade Proceedure
> >
> > Oh ok seems straight forward, I assume the kernel config remains the
> > same? i.e kernel drivers specified on first install are still in the
> > config.
>
> Ah, good point. If you have a "major" change, e.g. the kernel
> jumps from
> 2.6.16 to 2.6.18 or some such, then you also need to do (on target
> system):
> # depmod
> # mkinitrd /boot/initrd-2.6.18-xen 2.6.18-xen
> (Adjust version as applicable of course)
>
> For very minor upgrades, it's often enough to copy just the xen.gz to
> /boot on the target system - but that's if you know exactly what's
> changed!
>
> --
> Mats
> >
> >
> >
> > -----Original Message-----
> > From: Petersson, Mats [mailto:Mats.Petersson@xxxxxxx]
> > Sent: 14 May 2007 10:21
> > To: Ian Tobin; xen-users@xxxxxxxxxxxxxxxxxxx
> > Subject: RE: [Xen-users] Upgrade Proceedure
> >
> >
> >
> > > -----Original Message-----
> > > From: Ian Tobin [mailto:itobin@xxxxxxxxxxxxx]
> > > Sent: 14 May 2007 10:13
> > > To: Petersson, Mats; xen-users@xxxxxxxxxxxxxxxxxxx
> > > Subject: RE: [Xen-users] Upgrade Proceedure
> > >
> > > Hi,
> > >
> > > Is there an uninstall script?
> >
> > You can do "make uninstall", but you need to have the "old"
> version of
> > source-code on the target machine to do this. [Which is great for
> > developers that use the a single machine for Xen-development and
> > testing].
> >
> >
> > > And when you say tar up the
> > > dist directory
> > > is that from one of the servers that is running the latest release
> > > already?
> >
> > I meant from the machine you build Xen from Sources on - if
> that's one
> > of your servers or some other machine, I can't say.
> >
> > This is what I do:
> > # cd $XEN_ROOT
> > # make dist
> > # tar cjf dist.tar.bz2 dist
> > # scp dist.tar.bz2 some_machine:/tmp
> > # ssh some_machine
> > # cd tmp
> > # rm -rf dist ## Remove the OLD dist directory, if there is one.
> > # tar xjf dist.tar.bz2
> > # ./dist/install.sh
> > # reboot
> > # exit
> >
> >
> >
> > >
> > > Thanks
> > >
> > > Ian
> > >
> > >
> > >
> > > -----Original Message-----
> > > From: Petersson, Mats [mailto:Mats.Petersson@xxxxxxx]
> > > Sent: 14 May 2007 10:10
> > > To: Ian Tobin; xen-users@xxxxxxxxxxxxxxxxxxx
> > > Subject: RE: [Xen-users] Upgrade Proceedure
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
> > > > [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of
> > > Ian Tobin
> > > > Sent: 14 May 2007 09:27
> > > > To: xen-users@xxxxxxxxxxxxxxxxxxx
> > > > Subject: [Xen-users] Upgrade Proceedure
> > > >
> > > > Hi,
> > > >
> > > >
> > > >
> > > > We are looking to getting all our XEN boxes up to the latest
> > > > release. The lowest version we have is 3.0.
> > > >
> > > >
> > > >
> > > > I was wondering what the best way to do an upgrade is, we
> > > > have built all the XEN boxes from source.
> > >
> > >
> > > Tar up the "dist" directory and copy it to each of the
> new machines,
> > > untar and run "dist/install.sh"?
> > >
> > > Only problem is if you need to uninstall first - because
> there's no
> > > uninstall script... Usually you don't need to uninstall,
> > but sometimes
> > > you do (because some residual file means that the wrong version of
> > > library is used, or some such).
> > >
> > > --
> > > Mats
> > > >
> > > >
> > > >
> > > > Thanks
> > > >
> > > >
> > > >
> > > > Ian
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
> >
> >
> >
> >
> >
>
>
>
>
>
>
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
Home