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. Thanks Ian _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> -----Original Message----- > From: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Ian Tobin > Sent: 14 May 2007 09:27 > To: xen-users@lists.xensource.com > 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@lists.xensource.com http://lists.xensource.com/xen-users
Hi, Is there an uninstall script? And when you say tar up the dist directory is that from one of the servers that is running the latest release already? Thanks Ian -----Original Message----- From: Petersson, Mats [mailto:Mats.Petersson@amd.com] Sent: 14 May 2007 10:10 To: Ian Tobin; xen-users@lists.xensource.com Subject: RE: [Xen-users] Upgrade Proceedure> -----Original Message----- > From: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Ian Tobin > Sent: 14 May 2007 09:27 > To: xen-users@lists.xensource.com > 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@lists.xensource.com http://lists.xensource.com/xen-users
> -----Original Message----- > From: Ian Tobin [mailto:itobin@tidyhosts.com] > Sent: 14 May 2007 10:13 > To: Petersson, Mats; xen-users@lists.xensource.com > 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@amd.com] > Sent: 14 May 2007 10:10 > To: Ian Tobin; xen-users@lists.xensource.com > Subject: RE: [Xen-users] Upgrade Proceedure > > > > > -----Original Message----- > > From: xen-users-bounces@lists.xensource.com > > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of > Ian Tobin > > Sent: 14 May 2007 09:27 > > To: xen-users@lists.xensource.com > > 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@lists.xensource.com http://lists.xensource.com/xen-users
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. -----Original Message----- From: Petersson, Mats [mailto:Mats.Petersson@amd.com] Sent: 14 May 2007 10:21 To: Ian Tobin; xen-users@lists.xensource.com Subject: RE: [Xen-users] Upgrade Proceedure> -----Original Message----- > From: Ian Tobin [mailto:itobin@tidyhosts.com] > Sent: 14 May 2007 10:13 > To: Petersson, Mats; xen-users@lists.xensource.com > 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@amd.com] > Sent: 14 May 2007 10:10 > To: Ian Tobin; xen-users@lists.xensource.com > Subject: RE: [Xen-users] Upgrade Proceedure > > > > > -----Original Message----- > > From: xen-users-bounces@lists.xensource.com > > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of > Ian Tobin > > Sent: 14 May 2007 09:27 > > To: xen-users@lists.xensource.com > > 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@lists.xensource.com http://lists.xensource.com/xen-users
> -----Original Message----- > From: Ian Tobin [mailto:itobin@tidyhosts.com] > Sent: 14 May 2007 10:27 > To: Petersson, Mats; xen-users@lists.xensource.com > 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@amd.com] > Sent: 14 May 2007 10:21 > To: Ian Tobin; xen-users@lists.xensource.com > Subject: RE: [Xen-users] Upgrade Proceedure > > > > > -----Original Message----- > > From: Ian Tobin [mailto:itobin@tidyhosts.com] > > Sent: 14 May 2007 10:13 > > To: Petersson, Mats; xen-users@lists.xensource.com > > 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@amd.com] > > Sent: 14 May 2007 10:10 > > To: Ian Tobin; xen-users@lists.xensource.com > > Subject: RE: [Xen-users] Upgrade Proceedure > > > > > > > > > -----Original Message----- > > > From: xen-users-bounces@lists.xensource.com > > > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of > > Ian Tobin > > > Sent: 14 May 2007 09:27 > > > To: xen-users@lists.xensource.com > > > 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@lists.xensource.com http://lists.xensource.com/xen-users
What happens if you don''t have an initrd :) The reason i say that is ive compiled everything into the kernel not as modules -----Original Message----- From: Petersson, Mats [mailto:Mats.Petersson@amd.com] Sent: 14 May 2007 10:31 To: Ian Tobin; xen-users@lists.xensource.com Subject: RE: [Xen-users] Upgrade Proceedure> -----Original Message----- > From: Ian Tobin [mailto:itobin@tidyhosts.com] > Sent: 14 May 2007 10:27 > To: Petersson, Mats; xen-users@lists.xensource.com > 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@amd.com] > Sent: 14 May 2007 10:21 > To: Ian Tobin; xen-users@lists.xensource.com > Subject: RE: [Xen-users] Upgrade Proceedure > > > > > -----Original Message----- > > From: Ian Tobin [mailto:itobin@tidyhosts.com] > > Sent: 14 May 2007 10:13 > > To: Petersson, Mats; xen-users@lists.xensource.com > > 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@amd.com] > > Sent: 14 May 2007 10:10 > > To: Ian Tobin; xen-users@lists.xensource.com > > Subject: RE: [Xen-users] Upgrade Proceedure > > > > > > > > > -----Original Message----- > > > From: xen-users-bounces@lists.xensource.com > > > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of > > Ian Tobin > > > Sent: 14 May 2007 09:27 > > > To: xen-users@lists.xensource.com > > > 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@lists.xensource.com http://lists.xensource.com/xen-users
> -----Original Message----- > From: Ian Tobin [mailto:itobin@tidyhosts.com] > Sent: 14 May 2007 10:40 > To: Petersson, Mats; xen-users@lists.xensource.com > 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 > modulesThen 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@amd.com] > Sent: 14 May 2007 10:31 > To: Ian Tobin; xen-users@lists.xensource.com > Subject: RE: [Xen-users] Upgrade Proceedure > > > > > -----Original Message----- > > From: Ian Tobin [mailto:itobin@tidyhosts.com] > > Sent: 14 May 2007 10:27 > > To: Petersson, Mats; xen-users@lists.xensource.com > > 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@amd.com] > > Sent: 14 May 2007 10:21 > > To: Ian Tobin; xen-users@lists.xensource.com > > Subject: RE: [Xen-users] Upgrade Proceedure > > > > > > > > > -----Original Message----- > > > From: Ian Tobin [mailto:itobin@tidyhosts.com] > > > Sent: 14 May 2007 10:13 > > > To: Petersson, Mats; xen-users@lists.xensource.com > > > 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@amd.com] > > > Sent: 14 May 2007 10:10 > > > To: Ian Tobin; xen-users@lists.xensource.com > > > Subject: RE: [Xen-users] Upgrade Proceedure > > > > > > > > > > > > > -----Original Message----- > > > > From: xen-users-bounces@lists.xensource.com > > > > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of > > > Ian Tobin > > > > Sent: 14 May 2007 09:27 > > > > To: xen-users@lists.xensource.com > > > > 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@lists.xensource.com http://lists.xensource.com/xen-users
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@amd.com] Sent: 14 May 2007 10:46 To: Ian Tobin; xen-users@lists.xensource.com Subject: RE: [Xen-users] Upgrade Proceedure> -----Original Message----- > From: Ian Tobin [mailto:itobin@tidyhosts.com] > Sent: 14 May 2007 10:40 > To: Petersson, Mats; xen-users@lists.xensource.com > 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 > modulesThen 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@amd.com] > Sent: 14 May 2007 10:31 > To: Ian Tobin; xen-users@lists.xensource.com > Subject: RE: [Xen-users] Upgrade Proceedure > > > > > -----Original Message----- > > From: Ian Tobin [mailto:itobin@tidyhosts.com] > > Sent: 14 May 2007 10:27 > > To: Petersson, Mats; xen-users@lists.xensource.com > > 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@amd.com] > > Sent: 14 May 2007 10:21 > > To: Ian Tobin; xen-users@lists.xensource.com > > Subject: RE: [Xen-users] Upgrade Proceedure > > > > > > > > > -----Original Message----- > > > From: Ian Tobin [mailto:itobin@tidyhosts.com] > > > Sent: 14 May 2007 10:13 > > > To: Petersson, Mats; xen-users@lists.xensource.com > > > 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@amd.com] > > > Sent: 14 May 2007 10:10 > > > To: Ian Tobin; xen-users@lists.xensource.com > > > Subject: RE: [Xen-users] Upgrade Proceedure > > > > > > > > > > > > > -----Original Message----- > > > > From: xen-users-bounces@lists.xensource.com > > > > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of > > > Ian Tobin > > > > Sent: 14 May 2007 09:27 > > > > To: xen-users@lists.xensource.com > > > > 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@lists.xensource.com http://lists.xensource.com/xen-users
>>From: Ian Tobin [mailto:itobin@tidyhosts.com] >>Sent: 14 May 2007 10:13 >>To: Petersson, Mats; xen-users@lists.xensource.com >>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]. >Hi Ian, Mats, Thought I''d chime in here because I got bitten using the make uninstall script. Within the Makefile uninstall section is this line: rm -rf $(D)/boot/*xen* This will remove every file in your boot directory that contains the string "xen", so things like vixen or roxen will also match. More relevant though is that it will also remove previous versions of xen. If you are no longer interested in them, or don''t care that you may have to rebuild them this is not a problem. If it matters that you retain prior kernels you may want to comment out that line in the Makefile. In the current unstable that''s somewhere around line #186. Just a heads up ;) Mike Wright :m) _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Thanks for the Mike, noted :) Thanks Ian -----Original Message----- From: xen-users-bounces@lists.xensource.com [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Mike Wright Sent: 14 May 2007 18:56 To: xen-users@lists.xensource.com Subject: Re: [Xen-users] Upgrade Proceedure>>From: Ian Tobin [mailto:itobin@tidyhosts.com] >>Sent: 14 May 2007 10:13 >>To: Petersson, Mats; xen-users@lists.xensource.com >>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]. >Hi Ian, Mats, Thought I''d chime in here because I got bitten using the make uninstall script. Within the Makefile uninstall section is this line: rm -rf $(D)/boot/*xen* This will remove every file in your boot directory that contains the string "xen", so things like vixen or roxen will also match. More relevant though is that it will also remove previous versions of xen. If you are no longer interested in them, or don''t care that you may have to rebuild them this is not a problem. If it matters that you retain prior kernels you may want to comment out that line in the Makefile. In the current unstable that''s somewhere around line #186. Just a heads up ;) Mike Wright :m) _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Ian Tobin wrote:> > Hi Ian, Mats, > > Thought I''d chime in here because I got bitten using the make uninstall > script. > > Within the Makefile uninstall section is this line: > > rm -rf $(D)/boot/*xen* > > This will remove every file in your boot directory that contains the > string "xen", so things like vixen or roxen will also match. More > relevant though is that it will also remove previous versions of xen. > If you are no longer interested in them, or don''t care that you may have > > to rebuild them this is not a problem. If it matters that you retain > prior kernels you may want to comment out that line in the Makefile. In > > the current unstable that''s somewhere around line #186. > > Just a heads up ;) > > Mike Wright :m) >This is *precisely* why I like RPM''s and apt-based package managers: a lot of installers and uninstallers are pretty darned bad. Have you submitted a bug for this? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> -----Original Message----- > From: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of > Nico Kadel-Garcia > Sent: 15 May 2007 10:13 > To: Ian Tobin > Cc: Mike Wright; xen-users@lists.xensource.com > Subject: Re: [Xen-users] Upgrade Proceedure > > Ian Tobin wrote: > > > > Hi Ian, Mats, > > > > Thought I''d chime in here because I got bitten using the > make uninstall > > script. > > > > Within the Makefile uninstall section is this line: > > > > rm -rf $(D)/boot/*xen* > > > > This will remove every file in your boot directory that > contains the > > string "xen", so things like vixen or roxen will also match. More > > relevant though is that it will also remove previous > versions of xen. > > If you are no longer interested in them, or don''t care that > you may have > > > > to rebuild them this is not a problem. If it matters that > you retain > > prior kernels you may want to comment out that line in the > Makefile. In > > > > the current unstable that''s somewhere around line #186. > > > > Just a heads up ;) > > > > Mike Wright :m) > > > This is *precisely* why I like RPM''s and apt-based package > managers: a > lot of installers and uninstallers are pretty darned bad. Have you > submitted a bug for this?Actually, the bug is that there''s no uninstall script, rather than that the "make uninstall" removes the wrong stuff... The uninstall script should be generated by the install script to "remove exactly the files installed and nothing else". This is the REAL bug. Then we could use this install script to do "make uninstall" too. -- Mats> > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Petersson, Mats wrote:> > > >> -----Original Message----- >> From: xen-users-bounces@lists.xensource.com >> [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of >> Nico Kadel-Garcia >> Sent: 15 May 2007 10:13 >> To: Ian Tobin >> Cc: Mike Wright; xen-users@lists.xensource.com >> Subject: Re: [Xen-users] Upgrade Proceedure >> >> Ian Tobin wrote: >> >>> Hi Ian, Mats, >>> >>> Thought I''d chime in here because I got bitten using the >>> >> make uninstall >> >>> script. >>> >>> Within the Makefile uninstall section is this line: >>> >>> rm -rf $(D)/boot/*xen* >>> >>> This will remove every file in your boot directory that >>> >> contains the >> >>> string "xen", so things like vixen or roxen will also match. More >>> relevant though is that it will also remove previous >>> >> versions of xen. >> >>> If you are no longer interested in them, or don''t care that >>> >> you may have >> >>> to rebuild them this is not a problem. If it matters that >>> >> you retain >> >>> prior kernels you may want to comment out that line in the >>> >> Makefile. In >> >>> the current unstable that''s somewhere around line #186. >>> >>> Just a heads up ;) >>> >>> Mike Wright :m) >>> >>> >> This is *precisely* why I like RPM''s and apt-based package >> managers: a >> lot of installers and uninstallers are pretty darned bad. Have you >> submitted a bug for this? >> > > Actually, the bug is that there''s no uninstall script, rather than that > the "make uninstall" removes the wrong stuff... The uninstall script > should be generated by the install script to "remove exactly the files > installed and nothing else". This is the REAL bug. Then we could use > this install script to do "make uninstall" too. >And the uninstall script should not be part of the Makefile used to install the software precisely..... why? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> -----Original Message----- > From: Nico Kadel-Garcia [mailto:nkadel@gmail.com] > Sent: 15 May 2007 14:31 > To: Petersson, Mats > Cc: Ian Tobin; Mike Wright; xen-users@lists.xensource.com > Subject: Re: [Xen-users] Upgrade Proceedure > > Petersson, Mats wrote: > > > > > > > >> -----Original Message----- > >> From: xen-users-bounces@lists.xensource.com > >> [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of > >> Nico Kadel-Garcia > >> Sent: 15 May 2007 10:13 > >> To: Ian Tobin > >> Cc: Mike Wright; xen-users@lists.xensource.com > >> Subject: Re: [Xen-users] Upgrade Proceedure > >> > >> Ian Tobin wrote: > >> > >>> Hi Ian, Mats, > >>> > >>> Thought I''d chime in here because I got bitten using the > >>> > >> make uninstall > >> > >>> script. > >>> > >>> Within the Makefile uninstall section is this line: > >>> > >>> rm -rf $(D)/boot/*xen* > >>> > >>> This will remove every file in your boot directory that > >>> > >> contains the > >> > >>> string "xen", so things like vixen or roxen will also > match. More > >>> relevant though is that it will also remove previous > >>> > >> versions of xen. > >> > >>> If you are no longer interested in them, or don''t care that > >>> > >> you may have > >> > >>> to rebuild them this is not a problem. If it matters that > >>> > >> you retain > >> > >>> prior kernels you may want to comment out that line in the > >>> > >> Makefile. In > >> > >>> the current unstable that''s somewhere around line #186. > >>> > >>> Just a heads up ;) > >>> > >>> Mike Wright :m) > >>> > >>> > >> This is *precisely* why I like RPM''s and apt-based package > >> managers: a > >> lot of installers and uninstallers are pretty darned bad. Have you > >> submitted a bug for this? > >> > > > > Actually, the bug is that there''s no uninstall script, > rather than that > > the "make uninstall" removes the wrong stuff... The uninstall script > > should be generated by the install script to "remove > exactly the files > > installed and nothing else". This is the REAL bug. Then we could use > > this install script to do "make uninstall" too. > > > And the uninstall script should not be part of the Makefile used to > install the software precisely..... why?Because you may want to install/uninstall on a machine that doesn''t (need to) have the source-code (or corresponding Makefile). Of course, anyone who wishes to un-install can download the source-code, but it''s a completley unneccessary step to instal the source code on 15 machines just because you wanted to REMOVE the resulting files from that source code, don''t you think? If you''re not familiar with it, I''d like to point out that there is a INSTALL script in the distribution directory which can be used to install the resulting product of the make (which is what I described earlier in this thread). -- Mats> > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Petersson, Mats wrote:> > > >> -----Original Message----- >> From: Nico Kadel-Garcia [mailto:nkadel@gmail.com] >> Sent: 15 May 2007 14:31 >> To: Petersson, Mats >> Cc: Ian Tobin; Mike Wright; xen-users@lists.xensource.com >> Subject: Re: [Xen-users] Upgrade Proceedure >> >> Petersson, Mats wrote: >> >>> >>> >>> >>> >>>> -----Original Message----- >>>> From: xen-users-bounces@lists.xensource.com >>>> [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of >>>> Nico Kadel-Garcia >>>> Sent: 15 May 2007 10:13 >>>> To: Ian Tobin >>>> Cc: Mike Wright; xen-users@lists.xensource.com >>>> Subject: Re: [Xen-users] Upgrade Proceedure >>>> >>>> Ian Tobin wrote: >>>> >>>> >>>>> Hi Ian, Mats, >>>>> >>>>> Thought I''d chime in here because I got bitten using the >>>>> >>>>> >>>> make uninstall >>>> >>>> >>>>> script. >>>>> >>>>> Within the Makefile uninstall section is this line: >>>>> >>>>> rm -rf $(D)/boot/*xen* >>>>> >>>>> This will remove every file in your boot directory that >>>>> >>>>> >>>> contains the >>>> >>>> >>>>> string "xen", so things like vixen or roxen will also >>>>> >> match. More >> >>>>> relevant though is that it will also remove previous >>>>> >>>>> >>>> versions of xen. >>>> >>>> >>>>> If you are no longer interested in them, or don''t care that >>>>> >>>>> >>>> you may have >>>> >>>> >>>>> to rebuild them this is not a problem. If it matters that >>>>> >>>>> >>>> you retain >>>> >>>> >>>>> prior kernels you may want to comment out that line in the >>>>> >>>>> >>>> Makefile. In >>>> >>>> >>>>> the current unstable that''s somewhere around line #186. >>>>> >>>>> Just a heads up ;) >>>>> >>>>> Mike Wright :m) >>>>> >>>>> >>>>> >>>> This is *precisely* why I like RPM''s and apt-based package >>>> managers: a >>>> lot of installers and uninstallers are pretty darned bad. Have you >>>> submitted a bug for this? >>>> >>>> >>> Actually, the bug is that there''s no uninstall script, >>> >> rather than that >> >>> the "make uninstall" removes the wrong stuff... The uninstall script >>> should be generated by the install script to "remove >>> >> exactly the files >> >>> installed and nothing else". This is the REAL bug. Then we could use >>> this install script to do "make uninstall" too. >>> >>> >> And the uninstall script should not be part of the Makefile used to >> install the software precisely..... why? >> > > Because you may want to install/uninstall on a machine that doesn''t > (need to) have the source-code (or corresponding Makefile). >That''s what package management tools are for. If values are being set in the Makefile (such as the root directory!), then the uninstaller has to built by the Makefile and itself installed (conceivable!) and summoned as part of the uninstall procedure.> Of course, anyone who wishes to un-install can download the source-code, > but it''s a completley unneccessary step to instal the source code on 15 > machines just because you wanted to REMOVE the resulting files from that > source code, don''t you think? >The INSTALL script you mention works without the build directory in place? That''s a bit.... odd.> If you''re not familiar with it, I''d like to point out that there is a > INSTALL script in the distribution directory which can be used to > install the resulting product of the make (which is what I described > earlier in this thread). >I use Makefiles and RPM''s to support full-blown package management, version management, conflict reports, etc., etc., etc. Writing all of that into an installer or uniinstaller script is quite a lot of work. I recognize that not every OS has this kind of package management, and prefer to build on the fly. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
[snip a ton of old stuff]> The INSTALL script you mention works without the build directory in > place? That''s a bit.... odd.Not at all. It just takes the files in the "dist" directory (which is a copy of what''s been produced in the individual build directories, e.g. xen.gz, qemu-dm, vmlinuz, kernel modules, hvmloader, etc, etc), and copies it out to wherever it goes. Have a look at "dist/install.sh". It''s not complicated, it essentially just copies the files from "dist/install" to whatever destination you specify (defualt is "/").> > > If you''re not familiar with it, I''d like to point out that > there is a > > INSTALL script in the distribution directory which can be used to > > install the resulting product of the make (which is what I described > > earlier in this thread). > > > I use Makefiles and RPM''s to support full-blown package management, > version management, conflict reports, etc., etc., etc. Writing all of > that into an installer or uniinstaller script is quite a lot of work. > > I recognize that not every OS has this kind of package > management, and > prefer to build on the fly.Great if you have the environment to build the RPM, but if you take the xen-unstable.hg repo, it doesn''t come with spec-files to make RPM''s [afaics]. Obviously, most distributions will use some sort of packagemanagement, and that solves most of those problems. -- Mats> > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
The question is if doing an upgrade do you actually have to uninstall the files? I mean if its an upgrade then wouldn''t just untaring the dist directory and running the install thing work? thanks -----Original Message----- From: Petersson, Mats [mailto:Mats.Petersson@amd.com] Sent: 15 May 2007 15:36 To: Nico Kadel-Garcia Cc: Ian Tobin; Mike Wright; xen-users@lists.xensource.com Subject: RE: [Xen-users] Upgrade Proceedure [snip a ton of old stuff]> The INSTALL script you mention works without the build directory in > place? That''s a bit.... odd.Not at all. It just takes the files in the "dist" directory (which is a copy of what''s been produced in the individual build directories, e.g. xen.gz, qemu-dm, vmlinuz, kernel modules, hvmloader, etc, etc), and copies it out to wherever it goes. Have a look at "dist/install.sh". It''s not complicated, it essentially just copies the files from "dist/install" to whatever destination you specify (defualt is "/").> > > If you''re not familiar with it, I''d like to point out that > there is a > > INSTALL script in the distribution directory which can be used to > > install the resulting product of the make (which is what I described > > earlier in this thread). > > > I use Makefiles and RPM''s to support full-blown package management, > version management, conflict reports, etc., etc., etc. Writing all of > that into an installer or uniinstaller script is quite a lot of work. > > I recognize that not every OS has this kind of package > management, and > prefer to build on the fly.Great if you have the environment to build the RPM, but if you take the xen-unstable.hg repo, it doesn''t come with spec-files to make RPM''s [afaics]. Obviously, most distributions will use some sort of packagemanagement, and that solves most of those problems. -- Mats> > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> -----Original Message----- > From: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Ian Tobin > Sent: 15 May 2007 15:42 > To: Petersson, Mats; Nico Kadel-Garcia > Cc: Mike Wright; xen-users@lists.xensource.com > Subject: RE: [Xen-users] Upgrade Proceedure > > The question is if doing an upgrade do you actually have to uninstall > the files? I mean if its an upgrade then wouldn''t just > untaring the dist > directory and running the install thing work?Most of the time that will be fine. I''ve had cases where it''s not working (the case in particular is if you install a 64-bit on top of 32-bit Xen - which will be entirely broken if you do that, because it finds a mixture of 32-bit and 64-bit shared libraries, and that doesn''t work!) -- Mats> > thanks >[snip] _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Petersson, Mats wrote:> [snip a ton of old stuff] > >> The INSTALL script you mention works without the build directory in >> place? That''s a bit.... odd. >> > > Not at all. It just takes the files in the "dist" directory (which is a > copy of what''s been produced in the individual build directories, e.g. > xen.gz, qemu-dm, vmlinuz, kernel modules, hvmloader, etc, etc), and > copies it out to wherever it goes. Have a look at "dist/install.sh". > It''s not complicated, it essentially just copies the files from > "dist/install" to whatever destination you specify (defualt is "/"). > >>> If you''re not familiar with it, I''d like to point out that >>> >> there is a >> >>> INSTALL script in the distribution directory which can be used to >>> install the resulting product of the make (which is what I described >>> earlier in this thread). >>> >>> >> I use Makefiles and RPM''s to support full-blown package management, >> version management, conflict reports, etc., etc., etc. Writing all of >> that into an installer or uniinstaller script is quite a lot of work. >> >> I recognize that not every OS has this kind of package >> management, and >> prefer to build on the fly. >> > > Great if you have the environment to build the RPM, but if you take the > xen-unstable.hg repo, it doesn''t come with spec-files to make RPM''s > [afaics]. >The spec files don''t usually change much between different software versions, although I use hte xensource src.rpm files for that: The RHEL 5 and Fedora Core SRPM''s do a lot of...... extra stuff with virt-manager that I don''t feel a need for and in fact find inappropriate for most use. (This may be due to libvirt for RedHat releases being way behind the leading edge for the software!) For Xen kernels, and other kernels under RHEL, one normally does an "rpm -i", not an "rpm -U". this installs the new kernel as well as the old one: Post-install scripts may change some of the symlinks in /boot, and edit the grub or lilo appropriately: that takes knowledge and software control of the grub or lilo commands, and some expertise to do carefully. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi, well i did as you said but now the server wont boot. It says unable to mount root device. Im assuming its because it hasn''t got the SCSI device driver loaded into the kernel so it looks like i need to do more than just untar /dist and running ./install.sh do i need to import the config from the other source directory and run make arch=xen menuconfig ? If so how would i import the existing config (if possible) thanks Ian ________________________________ From: Petersson, Mats [mailto:Mats.Petersson@amd.com] Sent: Tue 15/05/2007 16:40 To: Ian Tobin; Nico Kadel-Garcia Cc: Mike Wright; xen-users@lists.xensource.com Subject: RE: [Xen-users] Upgrade Proceedure> -----Original Message----- > From: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Ian Tobin > Sent: 15 May 2007 15:42 > To: Petersson, Mats; Nico Kadel-Garcia > Cc: Mike Wright; xen-users@lists.xensource.com > Subject: RE: [Xen-users] Upgrade Proceedure > > The question is if doing an upgrade do you actually have to uninstall > the files? I mean if its an upgrade then wouldn''t just > untaring the dist > directory and running the install thing work?Most of the time that will be fine. I''ve had cases where it''s not working (the case in particular is if you install a 64-bit on top of 32-bit Xen - which will be entirely broken if you do that, because it finds a mixture of 32-bit and 64-bit shared libraries, and that doesn''t work!) -- Mats> > thanks >[snip] _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> -----Original Message----- > From: Ian Tobin [mailto:itobin@tidyhosts.com] > Sent: 21 May 2007 15:14 > To: Petersson, Mats; Nico Kadel-Garcia > Cc: Mike Wright; xen-users@lists.xensource.com > Subject: RE: [Xen-users] Upgrade Proceedure > > Hi, > > well i did as you said but now the server wont boot. It says > unable to mount root device. > > Im assuming its because it hasn''t got the SCSI device driver > loaded into the kernel so it looks like i need to do more > than just untar /dist and running ./install.shWell, if you build with the DEFAULT setup, you won''t get all drivers built-in, but all (or most) of the drivers get built as modules. I find it easier to build an initrd.> > do i need to import the config from the other source > directory and run make arch=xen menuconfig ?That would probably work, but beware that different versions of Xen use different kernel versions which often mean different config files. "arch=xen" is obsolete in recent versions of Xen (they use "subarch" instead). Just "make menuconfig" works just fine.> > If so how would i import the existing config (if possible)Either just copy it (after saving the original one), or use diff to create a diff-file and use patch to incorporate the differences into the new one. [something like "diff -c .../new/.../.config .../original/.../.config > diffs; patch < diffs" will work, I think]. -- Mats> > thanks > > Ian > > > ________________________________ > > From: Petersson, Mats [mailto:Mats.Petersson@amd.com] > Sent: Tue 15/05/2007 16:40 > To: Ian Tobin; Nico Kadel-Garcia > Cc: Mike Wright; xen-users@lists.xensource.com > Subject: RE: [Xen-users] Upgrade Proceedure > > > > > -----Original Message----- > > From: xen-users-bounces@lists.xensource.com > > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of > Ian Tobin > > Sent: 15 May 2007 15:42 > > To: Petersson, Mats; Nico Kadel-Garcia > > Cc: Mike Wright; xen-users@lists.xensource.com > > Subject: RE: [Xen-users] Upgrade Proceedure > > > > The question is if doing an upgrade do you actually have to > uninstall > > the files? I mean if its an upgrade then wouldn''t just > > untaring the dist > > directory and running the install thing work? > > Most of the time that will be fine. I''ve had cases where it''s not > working (the case in particular is if you install a 64-bit on top of > 32-bit Xen - which will be entirely broken if you do that, because it > finds a mixture of 32-bit and 64-bit shared libraries, and > that doesn''t > work!) > > -- > Mats > > > > thanks > > > [snip] > > > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users