Can't get VMware player to install in Ubuntu 12.04

May 3, 2013, 5:11 am

Latest and popular articles on VMWare Virtualization

≫ Next: Vmware Unity problems in gnome 3

≪ Previous: Installing Antivirus in the Guest OS

$

0

0

I am running Ubuntu 12.04 LTS and trying to install VMware Player for Linux 32-bit.

I have the file: VMware-Player-5.0.2-1031769.i386.txt

I double click on it and it opens and starts to unpack?

After about 2 hours it gets to line 742055 then stalls and closes (screenshot attached).

I get an error message (attached)

I have plenty of memory so I don't understand this failure

I have restarted the computor so that no other programs are running except this install

I have done this 5 times now with the same result

Any help, in very basic terms, will be very greatly appreciated

---

Vmware Unity problems in gnome 3

May 3, 2013, 4:44 pm

Latest and popular articles on VMWare Virtualization

≫ Next: Portforwarding not working on vmware backtrack with usb wifi adapter

≪ Previous: Can't get VMware player to install in Ubuntu 12.04

$

0

0

Hello!

I installed ubuntu 13.04 as a guest os on vmware. I then installed gnome 3 classic and normal. However, I still cannot start vmware unity. Does anyone know why? Yes, I checked and reinstalled vmware tools for linux.

Portforwarding not working on vmware backtrack with usb wifi adapter

May 4, 2013, 1:43 am

Latest and popular articles on VMWare Virtualization

≫ Next: Problem entering Unity mode/VMware Tools

≪ Previous: Vmware Unity problems in gnome 3

$

0

0

I have a backtrack virtual machine on vmware workstation with external usb wifi adapter. The portforwarding is not working, but it works fine with the Backtrack Live CD.

Pls help !!

Problem entering Unity mode/VMware Tools

May 5, 2013, 12:01 pm

Latest and popular articles on VMWare Virtualization

≫ Next: vmware player 5.0.2 on Mageia 3 RC x86_64 problem

≪ Previous: Portforwarding not working on vmware backtrack with usb wifi adapter

$

0

0

I just got VMware up and running Windows 7 Ultimate x64 as a guest in Ubuntu 13.04. I am now trying to enter Unity mode and I get the following:

 

"The virtual machine cannot enter Unity mode because:

-The guest operating system does not have VMware Tools installed.

-The guest operating system's resolution cannot be changed."

 

So I use the virtual machine bar up at the top and click Install VMware Tools.... Download and Install ... and I get the error:

 

"There was a problem updating a software component. Try again later and if the problem persists ..."

 

Any advice? Thanks.

vmware player 5.0.2 on Mageia 3 RC x86_64 problem

May 5, 2013, 3:52 pm

Latest and popular articles on VMWare Virtualization

≫ Next: vmware player dependency on hal, policykit, consolekit

≪ Previous: Problem entering Unity mode/VMware Tools

$

0

0

I'm having problems getting vmware player 5.0.2 x86_64 running on Mageia 3 RC (x86_64) which is at kernel 3.8.11.

(I note in this context that the vmware-modconfig script whose output is reproduced below is using the kernel 2.6.x kernel build system.  Is this part of the problem and how do I work around this?)

VMware player 5.0.2 x86_64  installed uneventfully, several vmware processes are running.  If I try and start vmplayer however, it crashes with:

 

# cd /usr/bin
# ./vmplayer
Logging to /tmp/vmware-root/vmware-modconfig-31594.log
filename:       /lib/modules/3.8.11-desktop-1.mga3/--appname=VMware/vmmon.ko
supported:      external
license:        GPL v2
description:    VMware Virtual Machine Monitor.
author:         VMware, Inc.
srcversion:     720B99362854B538D7E9A9A
depends:       
vermagic:       3.8.11-desktop-1.mga3 SMP mod_unload modversions
PANIC /build/mts/release/bora-1031769/bora/lib/unicode/unicodeCommon.c:330
Aborted

 

Any ideas?  Would really appreciate some help as to where to go from here.

Thanks to all,
Tony Blackwell

 

I did re-run config stuff as below.  There are 2 files: the console stuff immediately following this, and after some white space, the log file of attempting to run vmplayer, as referred to above:

 

# vmware-modconfig --console --install-all --appname="VMware Player" --icon="vmware-player"/usr/lib/vmware/bin
/usr/lib/vmware/bin/vmware-modconfig-console: invalid option -- '-'
Stopping vmware (via systemctl):                                [  OK  ]
Using 2.6.x kernel build system.
make: Entering directory `/tmp/modconfig-pBuPZc/vmmon-only'
/usr/bin/make -C /lib/modules/3.8.11-desktop-1.mga3/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-3.8.11-desktop-1.mga3'
  CC [M]  /tmp/modconfig-pBuPZc/vmmon-only/linux/driver.o
  CC [M]  /tmp/modconfig-pBuPZc/vmmon-only/linux/hostif.o
  CC [M]  /tmp/modconfig-pBuPZc/vmmon-only/linux/driverLog.o
  CC [M]  /tmp/modconfig-pBuPZc/vmmon-only/common/memtrack.o
  CC [M]  /tmp/modconfig-pBuPZc/vmmon-only/common/apic.o
  CC [M]  /tmp/modconfig-pBuPZc/vmmon-only/common/hashFunc.o
  CC [M]  /tmp/modconfig-pBuPZc/vmmon-only/common/vmx86.o
  CC [M]  /tmp/modconfig-pBuPZc/vmmon-only/common/cpuid.o
  CC [M]  /tmp/modconfig-pBuPZc/vmmon-only/common/task.o
  CC [M]  /tmp/modconfig-pBuPZc/vmmon-only/common/comport.o
  CC [M]  /tmp/modconfig-pBuPZc/vmmon-only/common/phystrack.o
  CC [M]  /tmp/modconfig-pBuPZc/vmmon-only/vmcore/moduleloop.o
/tmp/modconfig-pBuPZc/vmmon-only/linux/driver.c:1370:1: warning: always_inline function might not be inlinable [-Wattributes]
  LD [M]  /tmp/modconfig-pBuPZc/vmmon-only/vmmon.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/modconfig-pBuPZc/vmmon-only/vmmon.mod.o
  LD [M]  /tmp/modconfig-pBuPZc/vmmon-only/vmmon.ko
make[1]: Leaving directory `/usr/src/linux-3.8.11-desktop-1.mga3'
/usr/bin/make -C $PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/modconfig-pBuPZc/vmmon-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/modconfig-pBuPZc/vmmon-only'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory `/tmp/modconfig-pBuPZc/vmmon-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/modconfig-pBuPZc/vmnet-only'
/usr/bin/make -C /lib/modules/3.8.11-desktop-1.mga3/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-3.8.11-desktop-1.mga3'
  CC [M]  /tmp/modconfig-pBuPZc/vmnet-only/driver.o
  CC [M]  /tmp/modconfig-pBuPZc/vmnet-only/hub.o
  CC [M]  /tmp/modconfig-pBuPZc/vmnet-only/userif.o
  CC [M]  /tmp/modconfig-pBuPZc/vmnet-only/netif.o
  CC [M]  /tmp/modconfig-pBuPZc/vmnet-only/bridge.o
  CC [M]  /tmp/modconfig-pBuPZc/vmnet-only/filter.o
  CC [M]  /tmp/modconfig-pBuPZc/vmnet-only/procfs.o
  CC [M]  /tmp/modconfig-pBuPZc/vmnet-only/smac_compat.o
  CC [M]  /tmp/modconfig-pBuPZc/vmnet-only/vnetEvent.o
  CC [M]  /tmp/modconfig-pBuPZc/vmnet-only/smac.o
  CC [M]  /tmp/modconfig-pBuPZc/vmnet-only/vnetUserListener.o
  LD [M]  /tmp/modconfig-pBuPZc/vmnet-only/vmnet.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/modconfig-pBuPZc/vmnet-only/vmnet.mod.o
  LD [M]  /tmp/modconfig-pBuPZc/vmnet-only/vmnet.ko
make[1]: Leaving directory `/usr/src/linux-3.8.11-desktop-1.mga3'
/usr/bin/make -C $PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/modconfig-pBuPZc/vmnet-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/modconfig-pBuPZc/vmnet-only'
cp -f vmnet.ko ./../vmnet.o
make: Leaving directory `/tmp/modconfig-pBuPZc/vmnet-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/modconfig-pBuPZc/vmblock-only'
/usr/bin/make -C /lib/modules/3.8.11-desktop-1.mga3/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-3.8.11-desktop-1.mga3'
  CC [M]  /tmp/modconfig-pBuPZc/vmblock-only/linux/filesystem.o
  CC [M]  /tmp/modconfig-pBuPZc/vmblock-only/linux/stubs.o
  CC [M]  /tmp/modconfig-pBuPZc/vmblock-only/linux/file.o
  CC [M]  /tmp/modconfig-pBuPZc/vmblock-only/linux/block.o
  CC [M]  /tmp/modconfig-pBuPZc/vmblock-only/linux/inode.o
  CC [M]  /tmp/modconfig-pBuPZc/vmblock-only/linux/super.o
  CC [M]  /tmp/modconfig-pBuPZc/vmblock-only/linux/control.o
  CC [M]  /tmp/modconfig-pBuPZc/vmblock-only/linux/module.o
  CC [M]  /tmp/modconfig-pBuPZc/vmblock-only/linux/dentry.o
/tmp/modconfig-pBuPZc/vmblock-only/linux/inode.c:49:4: warning: initialization from incompatible pointer type [enabled by default]
/tmp/modconfig-pBuPZc/vmblock-only/linux/inode.c:49:4: warning: (near initialization for ‘RootInodeOps.lookup’) [enabled by default]
/tmp/modconfig-pBuPZc/vmblock-only/linux/control.c: In function ‘ExecuteBlockOp’:
/tmp/modconfig-pBuPZc/vmblock-only/linux/control.c:285:9: warning: assignment from incompatible pointer type [enabled by default]
/tmp/modconfig-pBuPZc/vmblock-only/linux/control.c:296:4: warning: passing argument 1 of ‘putname’ from incompatible pointer type [enabled by default]
In file included from include/linux/proc_fs.h:5:0,
                 from /tmp/modconfig-pBuPZc/vmblock-only/linux/control.c:28:
include/linux/fs.h:2052:13: note: expected ‘struct filename *’ but argument is of type ‘char *’
/tmp/modconfig-pBuPZc/vmblock-only/linux/dentry.c:38:4: warning: initialization from incompatible pointer type [enabled by default]
/tmp/modconfig-pBuPZc/vmblock-only/linux/dentry.c:38:4: warning: (near initialization for ‘LinkDentryOps.d_revalidate’) [enabled by default]
/tmp/modconfig-pBuPZc/vmblock-only/linux/dentry.c: In function ‘DentryOpRevalidate’:
/tmp/modconfig-pBuPZc/vmblock-only/linux/dentry.c:104:7: warning: passing argument 2 of ‘actualDentry->d_op->d_revalidate’ makes integer from pointer without a cast [enabled by default]
/tmp/modconfig-pBuPZc/vmblock-only/linux/dentry.c:104:7: note: expected ‘unsigned int’ but argument is of type ‘struct nameidata *’
  LD [M]  /tmp/modconfig-pBuPZc/vmblock-only/vmblock.o
  Building modules, stage 2.
  MODPOST 1 modules
WARNING: "putname" [/tmp/modconfig-pBuPZc/vmblock-only/vmblock.ko] undefined!
  CC      /tmp/modconfig-pBuPZc/vmblock-only/vmblock.mod.o
  LD [M]  /tmp/modconfig-pBuPZc/vmblock-only/vmblock.ko
make[1]: Leaving directory `/usr/src/linux-3.8.11-desktop-1.mga3'
/usr/bin/make -C $PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/modconfig-pBuPZc/vmblock-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/modconfig-pBuPZc/vmblock-only'
cp -f vmblock.ko ./../vmblock.o
make: Leaving directory `/tmp/modconfig-pBuPZc/vmblock-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/modconfig-pBuPZc/vmci-only'
/usr/bin/make -C /lib/modules/3.8.11-desktop-1.mga3/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-3.8.11-desktop-1.mga3'
  CC [M]  /tmp/modconfig-pBuPZc/vmci-only/linux/driver.o
  CC [M]  /tmp/modconfig-pBuPZc/vmci-only/linux/vmciKernelIf.o
  CC [M]  /tmp/modconfig-pBuPZc/vmci-only/common/vmciDriver.o
  CC [M]  /tmp/modconfig-pBuPZc/vmci-only/common/vmciResource.o
  CC [M]  /tmp/modconfig-pBuPZc/vmci-only/common/vmciContext.o
  CC [M]  /tmp/modconfig-pBuPZc/vmci-only/common/vmciDatagram.o
  CC [M]  /tmp/modconfig-pBuPZc/vmci-only/common/vmciHashtable.o
  CC [M]  /tmp/modconfig-pBuPZc/vmci-only/common/vmciEvent.o
  CC [M]  /tmp/modconfig-pBuPZc/vmci-only/common/vmciQueuePair.o
  CC [M]  /tmp/modconfig-pBuPZc/vmci-only/common/vmciDoorbell.o
  CC [M]  /tmp/modconfig-pBuPZc/vmci-only/common/vmciQPair.o
  CC [M]  /tmp/modconfig-pBuPZc/vmci-only/common/vmciRoute.o
  CC [M]  /tmp/modconfig-pBuPZc/vmci-only/driverLog.o
  LD [M]  /tmp/modconfig-pBuPZc/vmci-only/vmci.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/modconfig-pBuPZc/vmci-only/vmci.mod.o
  LD [M]  /tmp/modconfig-pBuPZc/vmci-only/vmci.ko
make[1]: Leaving directory `/usr/src/linux-3.8.11-desktop-1.mga3'
/usr/bin/make -C $PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/modconfig-pBuPZc/vmci-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/modconfig-pBuPZc/vmci-only'
cp -f vmci.ko ./../vmci.o
make: Leaving directory `/tmp/modconfig-pBuPZc/vmci-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/modconfig-pBuPZc/vsock-only'
/usr/bin/make -C /lib/modules/3.8.11-desktop-1.mga3/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-3.8.11-desktop-1.mga3'
  CC [M]  /tmp/modconfig-pBuPZc/vsock-only/linux/af_vsock.o
  CC [M]  /tmp/modconfig-pBuPZc/vsock-only/linux/vsockAddr.o
  CC [M]  /tmp/modconfig-pBuPZc/vsock-only/linux/notifyQState.o
  CC [M]  /tmp/modconfig-pBuPZc/vsock-only/linux/util.o
  CC [M]  /tmp/modconfig-pBuPZc/vsock-only/linux/stats.o
  CC [M]  /tmp/modconfig-pBuPZc/vsock-only/linux/notify.o
  CC [M]  /tmp/modconfig-pBuPZc/vsock-only/driverLog.o
  LD [M]  /tmp/modconfig-pBuPZc/vsock-only/vsock.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/modconfig-pBuPZc/vsock-only/vsock.mod.o
  LD [M]  /tmp/modconfig-pBuPZc/vsock-only/vsock.ko
make[1]: Leaving directory `/usr/src/linux-3.8.11-desktop-1.mga3'
/usr/bin/make -C $PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/modconfig-pBuPZc/vsock-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/modconfig-pBuPZc/vsock-only'
cp -f vsock.ko ./../vsock.o
make: Leaving directory `/tmp/modconfig-pBuPZc/vsock-only'
Starting vmware (via systemctl):                                [  OK  ]

 

 

 

 

 

 

And now the log referred to above:
2013-05-05T19:07:47.598+10:00| vthread-3| I120: Log for VMware Workstation pid=31594 version=9.0.2 build=build-1031769 option=Release
2013-05-05T19:07:47.598+10:00| vthread-3| I120: The process is 64-bit.
2013-05-05T19:07:47.598+10:00| vthread-3| I120: Host codepage=UTF-8 encoding=UTF-8
2013-05-05T19:07:47.598+10:00| vthread-3| I120: Host is Linux 3.8.11-desktop-1.mga3 Mageia 3
2013-05-05T19:07:47.598+10:00| vthread-3| I120: Msg_Reset:
2013-05-05T19:07:47.598+10:00| vthread-3| I120: [msg.dictionary.load.openFailed] Cannot open file "/usr/lib/vmware/settings": No such file or directory.
2013-05-05T19:07:47.598+10:00| vthread-3| I120: ----------------------------------------
2013-05-05T19:07:47.598+10:00| vthread-3| I120: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.
2013-05-05T19:07:47.598+10:00| vthread-3| I120: Msg_Reset:
2013-05-05T19:07:47.598+10:00| vthread-3| I120: [msg.dictionary.load.openFailed] Cannot open file "/root/.vmware/config": No such file or directory.
2013-05-05T19:07:47.598+10:00| vthread-3| I120: ----------------------------------------
2013-05-05T19:07:47.598+10:00| vthread-3| I120: PREF Optional preferences file not found at /root/.vmware/config. Using default values.
2013-05-05T19:07:47.598+10:00| vthread-3| I120: Msg_Reset:
2013-05-05T19:07:47.598+10:00| vthread-3| I120: [msg.dictionary.load.openFailed] Cannot open file "/root/.vmware/preferences": No such file or directory.
2013-05-05T19:07:47.598+10:00| vthread-3| I120: ----------------------------------------
2013-05-05T19:07:47.598+10:00| vthread-3| I120: PREF Failed to load user preferences.
2013-05-05T19:07:47.598+10:00| vthread-3| W110: Logging to /tmp/vmware-root/vmware-modconfig-31594.log
2013-05-05T19:07:47.604+10:00| vthread-3| I120: Reading in info for the vmmon module.
2013-05-05T19:07:47.604+10:00| vthread-3| I120: Reading in info for the vmnet module.
2013-05-05T19:07:47.604+10:00| vthread-3| I120: Reading in info for the vmblock module.
2013-05-05T19:07:47.604+10:00| vthread-3| I120: Reading in info for the vmci module.
2013-05-05T19:07:47.604+10:00| vthread-3| I120: Reading in info for the vsock module.
2013-05-05T19:07:47.604+10:00| vthread-3| I120: Setting vsock to depend on vmci.
2013-05-05T19:07:47.604+10:00| vthread-3| I120: Created new pathsHash.
2013-05-05T19:07:47.604+10:00| vthread-3| I120: Invoking modinfo on "vmmon".
2013-05-05T19:07:47.609+10:00| vthread-3| I120: "/sbin/modinfo" exited with status 0.
2013-05-05T19:07:47.609+10:00| vthread-3| I120: Invoking modinfo on "vmnet".
2013-05-05T19:07:47.614+10:00| vthread-3| I120: "/sbin/modinfo" exited with status 0.
2013-05-05T19:07:47.614+10:00| vthread-3| I120: Invoking modinfo on "vmblock".
2013-05-05T19:07:47.619+10:00| vthread-3| I120: "/sbin/modinfo" exited with status 0.
2013-05-05T19:07:47.619+10:00| vthread-3| I120: Invoking modinfo on "vmci".
2013-05-05T19:07:47.624+10:00| vthread-3| I120: "/sbin/modinfo" exited with status 0.
2013-05-05T19:07:47.624+10:00| vthread-3| I120: Invoking modinfo on "vsock".
2013-05-05T19:07:47.628+10:00| vthread-3| I120: "/sbin/modinfo" exited with status 0.

 

vmware player dependency on hal, policykit, consolekit

May 5, 2013, 8:38 pm

Latest and popular articles on VMWare Virtualization

≫ Next: USB 3.0 ... Again ...

≪ Previous: vmware player 5.0.2 on Mageia 3 RC x86_64 problem

$

0

0

Is there going to be a new version of vmware player which does not have dependencies on these deprecated or dropped packages?  It seems that vmware player will not run on some modern linux distributions due to these deprecated/rmoved dependencies.

USB 3.0 ... Again ...

October 30, 2012, 1:25 am

Latest and popular articles on VMWare Virtualization

≫ Next: 0 bytes of system swap space is available

≪ Previous: vmware player dependency on hal, policykit, consolekit

$

0

0

Hi,

 

First time poster, be gentle.

 

M/C Alienware M14X 1 x USB 2.0, 2 x USB 3.0

Host O/S WIndows 7 Ultimate 64 Bi.

VM Player 5.00

Guest O/S OpenSuse 12.2

 

Connecting external drives through the USB 3.0 ports results in the following in the VMWARE log file:

 

2012-10-29T16:23:37.547Z| vmx| I120: USB: Found device [name:Iomega\ ASMedia vid:059b pid:0570 path:1/9/1 speed:super family:storage virtPath:ehci:0 instanceId:USB\\VID_059B&PID_0570\\0123456789ABCDEF serialnum:0123456789ABCDEF disconnected:1 arbRuntimeKey:5 version:2], connected to [EHCI Port 1]

...

2012-10-29T16:23:46.207Z| vmx| W110: USBGA: Failed to connect device 20000005059b0570, error (4)
2012-10-29T16:23:46.207Z| vmx| I120: Msg_Post: Warning
2012-10-29T16:23:46.207Z| vmx| I120: [msg.usb.connectFailedErr] The connection for the USB device "Iomega ASMedia" was unsuccessful. Driver error.

 

When connecting through the USB 2.0 ... all is fine ...

 

2012-10-29T17:54:02.699Z| vmx| I120: USB: Found device [name:Iomega\ ASMedia vid:059b pid:0570 path:1/0/0/1 speed:high family:vendor,storage virtPath:ehci:0 instanceId:USB\\VID_0E0F&PID_0001\\0123456789ABCDEF serialnum:0123456789ABCDEF arbRuntimeKey:8 version:2], connected to [EHCI Port 1]

 

This is a "default" install, and the VM was created using the "USB 3.0" switch.

I have two completely different USB 3.0 drives, both report exactly the same, so not "drive specific".

 

Any comments / suggestions / help?

 

Further information available on request (i.e. a complete clean log file from start up, clean USB 2.0 usage, failed USB 3.0 usage).

 

JJ

0 bytes of system swap space is available

May 6, 2013, 11:42 am

Latest and popular articles on VMWare Virtualization

≫ Next: Error while powering on: Unable to open file that exists

≪ Previous: USB 3.0 ... Again ...

$

0

0

I just installed VMware Player and get this:

 

 

 

VMware Player recommends 512 MB of system swap space for the set of currently running virtual machines. 0 bytes of system swap space is available. For optimum performance increase the amount of system swap space, or configure all virtual machine memory to use reserved host RAM under Preferences.

 

 

 

I'm on Ubuntu 12.04 and Im sure I have GBs of space in Linux swap partition available. I'm not sure how do I fix this error message?

 

config file:

.encoding = "UTF-8"

NETWORKING = "yes"

VMBLOCK_CONFED = "yes"

gksu.rootMethod = "sudo"

libdir = "/usr/lib/vmware"

VMCI_CONFED = "yes"

VSOCK_CONFED = "yes"

initscriptdir = "/etc/init.d"

authd.fullpath = "/usr/sbin/vmware-authd"

bindir = "/usr/bin"

installerDefaults.componentDownloadEnabled = "yes"

installerDefaults.autoSoftwareUpdateEnabled.epoch = "6720694112"

vix.config.version = "1"

player.product.version = "5.0.2"

installerDefaults.dataCollectionEnabled.epoch = "6574561566"

installerDefaults.dataCollectionEnabled = "no"

installerDefaults.transferVersion = "1"

installerDefaults.autoSoftwareUpdateEnabled = "yes"

product.buildNumber = "1031769"

---

Error while powering on: Unable to open file that exists

May 6, 2013, 10:11 am

Latest and popular articles on VMWare Virtualization

≫ Next: Ongoing problem with VMware Player

≪ Previous: 0 bytes of system swap space is available

$

0

0

This weekend a partition containing my VMWare virtual machines was accidently deleted by Acronis backup software
I rebuilt the partition and re-assigned the same drive letter.
I then restored the "Virtual Machines" folder from my backup.
Now when I launch VMPlayer and start my virtual machine I get the following error:

Error while powering on: Unable to open file "H:\Virtual Machines\Windows\XP Professional\Windoes XP Professional.vmdk": The system cannot find the file specified.

Looking in the directory I find the file with the correct directory path and filename.
No attributes (hidden, readonly etc.) are on.
I am logged in as administrator.

Is there some other files/directories I should have also restored?
Suggestions?

Ongoing problem with VMware Player

May 6, 2013, 1:44 am

Latest and popular articles on VMWare Virtualization

≫ Next: Unity + Lync 2013 = lots of windows.

≪ Previous: Error while powering on: Unable to open file that exists

$

0

0

etsah57 wrote:

 

Sudo worked, opening VMware didn't

Terminal

etsah57@etsah57-KZ208AA-ABG-m9385a:~$ sudo su root

/sudo password for etsah57:

root@etsah57-KZ208AA-ABG-m9385a:/home/etsah57# sh VMware-Player-e.x.p-5.0.2-1031769.i386.bundle

sh: 0: Can't open VMware-Player-e.x.p-5.0.2-1031769.i386.bundle

root@etsah57-KZ208AA-ABG-m9385a:/home/etsah57# ^C

root@etsah57-KZ208AA-ABG-m9385a:/home/etsah57#

 

Things to consider:

 

Did you validate the MD5/SHA1 checksum for the downloaded file against its published values?

 

If the .bundle in not in the current directory show in Terminal you need to include the FQP.

 

In some cases if the file in in the current directory show in Terminal one may need to preface the .bundle file with./ and both the second and third points here are SOP with Linux/Unix OSes.  These are things any Linux/Unix User should know!

I use Ubuntu because I don't like microsoft. I have no knowledge of programming or computer language.

I went back to the download page: https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_player/5_0

 

and clicked on details. I noted that the file does end in .bundle, does not explain why mine downloaded as .txt

I also saw the checksums.

I went to my downloaded file and right clicked on it and went to properties. In the 'open with' tab it says 'Select an application to open VM....bundle and other files of type "shell script"

Default Application

gedit

Related Applications

notepad

I couldn't find anything to tell me about checksums

Unity + Lync 2013 = lots of windows.

May 7, 2013, 9:32 am

Latest and popular articles on VMWare Virtualization

≫ Next: Editing Nat and host-only settings (vmnetcfg.exe)

≪ Previous: Ongoing problem with VMware Player

$

0

0

Unity and LYNC 2013 don't seem to get along quite well.  When you open a chat window, 4 windows open along side it, if you open 2, you get 8 windows (they are all blank/no substance/nothing to maxamize).  Not sure if bug, or I'm doing something wrong. 

 

Any help would be great.

 

http://i.imgur.com/d539Nmf.png

 

v/r,

Zach

Editing Nat and host-only settings (vmnetcfg.exe)

May 7, 2013, 8:15 am

Latest and popular articles on VMWare Virtualization

≫ Next: Vmware Player has no 3d acceleration on Ubuntu 12.10 on ThinkVantage X60

≪ Previous: Unity + Lync 2013 = lots of windows.

$

0

0

Using VMware Player 5.0.2 I try to edit settings for Nat and host-only network connections.

In the past I used vmnetcfg.exe but it looks it'not available anymore.

What can I use to configure the network settings for either Nat and host-only network connections?

Regards

marius

Vmware Player has no 3d acceleration on Ubuntu 12.10 on ThinkVantage X60

May 7, 2013, 11:10 pm

Latest and popular articles on VMWare Virtualization

≫ Next: Virtual BIOS and boot order

≪ Previous: Editing Nat and host-only settings (vmnetcfg.exe)

$

0

0

I started years ago using wmplayer on my ubuntu partition while having wm workstation set on the windows partition.

After updating to ubuntu 10.x i noticed the message that 3d acceleration was not enabled and since then I never was able to get it working.

No matter what the guest os is, never 3d acceleration runs in ubuntu, while it runs on windows host and used to work in ubuntu too. I have now updated ubuntu to 12.10 and still get no acceleration.

 

So far I have figured out the problem residing in some misrecognized or unrecognized video chip ( INTEL 945GM/GMS and INTEL 943/940GMLExpress Integrated Graphic Controller Rev.3) in Ubuntu, but despite I found and applied me\any different corrections I still don't get the thing running.

I added all possible ram and a fast ssd to my old notebook and it is still ways much faster than any new Lenovo thing of the same class, thus I will not give it up until it falls apart.

Yet I need to have it supporting 3d acceleration on Ubuntu.

I'll be happy to share any information (i.e. how to make an old X60 run faster than new boxes), test results, findings with who wants to help me out with this issue.

Ciao,

Pietro

Virtual BIOS and boot order

May 8, 2013, 1:27 pm

Latest and popular articles on VMWare Virtualization

≫ Next: VMware Player 5.02 has problem with connection to USB 3.0 devices

≪ Previous: Vmware Player has no 3d acceleration on Ubuntu 12.10 on ThinkVantage X60

$

0

0

I recently decided to expand the virtual drive for a Linux VM running in VMPlayer in Windows 7.  The last step is to modify partitions using a 3rd party software: GParted.  In principle, GParted should be started from a live CD in the virtual machine (can't modify partitions in use).  To achieve this:

 

1) I set Player -> Manage -> VM Settings - > CD/DVD (IDE) to use file C:\Users\ .... \ gparted-live-.., .iso;

2) I have then shutdown and restarted using F2 to get to the Virtual BIOS;

3) In the virtual BIOS I set the boot order to CD first, then save and exit.

 

Unfortunately, the VM still boots up, apparently, from the HD in to Linux.  How do I get a VM to boot from the CD?  Tnx in advance for any assistance.

VMware Player 5.02 has problem with connection to USB 3.0 devices

May 9, 2013, 2:27 am

Latest and popular articles on VMWare Virtualization

≫ Next: VMWare Player Mouse does not snap to a menu

≪ Previous: Virtual BIOS and boot order

$

0

0

I use VMware Player 5.02 under windows 8 64 bit system to create a virtual system windows 8 32 bit. I can connect USB 2.0 devices in the host and guest systems and I can use USB 3.0 in the host system. But when I connected the USB 3.0 devices to the guest system, the following message appeared and after I press OK button, the windows 8 32 bit shut down at once.

"VMware Player unrecoverable error: (Worker#0)

 

Exception 0xc0000005 (access violation) has occurred.

 

A log file is available in "D:\Virtual Win 8\vmware.log".

 

You can request support.

 

To collect data to submit to VMware technical support, run "vm-support".

 

We will respond on the basis of your support entitlement."

 

the log files are zipped and enclosed in the attahment.

 

 

Could you tell me how to solve this problem?

---

VMWare Player Mouse does not snap to a menu

May 9, 2013, 1:30 pm

Latest and popular articles on VMWare Virtualization

≫ Next: Debian Wheezy - VMWare Player and Gnome3

≪ Previous: VMware Player 5.02 has problem with connection to USB 3.0 devices

$

0

0

I am using VMWare Player 5 and I open some software and it has drill down type menus.  If the menu option I need to click is at the bottom of the screen and the next menu I choose happens to be shorter and thus at the top of the screen the mouse stays at the bottom of the screen and does not snap to the menu at the top and if I move the mouse from the bottom of the screen to go to the menu at the top of the screen the menu disappears.  When on a physical machine the mouse will snap to the new menu regardless of where it is on the screen.  I have not seen any options or posts that will fix this.

 

Has anyone else experienced this behavior?

 

I have gone through a bunch of settings on the VM as well as the CentOS 5.9 machine to no avail. 

Debian Wheezy - VMWare Player and Gnome3

May 10, 2013, 5:56 am

Latest and popular articles on VMWare Virtualization

≫ Next: Downloading the latest VMwareTools for player and workstation

≪ Previous: VMWare Player Mouse does not snap to a menu

$

0

0

I have installed Debian Wheezy in VMWare Player 5.0.2 build-1031769 and all is fine. Except the "Failed to load Gome3" messages keep on coming. This is what I did so far:

 

• Installed VMWare Tools (some answers on the web claim that did does the trick. No luck so far here).
• Setting the accelerate 3D Graphics to true in the virtual machine (some answers on the web claim that did does the trick. No luck so far here).
• Install Whezy into Oracle VirtualBox (some answers on the web indicate that Virtualbox has sometimes better support . Allthough that may true, still no Gnome3, just the fallback).
• One site suggest I just have to make a ~/.config/autostart/gnome3-desktop file and restart the session (still no Gnome3).

 

The question is simple: Is there a way to make this working ? Other than waiting on Gnome3 support in VMWare Player.

 

(I asked this question also at superuser.com, but I recon this is a more appropriate place)

 

I think this is a more general question that has to do with 3d-hardware virtualization. I could have asked the same question for a modern Fedora, Ubuntu, or something like that.

Downloading the latest VMwareTools for player and workstation

May 10, 2013, 9:46 am

Latest and popular articles on VMWare Virtualization

≫ Next: 32 bit USB driver in VMware Player

≪ Previous: Debian Wheezy - VMWare Player and Gnome3

$

0

0

I work with VMware player and workstation on isolated environments.  Where can I download the latest versions of VMwareTools for player v4, v5 and workstation v8?

 

Thank you.

32 bit USB driver in VMware Player

May 11, 2013, 6:27 pm

Latest and popular articles on VMWare Virtualization

≫ Next: Cannot connect to Internet using NAT on Linux guest in VMPlayer

≪ Previous: Downloading the latest VMwareTools for player and workstation

$

0

0

I have  a USB Oscilloscope that does not have 64 bit drivers for Windoes 7. So I thought I would try a virtual machine. Should I be able to install the 32 bit version (which runs on XP) into VMware player? I can't get player to install the USB driver and recognize the device.

Thanks,

Brian

Cannot connect to Internet using NAT on Linux guest in VMPlayer

May 13, 2013, 6:24 am

Latest and popular articles on VMWare Virtualization

≫ Next: The operation is not supported for the specified parameters

≪ Previous: 32 bit USB driver in VMware Player

$

0

0

Hi,

 

I have a machine with vmware workstation 9.0.1 with a linux guest O/S and this works fine for connecting to the internet using NAT.

 

I am looking at VMPlayer also and the same linux build gives a host unreachable when I try to connect to the internet.

 

I have put the machines side by side and tried to mirro settings but still does not work. Is there any known issue with NAT on VMPlayer as there is no briged mode option?

 

Thanks Kate