Tutorials
This page will be a marker for some of the steps required to get certain projects going. Even though many of these will be assigned to specific virtual machines, wanted to have a page linked to all of them in one spot.
This page will be a marker for some of the steps required to get certain projects going. Even though many of these will be assigned to specific virtual machines, wanted to have a page linked to all of them in one spot.
Although VMWare is the most common that I have encountered, have also seen a spike in the usage of Red Hat’s KVM, as well as a slight increase in Microsoft’s Hyper-V hypervisors (which require a Windows Server 2012 install; there’s a 2008 version but still not a hundred percent that is free). In my current
One of the pitfalls with using Windows as a workstation (which I need to as my wife uses the same machine – we consolidated into one machine) is that you cannot run virt-manager to handle your virtual machines. Additionally, the ESXi VMWare client only runs natively on Windows, so you must have at least one
Wolverine is configured almost identically to Cyclops, the only difference is that it uses bonds (groups of NICs) to communicate instead of individual NICs. This is useful for both load balancing and redundancy. It has the following specs: Dell R510 Server 2 (Wolverine) Primary Purpose: Hypervisor CPU: Dual L5520 Xeon CPUs (quad core) RAM: 32GB DDR3
This page will be a moving target as we will be checking out new machines and technologies, and likely adding and deleting current virtual machines to keep up with current technologies. Below is a list of the virtual machines that I hope to create (each on their own page, with their own trials and tribulations).