Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
?
Solved

Vmware Fusion 6 and Workstation 10 not playing nice

Posted on 2014-03-07
5
Medium Priority
?
361 Views
Last Modified: 2014-03-13
I am trying to do something that Vmware claims is supported but certainly does not seem like it is. Using vmware virtual machines under Fusion 6 and Workstation 10. If I create a VM in Fusion then try to open it in Workstation I will receive an error "the hard drive is too large over 2GB, or that the virtual machine is corrupted." What am I missing?
0
Comment
Question by:finkeltron
  • 3
  • 2
5 Comments
 
LVL 9

Expert Comment

by:bas2754
ID: 39913123
This seems to occur if you try to run a VM off of a FAT32 formatted disk.  Not sure if that applies in your case or not.  Only solution I have seen is to try to run the VM off of a disk formatted with HPFS (MacOS) or the NTFS (Windows).

Please confirm as to whether you are running the VM off of a FAT32 filesystem when using Workstation 10.
0
 

Author Comment

by:finkeltron
ID: 39913227
I'm storing the virtual machines on my Mac partition so that would HFS+.
I am using a bootcamp setup with Fusion installed on the Mac side of course and workstation on the Windows 7 side. I am using Macdrive utility to read/write to the HFS partition while running in windows 7.
0
 
LVL 9

Expert Comment

by:bas2754
ID: 39914193
Interesting.   I wonder if the utility interfacing with the HFS filesystem from Windows is what is causing the issue.  Do you have any way of copying the vm to an ntfs formatted drive or partition to test.  Even an external drive would work although it would be slow.
0
 

Author Comment

by:finkeltron
ID: 39927106
I contacted Medifour (Macdrive) and they said it is a problem with vmware in how it creates virtual disks. I can't really explain it but it does need to be on a NTFS volume. I tried using ExFat and that did work for running VM's in Mac and Windows. So I guess this is a solution but it means I have to partition out my boot volume which is not what I wanted to do. Was hoping to keep it HFS for everything on a single volume.
0
 
LVL 9

Accepted Solution

by:
bas2754 earned 1500 total points
ID: 39927432
Sorry to hear that there is not a workaround that is really a good solution for your situation.  I hope I was able to at least point in the right direction.
0

Featured Post

Put Machine Learning to Work--Protect Your Clients

Machine learning means Smarter Cybersecurity™ Solutions.
As technology continues to advance, managing and analyzing massive data sets just can’t be accomplished by humans alone. It requires huge amounts of memory and storage, as well as the high-speed power of the cloud.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

When converting a physical machine to a virtual machine using VMware vCenter Converter Standalone or vCenter Converter Enterprise, if an adapter type is not selected during the initial customization the resulting virtual machine may contain an IDE d…
In this article, I will show you HOW TO: Perform a Physical to Virtual (P2V) Conversion the easy way from a computer backup (image).
Teach the user how to use create log bundles for vCenter Server or ESXi hosts Open vSphere Web Client: Generate vCenter Server and ESXi host log bundle:  Open vCenter Server Appliance Web Management interface and generate log bundle: Open vCenter Se…
Teach the user how to join ESXi hosts to Active Directory domains Open vSphere Client: Join ESXi host to AD domain: Verify ESXi computer account in AD: Configure permissions for domain user in ESXi: Test domain user login to ESXi host:
Suggested Courses

578 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question