Hi All, I''ve tried upgrading from 3.0.1 to 3.0.2 on a couple of test servers and had the same strange results on both... In both cases I had a running 3.0.1server, then downloaded the 3.0.2 source. Next, I extracted the files and executed "make XEN_TARGET_X86_PAE=y world". Upon completion I executed "dist/install.sh", changed the grub.conf and rebooted. Once the machines rebooted both began complaining that files in "/etc/rc.d/*" were missing. Various services failed to start because of this as well as networking. Does anyone know what may have caused this based on the steps above? Is there a more preferred way to upgrade from one version to the next? _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Fwiw, I just upgraded two servers. The first one didn''t boot first time around because the install script hadn''t done a ''depmod -a 2.6.16-xen'' so mkinitramfs didn''t install any modules. The second one refuses to start xend properly for some reason, but I just noticed it is pointing at a local but unmaintained Debian repository, so everything is much more out of date than it should be. I''m upgrading it now. I haven''t encountered any of the problems that you refer too. James> -----Original Message----- > From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel- > bounces@lists.xensource.com] On Behalf Of rhce admin > Sent: Saturday, 8 April 2006 14:55 > To: xen-devel@lists.xensource.com > Subject: [Xen-devel] upgrading from 3.0.1 to 3.0.2 > > Hi All, > > I''ve tried upgrading from 3.0.1 to 3.0.2 on a couple of test serversand> had the same strange results on both... In both cases I had a running > 3.0.1 server, then downloaded the 3.0.2 source. Next, I extracted the > files and executed "make XEN_TARGET_X86_PAE=y world". Upon completionI> executed "dist/install.sh", changed the grub.conf and rebooted. Oncethe> machines rebooted both began complaining that files in "/etc/rc.d/*"were> missing. Various services failed to start because of this as well as > networking. > > Does anyone know what may have caused this based on the steps above?Is> there a more preferred way to upgrade from one version to the next?_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
> The second one refuses to start xend properly for some reason, but I > just noticed it is pointing at a local but unmaintained Debian > repository, so everything is much more out of date than it should be. > I''m upgrading it now.Actually, it turns out I didn''t update a link on the tftp server so it was still booting 2.6.12 from 3.0.1. Working fine now. James _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Looked closer at my failed upgrades this morning. It appears that "/etc/init.d/*" is being overwritten. Only "/etc/init.d/xend" and "/etc/init.d/xendomains" remain in the "/etc/init.d" directory after running install.sh. These are both Fedora Core 2 systems. I assume that the install.sh script has changed the way that it copies over. Anyine else seen this? On 4/8/06, James Harper <james.harper@bendigoit.com.au> wrote:> > > The second one refuses to start xend properly for some reason, but I > > just noticed it is pointing at a local but unmaintained Debian > > repository, so everything is much more out of date than it should be. > > I''m upgrading it now. > > Actually, it turns out I didn''t update a link on the tftp server so it > was still booting 2.6.12 from 3.0.1. Working fine now. > > James >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel