Joseph Heenan <joseph(a)heenan.me.uk> writes:
On 07/02/2011 10:30, Michael Stevens wrote:
I'm going to have a go at this soon, any
chance someone who succeeds can
write it up?
My upgrade is now finished and all working thanks to Andy.
Another succesful upgrade here, with comments below.
Don't really have time just now to write up a
wiki, but basically I
followed the upgrade section in the release notes.
Various bitfolk specific things I'm aware of
Before starting:
- make sure you know how to access your console before you start (you
shouldn't need it, but if anything goes wrong you'll need it)
- optionally, ask support to take a snapshot before starting
- check before you upgrade that if you have root partition on
/dev/xvda1 that fdisk -l /dev/xvda works. If it doesn't you need your
xvda1 renaming to xvda, contact support.
Didn't encounter that problem.
At the point where the release notes tell you to
install a kernel then
udev and reboot:
- make sure grub-legacy is installed (or at least that grub2 is not
installed), as grub2 doesn't work at bitfolk yet and is likely to be
installed during the upgrade
grub2 is definitely installed, so don't allow it to write to your
partition (at some point in the upgrade you are asked to do that).
I had to switch back to grub-legacy before rebooting.
- use the linux-image-686-bigmem kernel; check
update-grub and/or
/boot/grub/menu.lst does point at the right kernel
Well, linux-image-2.6-xen-686 works also, and was offered by default in
the upgrade process:) I was able to switch back to a bigmem one.
- ensure grub kopts doesn't contain
clocksource=jiffies
After upgrade:
- check again that grub-legacy is there and menu.lst still defaults to
the correct bigmem kernel
I noticed that xen.independent_wallclock (set to 0 in /etc/sysctl.conf) was no
longer accessible after the upgrade.
/sys/devices/system/clocksource/clocksource0/current_clocksource
contains xen, so I am wondering if running ntpd now makes any sense?
Cheers.
--
Bernard Urban