Roger Osborne has posted a great article with a Windows Server 2012 Hyper-V best practices checklist.
I especially like the fact that it’s not just a checklist, but it also explains what it does and why it is considered a best practice to do it this way (in specific situations).
Additionally you might also want to take a look at “Top 20 Hyper-V Performance Metrics You Should Care About” and System Center Advisor.
Like this:
Like Loading...
Tags: best practice, best practices, best practices checklist, check list, checklist, Hyper-V, Hyper-V 3.0, hypervisor, hypervizor, ICT, Microsoft, Server 2012, virtualisation, virtualization, Windows 2012, Windows 2012 Server, Windows Server 2012
In yesterday’s post I described that for my purposes it was still necessary to run VMware Workstation sometimes despite having Client Hyper-V installed on my Windows 8 machine.
What you have to keep in mind though, is that you’re already running a hypervisor when you have Client Hyper-V installed in Windows 8. Installing and running VMware Workstation might cause problems. So unfortunately you cannot run them at the same time. This is also true for other virtualization products like by example virtualbox.
As a workaround you can either uninstall or (temporarily) disable Hyper-V. When you want to switch between Hyper-V and VMware Workstation it is ofcourse best to just temporarily disable Hyper-V.
In this forum post, a couple of methods are described to (temporarily) disable Hyper-V. It includes creating a seperate boot menu entry to boot with Hyper-V disabled and modifying the setting either through registry or a command. All methods do require a reboot however.
PS:
- This kind of configuration is ofcourse not supported and should only be used for testing purposes in non production environments.
- Depending on both your hardware and what your planning to do, you might also want to consider:
- Running VMware ESXi from a USB stick
- Running Windows 8 from a USB stick with Windows To Go (WTG).
- It should also work on Hyper-V in Windows Server 2008 and up, but I haven’t tested it.
Like this:
Like Loading...
Tags: Citrix, Citrix XenServer, Client Hyper-V, ESXi, home lab, Hyper-V, Hyper-V 3.0, hypervisor, Microsoft, multiple hypervisors, nested esxi, nested hypervisor, Server 2012, test lab, virtualbox, virtualization, VMware, VMware ESXi, VMware ESXi 5.1, VMware Fusion, VMware vSphere, VMware vSphere 5.1, VMware Workstation, VMware Workstation 9, Windows, Windows 2012 Server, Windows 8, Windows Server 2012, Windows To Go, workstation, WTG, XenServer
As a passionate ICT person, I work with multiple virtualization products including Microsoft Hyper-V and VMware vSphere.
At home I’m running Server 2012 with Hyper-V in my home lab and even though it works perfectly, I miss the option to be able to run multiple other hypervisors beneath it like by example multiple Hyper-V, VMware ESXi or Citrix XenServer instances.
With VMware products like VMware Fusion, VMware Workstation you can enable this with only a couple of minor adjustments as described in these great articles:
For me personally, I’ll stay with my Hyper-V based home server and my Windows 8 Client with Client Hyper-V installed. For testing purposes however, I’ll have to use VMware Workstation 9 on my Windows 8 machine. (even though I have Client Hyper-V installed). This way I can still run other hypervisors when needed.
I still hope though that Microsoft will add a similar feature to Hyper-V in the future.
Like this:
Like Loading...
Tags: Citrix, Citrix XenServer, Client Hyper-V, ESXi, home lab, Hyper-V, Hyper-V 3.0, hypervisor, Microsoft, multiple hypervisors, nested esxi, nested hypervisor, Server 2012, test lab, virtualization, VMware, VMware ESXi, VMware ESXi 5.1, VMware Fusion, VMware vSphere, VMware vSphere 5.1, VMware Workstation, VMware Workstation 9, Windows, Windows 2012 Server, Windows 8, Windows Server 2012, workstation, XenServer
In the first part of this LAB setup guide, I described the hardware selection process. In this second part I will be describing the hypervisor selection and installation.
Hypervisor selection
First of all, you have to decide on which bare metal hypervisor(s) you wish to use. Personally I prefer Microsoft Hyper-V and VMWare ESXi. Alternatives include but are not limited to Citrix XenServer, Xen, KVM, Red Hat Enterprise Virtualization. I don’t have much experience with these hypervisors though.
Characteristics that could influence your choice of hypervisor:
- Supported hardware.
- Performance of the hypervisor.
- Features of the hypervisor. By example when using Transparent Memory Page Sharing, it requires less memory when you run many highly identical systems on a host.
- Footprint / attack surface.
- Supported methods for running the OS. By example run from USB stick.
- Price (many hypervisors have free versions available, compare features).
- Support (for a home lab probably not that important).
- Available documentation / study resources.
- How active the community behind it is.
- Supported VM / guest operating systems.
- Ease-of-use.
- Availabilty of downloadable virtual appliances (VMWare) or pre-prepped environments (Microsoft) without having to (try and) convert them.
Everyone needs to determine which hypervisor best meets their needs. Personally I mainly work with Microsoft software and decided to use Hyper-V 3.0 in Windows Server 2012. It’s convenient for me to be able to easily load pre-prepped environments that are provided by Microsoft (in Hyper-V format). I also run Client Hyper-V on my Windows 8 laptop, which makes it easier for me to take my VM’s with me. I do plan to keep up with VMWare developments as well though, so I will create a bootable USB flash drive to boot in VMWare from time to time.
Hypervisor installation
- Before installing the hypervisor, make sure that virtualization related settings are enabled. The names of these settings may differ. Examples are Intel VT (Virtualization Technology), AMD-V and Hardware DEP (Data Execution Prevention), EM64T, Execute Disable Bit. During installation you will get prompted normally though if you have forgotten to enable these.
- There are often many options with regards to the installation. By example do a GUI install or a scripted/CLI install. Or install/run from normal harddisk or flash drive. With Server 2012 Hyper-V you can choose to run it in Windows Server 2012 core or in the GUI version. I chose to use the Server 2012 GUI Hyper-V installation because I’m not sure if my raid management software will work from within the core version.
- Installation of the hypervisor is normally pretty straight forward. But before you install, read the documentation.
- After you’re done installing, you still need to configure the settings to meet your requirements. Preferrably you’ve already created and documented your own design.
- Don’t forget to configure hardware monitoring if possible. In my case I’ve configured my raid controller management software to send e-mails when storage related issues are detected.
- Think about and implement a strategy for backing up and recovering your hypervisor. There are numerous programs for backing up and most are free for personal use. I have no personal experience with specific products, but VeeAm has a good reputation and I’ll be trying if for my lab. Also if you’re a Microsoft Certified Professional, you can get a free NFR license for Veeam Backup & Replication v6.5 for Hyper-V. The same is true if you’re a VMWare Certified Professional (VCP).
In the next post I will describe the VM guest preparations, installations and storage strategy.
Like this:
Like Loading...
Tags: Citrix, Citrix XenServer, ESXi, ESXi 5.1, guest, Hyper-V, Hyper-V 3.0, hypervisor, ICT, KVM, lab, Red Hat Enterprise Virtualization, RHEV, virtualization, VM, VMware ESXi, Windows Server 2012, Xen, XenServer
Since I’m currently working with System Center Operations Manager 2012 (also often referred to as SCOM 2012 or OpsMgr 2012), I needed a testing environment.
Because time is precious, I want to minimize the time and effort needed to set it up. This is what I did:
- Install and configure Hyper-V on my Windows 8 laptop.
- Deploy a VM with Server 2012 Datacenter edition.
Configure a static IP address.
Configure AD DS / domain controller role.
Configure DHCP server role.
Configure DNS server role (if desirable, include DNS forwarder for internet DNS queries).
- Download and extract the pre-configured SCOM 2012 SP1 beta VHD (running Server 2012 Datacenter edition). System Center 2012 SP1 adds Windows Server 2012 SQL Server 2012 Support.
- Create a new VM for SCOM and configure it to use the downloaded pre-configured VHD.
Configure it with sufficient virtual CPUs and memory for the DB and the SCOM components.
- Start the SCOM VM, and follow the onscreen instructions. NOTE: First time configuration took about 1-2 hours, but this might be related to my hardware. Still it might be smart to plan the installation.
- Convert the Server 2012 Datacenter edition from ServerDatacenterEval to ServerDatacenter by running an elevated CMD as administrator and issuing the following command:
DISM /online /Set-Edition:ServerDatacenter> ProductKey:<productkey> /AcceptEula
Reboot.
- Replace the SCOM 2012 evaluation license with your own license using Operations Manager Shell:
Set-SCOMLicense -ProductId “yourlicensekey“
Reboot
Check the license using the Operations Manager Shell:
Get-SCOMManagementGroup | ft skuforlicense, version, timeofexpiration –a
- Shut down your SCOM 2012 VM.
- Shut down your AD DS / domain controller VM.
- Create a snapshot and/or export of both VM’s so you can more easily revert to a good starting point.
Also be sure to read Stefan Stranger’s blog post that goes into more detail with regards to the domain controller and automating the task for setting it up. It also includes screenshots to give you a better idea of the process.
PS: I love how Microsoft provides these pre-configured VHD’s. This has been great in the past, but now with client Hyper-V 3.0 in Windows 8 it saves me even more time because I don’t have to boot to Windows Server 2008 or Windows Server 2012 for Hyper-V.
Like this:
Like Loading...
Tags: Beta, blog, Hyper-V, Hyper-V 3.0, ICT, lab, Microsoft, Microsoft System Center Operations Manager 2012, operations management, operations manager, Operations Manager 2012, OpsMgr, OpsMgr 2012, OpsMgr2012, SCOM, SCOM 2012, SCOM 2012 SP1, SCOM 2012 SP1 Beta, SCOM2012, Server 2012, service pack 1, SP1, System Center, System Center Operations Manager, System Center Operations Manager 2012, test, testing environment, virtual lab
blog.bjornhouben.com 