OK all -
Host is Mandriva Linux 2007/x86-64.
Workstation 5.5.3, installed from tarball; used vmware-any-any-1.05; modules compiled and loaded OK.
When I try to start up a guest OS, I get:
"Unable to change virtual machine power state: Failed to connect to peer process."
I found (I believe in the FAQ but can't recall for sure) that the libXrender library has to be installed. Well, it is.....
\[root@yoda: /home/rcs]$ findr libXrender.so.1
/usr/lib/libXrender.so.1
/usr/lib64/libXrender.so.1
/local/mdk/lib/vmware/lib/libXrender.so.1
/local/mdk/lib/vmware/lib/libXrender.so.1/libXrender.so.1
Is there something new in this version that I need to know about?
5.5.2 would at least let me start up the guest (it later bombed because WS can't handle SATA raw drives, but it at least made the effort).
Thanks
Bob
OK, tried it again, this time using the 5.5.3 rpm file instead of installing from the tarball..
Same error: "Unable to change virtual machine power state: Failed to connect to peer process".
I have run a search on this forum. The solutions seem to involve having libXrender installed (it is), permissions on vmware-vmx ("other" user has execute permission) and adding the regular user to the vmware group (does not exist on this system).
System setup:
Athlon-64x2
Mandriva 2007, kernel-multimedia-2.6.17.13-3mdvsmp (x86-64); ia32 compatibility enabled.
\[root@yoda: / ]$ findr libXrender*
/usr/lib/libXrender.so.1
/usr/lib/libXrender.so.1.3.0
/usr/lib/vmware/lib/libXrender.so.1
/usr/lib/vmware/lib/libXrender.so.1/libXrender.so.1
/usr/lib64/libXrender.so
/usr/lib64/libXrender.so.1
/usr/lib64/libXrender.la
/usr/lib64/libXrender.so.1.3.0
\[root@yoda: / ]$ lsl /usr/lib/vmware/bin/vm*
-r-xr-xr-x 1 root root 4436180 Nov 13 13:10 /usr/lib/vmware/bin/vmplayer*
-r-xr-xr-x 1 root root 2278828 Nov 13 13:10 /usr/lib/vmware/bin/vmrun*
-r-xr-xr-x 1 root root 6892268 Nov 13 13:10 /usr/lib/vmware/bin/vmware*
-r-sr-xr-x 1 root root 4195608 Nov 13 13:10 /usr/lib/vmware/bin/vmware-vmx*
Any help would be appreciated. Thanks.
Bob
Just to clarify the host is running Madriva and VM Ware Workstation 5.5.3 has installed but does not work. It use to work on 5.5.2.
Do you have a backup of the system before you installed 5.5.3 ?
Did you suspend or shutdown the machine before doing the uppgrade? Can you list the content of your Guest OS folder?
\-- Edi
Just to clarify the host is running Madriva and VM
Ware Workstation 5.5.3 has installed but does not
work. It use to work on 5.5.2.
Do you have a backup of the system before you
installed 5.5.3 ?
Yes, 5.5.3, Mandriva 2007/x86_64 SMP. It never actually worked well under 5.5.2, but it at least tried to boot the guest (before bombing out because it can't boot from a raw SATA partition).
Under 5.5.3, it doesn't even do that...and it would not let me set up a non-raw VM (gave the same error as in the original post).
The 5.5.2 backup was over-written quite a while ago.
Bob
Post the output from the following
ldd /usr/lib/vmware/bin/vmware
ldd /usr/lib/vmware/bin/vmware
Post the output from the following
ldd /usr/lib/vmware/bin/vmware
OK.....
\[rcs@yoda: ~]$ ldd /usr/lib/vmware/bin/vmware
linux-gate.so.1 => (0xffffe000)
libdl.so.2 => /lib/libdl.so.2 (0xf7ef7000)
libm.so.6 => /lib/libm.so.6 (0xf7ed1000)
libX11.so.6 => /usr/lib/libX11.so.6 (0xf7dd3000)
libXext.so.6 => /usr/lib/libXext.so.6 (0xf7dc4000)
libXi.so.6 => /usr/lib/libXi.so.6 (0xf7dbb000)
libexpat.so.0 => /usr/lib/libexpat.so.0 (0xf7d99000)
libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0xf7d6b000)
libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0xf7cfe000)
libXrender.so.1 => /usr/lib/libXrender.so.1 (0xf7cf5000)
libXft.so.2 => /usr/lib/libXft.so.2 (0xf7ce1000)
libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0xf7c44000)
libgmodule-2.0.so.0 => /usr/lib/libgmodule-2.0.so.0 (0xf7c40000)
libgobject-2.0.so.0 => /usr/lib/libgobject-2.0.so.0 (0xf7c02000)
libgthread-2.0.so.0 => /usr/lib/libgthread-2.0.so.0 (0xf7bfd000)
libatk-1.0.so.0 => /usr/lib/libatk-1.0.so.0 (0xf7be1000)
libpango-1.0.so.0 => /usr/lib/libpango-1.0.so.0 (0xf7ba3000)
libpangoft2-1.0.so.0 => /usr/lib/libpangoft2-1.0.so.0 (0xf7b73000)
libpangoxft-1.0.so.0 => /usr/lib/libpangoxft-1.0.so.0 (0xf7b6c000)
libpangox-1.0.so.0 => /usr/lib/libpangox-1.0.so.0 (0xf7b60000)
libgdk-x11-2.0.so.0 => /usr/lib/libgdk-x11-2.0.so.0 (0xf7ad3000)
libgdk_pixbuf-2.0.so.0 => /usr/lib/libgdk_pixbuf-2.0.so.0 (0xf7abb000)
libgtk-x11-2.0.so.0 => /usr/lib/libgtk-x11-2.0.so.0 (0xf772d000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0xf7721000)
libstdc+.so.5 => /usr/lib/libstdc+.so.5 (0xf7662000)
libsigc-2.0.so.0 => not found
libglibmm-2.4.so.1 => not found
libglibmm_generate_extra_defs-2.4.so.1 => not found
libatkmm-1.6.so.1 => not found
libpangomm-1.4.so.1 => not found
libgdkmm-2.4.so.1 => not found
libgtkmm-2.4.so.1 => not found
libart_lgpl_2.so.2 => /usr/lib/libart_lgpl_2.so.2 (0xf7647000)
libxml2.so.2 => /usr/lib/libxml2.so.2 (0xf7519000)
libglade-2.0.so.0 => not found
libgnomecanvas-2.so.0 => not found
libgnomecanvasmm-2.6.so.1 => not found
librsvg-2.so.2 => not found
libview.so.2 => not found
libsexy.so.1 => not found
libsexymm.so.1 => not found
libpthread.so.0 => /lib/libpthread.so.0 (0xf7505000)
libz.so.1 => /lib/libz.so.1 (0xf74f3000)
libc.so.6 => /lib/libc.so.6 (0xf73c5000)
/lib/ld-linux.so.2 (0xf7f19000)
libXau.so.6 => /usr/lib/libXau.so.6 (0xf73c2000)
libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0xf73bc000)
librt.so.1 => /lib/librt.so.1 (0xf73b3000)
libpangocairo-1.0.so.0 => /usr/lib/libpangocairo-1.0.so.0 (0xf73a9000)
libcairo.so.2 => /usr/lib/libcairo.so.2 (0xf733b000)
libXinerama.so.1 => /usr/lib/libXinerama.so.1 (0xf7338000)
libXrandr.so.2 => /usr/lib/libXrandr.so.2 (0xf7334000)
libXcursor.so.1 => /usr/lib/libXcursor.so.1 (0xf732a000)
libXfixes.so.3 => /usr/lib/libXfixes.so.3 (0xf7325000)
libpng12.so.0 => /usr/lib/libpng12.so.0 (0xf72ff000)
Ok...it's saying some aren't found - but:
\[root@yoda: ~]$ findr libsigc-2.0.so.0
/usr/lib/vmware/lib/libsigc-2.0.so.0
/usr/lib/vmware/lib/libsigc-2.0.so.0/libsigc-2.0.so.0
/usr/lib64/libsigc-2.0.so.0
\[root@yoda: ~]$ findr libglibmm-2.4.so.1
/usr/lib/vmware/lib/libglibmm-2.4.so.1
/usr/lib/vmware/lib/libglibmm-2.4.so.1/libglibmm-2.4.so.1
/usr/lib64/libglibmm-2.4.so.1
...and so forth...I didn't check them all, but the first five of those "missing" files do exist.
???
Thanks
Bob
Open a terminal window and loin as root ( su - )
VMWARE_DEBUG=yes vmware-config.pl
Any reported erorrs?
Check that /dev/vmmon exists and that the vmmon kernel module is being loaded ( lsmod | grep vm )
By the way, I would use the any-any-update108 patch
Open a terminal window and loin as root ( su - )
VMWARE_DEBUG=yes vmware-config.pl
Any reported erorrs?
Check that /dev/vmmon exists and that the vmmon
kernel module is being loaded ( lsmod | grep vm )
By the way, I would use the any-any-update108 patch
Here you go:
NOTE: These "missing" library files DO exist, in /usr/ib, /usr/lib64, /lib, or /lib64. Also, this distro DOES use glibc.
\[root@yoda: ~]$ VMWARE_DEBUG=yes vmware-config.pl
The correct version of one or more libraries needed to run VMware Workstation
may be missing. This is the output of ldd /usr/bin/vmware:
linux-gate.so.1 => (0xffffe000)
libm.so.6 => /lib/libm.so.6 (0xf7f8d000)
libdl.so.2 => /lib/libdl.so.2 (0xf7f89000)
libpthread.so.0 => /lib/libpthread.so.0 (0xf7f76000)
libX11.so.6 => /usr/lib/libX11.so.6 (0xf7e78000)
libXtst.so.6 => not found
libXext.so.6 => /usr/lib/libXext.so.6 (0xf7e68000)
libXt.so.6 => /usr/lib/libXt.so.6 (0xf7e11000)
libICE.so.6 => /usr/lib/libICE.so.6 (0xf7df8000)
libSM.so.6 => /usr/lib/libSM.so.6 (0xf7def000)
libXrender.so.1 => /usr/lib/libXrender.so.1 (0xf7de6000)
libz.so.1 => /lib/libz.so.1 (0xf7dd3000)
libc.so.6 => /lib/libc.so.6 (0xf7ca6000)
/lib/ld-linux.so.2 (0xf7fd1000)
libXau.so.6 => /usr/lib/libXau.so.6 (0xf7ca3000)
libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0xf7c9d000)
This program cannot tell for sure, but you may need to upgrade libc5 to glibc
before you can run VMware Workstation.
Hit enter to continue.
Making sure services for VMware Workstation are stopped.
Stopping VMware services:
Virtual machine monitor \[ OK ]
Bridged networking on /dev/vmnet0 \[ OK ]
Virtual ethernet \[ OK ]
Configuring fallback GTK+ 2.4 libraries.
In which directory do you want to install the mime type icons?
What directory contains your desktop menu entry files? These files have a
In which directory do you want to install the application's icon?
Trying to find a suitable vmmon module for your running kernel.
None of the pre-built vmmon modules for VMware Workstation is suitable for your
running kernel. Do you want this program to try to build the vmmon module for
your system (you need to have a C compiler installed on your system)? \[yes]
Using compiler "/usr/bin/gcc". Use environment variable CC to override.
What is the location of the directory of C header files that match your running
kernel?
Extracting the sources of the vmmon module.
Building the vmmon module.
Using 2.6.x kernel build system.
make: Entering directory `/root/tmp/vmware-config2/vmmon-only'
make -C /lib/modules/2.6.17.13-3mdvmmcustom-k8-smp/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/kernel-multimedia-2.6.17.13-3mdv'
CC /root/tmp/vmware-config2/vmmon-only/linux/driver.o
CC /root/tmp/vmware-config2/vmmon-only/linux/hostif.o
CC /root/tmp/vmware-config2/vmmon-only/common/cpuid.o
CC /root/tmp/vmware-config2/vmmon-only/common/hash.o
CC /root/tmp/vmware-config2/vmmon-only/common/memtrack.o
CC /root/tmp/vmware-config2/vmmon-only/common/phystrack.o
CC /root/tmp/vmware-config2/vmmon-only/common/task.o
CC /root/tmp/vmware-config2/vmmon-only/common/vmx86.o
CC /root/tmp/vmware-config2/vmmon-only/vmcore/moduleloop.o
LD /root/tmp/vmware-config2/vmmon-only/vmmon.o
Building modules, stage 2.
MODPOST
CC /root/tmp/vmware-config2/vmmon-only/vmmon.mod.o
LD /root/tmp/vmware-config2/vmmon-only/vmmon.ko
make[1]: Leaving directory `/usr/src/kernel-multimedia-2.6.17.13-3mdv'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory `/root/tmp/vmware-config2/vmmon-only'
The module loads perfectly in the running kernel.
This program previously created the file /dev/parport1, and was about to remove
it. Somebody else apparently did it already.
This program previously created the file /dev/parport2, and was about to remove
it. Somebody else apparently did it already.
This program previously created the file /dev/parport3, and was about to remove
it. Somebody else apparently did it already.
You have already setup networking.
Would you like to skip networking setup and keep your old settings as they are?
(yes/no) \[yes]
Extracting the sources of the vmnet module.
Building the vmnet module.
Using 2.6.x kernel build system.
make: Entering directory `/root/tmp/vmware-config2/vmnet-only'
make -C /lib/modules/2.6.17.13-3mdvmmcustom-k8-smp/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/kernel-multimedia-2.6.17.13-3mdv'
CC /root/tmp/vmware-config2/vmnet-only/driver.o
CC /root/tmp/vmware-config2/vmnet-only/hub.o
CC /root/tmp/vmware-config2/vmnet-only/userif.o
CC /root/tmp/vmware-config2/vmnet-only/netif.o
CC /root/tmp/vmware-config2/vmnet-only/bridge.o
CC /root/tmp/vmware-config2/vmnet-only/procfs.o
CC /root/tmp/vmware-config2/vmnet-only/smac_compat.o
SHIPPED /root/tmp/vmware-config2/vmnet-only/smac_linux.x86_64.o
LD /root/tmp/vmware-config2/vmnet-only/vmnet.o
Building modules, stage 2.
MODPOST
CC /root/tmp/vmware-config2/vmnet-only/vmnet.mod.o
LD /root/tmp/vmware-config2/vmnet-only/vmnet.ko
make[1]: Leaving directory `/usr/src/kernel-multimedia-2.6.17.13-3mdv'
cp -f vmnet.ko ./../vmnet.o
make: Leaving directory `/root/tmp/vmware-config2/vmnet-only'
The module loads perfectly in the running kernel.
Starting VMware services:
Virtual machine monitor \[ OK ]
Virtual ethernet \[ OK ]
Bridged networking on /dev/vmnet0 \[ OK ]
The configuration of VMware Workstation 5.5.3 build-34685 for Linux for this
running kernel completed successfully.
You can now run VMware Workstation by invoking the following command:
"/usr/bin/vmware".
Enjoy,
--the VMware team
I will look for the any-any-108 patch
Thanks....Bob
I am having a similar problem on a Fedora Core 6, with kernel:
kernel-xen-2.6.19-1.2911.fc6
kernel-xen-devel-2.6.19-1.2911.fc6
kernel-headers-2.6.19-1.2911.fc6
When I start the VM I see no bios messages, nothing, and it stays there until it times-out and says:
Cannot find a valid peer process to connect to.
I've tried to turn on logging but couldn't file where it is logging, tried adding
log.filename = "/tmp/vm1.log"
to the .vmx file but that does not seems to be ignored, or the thing does not even get to the point of creating the log file.
I don't see the same complains about missing libraries with
VMWARE_DEBUG=yes vmware-config.pl
(...)
Configuring fallback GTK+ 2.4 libraries.
(...)
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config0/vmmon-only'
make -C /usr/src/kernels/2.6.19-1.2911.fc6-xen-i686/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/kernels/2.6.19-1.2911.fc6-xen-i686'
CC /tmp/vmware-config0/vmmon-only/linux/driver.o
CC /tmp/vmware-config0/vmmon-only/linux/hostif.o
CC /tmp/vmware-config0/vmmon-only/common/cpuid.o
CC /tmp/vmware-config0/vmmon-only/common/hash.o
CC /tmp/vmware-config0/vmmon-only/common/memtrack.o
CC /tmp/vmware-config0/vmmon-only/common/phystrack.o
CC /tmp/vmware-config0/vmmon-only/common/task.o
CC /tmp/vmware-config0/vmmon-only/common/vmx86.o
CC /tmp/vmware-config0/vmmon-only/vmcore/moduleloop.o
LD /tmp/vmware-config0/vmmon-only/vmmon.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-config0/vmmon-only/vmmon.mod.o
LD /tmp/vmware-config0/vmmon-only/vmmon.ko
make[1]: Leaving directory `/usr/src/kernels/2.6.19-1.2911.fc6-xen-i686'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory `/tmp/vmware-config0/vmmon-only'
The module loads perfectly in the running kernel.
(...)
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config0/vmnet-only'
make -C /usr/src/kernels/2.6.19-1.2911.fc6-xen-i686/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/kernels/2.6.19-1.2911.fc6-xen-i686'
CC /tmp/vmware-config0/vmnet-only/driver.o
CC /tmp/vmware-config0/vmnet-only/hub.o
CC /tmp/vmware-config0/vmnet-only/userif.o
CC /tmp/vmware-config0/vmnet-only/netif.o
CC /tmp/vmware-config0/vmnet-only/bridge.o
CC /tmp/vmware-config0/vmnet-only/procfs.o
CC /tmp/vmware-config0/vmnet-only/smac_compat.o
SHIPPED /tmp/vmware-config0/vmnet-only/smac_linux.x386.o
LD /tmp/vmware-config0/vmnet-only/vmnet.o
Building modules, stage 2.
MODPOST 1 modules
WARNING: could not open /tmp/vmware-config0/vmnet-only/includeCheck.h: Invalid argument
CC /tmp/vmware-config0/vmnet-only/vmnet.mod.o
LD /tmp/vmware-config0/vmnet-only/vmnet.ko
make[1]: Leaving directory `/usr/src/kernels/2.6.19-1.2911.fc6-xen-i686'
cp -f vmnet.ko ./../vmnet.o
make: Leaving directory `/tmp/vmware-config0/vmnet-only'
The module loads perfectly in the running kernel.
Starting VMware services:
Virtual machine monitor \[ OK ]
Virtual ethernet \[ OK ]
Bridged networking on /dev/vmnet0 \[ OK ]
Host-only networking on /dev/vmnet8 \[ OK ]
NAT service on /dev/vmnet8Using configuration file: /etc/vmware/vmnet8/nat/nat.conf.
IP address: 192.168.17.2
Subnet: 255.255.255.0
External IP address: 0.0.0.0
Device: /dev/vmnet8.
MAC address: 00:50:56:FD:BE:04.
Ignoring host MAC address: 00:50:56:C0:00:08.
\[ OK ]
Only this "WARNING: could not open /tmp/vmware-config0/vmnet-only/includeCheck.h: Invalid argument" looks out of the ordinary.
The same missing files are reported with
ldd /usr/lib/vmware/bin/vmware
(...)
libsigc-2.0.so.0 => not found
libglibmm-2.4.so.1 => not found
libglibmm_generate_extra_defs-2.4.so.1 => not found
libatkmm-1.6.so.1 => not found
libpangomm-1.4.so.1 => not found
libgdkmm-2.4.so.1 => not found
libgtkmm-2.4.so.1 => not found
(...)
libgnomecanvasmm-2.6.so.1 => not found
(...)
libview.so.2 => not found
libsexy.so.1 => not found
libsexymm.so.1 => not found
But they also exist on vmware land:
\# ls /usr/lib/vmware/lib/libsigc-2.0.so.0
libsigc-2.0.so.0
\# ls /usr/lib/vmware/lib/libglibmm-2.4.so.1
libglibmm-2.4.so.1
Finaly, can you give us a pointer for this any-any-108 pacth? I can't find it anywhere.
What is this patch about?
Thanks for your help.
Fernando
Do not use a xen kernel. Change to a standard kernel if you want to install VMware products. Otherwise, you have competing hypervisors.
Finaly, can you give us a pointer for this any-any-108 pacth? I can't find it anywhere.
Petr's latest vmware-any-any-update patch( vmware-any-any-update108.tar.gz) . Can be found here:
http://platan.vc.cvut.cz/ftp/pub/vmware/
kernel-2.6.19-1.2911.fc6
kernel-devel-2.6.19-1.2911.fc6
Packages, since you can not use a xen kernel
Thanks, it works fine with the non-xen kernel, I didn't even had to use the any-any patch.
OK, applied the any-any-108 patch. Still no go. I get these errors when executing vmware from a terminal window:
\[rcs@yoda: ~]$ vmware
/usr/lib/vmware/bin/vmware: /usr/lib/vmware/lib/libpng12.so.0/libpng12.so.0: no version information available (required by /usr/lib/libcairo.so.2)
/usr/lib/vmware/bin/vmware-vmx: error while loading shared libraries: libXtst.so.6: cannot open shared object file: No such file or directory
However:
\[root@yoda: ~]$ findr libXtst*
/usr/lib64/libXtst.so
/usr/lib64/libXtst.so.6
/usr/lib64/libXtst.so.6.1.0
/usr/lib64/libXtst.la
\[root@yoda: ~]$ findr libpng12.so.0
/usr/lib/libpng12.so.0
/usr/lib/vmware/lib/libpng12.so.0
/usr/lib/vmware/lib/libpng12.so.0/libpng12.so.0
/usr/lib64/libpng12.so.0
Is the problem simply that vmware can't use the 64-bit library files, or is it a library path problem?
Thanks
Bob
