VMware Communities
s_bd
Contributor
Contributor

not accepting another drive

Hi, I'm relatively new to VMWare Workstation. I've downloaded VMWare Workstation 16 (free version) on my Windows 10 Pro OS to create  Linux VM CentOS8.

Problem is; VMWare Workstation is not accepting D:\Virtual Machines to install a virtual machine for CentOS8. There is enough space in D:\ drive. Instead it's accepting only C:\ drive (C:\Users\HP\Documents\Virtual Machines).

But my requirement is to install VMs on D:\ drive. I tried to copy Virtual Machines folder to D:\ but then also it didn't accept.

Error I'm getting is:

Unable to create a new virtual machine: Cannot open configuration file
"D:\Virtual Machine\CentOS 8 64-bit.vmx": Access is denied.

 Requesting help in this matter. Thanks in advance.

Reply
0 Kudos
4 Replies
RaSystemlord
Expert
Expert

There is no specific reason why you couldn't create a VM wherever you like. I use sometimes USB-3 disks exclusively. My first guess is that you just don't have proper user permissions on your directories and thus the files on d-drive.

However, for a fluent and no-hassle approach, I suggest the following workflow, which allows to see what really happens (if in case you didn't use it).

In step one, create the virtual machine first:

- create a directory somewhere to hold your VMs and your particular new VM, like "d:\VMs\Cent08_trial"

- create with enough disk space, not pre-allocated, in slices not with a single file (a longer story as such, why). Since you don't preallocate, you don't actually need to have that space ... you can move your VM later to another disk or another computer with different OS, which does have the space, if needed (this isn't the only benefit, just mentioning for clarity what is possible)

- select the correct OS when creating

In step two, open up the virtual machine settings and add and correct:

- take off hardware that does not make sense to have automatically connected (like usb, bluetooth), 3D acceleration (you can later adjust them back)

- make sure that RAM allocation is something meaningfull (and within your host capabilities)

- make sure that processor (core, thread) count is within your host capabilities

In step 3, install the OS:

- select virtual CD/DVD and attach the correct ISO

- check that it will power ON in reboot

- reboot and follow the OS related messages to install

 

When following this, it becomes more obvious that the matter of "CentOS" has no relevance in Steps 1 and 2, regarding your error message. Selecting correct OS is still important for step 3.

EDIT: OK, there is one, not so obvious reason, which may or may not bring that error message in Windows: Your d-drive is FAT (or FAT-32 whatever), and your single virtual disk files are over 4 GB (which can easily happen with 80 GB definition with slices).

Reply
0 Kudos
s_bd
Contributor
Contributor

Thank you for the reply RaSystemlord. D-drive is NTFS. Regarding space, both C and D drives have sufficient space.

But again i'm getting same error as mentioned in my first post.

Yes, it may be case of file or folder permission. I tried to compare  D-drive with C-drive,  but it looks same as C-drive.

Will try to see again what permission is not letting me to install VM on D-drive.

Reply
0 Kudos
RaSystemlord
Expert
Expert

OK, the permissions both on folder and files need to be write&read. Full doesn't make any difference.

Just try to create the folder of your own and a file of your own in that folder. That should be enough to check the permissions. VMware works on user permissions if you start it up normally. If you cannot create a file, that's the reason.

If D is a mapped folder from the network, then it is another ballgame.

Reply
0 Kudos
RaSystemlord
Expert
Expert

... actually, there is one more thing ...

The selecting of the virtual machine location has a bit of a confusing GUI. It is easy to misplace the VM somewhere, where you didn't intent to. I cannot explain it in precise terms, but I'm sure you can find that out when you just pay extra attention to the process of selecting the location. I mean, then you could get this error message if your location is somewhere else than you anticipate (for instance, not sure if the root of D is allowed - certainly that is very wrong for a location).

Reply
0 Kudos