7 Jan
2011
7 Jan
'11
4:35 p.m.
Hi all,
With reference to the quoted emails below. My upgrade from 8.04 LTS Hardy to 10.04 LTS
Lucid had gone well, primarily thanks to Andy.
First I ran the 'do-release-upgrade' command. Then I let the machine do its thing,
and when it asked to be rebooted I said no and did
'aptitude install linux-image-virtual'
but what I didn't do, was read Andy's instructions properly, which were in this
message:
http://lists.bitfolk.com/lurker/message/20100504.163132.4db7405a.en.html
Particularly this part:
~~~~~
I made an /etc/init/hvc0.conf file that looks like this:
#----8<---------------------------------------------------------------------
# hvc0 - getty
#
# This service maintains a getty on hvc0 from the point the system is
# started until it is shut down again.
start on stopped rc RUNLEVEL=[2345]
stop on runlevel [!2345]
respawn
exec /sbin/getty -8 38400 hvc0
#----8<---------------------------------------------------------------------
I found that update-grub wouldn't find linux-image-2.6.32-21-generic
as it kept saying it was a non-Xen kernel while I'm on Xen (probably
because at this point I was still booted in the 8.04 Xen kernel) so
I made sure there was a manual stanza in /boot/grub/menu.lst that
looked like:
#----8<---------------------------------------------------------------------
title Ubuntu 10.04 LTS, kernel 2.6.32-21-generic-pae
root (hd0,0)
kernel /boot/vmlinuz-2.6.32-21-generic-pae root=UUID=d8affdac-b42e-42da-9faf-a54b4ad3a31d
ro console=hvc0
initrd /boot/initrd.img-2.6.32-21-generic-pae
#----8<---------------------------------------------------------------------
I made sure not to have any clocksource=jiffies of xencons=tty there
in the kernel parameters.
I then shut down and booted from the xen shell into this kernel and
it seems OK so far. After boot I was able to update-grub to get a
proper generated menu.lst.
~~~~~
If I would have read (and understood) those few lines I wouldn't have had to bother
Andy. Sorry! :)
And if I understood what Andy said, then this should have been sufficient to do the
upgrade. And please request the snapshot before you go ahead.
Hope that helps anyone.
Cheers,
/Jocke
On 7 Jan 2011, at 11:53, Andy Smith wrote:
Hi Jocke,
On Fri, Jan 07, 2011 at 11:24:48AM +0000, Jocke Selin wrote:
On 12 May 2010, at 12:28, James Gregory wrote:
> All appears to be working OK at present with ours. The only thing to
> remind people of is the need to install linux-image-virtual *before*
> rebooting.
[...]
It seems like I need to upgrade my VPS, from 8.04
LTS Hardy to 10.04 LTS Lucid.
Is this, above, the only thing I need to be concerned about after running
do-release-upgrade [1]?
We've had some people on 240M RAM complain that do-release-upgrade
died part way through due to lack of RAM. Others do seem to have
managed it in 240M RAM though.
I think that and the kernel thing are the only "gotchas" I'm aware
of.
As usual for any major upgrade we recommend that customers ask for a
disk snapshot first. That way, if it all goes terribly wrong, we can
relatively quickly put your VPS back how it was before. Without a
snapshot all we can do in the event of disaster is give you a new,
default VPS, leaving you to put all your services and data back in
place.
As an alternative to doing a major upgrade on a VPS that may be "in
service", we can offer a free migration window of two weeks:
https://tools.bitfolk.com/wiki/Migrating_to_a_new_VPS
Finally, if deciding to do a clean install, this can also be done by
yourself now:
https://tools.bitfolk.com/wiki/Using_the_self-serve_net_installer