WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

RE: [Xen-users] howto upgrade

On Tue, 27 Jan 2009, Robert Dunkley wrote:

We saw time keeping issues with the Tyan B4989 Quads Opterons, I think
it is fairly common. In the end we found using the /acpi=on (Might want
to try numa=on as well) in the bootloader and setting hpet=0 in the VM
config file reduced the problem significantly and NTP on the actual VMs
could then compensate for small differences. This problem sounds similar
to the one you are having in Dom 0, try changing the ACPI HPET option in
the bios (If the VX50 has it).

Hi Rob,

thanks for the answer! Here are some new questions... :-)

What does HPET actually mean? In the BIOS I have found a Hammer Configuration menu in the Advanced section. In that there is a "ACPI 2.0 Static Resources Affinity Table for ccNUMA systems" option which I have switched off (till this time it was Enabled). I am curious if that helps...

The timer problem often appeared already during the boot process of xen and sometimes it led to system hangup with
"BUG: soft lockup detected on CPU#2" (the number 2 is just an example)
messages...

Here you can find some typical logs:
http://www.mm.bme.hu/~szazs/tmp/xenlogs.php
(there was no backup after midnight between Jan 07 and Jan 25 because of a typo in the dirvish.conf)

On Jan 27 I could not reboot XEN because the backup partition get corrupted, so I have rebooted a simple debian kernel (2.6.24-etchnhalf-amd64) to rebuild-tree and to do some maintenance... and I saw that raid1 has problem with sdd3 so I removed it from the mirror.

Since the reboot this morning it runs "smoothly" but I do not know whether
it is because of either the BIOS change or the rebuilt backup partition or the kicked off mirror partition...

As for upgrading with rollback, this can be done by building the new
kernel and adding it as a separate option in your bootloader (eg. Grub).
I'm quite new to Kernel building and have only just got my first builds
working so you might want to wait for advice from a more experienced
user on that.

So the changed libs cannot be a problem...? Are there any special things when considering an upgrade? (from 3.1.x to 3.2.x the network bridge setup scripts have changed, so I needed some time to figure out the new syntax)

TIA,
--
Zsolt

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>