Vmware fusion 4 needs vitalization technology enabled

I need to install windows server 2008 because i need it for school, it installs with no problems in vmware, but when I try to enable hyper-v role it said that i need to have vt enabled. I tried the refit firmware, but when it starts i can't find the console to enable vt. what can i do?

What you are trying to do is enable virtualization in a virtual machine. You lose the VT capability in a virtual machine because vmware fusion is using it for your virtual machines. It's possible to do nested virtual machines in certain scenerio's, but not for hyper-v I am afraid.

Similar Messages

I have a 160GB Hard Drive in my MBP and use VMWare Fusion and had a 60GB Virtual Machine running Windows XP. Deleted the Virtual Machine and CANNOT find the 60GB space I desperately need! Anybody out there with a similar problem? Help!

I have a 160GB Hard Drive in my MBP and use VMWare Fusion and had a 60GB Virtual Machine running Windows XP. Deleted the Virtual Machine and CANNOT find the 60GB space I desperately need! Anybody out there with a similar problem? Help!

Thanks - Of Course the first thing I checked and did.
Disc Utility reads as follows:
Capacity : 159.18 GB (159,182,127,104 Bytes)
Format : Mac OS Extended (Journaled) Available : 11.47 GB (11,472,896,000 Bytes)
Owners Enabled : Yes Used : 147.71 GB (147,709,231,104 Bytes)
Number of Folders : 139,540 Number of Files : 511,832
Activity Monitor(Disc Usage) shows something quite interesting. Mac HD and Ramanan (Main User) - My hard drive is only 160GB! Would the retired engineer gentleman please note as well. Many thanks. Rams

Opinions needed on VMware Fusion or Windows programs on Mac

I am new to the Mac Family. My son is going to college this fall for Computer Animation, so I thought I would treat him and the family to a new computer system. After much research, the Mac Pro was the computer to get. I have a lot of software and downloads that are still PC. I was told that VMware Fusion is a good support system for Windows on Macs. Has anyone used this product and has anyone used it with Windows Vista?
P.S. I got my Pro Mac with 3.00 GHZ Dual Core, 4 GB Memory, and 500 GB Serial ATA 3Gb/s hard drive.
P.S.S. If I go with a conversion system (VMware Fusion), do I need a good anti-virus program (Norton/McAfee, etc.), or does that conflict with Leopard os X?

Windows on Intel Macs
There are presently several alternatives for running Windows on Intel Macs.
1. Install the Apple Boot Camp software. Purchase Windows XP w/Service Pak 2 or Vista. Follow instructions in the Boot Camp documentation on installation of Boot Camp, creating Driver CD, and installing Windows. Boot Camp enables you to boot the computer into OS X or Windows.
2. Parallels Desktop for Mac and Windows XP, Vista Business, or Vista Ultimate. Parallels is software virtualization that enables running Windows concurrently with OS X.
3. VM Fusionand Windows XP, Vista Business, or Vista Ultimate. VM Fusion is software virtualization that enables running Windows concurrently with OS X.
4. CrossOver which enables running many Windows applications without having to install Windows. The Windows applications can run concurrently with OS X.
Note that Parallels and VM Fusion can also run other operating systems such as Linux, Unix, OS/2, Solaris, etc. There are performance differences between dual-boot systems and virtualization. The latter tend to be a little slower (not much) and do not provide the video performance of the dual-boot system.
If you install Vista you must use Vista Business or Ultimate with the virtual machine software. You will need Windows anti-virus software. It isn't required for OS X.

Need Help Cloning Old Windows XP to Mac with VMWare Fusion

Hello I'm new to the forums and I have been searching all over for a good answer on how to do this.
I have a ton of applications, docs, etc. on my old windows xp machine that I need and I am looking for a way to clone the drive it to my mac that is using VMWare Fusion. I have an external hard drive and have tried acronis true image but apparently that doesnt work. So I am looking for a good step by step process on how to do this.
Also later I want to clone the same windows xp drive to another mac that is using boot camp. will that be the same?
Thanks

The easiest way would be to put the PC hard drive into an external enclosure and use Disk Utility or a similar tool to create a disk image file that you can copy to the Mac. You may be able to read the PC disk image format and get VMWare to read the resulting image.
Even if you make it that far, I don't think you will be able to get Windows to use it as a boot drive. You will have much more success just creating a new disk image and reinstalling everything with the correct drivers. Then just copy your documents back over using more traditional methods.

I'm running VMWare Fusion, and will need to install MS Project. Do I need Microsoft Office as well to run MS Project?

I'm running VMWare Fusion, and will need to install MS Project. Do I also need to install Microsoft Office to run MS Project? I already have MS Project for MAC.

Microsoft Office is typically a separate product from Project. You should not have to install Office to get Project.

I have installed VMware Fusion but having trouble with Calyx Point software and was told Bootcamp needed to be installed. Will I not have to uninstall Calyx, VMWare and Windows 7 prior to installing Bootcamp?

I have just bought a new MacBook Pro and I really like it. However, for my job I have to use Calyx Point software which has to be ran on the Windows side, so they sold me VMware Fusion software. It works fine until I try to save a PDF or email docs. I have called Calyx and they have advised me that bootcamp works. I am wondering if this is going to help and since I have already installed VMware am I not going to have to uninstall that program, Windows and Point and then install bootcamp and reinstall Windows and Point? If I'm beating my head against the wall, and just need to return the laptop, then that's what I will do, but I sure hate to as I really like my Mac.

Checked VMware Fusion Community Forum?
Most install Windows (natively) and then 'attach' the (Boot Camp) partition to Fusion.
that way you can dual boot and run Windows natively when needed, and run Windows as a Guest OS VM under Mac OS.
But.... and I don't know about Calyx, doing things like save pdf and email should work fine same as usual.
Maybe there is something you didn't or need to do to Fusion (Tools or install Acrobat) or in configuring.
I used Fusion but found I prefered running Windows natively at the time.
If you do need to use one install in both manners, then you need to do through and partition your drive and reinstall Windows that way, and only then attach Fusion to it.
If you need to run Windows for work, I'd exchange it - especially if you have only had it a couple days, and get another. There are a lot of new laptops coming out in the next months that look nice, fast and won't have some of the issues you run into with Windows on a Mac.

If i buy VMware fusion or Parallels desktop, i need a version of windows?

do i need windows with parallels or VMware?
a lot of thanks

nicholasfromcorreggio wrote:
do i need windows with parallels or VMware?
a lot of thanks
You don't need Windows if you want to run a different OS as your "guest". You can download many different flavors of Linux for free, and most of them will run in Parallels or VMWare Fusion... If you want to run Windows though, you will need a copy of that OS to install in the virtual machine of your choice...

Which version of windows 7 is needed for vmware fusion 5 - 32 or 64 bit

I just downloaded VMWare Fusion 5 and am in the process of getting Windows 7 from the Microsoft Store. Which version of windows is needed to run properly on my Mac - 32-bit or 64-bit? I believe it's the .iso application too, right?
Thanks!

vegasgator wrote:
here are my specs:
i've got a 2.3 GHz i7, 8GB RAM
I only plan on running 3 Windows programs thru Fusion and Internet Explorer some. i think i want to save as much capacity or power for my Mac so would 32-bit be better or does that not make a difference?
Thanks again
32 or 64 makes little difference, and when you are not running Windows (Fusion) your Mac has all the power it had before you installed Windows.

Need to repair disk frequently, only happens after running VMWare Fusion, though

I have to repair my disk by booting with command-R at least twice a week. The disk gets corrupted and peformance goes down the toilet.
I have finally isolated that it happens only after I am have run VMWare Fusion 3.1.3. Whether I leave it open or suspend the VM doesn't matter. Of course the solution from VMWare was "pay for an upgrade to Vmware 4", but that is not in the cards for me.
Anyone have similar issues or problems.
Model Name:          MacBook
Model Identifier:          MacBook6,1
Processor Name:          Intel Core 2 Duo
Processor Speed:          2.26 GHz
Number of Processors:          1
Total Number of Cores:          2
L2 Cache:          3 MB
Memory:          4 GB
Bus Speed:          1.07 GHz
Boot ROM Version:          MB61.00C8.B00
SMC Version (system):          1.51f53
Serial Number (system):          W89433W88PX
Hardware UUID:          8DB112AF-8BE0-5614-A976-77A0D903A028
Sudden Motion Sensor:
State:          Enabled

Tony Politano wrote:
Sorry, I should have been clearer on the VMware response. 3.1.3 is the lowest version they run on Lion and should work (minus the bells and whistles of 4), but I think he was just trying to upsell me 4.
Unfortunately, no. While the initial response from VMware was the release of the 3.1.3 update, it was quickly determined from all the reports that people were still experiencing issues with 3.1.3 on Lion. (I suspect it became more prevelant after the 10.7.1 and 10.7.2 updates. For the record, I did not have an issue with 3.1.3 on Lion, but I upgraded to Fusion4 before 10.7.1 came out.) While not everyone experienced an issue with 3.1.3 on Lion, there were enough reports coming in that VMware has pretty much stopped saying 3.1.3 is ok on Lion. But old webpages with outdated info still live on in Google, etc.
On a brighter note, VMware dropped the price of Fusion. Fusion3 was $70 when it was initially released. Fusion4 is $50. So from that point of view, VMware is give you $20 off.

VMWare Fusion VT support

When I try to boot Windows XP in VMware I get this error:
"VMWare Fusion has detected that your host system contains a mix of processors with incompatible VT feature sets.
Click Cancel to abort or OK to continue without using VT."
VMWare runs a heck of a lot faster on my MBP than on my 3GHZ 8-core Mac Pro. And that's just wrong!
I suspect that because VT is not enabled its falling back to software virtualization which is a lot slower.
Does anyone know a way to enable this? I tried various workarounds like sleeping the machine and then trying again already without luck
thanks
-hex.

We've had other threads asking about VT, which is appropriate to this forum.
I see you already asked Fusion Community, and didn't get any response that helped.
I only used 64-bit Vista, even in Fusion, sorry.
I had better luck looking up "Intel VT" in Google and Wiki.
http://www.intel.com/technology/virtualization/
http://communities.intel.com/openport/blogs/server/2008/09/22/3d-graphics-in-vir tualization-using-intel-vtd-on-workstations
I recall some Mac Pro owners running Vista natively, and running Guest VMs in Vista which was interesting.

VMware Fusion question - Multiple Monitors

I apologize if this is in the wrong area, but I am desperate for some help. I have also posted this same question in the VMware communities but I have not had any luck with anyone responding yet.
It seems that I am having an issue with my virtual machine (windows XP) viewing in full screen or unity across my multiple monitor setup on my Mac Pro. Every time I go to view in full screen or unity I get a VMware popup warning/error that reads:
The virtual machine "Windows XP Professional" is configured for a smaller display size than the one your Mac is currently using. VMware Fusion needs to shut down your virtual machine to enable support for your Mac's display size in Full Screen. Do you want to shut down this virtual machine now?
I have two options, one to shut down, or one to go into full screen. If I go into full screen, full screen works with the correct resolution and everything looks great except its only in the one monitor (not the multiple monitor). If I shut down and restart the virtual machine and try to go to full screen I get the same error.
The VMware tools have been installed and I did go to the view, use all displays in full screen opiton.
My current setup is a mac pro with 3 monitors using 2 NVIDIA GeForce 8800 GT Video Cards.
Any help would be greatly appreciated!
Thanks

I found a link to a VMWare Knowledge Base entry about specifying video ram in Fusion 1. Maybe it is still true.
http://kb.vmware.com/selfservice/search.do?cmd=displayKC&docType=kc&externalId=1 001876&sliceId=1&docTypeID=DTKB_11&dialogID=16580386&stateId=1%200%2016578530

Using VMWare Fusion for playing games

Hi all and I hope you can help.
I have a recent 17" MBP with 2GB of RAM and a Core 2 Duo and I am trying to get some decent game software running on it. To do this I have installed VMWare Fusion, XP Pro and Crysis.
My problem is, I can get the game to run but it is VERY choppy and unplayable.
I have tried various virtual settings, including using 1 and 2 processors, 512mb to 1.5gb RAM but never getting it to run properly.
I am not trying to run it full screen or anywhere near high settings and have allowed the game to scan the hardware to find it's optimal settings and still no luck.
I know Crysis is quite a heavy load but with the hardware in an MBP it should be able to run it without many problems.
Am I being too optimistic trying to run Crysis or are there a set of parameters that are optimised for doing this?

VMWare will also allow you to virtualize a boot camp partition.
The problem with virtualization and gaming is that, while you get direct CPU access and protected memory access, you do not get video access - so there is absolutely no video acceleration, it's all emulated or translated by the virtualizer.
You'll see a very minor CPU hit on anything that just using processor power or takes a lot of data (so long as you have enough physical RAM, and have enough RAM allocated to the virtual machine, to prevent disk swapping), but anything that needs video acceleration will suffer tremendously if it's virtualized.
In general, anything more than Solitare or Minesweeper, and you will want to use Bootcamp if there is no Mac OS X native version of the game (hooray for Blizzard, and all you other mac-native developers). I know the latest versions of VMWare and Parrallels all say they have new DirectX support, and Crossover has a version out just for gaming, but you'll disappoint yourself if you think these will do much more than just show the splash screen and a slide show for most games.
The good news is more game companies are starting to take Mac OS X seriously, and technologies such as Cider are helping developers port their code easier. But it's a long road, and the Macintosh has notoriously been spotty for gaming.

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)

Installing OS X 10.5 or lower on VMware Fusion running 10.6.1 Snow Leopard?

+hello, i am new to this forum technology so please be nice+
*alright, so i am running OS X 10.6.1 Snow Leopard and i am trying to figure out how to install an OS that is 10.5 or lower on VMware Fusion on the snow leopard that im running, so i can run older programs and games and such. so how would i go by doing this?*
*Thanks in advanced for the help!*

Sheepshaver's legality is questionable, because it requires extracting ROM from an older Mac. You are much more likely to get something that works, and is legal, if you buy a used or refurbished Mac that meets your needs*:
http://www.macmaps.com/usedrefurbished.html
- * Links to my pages may give me compensation.

VMWare Fusion, Boot Camp, and Orb

I'm trying to use Orb to stream audio files (podcasts downloaded daily within iTunes to be exact) to a Blackberry. Orb is currently only Win compatible (meaning the streaming can only be done from a Win computer), so I've got VMWare Fusion loaded on the Mac running Windows XP via a Boot Camp partition (I think I've described this properly). In order to enable the XP side to access the podcast files, I've set up shared folders within VMWare Fusion, and then targeted those shared folders within Orb to be streamed.
The problem is that Orb is supposed to regularly rescan those folders looking for changes to the content (as in new podcasts), but this doesn't seem to be happening. And I'm wondering if anyone has idea as to why. Could it possibly be because I am doing Windows via a Boot Camp partition? I see within Fusion that I can't use mirrored folders in this setup (Windows in a Boot Camp partition...at least I think this is the case). Would that make a difference (mirrored folders vs. the basic shared folders approach)?
I know this is sort of in the weeds in a non-Mac product (Orb), but it will make my wife really happy on her two hours of daily commuting if she can access those podcasts without having to remember to attach the iPod to the computer every night, which this setup (if it works properly) should enable her to do. The Blackberry is always with her.
Thanks very much.

Yes, you need to make some changes, for some reason VMware still claims non or limited support for 64-bit but you can edit a file and work around the problem. When creating a fresh new Fusion environment for Vista.
http://communities.vmware.com/community/vmtn/desktop/fusion

Vmware fusion 4 needs vitalization technology enabled

Similar Messages

Maybe you are looking for