Hello All,
Yesterday afternoon 4 guest VM's running WIN2K3 (32-bit Standard Edition)
SP1 RC2 crashed approx every 20 minutes for about 3 hours, we run 2 reference
hosts that run WIN2K3 (32-bit Enterprise Edition) SP1 RC2, 1 host has 3 guest
VM's, the other has 4 guest VM's, the machine with the 4 guest VM's was the one
experiencing the problems, the other host was fine. Prior to this the VM’s had
been stable for months.
The host machines are Fujitsu-Siemens RX300 S3, consisting of dual core
Intel XEON 3ghz processors, 8gb Memory, the VM's are held on a RAID5 disk
partition. We are running VMWARE Server 1.04.56528 and have VMTools installed.
The guest VM's are all configured the same way, 32-bit, dual processor,
784mb Memory, WIN2K3 Std Edt, SP1, RC2, VMTools Installed.
I have not changed any of the advanced settings such as Disable Memory
trimming or Disable Acceleration.
From searching through the communities it appears that this is problem is a
common one, especially amongst LINUX users, however I can't seem to find much
that relates to WIN2K3 environments.
My line of thinking is that are we potentially overloading the amount of
physical memory by assigning too much memory per guest VM, this might explain
why the host server running only 3 guest VM's hasn’t experienced this problem.
So if we threw more physical memory at the 4 * guest VM host would that solve
the problem, or is it a bug within this level of VMWARE Server.
The guest VM's on this host have been stable since 19:00 last night, nothing
has been changed config wise, and prior to yesterday afternoon the guest VM's
had been stable for months.
I have attached copies of both the vmware.log from one of the guest VM's,
and also the vmware-serverd.log file.
Thanks in advance for your time.
Regards Jon
Yesterday afternoon 4 guest VM's running WIN2K3 (32-bit Standard Edition)
SP1 RC2 crashed approx every 20 minutes for about 3 hours, we run 2 reference
hosts that run WIN2K3 (32-bit Enterprise Edition) SP1 RC2, 1 host has 3 guest
VM's, the other has 4 guest VM's, the machine with the 4 guest VM's was the one
experiencing the problems, the other host was fine. Prior to this the VM’s had
been stable for months.
The host machines are Fujitsu-Siemens RX300 S3, consisting of dual core
Intel XEON 3ghz processors, 8gb Memory, the VM's are held on a RAID5 disk
partition. We are running VMWARE Server 1.04.56528 and have VMTools installed.
The guest VM's are all configured the same way, 32-bit, dual processor,
784mb Memory, WIN2K3 Std Edt, SP1, RC2, VMTools Installed.
I have not changed any of the advanced settings such as Disable Memory
trimming or Disable Acceleration.
From searching through the communities it appears that this is problem is a
common one, especially amongst LINUX users, however I can't seem to find much
that relates to WIN2K3 environments.
My line of thinking is that are we potentially overloading the amount of
physical memory by assigning too much memory per guest VM, this might explain
why the host server running only 3 guest VM's hasn’t experienced this problem.
So if we threw more physical memory at the 4 * guest VM host would that solve
the problem, or is it a bug within this level of VMWARE Server.
The guest VM's on this host have been stable since 19:00 last night, nothing
has been changed config wise, and prior to yesterday afternoon the guest VM's
had been stable for months.
I have attached copies of both the vmware.log from one of the guest VM's,
and also the vmware-serverd.log file.
Thanks in advance for your time.
Regards Jon
Attachments:
- vmware.log (55.4 K)
- vmware-serverd.log (55.4 K)
Tags:
error,
server,
vmware,
vmware_server,
windows