So I finally got my hands on a sweet HP rig (ProLiant BL460c Gen8) with Windows Server 2012 R2 installed. Yeah, it’s got 32 processor cores with Hyperthreading, 128 GB of RAM, and 3 TB of SAN storage over a fiber network…no biggie.
You might wonder why I’m not simply using Red Hat Enterprise Linux 7 and the KVM Virtualization Platform, since I intend to virtualize a number of Red Hat Enterprise Linux (5.10, 6.5, 7) operating systems, and the answer is that Hyper-V is the hypervisor of choice for my organization, so this is what I have been directed to use (I did initially propose the use of a RHEL system with KVM). Fortunately for all of us, I am no dogmatist when it comes to information technology. Prior to 2013, my experience is almost entirely with Microsoft systems (I’m an Microsoft Certified IT Professional Enterprise Administrator on Windows Server 2008, Enterprise Messaging Administrator on Exchange 2010, and Enterprise Support Technician on Windows Vista). It was only in late 2013 that I began working with Red Hat Enterprise Linux professionally.
Anyway, this should provide a great new frontier of material for the blog. It wasn’t long before I encountered my first issue. I decided to build my first guest domain with RHEL 6.5. I obtained the ISO from Red Hat, and I built a basic Generation 2 VM. I (mis)read the Microsoft guidelines at http://technet.microsoft.com/en-us/library/dn531026.aspx and did not notice that RHEL 7 is the only version of Red Hat Enterprise Linux (and therefore, CentOS, Scientific Linux, and any other RHEL derivatives) which supports Generation 2 virtual machines, and then only if Secure Boot is disabled.
So, without properly understanding the lack of support for Generation 2 virtual machines in Hyper-V, I was immediately faced with some error text following the splash message indicating that the system will boot into RHEL 6.5 in 3..2..1…:
“Trying to allocate 1005 pages for VMLINUZ”
When I Googled that message looking for some assistance, I saw plenty of people complaining about the same message with CentOS 6.5, many of whom indicated in the complaint that they were attempting to deploy Generation 2 VMs, but I didn’t see a single response pointing out that CentOS versions below 7 do not function in Generation 2 VMs.
So I thought I’d point that out, if anyone’s still troubled by this.