Andy's VMware vSphere tip#4: Partitions :- OS Partitions have no place in VMware vSphere or Hyper-V. So do not create a C: Partition or volume, and D: Partition or volume on the same virtual disk. We used partitions in the dark old ages of DOS, when the limits of a partition were 32MB, so we had to create multiple partitions on our disks, to use all the disk space.

Keep a single partition per virtual disk. e.g. create a single virtual disk for C:, if you need a D; create another virtual disk.

You will thank me in the future, because it becomes much easier to expand C: and D:, if they are on separate virtual disks. You've also got the benefit of being able to specify which datastore, these will be hosted on which is important if you have tiered storage for performance.

So in Summary do not create partitions, C: D: E: F: on the same virtual disk, you will regret it, later and then you will have to use VMware Converter, to convert your machine and remedy the situation.

https://www.experts-exchange.com/articles/31526/HOW-TO-P2V-V2V-for-FREE-VMware-vCenter-Converter-Standalone-6-2.html

Please feel free to post a question to the VMware or Virtualization topic areas to discuss this further.
1
LVL 114

Expert Comment

by:John
You wrote "So do not create a C: Partition or volume, and D: Partition or volume on the same virtual disk. We used partitions in the dark old ages of DOS,"

Absolutely!   Same goes for dual boot.

Next year (as I recall) BIOS goes away as well.  

Good to see the old stuff die a natural death.
0
LVL 133

Author Comment

by:Andrew Hancock (VMware vExpert / EE Fellow)
It may go away on new machines, but still will be with us a long time to come...

EE questions still being asked about Windows 2000 and Windows 2003
0
LVL 114

Expert Comment

by:John
Yes, older machines will have BIOS, but new ones just UEFI and Windows 10  (or Server 2016 and beyond)

Still, we are on the same page :)
0

Keep in touch with Experts Exchange

Tech news and trends delivered to your inbox every month