If we look at the way a virtual machine (and a physical machine, indirectly) runs, the most important resources are RAM and CPU. Disk storage is (sort of) secondary. The exception to this is streaming media or backup servers. Typically, performance difference is minimal.
Does Vmware have Microsoft Vista properties? You know, we’ll just chuck it in at the end and pray it works.
Templates and their usage are one of the big time savers in ESX. The ability to setup a “perfect” vritual machine and then deploy multiple copies of it allows us to minimise the risk of deployment errors. However, there are a few limits around what can be achieved.
Whilst researching some storage options for a client, I stumbled across this pretty useful information
There are a number of ways to upload and download files to and from the actual ESX server in my environment. The least favourite one I have would have to be browsing the datastore via VI Client!
This ISN’T something that occurs frequently, but it is something that I would want to test in HA (High Availabilty) before I went to production!
Vmware Convertor allows us to P2V (Physical to Virtual) migrations. That is, taking (potentially) a running machine on my network and importing it directly into my virtual infrastructure.
As we all know, it’s a 440BX based mother board being fed into our virtual machines. The advantage? It’s sooooooooo generic that every operation system should be able to recognise and use it.
Has that changed in vSphere (ESX 4)?
Vmware’s launch of their new operating system, vSphere (Vmware ESX 4!), is being lauded as the first “cloud operating system”.
Greetings, faithful reader,
This one is as much a reminder for me as it is one to you!