Get your free NFR license for Veeam Backup & Replication v6 for Hyper-V

http://platform.twitter.com/widgets/hub.1326407570.html

Veeam is offering an NFR license for MVP/MCP/MCTS:

http://www.veeam.com/nfr/free-nfr-license-hyper-v

Get your free NFR license for
Veeam Backup & Replication v6 for Hyper-V

If you are a Microsoft Certified Professional (MCP), Microsoft Certified Technology Specialist (MCTS) or a Most Valuable Professional (MVP), you can get a FREE 2-socket NFR* license for Veeam Backup & Replication v6 for your home or work lab.

Register NOW! Get your FREE NFR license from Veeam

*An NFR (Not for Resale) license can only be used for evaluation or demonstration purposes. Read EULA for more details.

 

 

Hyper-V as a vSphere VM/Nested x64 OSes on VMWare ESXi/Workstation 8

I’ve been playing around with the new vSphere 5 Hypervisor (ESXi5) lately and I came across a few cool tricks from virtuallyghetto (http://www.virtuallyghetto.com/2011/07/how-to-enable-support-for-nested-64bit.html):  running x64 VMs on ESXi5 while itself is a VM under Workstation 8 and running VMs under Hyper-V server under ESXi.

Running a Hyper-V VM while Hyper-V is itself a VM under ESXi5 does work, it’s not really something you’d want to do, unless you’re masochistic.  I was able to get Windows 2000 Pro running walking as a VM successfully.  The stability of ESXi seems to be greatly affected by doing this also, since my ESXi host hung at some point overnight.

VMWare vSphere Hypervisor 5

I was excited to try out the new free version of ESXi 5 today on a test system with a Core 2 Quad Q6600. 

I received an ominous message that “VMWare ESXi 5.0 installs on most systems but only systems on VMWare’s compatibility Guide are supported.”  I didn’t think much of it until I got to the next stage of the install and got this message:

“Error(s) <CPU_CORES ERROR: This host has [1] cpu core(s) which is less than recommended [2] cpu cores>”

“(F9) Back                (F11) Reboot”

Game over?  Not quite.  I found a post http://communities.vmware.com/message/1082035#1082035 with an almost identical hardware config referring to the same issue for ESX 3. 

Disable MAX CPUid in the BIOS, installation completed.