When selecting you hardware, there are many factors to consider; How many Virtual Machines do you want to run at a time? How busy will these Virtual Machines be? If you are getting ready to P2V a bunch of virtual machines, then you should use Perfmon (In a Windows Environment) to take a benchmark before proceeding. In this article, I am not going to focus on sizing your environment, but rather making sure that the hardware you select is going to be compatible with what you want to do. **Note, Read more […]Read More
Portability of Software is the ability to run the same software on a number of different systems. One of the goals of many software developers are to be able to write the application once, and run it on as many platforms as possible. A similar goal of Systems administrators is to ensure you can run software with as few conflicts as possible Typically when one thinks of portability of software in the context of virtualization, two things come to mind, Published Applications and Application Virtualization. Read more […]
Spectre (CVE-2017-5753 and CVE-2017-5715) and Meltdown (CVE-2017-5754) are exploits in CPU architecture allowing attakers access to protected memory they should not have access to. Spectre effects all CPU vendors, while Meltdown is specific to Intel chips. More details below.Lucky for you, there are patches available to remediate or workaround the issue. The downside is there is up to a 30% performance reduction in CPU performance after installing these patches. Older intel CPU’s will be harder Read more […]
Ensuring your Puppet Agent is installed on all machines in your environment can be a challenging task. Today I will share a tip on how you can ensure that the puppet agent us automatically deployed to all of your new virtual machines. Explanation When you deploy a VMWare template, you have the option to create a customization specification. You can add a command to this customization specification to automatically deploy the puppet agent, after the template has finished deploying. One of Read more […]
Sometimes virtual machines within your VMWare environment may show up as invalid. The machine is in-fact still running at this point; but you are unable to manage the virtual machine. This can happen for a few reasons, but in my experience the most common is when the esx host is unable to access the storage.
I have seen this caused by high latency when accessing an NFS datastore, when you leave an offline datastore mounted for an extended period, and I have also seen this happen when a SAN controller failover event occurs.
This condition happens when the esx host cannot access the vmx file (vmware configuration file) in the datastore, so VMWare just sort of forgets the configuration of the machine. The process which runs the virtual machine is still running on the host, so your VM does not crash. But, you still need to recover since HA, DRS, etc… no longer work when the VM is in this state.