Unable to launch VMware Fusion.

I used to using VMware with Bootcamp, but I deleted VMware and now use only Bootcamp. I've been encountering an issue on mac.
Every time I click on a website link, say in an e-mail, I get a message:
“Firefox-Boot Camp partition.
VMware Fusion failed to launch.
Unable to launch VMware Fusion"
Any solution?
Thanks,

Please post Fusion related questions on the Fusion forums as Apple discussions only provide support for Apple products:
http://communities.vmware.com/community/vmtn/desktop/fusion

Similar Messages

Issues launching VMWare Fusion 2.0 after Lion install?

Getting the message "VMware Fusion cannot connect to the virtual machine. Make sure you have rights to run the program and to access all directories it uses and right to access all directories for temporary files." Other than the Lion install, I have changed nothing on my system. Any suggestions?

Issue was resolved by upgrading to Fusion 3.1 from 2.1

Address Book – 'Call with Skype' launches VMWare Fusion

Clicking 'Call with Skype' against a number in Address Book launches Fusion and starts up XP. I had the Windows version of Skype installed in XP under Fusion but have removed it using the correct Add/Remove Software process. Clicking 'Call with Skype' once again starts the dialling from the Mac version of Skype. Weird and unwanted..... Any ideas to prevent this?

Not a problem afterall, as it turns out. Only shame on me for being a newb.
Though during my puzzle-solving process came across the skype-plugins for the AB. They are located in /library/Address Book Plug-Ins/ folder and are not automatically removed, when uninstalling Skype.
Names: SkypeABDialer.bundle and SkypeABSMS.bundle.

VMware Fusion suddenly hogging resources and fan running constantly

I have had my MacBook for about a year now and until 2 weeks ago had no problems with this issue before. Now suddenly, if I launch VMware Fusion (even not running any programs) the MacBook fan comes on and stays on. When I launch the Mac "Activity Monitor' App, sure enough VMware is hogging all the resources. I have added nothing to the XP side of things during this time. Any ideas on what might be happening as the constant fan 'on' issue is a pain and it FEELS like it's a drag on regular Mac performance. Thanks.

Is it possible that your Anti-Virus software (Not sure if you installed one) is performing a scheduled virus scan at bootup? Until that is finished, it will continue to attempt to start/finish the scan at boot up.
Just a thought.
Axel F.

10.6.4 complete system freeze when resuming from screensaver-VMWare Fusion

I have a Macbook Pro, 3,1. I just upgraded to 10.6.4 and noticed the following symptoms:
Shortly after launching VMWare Fusion 3.1 running a Windows XP VM (from a Bootcamp partition), a series of pop up messages were complaining about a bad OpenGL driver. The message popped up repeatedly and wouldn't let me out, even though I kept pressing "Ok". I had to force quit Fusion, which caused a chkdsk on relaunch of the XP VM.
After a complete reboot, I started VMWare again. The Fusion complaints haven't shown up again, but when resuming from the screensaver, the system either completely freezes up, or the screen login window starts to flash rapidly and seize up. I'm running Spaces with 6 virtual screens. Whether I'm in the Fusion Spaces screen or any other Spaces screen, the system freaks out when resuming from a screensaver.
I use this system at work, so I have to be able to lock my screen when I leave my cube. The only way I've been able to ensure the system doesn't freeze up and cause a hard reset of the XP VM is to completely disable the screensaver and power saver features, such as Start Screen Saver = Never, Computer Sleep = Never, Display Sleep = Never and launch the login window by clicking on my user name in the upper right corner of the screen on the menu bar. Even that causes a sluggish screen and I'm not confident it will keep working. I also made sure (from day one) that the Windows XP screensaver functions were all completely disabled. I prefer to use the OS X screensaver for everything, if for no other reason than having a single screen locking/unlocking point for when I step away.
This was all working properly in 10.6.3. The only nit-nat I noticed about Fusion in 10.6.3 was that it had to be launched in the "Primary Window", which seems to be the upper leftmost Spaces desktop. If I ever moved it to, or started in any other Spaces desktop, it would also exhibit the same random lockups. Keeping it in the "primary" space seems to have stopped the lockups.
I noticed that there seemed to be significant updates to the OpenGL drivers in 10.6.4. I am experiencing an unfortunate side effect of these updates and hope I'm not alone and that a fix is coming soon. Looking at the other posts, there seem to be a lot of similar problems. I wanted to describe my configuration in case the Apple dev team reads these posts. Thanks.

I ended up doing an erase and fresh install of Snow Leopard (10.6.0), upgraded to 10.6.4 with the combo update, then a fresh install of all my apps, including VMware 3.1. Everything has been solid for 2 days now. I'm guessing that my system had a magic combination of issues that weren't visible in 10.6.3 but became obvious only after upgrading to 10.6.4. I had been upgrading my OS since 10.5.0 over the last 2 years and needed to do a clean re-install for some time now.
I'm guessing that others who are noticing problems with the 10.6.4 update have a similar situation with their installations. Think back on all the times a software installation failed, or the system required a hard boot. Plus, I had a lot of 3rd party apps on my box that never posted updates for later Snow Leopard releases, so who knows? Anyway, it's good to have a clean and snappy system again. A lot of my apps launch a lot faster now and survive the screen saver and power saver modes just fine.
Message was edited by: mausoleum

Why single core only on a MBP13 Core i5 w/ VMware Fusion + Win7 BootCamp Partition

1. When I boot into OS X and launch VMware Fusion running Windows7 on a 2011 MacBook Pro 13" w/ Core i5:
I see only a single core in-use in the Windows 7 CPU performance widget running VMware Fusion using Windows 7 installed in BootCamp Partition?
2. When I boot directly into Windows 7 using the BootCamp Partition on the same MacBook Pro as above:
I see all four cores in-use in the Windows 7 CPU performance widget. Why doesn't VMware fusion use all four virtual cores that the MAcBook Pro 13" Core i5 provides? Core i5 has 2 physical cores but 4 hyper-threads which appear as 4 virtual cores to the OS as I understand it.
Is this expected behavior for this config? Why can't VMware Fusion on OS X see all four virtual cores? I see that the CPU submenu is greyed out under the VM Settings menu? So it appears CPU settings can't be changed for a running VM instance? Any suggestion and pointers would be greatly appreciated.
Thanks in advance!
Fuji Apple Pie

I think your i5 is 2-cores with 4-threads (the name virtual core for HT is just a way to get 20-35% more per physical core).
And one physical core has to be assigned to Mac.
If you had the i7 4-core / 8-threads, I can see more load balancing.
Comparison Fusion and Parallels

I no longer want to use vmware fusion to run my windows session, can I use boot camp to launch my vmware windows install or do I have to start again with a brand new installation?

Hi,
I would like to know if I'm able to use my current VMWare windows installation through Boot Camp, I don't want to use fusion anymore but I'm hoping there's a way to set up boot camp and not have to re-install windows again, if anyone could let me know that would be great

Thank you for your response GabeAlan, am i able to back up my virtual windows without access through VMware fusion? its locked me out since i upgraded to Yosemite, i prefer to see if i can avoid having to pay to upgrade to the latest fusion

Unable to launch Object Wizard from Agentry Connector Studio

I am running Eclipse Juno (64-bit) with the Agentry Editor installed. When I try to launch the Object Wizard in the Agentry Connector Studio nothing happens. No error message, but the wizard doesn't appear. I am using version 6.0.46.0 of the Agentry editor.
This problem was reported in this thread but no resolution was provided. I did try opening the database development perspective as Welly suggested but it made no difference.
Unable to launch Object Wizard from Agentry connector studio..
Anyone know why this would happen, or if there is a log that might contain an entry that would tell me what went wrong?
Update: I just tried it again after rebooting Windows and now the Object Wizard is grayed out when using the Database Development Perspective. If I switch to the Agentry(Properties) perspective it is not grayed out but still nothing happens when I select it.
Full disclosure: I am running Windows in VMWare Fusion on a Mac. I am seeing some strange behavior in general with Eclipse and I've reinstalled it a number of times without resolving the problem.
Thanks,
Dave

One of the applications I have issue issues if you export the application you will not be able to load it on any other editor except from the the editor running on the Fusion VM machine and the issue was also the server failed to load the application that was published from the editor.
I am just letting you know to look see if you also run into this issue and that was the reason why then had to run on a windows machine.
Stephen.

VMWare Fusion, Linksys CIT200 and a stubborn OSX

Hello,
I'm a switcher, with a lot of Windows dependencies (one less now that Picasa launched on OSX!) but to get rid of the two machine hassle I got VMWare Fusion and just moved the whole Windows PC into a virtual machine using the VMWare Converter. All fine, however I am very dependent on my Linksys CIT200 Skype Phone.
When connected it lights up, however it is not recognized by OS X, ie it will not turn up in the profiler. If it would, I could use it in VMWare. People with Linux have managed to get this phone working in virtual machines. Why on earth will OS X not see this device and what can I do so it would, so I can pass this USB device on to VMWare?
All help appreciated!

Thanks for your quick response, PAHU. However, I tried out your suggestion and, first of all, it wouldn't let me import the Virtual Machine which I had copied out to an external drive. The name of the file was just grayed out and it wouldn't let me click on it. Then I tried to create another Win 7 virtual machine and it came up with the same error messages as before. These messages, in sequence, are as follows:
"Unable to retrieve kernel zone sizes"
"Failed to initialize monitor device"
"Cannot find a valid peer process to connect to"
The same messages appeared when I tried to create a Win XP Professional virtual machine.
As I said in my previous message, this has only started happening after I upgraded Mac OSX to 10.7.4. It was working fine up to 10.7.3.

Mini displayport to vga limits second screen resolution in VMWare Fusion

I am using a Mini Displayport to VGA adapter which works fine in except when I use it with VMWare fusion. In VMWare I am unable to use the secondary display effectively. My screen does extend but I am unable to interact with anything on the second monitor.
help!

Hi m,
This sounds like it could be a Fusion issue. If you don't get help here, you may want to contact Fusion's tech support.

Vmware Fusion 3.0 and OSX 10.7.4

Vmware Fusion 3.0 was working fine until I upgraded to 10.7.4. After that it has stopped working and gives two or three errors about kernel space, etc and refuses to start.
A Windows 7 virtual machine was in a suspended state when I upgraded the OS. Was this a mistake and should I have completely quit Windows before updating? If so what is the way out now? Will it start working again if I delete the virtual machine and install Windows again?
Thanks in advance

Thanks for your quick response, PAHU. However, I tried out your suggestion and, first of all, it wouldn't let me import the Virtual Machine which I had copied out to an external drive. The name of the file was just grayed out and it wouldn't let me click on it. Then I tried to create another Win 7 virtual machine and it came up with the same error messages as before. These messages, in sequence, are as follows:
"Unable to retrieve kernel zone sizes"
"Failed to initialize monitor device"
"Cannot find a valid peer process to connect to"
The same messages appeared when I tried to create a Win XP Professional virtual machine.
As I said in my previous message, this has only started happening after I upgraded Mac OSX to 10.7.4. It was working fine up to 10.7.3.

Fix for BT headset nightmare in VMWare Fusion? (Macbook Leopard)

Appreciate any help after struggling for over a day trying to connect a top Bluetooth headset (Jawbone)...
Thanks,
Mark
Openworld.com
CASE:
2 GB Ram Macbook
Leopard OS
Fusion 1.0 running WinXP Service Pack 2
Jawbone Bluetooth Headset
Bluetooth headset works for sound input/output when paired and turned on -- in Leopard OS (only)
Bluetooth Enabler installer for Windows successfully installed (as prompted by VMWare) from the Leopard CD drivers folder
VMWare's Sound, USB Bluetooth menu items in Fusion confirm association with Leopard
VMWare window Bluetooth icon (at bottom) shows Bluetooth link to Leopard remains OK
PROBLEM
Bluetooth control panel (in Mac OS) disappears for the entire time that WinXP is launched in Fusion
In WinXP, sound input/output to Jawbone headset does not work, even though the sharing icon for Bluetooth at bottom of VMWare Fusion window remains active (showing blue rather than black)
On exiting WinXP, the missing Bluetooth control panel in Leopard system preference reappears -- but a working link in Leopard with Jawbone headset can only be restored after a Macbook retstart
FIXES TRIED WITH APPLECARE (all unsuccessful)
Removing Library preferences (main and user-specific) for bluetooth and restarting
Zapping the PRAM
Creating a new user with Admin privileges, and creating a new linke
Removing the battery
NEXT STEPS
Please suggest any troubleshooting ideas ... Applecare tech support reps' concluded (after 3+ hours on two calls) that this may be a a VMWare Fusion 1.0 bug

This is no Mac, Leopard or Headset issue - I experience the same on a MacMini DualCore, OS 10.4.11, VMWare Fusion 1.0 and Win2K.
Another guy was even less lucky:
http://communities.vmware.com/thread/104908
Let's ask VMware about it.

HTTP check RW-5001 - Oracle EBS 12.1.1 Rapidwiz on RHEL 5 VMWARE Fusion

Dear All,
I have been attempting to install Oracle EBS 12.1.1 Using Rapidwiz on RHEL 5 VMWARE Fusion for the past month, i have run through the install on a few occaisions now just to ensure that i have followed all the pre-reqs correctly and also set up the guest OS as described in several posts including (http://www.oraclenerd.com/2009/12/ebs-install-guide-part-1.html, http://gerardnico.com/wiki/ebs/installation and always refering back to My Oracle Support Doc ID 761566.1: Oracle Applications Installation and Upgrade Notes Release 12 (12.1.1) for Linux x86-64.
I have installed (prior to running rapidwiz) the oracle recommended patch p6078836_101330_LINUX.zip and confirmed from the install that the Database listener and Database are up and running (checked by running the db.env script and running addbctl.sh and addlnctl.sh respectively). However, the rapid install completes with an error for HTTP, java, Login Page, Help files, in the post intall checks.
The error displayed for the HTTP check RW-50015: Error: - HTTP Listener is not responding. The service might not have started on the port yet. Please check the service and use the retry button.
I've found posts relating to this message, and proceeded to check the status and try and start the apps services manually; however, i'm experiencing another error message;
You are running adopmnctl.sh version 120.6
Checking the status of opmn managed process...
Unable to connect to open
opmn may not be up.
Then i try and start the services manually after running the INST_computername.env scripts;
*[applvis@oracler12 scripts]$ ./adopmnctl.sh start*
You are running adopmnctl.sh version 120.6
Starting Oracle Process Manager (OPMN) ...
libopmnoraclenls.so: unable to load
*/d01/oracle/VIS/inst/apps/VIS_oracler12/ora/10.1.3/opmn/bin/opmnctl: line 898: 1228 Segmentation fault $OPMNADMIN ping*
libopmnoraclenls.so: unable to load
libopmnoraclenls.so: unable to load
*/d01/oracle/VIS/inst/apps/VIS_oracler12/ora/10.1.3/opmn/bin/opmnctl: line 898: 1234 Segmentation fault $OPMNADMIN pingwait*
opmnctl: opmn start failed.
adopmnctl.sh: exiting with status 0
adopmnctl.sh: check the logfile /d01/oracle/VIS/inst/apps/VIS_oracler12/logs/appl/admin/log/adopmnctl.txt for more information ...
I'm not a DBA and i'm just starting out to learn how ebusiness suite is installed and how the applications run in parralel to the database. (my history of oracle ebs front end development and functional support)
I know there are a few posts out there within these forums that go into some details on what this issue may be, however, i cannot find any that specifically address my type of install and OS setup, and sometimes find it hard to understand the terminology and techniques used to diagnose these kinds of issues.
What i'm looking for is for some help in diagnosing and trouble shooting my issue, i will be happy to provide any output that is required to help address the issue and will be online regularly until i can have this issue resolved.
So, if you can help, please let me know where we can start.
Many thanks
Simon

Hi All,
Problem solved, although not on RHEL 5. I started over with a clean install of OEL 5.4, completed all the pre-reqs and applied reccommended patching, install completed fine, not experienced same issues with http. Differing install steps;
A) Selected different Port pool - 67 instead of 55
B) in OEL 5 when installing, if gives you the option to turn off SELINUX, which i compelted.
C) Checking the OS, i noticed the rpm versions were quite different (probably somewhat obvious, but im not sure if this had an impact)
Although, this was a fristrating set up, i have (i think) learnt a bit more about linux and installing ebs.
Thanks all for your guidance and help
Simon

VMware Fusion 4 guest

Hello,
I've installed Arch in a VM running on VMware Fusion 4. Out of the box it doesn't fit the resolution to the window so if I go fullscreen it gets ugly. When I try to install vmware-tools I get an error:
[Fleet@mba vmware-tools-distrib]$ sudo ./vmware-install.pl
Creating a new VMware Tools installer database using the tar4 format.
Installing VMware Tools.
In which directory do you want to install the binary files?
[/usr/bin]
What is the directory that contains the init directories (rc0.d/ to
rc6.d/)? /etc/rc.d/vmware.d
What is the directory that contains the init scripts?
[/etc/rc.d/vmware.d] /etc/rc.d
In which directory do you want to install the daemon files?
[/usr/sbin]
In which directory do you want to install the library files?
[/usr/lib/vmware-tools]
In which directory do you want to install the documentation files?
[/usr/share/doc/vmware-tools]
The path "/usr/share/doc/vmware-tools" does not exist currently. This program
is going to create it, including needed parent directories. Is this what you
want? [yes]
The installation of VMware Tools 8.8.0 build-465068 for Linux completed
successfully. You can decide to remove this software from your system at any
time by invoking the following command: "/usr/bin/vmware-uninstall-tools.pl".
Before running VMware Tools for the first time, you need to configure it by
invoking the following command: "/usr/bin/vmware-config-tools.pl". Do you want
this program to invoke the command for you now? [yes]
Initializing...
Use of uninitialized value $subLevel in split at /usr/bin/vmware-config-tools.pl line 5324.
Use of uninitialized value $subLevel in concatenation (.) or string at /usr/bin/vmware-config-tools.pl line 5325.
Argument "0-ARCH" isn't numeric in multiplication (*) at /usr/bin/vmware-config-tools.pl line 4859.
Use of uninitialized value $subLevel in addition (+) at /usr/bin/vmware-config-tools.pl line 4859.
Making sure services for VMware Tools are stopped.
Stopping VMware Tools services in the virtual machine:
Guest operating system daemon: done
Virtual Printing daemon: done
Unmounting HGFS shares: done
Guest filesystem driver: done
/etc/rc.d/vmware-tools: line 1114: [: BASH=/bin/sh: integer expression expected
/etc/rc.d/vmware-tools: line 1114: [: BASH=/bin/sh: integer expression expected
/etc/rc.d/vmware-tools: line 1199: [: BASH=/bin/sh: integer expression expected
[EXPERIMENTAL] The VMware FileSystem Sync Driver (vmsync) is a new feature that
creates backups of virtual machines. Please refer to the VMware Knowledge Base
for more details on this capability. Do you wish to enable this feature?
[no]
Before you can compile modules, you need to have the following installed...
make
gcc
kernel headers of the running kernel
Searching for GCC...
Detected GCC binary at "/usr/bin/gcc".
The path "/usr/bin/gcc" appears to be a valid path to the gcc binary.
Would you like to change it? [no]
Searching for a valid kernel header path...
Detected the kernel headers at "/lib/modules/3.0-ARCH/build/include".
The path "/lib/modules/3.0-ARCH/build/include" appears to be a valid path to
the 3.0-ARCH kernel headers.
Would you like to change it? [no]
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmci-only'
make -C /lib/modules/3.0-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-3.0-ARCH'
CC [M] /tmp/vmware-root/modules/vmci-only/linux/driver.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciDatagram.o
CC [M] /tmp/vmware-root/modules/vmci-only/linux/vmciKernelIf.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciDriver.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciRoute.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciResource.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciHashtable.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciEvent.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciContext.o
CC [M] /tmp/vmware-root/modules/vmci-only/driverLog.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciQueuePair.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciQPair.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciDoorbell.o
LD [M] /tmp/vmware-root/modules/vmci-only/vmci.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-root/modules/vmci-only/vmci.mod.o
LD [M] /tmp/vmware-root/modules/vmci-only/vmci.ko
make[1]: Leaving directory `/usr/src/linux-3.0-ARCH'
make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmci-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmci-only'
cp -f vmci.ko ./../vmci.o
make: Leaving directory `/tmp/vmware-root/modules/vmci-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmci-only'
make -C /lib/modules/3.0-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-3.0-ARCH'
CC [M] /tmp/vmware-root/modules/vmci-only/linux/driver.o
CC [M] /tmp/vmware-root/modules/vmci-only/linux/vmciKernelIf.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciDatagram.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciDriver.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciRoute.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciResource.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciContext.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciHashtable.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciEvent.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciQPair.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciQueuePair.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciDoorbell.o
CC [M] /tmp/vmware-root/modules/vmci-only/driverLog.o
LD [M] /tmp/vmware-root/modules/vmci-only/vmci.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-root/modules/vmci-only/vmci.mod.o
LD [M] /tmp/vmware-root/modules/vmci-only/vmci.ko
make[1]: Leaving directory `/usr/src/linux-3.0-ARCH'
make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmci-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmci-only'
cp -f vmci.ko ./../vmci.o
make: Leaving directory `/tmp/vmware-root/modules/vmci-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vsock-only'
make -C /lib/modules/3.0-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-3.0-ARCH'
CC [M] /tmp/vmware-root/modules/vsock-only/linux/af_vsock.o
CC [M] /tmp/vmware-root/modules/vsock-only/linux/vsockAddr.o
CC [M] /tmp/vmware-root/modules/vsock-only/linux/util.o
CC [M] /tmp/vmware-root/modules/vsock-only/linux/notifyQState.o
CC [M] /tmp/vmware-root/modules/vsock-only/driverLog.o
CC [M] /tmp/vmware-root/modules/vsock-only/linux/stats.o
CC [M] /tmp/vmware-root/modules/vsock-only/linux/notify.o
LD [M] /tmp/vmware-root/modules/vsock-only/vsock.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-root/modules/vsock-only/vsock.mod.o
LD [M] /tmp/vmware-root/modules/vsock-only/vsock.ko
make[1]: Leaving directory `/usr/src/linux-3.0-ARCH'
make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vsock-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vsock-only'
cp -f vsock.ko ./../vsock.o
make: Leaving directory `/tmp/vmware-root/modules/vsock-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmxnet3-only'
make -C /lib/modules/3.0-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-3.0-ARCH'
CC [M] /tmp/vmware-root/modules/vmxnet3-only/vmxnet3_shm.o
CC [M] /tmp/vmware-root/modules/vmxnet3-only/vmxnet3_ethtool.o
CC [M] /tmp/vmware-root/modules/vmxnet3-only/vmxnet3_drv.o
LD [M] /tmp/vmware-root/modules/vmxnet3-only/vmxnet3.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-root/modules/vmxnet3-only/vmxnet3.mod.o
LD [M] /tmp/vmware-root/modules/vmxnet3-only/vmxnet3.ko
make[1]: Leaving directory `/usr/src/linux-3.0-ARCH'
make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmxnet3-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmxnet3-only'
cp -f vmxnet3.ko ./../vmxnet3.o
make: Leaving directory `/tmp/vmware-root/modules/vmxnet3-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/pvscsi-only'
make -C /lib/modules/3.0-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-3.0-ARCH'
CC [M] /tmp/vmware-root/modules/pvscsi-only/pvscsi.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-root/modules/pvscsi-only/pvscsi.mod.o
LD [M] /tmp/vmware-root/modules/pvscsi-only/pvscsi.ko
make[1]: Leaving directory `/usr/src/linux-3.0-ARCH'
make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/pvscsi-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/pvscsi-only'
cp -f pvscsi.ko ./../pvscsi.o
make: Leaving directory `/tmp/vmware-root/modules/pvscsi-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmmemctl-only'
make -C /lib/modules/3.0-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-3.0-ARCH'
CC [M] /tmp/vmware-root/modules/vmmemctl-only/backdoorGcc64.o
CC [M] /tmp/vmware-root/modules/vmmemctl-only/os.o
CC [M] /tmp/vmware-root/modules/vmmemctl-only/vmballoon.o
LD [M] /tmp/vmware-root/modules/vmmemctl-only/vmmemctl.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-root/modules/vmmemctl-only/vmmemctl.mod.o
LD [M] /tmp/vmware-root/modules/vmmemctl-only/vmmemctl.ko
make[1]: Leaving directory `/usr/src/linux-3.0-ARCH'
make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmmemctl-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmmemctl-only'
cp -f vmmemctl.ko ./../vmmemctl.o
make: Leaving directory `/tmp/vmware-root/modules/vmmemctl-only'
The VMware Host-Guest Filesystem allows for shared folders between the host OS
and the guest OS in a Fusion or Workstation virtual environment. Do you wish
to enable this feature? [yes]
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmci-only'
make -C /lib/modules/3.0-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-3.0-ARCH'
CC [M] /tmp/vmware-root/modules/vmci-only/linux/driver.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciDatagram.o
CC [M] /tmp/vmware-root/modules/vmci-only/linux/vmciKernelIf.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciContext.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciDriver.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciDoorbell.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciHashtable.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciResource.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciRoute.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciQueuePair.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciEvent.o
CC [M] /tmp/vmware-root/modules/vmci-only/driverLog.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciQPair.o
LD [M] /tmp/vmware-root/modules/vmci-only/vmci.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-root/modules/vmci-only/vmci.mod.o
LD [M] /tmp/vmware-root/modules/vmci-only/vmci.ko
make[1]: Leaving directory `/usr/src/linux-3.0-ARCH'
make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmci-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmci-only'
cp -f vmci.ko ./../vmci.o
make: Leaving directory `/tmp/vmware-root/modules/vmci-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmhgfs-only'
make -C /lib/modules/3.0-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-3.0-ARCH'
CC [M] /tmp/vmware-root/modules/vmhgfs-only/message.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/cpName.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/rpcout.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/link.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/filesystem.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/dentry.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/module.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/file.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/stubs.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/request.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/hgfsUtil.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/tcp.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/backdoor.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/vmci.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/transport.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/bdhandler.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/page.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/cpNameLinux.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/dir.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/super.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/fsutil.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/hgfsBd.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/backdoorGcc64.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/hgfsEscape.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/inode.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/cpNameLite.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/kernelStubsLinux.o
LD [M] /tmp/vmware-root/modules/vmhgfs-only/vmhgfs.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-root/modules/vmhgfs-only/vmhgfs.mod.o
LD [M] /tmp/vmware-root/modules/vmhgfs-only/vmhgfs.ko
make[1]: Leaving directory `/usr/src/linux-3.0-ARCH'
make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmhgfs-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmhgfs-only'
cp -f vmhgfs.ko ./../vmhgfs.o
make: Leaving directory `/tmp/vmware-root/modules/vmhgfs-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmxnet-only'
make -C /lib/modules/3.0-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-3.0-ARCH'
CC [M] /tmp/vmware-root/modules/vmxnet-only/vmxnet.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-root/modules/vmxnet-only/vmxnet.mod.o
LD [M] /tmp/vmware-root/modules/vmxnet-only/vmxnet.ko
make[1]: Leaving directory `/usr/src/linux-3.0-ARCH'
make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmxnet-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmxnet-only'
cp -f vmxnet.ko ./../vmxnet.o
make: Leaving directory `/tmp/vmware-root/modules/vmxnet-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmblock-only'
make -C /lib/modules/3.0-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-3.0-ARCH'
CC [M] /tmp/vmware-root/modules/vmblock-only/linux/stubs.o
CC [M] /tmp/vmware-root/modules/vmblock-only/linux/dbllnklst.o
CC [M] /tmp/vmware-root/modules/vmblock-only/linux/file.o
CC [M] /tmp/vmware-root/modules/vmblock-only/linux/block.o
CC [M] /tmp/vmware-root/modules/vmblock-only/linux/module.o
CC [M] /tmp/vmware-root/modules/vmblock-only/linux/super.o
CC [M] /tmp/vmware-root/modules/vmblock-only/linux/inode.o
CC [M] /tmp/vmware-root/modules/vmblock-only/linux/control.o
CC [M] /tmp/vmware-root/modules/vmblock-only/linux/filesystem.o
CC [M] /tmp/vmware-root/modules/vmblock-only/linux/dentry.o
LD [M] /tmp/vmware-root/modules/vmblock-only/vmblock.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-root/modules/vmblock-only/vmblock.mod.o
LD [M] /tmp/vmware-root/modules/vmblock-only/vmblock.ko
make[1]: Leaving directory `/usr/src/linux-3.0-ARCH'
make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmblock-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmblock-only'
cp -f vmblock.ko ./../vmblock.o
make: Leaving directory `/tmp/vmware-root/modules/vmblock-only'
!!! [EXPERIMENTAL] !!!
VMware automatic kernel modules enables automatic building and installation of
VMware kernel modules at boot they are not already present. By selecting yes,
you will be enabling this experimental feature. You can always disable this
feature by re-running vmware-config-tools.pl.
Would you like to enable VMware automatic kernel modules?
[no]
Detected X server version 1.10.4
Distribution provided drivers for Xorg X server are used.
Skipping X configuration because X drivers are not included.
Warning: This script could not find mkinitrd or update-initramfs and cannot
remake the initrd file!
Starting VMware Tools services in the virtual machine:
Switching to guest configuration: done
Paravirtual SCSI module: done
Guest memory manager: done
/etc/rc.d/vmware-tools: line 1114: [: BASH=/bin/sh: integer expression expected
VM communication interface: failed
VM communication interface socket family: failed
/etc/rc.d/vmware-tools: line 1114: [: BASH=/bin/sh: integer expression expected
Blocking file system: done
VMware User Agent: done
/etc/rc.d/vmware-tools: line 1199: [: BASH=/bin/sh: integer expression expected
Guest operating system daemon: done
Virtual Printing daemon: done
Unable to start services for VMware Tools
Execution aborted.
I can't figure out what to do different. Do you have any suggestions? I have also tried open-vm-tools but resolution auto switch and the other functionality didn't seem to work for me.
Last edited by Fleet (2011-09-25 15:48:14)

I am evaluating Virtualbox as an alternative but Arch performes sluggish in VB though it allows me to run fullscreen with native resolution (1440x900).
Last edited by Fleet (2011-10-14 19:56:06)

Mouse problems with v10.7 Lion and VMWare Fusion 3.1.3; reboot of Lion temporarily fixes it

Since installing Lion, my VMWare Fusion 3.1.3 Windows 7 and XP virtual machines have very strange mouse problems. I thought it might have been caused by 3rd party software on my iMac (Mouse Zoom), because it seemed to work after removing the software, but I have now discovered that it is actually the reboot of OS X v10.7 (and now v10.7.1) that temporarity removes the problem. However, after a while the problem comes back, requiring another reboot of Lion.
The problem is strange behavior of mouse button clicks inside the virtual machine, e.g. unable to double click on a folder or program in Windows because it jumps back to the higher folder tree, as if I had hit the ESC key. In addition to my USB and BlueTooth mice, the Mac touchpad also has the problem. I have confirmed that the problem is probably in how VMWare maps the iMac human interface devices (HIDs) to the virtual mouse inside the VM, because I am able to get correct mouse function by attaching one of my mice directly to the Virtual Machine (there is an edit to the VMX file that enables HID devices).
I have deleted and reinstalled VMWare Fusion 3.1.3 per suggestions on the VMWare support site and/or various forums, but that did not help.

According to: http://roaringapps.com/app:61 Version 3.1.3 has issues with Lion. There is a 2011 beta that works better.

Unable to launch VMware Fusion.

Similar Messages

Maybe you are looking for