Seems to work better on RC1 when I rolled back guest to run 2.6.24-18-server
I have this problem (freeze up) when I use 2 virtual cpus for 64 bit ubuntu and 32 bit fedora 7.
Both machines were installed with #cpu's = 2.
Both machines work fine when I changed the #cpu's to 1.
I am also having this issue in VMware ESX 3.5 on multiple servers.
Looks like some sort of SMP incompatibility with this kernel and VMWare.
I'm experiencing this as well.
Host is Ubuntu 8.04.1 64-bit running 2.6.24-19-server. It has 4GB of ram with two Dual-Core Opteron 2210's. The vm has 2GB of ram and two 64-bit cpus. The guest runs the same operating system. Vmware Server RC2 build 110949.
Symptoms are as follows. At seemingly random intervals the vm will completely freeze. Oddly, it responds to pings still, but no other processes work. The console does not respond. There are no errors in any of the guest's log files that would give a hint as to what is the cause. Neither have I isolated any particular conditions under which the freeze happens. The frequency is 1-3 times a day.
I've just rolled back the kernel on the guest to 2.6.24-18-server to see if that helps. If I have to, I'll downgrade the machine to a single processor, but I'd much rather avoid that.
Rolling back the kernel did not help at all. Dropping to a single process seemed to reduce the frequency of the freezes, but they still occur every 1 - 2 days.
I'll probably have to drop back to vmware 1.0 on this server. I also can't yet rule out that the problem isn't with Ubuntu rather than vmware.
With VMware Server 2.0 (Beta or RC) and with VMware ESX/ESXi Server 3.5:
1) your VM is running Ubuntu (Server Edition or Desktop Edition version 8.04.1 or older) as guest OS;
2) the Ubuntu version is 64 bit;
3) your VM has more than one CPU (it means two CPUs / SMP)
Then you HAVE to start the kernel with the following parameter:
If not, you will always have your VM freezing (after some minutes or hours, or the clock jumping to year 2240 or so).
See here for more info (this doc is for VMware ESX/ESXi Server, but the problem is the same for VMware ESX/ESXi Server 3.5 and VMWare Server 2.0):
1) http://www.vmware.com/pdf/GuestOS_guide.pdf -- p. 235:
Ubuntu 8.04 LTS, 64-Bit SMP Can Stall When Running, Installing, or Booting On an Intel Host:
Ubuntu 8.04 LTS, 64‐bit SMP guest operating system might take a long time to install (up to two hours with
numerous error messages), might stall at boot, or might stall while running on an Intel Host. For instructions
that fix this problem, see kb.vmware.com/kb/1004384.
2) kb.vmware.com/kb/1004384 (how to adapt your grub boot loader file to include "clocksource=acpi_pm").
After the guest starts, edit the /boot/grub/menu.lst file to make these changes permanent, which will ensure that each time you reboot or run the guest it does not stall:
1. Log in as root at the command line.
2. Use the vi editor to edit the /boot/grub/menu.lst file.
You will see following section in the file:
title Ubuntu 8.04 LTS(7.10), kernel 2.6.22-14-server
kernel /boot/vmlinuz-2.6.22-14-server root=UUID=...... ro quiet splash
3. Add the clocksource=acpi_pm kernel option to the end of the following line:
kernel /boot/vmlinuz-2.6.22-14 -server root=UUID=...... ro quiet splash
4. Save the changes.
Thanks, I've given it a shot on with a single 64-bit processor which is what I'm currently running to try and isolate the problem. Sadly, the freezes still seem to happen when the system is under load. It's too early to say whether the frequency of the freezes has changed at all.