eWEEK Labs Tests Windows Server 2008 Virtualization

While the so-called community technology preview version of Microsofts new hypervisor rides with Windows Server 2008 RC0, the new Microsoft virtualization bits arent, strictly speaking, part of RC0. The upshot of this is that I had to install a couple o

After applying the requisite updates duo, Windows virtualization appeared alongside Windows Server 2008s other roles.

Viridians status as a Windows virtualization role earns the feature a spot in Windows Server Manager, where configuration and management options for the hypervisor sit alongside advice from Microsoft on the hows and whys of virtualization.

Administrators who are getting their feet wet with virtualization can take comfort in the fact that Windows typically handholding ways extend to Viridian.

I set about nesting a virtual Windows Server 2008 Core instance within the physical Server Id just installed.

Creating a new instance with Windows virtualization system is fairly simple, with plenty of installation source options. I stuck to the RC0 media still in the drive of my test system.

Windows waited until just before I launched my freshly minted virtual instance to tell me that its hypervisor wasnt running. Although Id previously used the same test machine to run a Windows instance from a XenEnterprise hypervisor, Windows wasnt happ

Fortunately, updating my BIOS was all it took to satisfy Viridian, and the installation of my virtual Windows Server instance was under way.

I also installed a Linux instance on Windows Viridian–I chose an rPath MediaWiki appliance for the test.

The rPath installers Linux kernel panicked shortly after boot.

I took the advice of Linux kernels error message, booted the installer with the flag noapic, and proceeded with the installation.

• eWEEK Labs Walk-Through of VMware Fusion
• Ten Things Holding Virtualization Back