Windows 10: VM - run on SSD or Spinner?
Thanks for your reply.
Could you please elaborate on why you think "management of VM's with Hyper-V is a pain "?
When one connects an external USB device to a VM, one only needs to disconnect from VM and then the device is re-connected to host. I've done this with external HDDs/Flash Drives etc. I didn't have to close down the VM for this.
Could you perhaps be talking about something else?
my experience has been similar to yours.
Thanks for your reply.
So, install VMWare Workstation on SSD, put VHD files on HDD? Or did I miss something?
Sure, my complaints are more related to the enterprise segment, as I use these products for a living professionally.
#1). Hyper-V is a Windows box, and thus needs frequent Windows patching and regular reboots. That's never ideal for a hypervisor
#2). With VMWare, you can install a simple client and connect from any machine with a username/password and it just works. On the other hand, under Hyper-V, remote connections and management can be difficult from a machine that is NOT on the domain.
#3). Built in monitoring is lackluster, without the use of 3rd party tools.
#4). only officially supports about 15 OS's, which are almost all just Windows.
#5). VMware offers fault tolerant VM's with up to 4 vCPU's, compared to no FT at all with Hyper-V
#5). VMWare offers hot-add hardware, Hyper-V does not
#6). High availability in VMware is a checkbox, and is reasonably complex to setup in Hyper-V.
Those are just a few things. For home users, not really major concerns. But since I use VMware at work, I use it at home too.
What I did was to install an SSD specifically for the running of VMs. I installed a 240 g SanDisk Ultra II 550 read and 500write, and this really makes a different when running VMs. . .
Put the VMs on the SSD if you have space. It will be much faster and you don't really need to worry about wearing out SSD. This was a worry 10 years ago.
There were a couple of comments about defining the actual disk as SSD to the guest. Hyper-V is a type 1 hypervisor so it isn't relevant but both VBox and VMware pass through disk access direct. You can (in both cases) indicate to the guest that it is SSD but it is pretty much pointless unless you are trying to test something in a VM that relies on an emulated SSD.
If you are short of space you can simply move the virtual disk back and forward to the fastest place when you want to use it.
I find that running compact /compactos:always in the guest makes my VM run quicker irrespective of hypervisor or storage medium.
If you don't change it much (or after an upgrade when you have deleted stuff) it is worth running in the guest
And then compact it.
defrag C: /h /x
defrag C: /h /o
sdelete C: /z
I can say for sure that in my case USB2 is the slowest, next slowest is SD card, then internal 7200, then SSD.
This is a bit like flogging a DEAD HORSE.
If you have something like Windows as a VM then it makes huge sense to have the OS on an SSD.
With Linux VM's it really doesn't matter (apart from initial time of loading the OS which usually is pretty fast anyway).
Most Linux systems unless you go mega bonkers and install about everything on the planet are small optimised OS'es and probably run quite nicely within your RAM space -- VM's tend to EAT RAM for breakfast so that's often a bit of a bottleneck.
Latest VMWARE workstation though manages Dynamic RAM so if you have VMware workstation the amount of RAM allocated to your VM isn't fixed as it used to be.
Managing DATA whether on HOST or VM is another thing entirely --data drives probably would be better on SSD's - especially if doing things like PHOTOHOP / video editing etc - but for multimedia and basic file serving decent spinners are OK.
Certainly if you are using a VM as a Network File server or as a multi media server you don't need the mega fastest I/O --your network is probably the bottleneck. I've found though for this type of data add them as RAW / Phystcal Disks so you can use the Native file systems on the GUEST OS.
Also if using Linux GUESTS use the SOFTWARE RAID (mdadm) which is in pretty well all Linux distros these days - and to READ / WRITE Windows NTFS files install package ntfs-3g.
For easy sharing also install SAMBA.
For Windows GUESTS also add RAW / Physical HDD's and use Storage spaces (sort of Windows software RAID).
For serious use of VM's really forget about Virtual Disks - that gives an extra lot of I/O overhead between HOST and VM. For simple testing scenarios - fine but if you are actually using VM's for serious work then use NATIVE / PHYSICAL / RAW HDD's - they can be offline to a Windows Host - no probs there.
My theory was that by telling Windows in the Guest that it's running on an SSD, it wouldn't try to defrag it in the same way as if the Guest thought it was running on a 'spinner'? I admit I don't really know how that aspect works though.
No. It doesn't work like that.
I'm in the process of downloading Win 10 latest ISO. Can it be installed on an eSATA spinner HD as standalone, or must it be installed over existing OS such as Vista, 7 or 8?