You are not logged in.

#1 2008-09-06 15:14:34

maxbally
Member
Registered: 2008-09-02
Posts: 2

bump VMware Server 1.0.7 Latest error --Not enough memory...

VMware Server Help Post

Platform:
Intel core 2 Duo E2168.
2G ram, but 1/2 just went missing. If this is causing my problems, the mind wobbles, yet it's easy to fix, yay!
Lots of harddrives! Lots of harddrive space.
gigabit eth.
Nvidia 7600GS 512MB
Highpoint raid card (soft) 132Gigs for VMs
Archlinux w/ 2.6.26.3-1 kernel
kernel-headers 2.6.25.8-1

History:
Four weeks ago--
Patched and installed VMware Server 1.0.5 on Archlinux with kernel 2.6.25... everything worked well. Bliss!
About 2 weeks ago--
Upgraded kernel to 2.6.26... time suck began.

Current status:
After banging on VMware and vmmon patch and source code for a while,
now have on kernel 2.6.26-arch--
VMware Server 1.0.7 with patch ...117d, modified as follows:

    In .../vmmon-only/include/iocontrols.h
line 48 #define VMMON_VERSION           (168 << 16 | 0)   changed to:
line 48 #define VMMON_VERSION           (138 << 16 | 0)

Patch reasoning [limited newb alert]:

Without 117d, vmmon fails to compile with error re: .nopage
With 117d, vmmon compiles and installs successfully but VMs
  won't start with error re: expect version 138 got 168
With patch modified, now past the version error, but getting the error:

Not enough physical memory is available to power on this virtual machine.
To fix this problem, power off other virtual machines                      [No others on]
   or adjust the additional memory settings to allow more virtual machine
   memory to be swapped                                   [There's plenty of memory]
If you were able to power on this virtual machine on this host computer
   in the past, try rebooting the host computer. Rebooting may allow you
   to use slightly more host memory to run virtual machines.                [Rebooting had no effect]

In log:
Failed to connect to vm: /mnt/VMs/Test Booger/Test Booger.vmx
vmdbPipe_Streams Couldn't read: OVL_STATUS_EOF

Error during launch: 11, The process exited with an error:
End of error message
Operation failed to change the VM to the expected power state.

Not enough physical memory is available to power on this virtual machine.
To fix this problem, power off other virtual machines                      [No others on]
   or adjust the additional memory settings to allow more virtual machine
   memory to be swapped                                   [There's plenty of memory]
If you were able to power on this virtual machine on this host computer
   in the past, try rebooting the host computer. Rebooting may allow you
   to use slightly more host memory to run virtual machines.                [Rebooting had no effect]


There's plenty of memory and disk free space--

top -b >> top_out
top - 06:59:46 up 40 min,  0 users,  load average: 0.02, 0.05, 0.03
Tasks: 113 total,   1 running, 112 sleeping,   0 stopped,   0 zombie
Cpu(s):  1.1%us,  0.5%sy,  0.0%ni, 97.2%id,  1.2%wa,  0.0%hi,  0.0%si,  0.0%st
Mem:   1034920k total,   441944k used,   592976k free,    17604k buffers
Swap:  2000084k total,        0k used,  2000084k free,   227224k cached


df -ha
Filesystem            Size  Used Avail Use% Mounted on
/dev/sda3              72G   44G   25G  65% /
/dev/sdc1              20G   12G  7.5G  61% /mnt/home2
/dev/mapper/hpt45x_dcafabbcai1
                      153G   21G  132G  14% /mnt/VMs


I reduced host memory settings to 408MB and guest to 256MB as a test.            [No effect]

After the tests I've done, I don't believe this error really has anything to do with low memory.
I don't know whether this is a bug, a patch problem, or, or, or, or .....

And so I post.
What next?
thanx in advance. smile

Last edited by maxbally (2008-09-15 23:33:21)

Offline

Board footer

Powered by FluxBB