VMware Communities
PeterP86
Contributor
Contributor
Jump to solution

VMware ESX3.5u4 as VM + VM in virtualized ESX3.5u4

The situation is based on my experience. Please leave the idea of this tests and don't ask why.

Scenario:

On Lenovo T400 I have installed VMware Workstation 7. I have created virtual machine with ESX3.5u4. There were no problems with installing it. After that, in virtualized ESX3.5u4 I have created another virtual machine with Debian 6.0 Squeeze 32 bit. To launch it as we all know, we need to add a line "monitor_control.restrict_backdoor = TRUE" to .vmx file of ESX3.5u4 VM.

After installing VMware Tools on Debian 6.0 Squeeze VM, I`am launching vmware-config and get errors:

"This configuration program is to be executed in a virtual machine.

Execution aborted."

I'am also checking sh scripts from /usr/bin/

vmware-questd
The VMware service must be run from within a virtual machine.
Log: The VMware service must be run from within a virtual machine.
Log: Backtrace:
Log: Backtrace[0] 0xbff552d8 eip 0x8072131
Log: Backtrace[1] 0xbff556f8 eip 0x80768b6
Log: Backtrace[2] 0xbff55708 eip 0x8067f88
Log: Backtrace[3] 0xbff55748 eip 0x804c9e4
Log: Backtrace[4] 0xbff557c8 eip 0xb7628c76
Log: Backtrace[5] 00000000 eip 0x804a961

vmware-user
/usr/lib/vmware-tools/bin32/vmware-user: error while loading shared libraries:
libXi.so.6: cannot open shared object file: No such file or directory

vmware-checkvm
Couldn't get version

vmware-hgfsclient
[hgfsclient] WARNING: This application must be run in a Virtual Machine.

vmware-toolbox
PANIC: The VMware Toolbox must be run inside a virtual machine.

vmware-tools-upgrader
Log: HOSTINFO: Seeing Intel CPU, numCoresPerCPU 1 numThreadsPerCore 1.
Log: HOSTINFO: This machine has 1 physical CPUS, 1 total cores, and 1 logical CPUs.
PANIC: The VMware Tools Upgrader application must be run in a Virtual Machine.

Can anybody explain how VMware tools are recognizing if they are in virtual machine?

0 Kudos
1 Solution

Accepted Solutions
admin
Immortal
Immortal
Jump to solution

Remove the monitor_control.restrict_backdoor setting from the inner VM.  This setting is to be used for the outer VM.

View solution in original post

0 Kudos
4 Replies
continuum
Immortal
Immortal
Jump to solution

Hi
this works for me

please attach the vmx of the nested VM and the vmware.log from the ESX3.5u4 VM so that I can compare with what I have


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

0 Kudos
PeterP86
Contributor
Contributor
Jump to solution

Here are the files:

0 Kudos
admin
Immortal
Immortal
Jump to solution

Remove the monitor_control.restrict_backdoor setting from the inner VM.  This setting is to be used for the outer VM.

0 Kudos
PeterP86
Contributor
Contributor
Jump to solution

It doesn`t change a thing. Oh it does. OK. Works now. I don`t know how did I add this line to nested vm.

0 Kudos