Partager via

Installing "Viridian" CTP on Windows Server 2008 RC0

  • Article

So, it appears that the RC0 bits for Windows Server 2008 have been posted to the intarwebs.  As I said in a previous post, the CTP release of the "Viridian" virtualization technology is included in this release of Windows Server.

Ben Armstrong has some good reminders for anyone who wants to try this out, so I would very much recommend that you go check his post before you proceed with the installation.

Things to keep in mind:

  • This is a preview release - the performance of this build is not anywhere close to what it will be at the RTM release of Windows Server virtualization.  
  • Installing the CTP of "Viridian" will prevent you from upgrading to a newer build of Windows.  If you install "Viridian" CTP, there is no upgrade path - you must either clean install your server, or uninstall the "Viridian" CTP before you upgrade to a newer Windows build.
  • "Viridian" requires you have a processor that has Hardware-assisted Virtualization (Intel VT or AMD Pacifica) present and enabled in the BIOS. On AMD machines we require that the processor stepping be >=F3 (or that F2 processors have BIOS support).  To determine what revision your processor is, check out the utility from www.cpuid.com.
  • You also need to have NX (also known as XD for eXecute Disable) turned on in the BIOS. 
  • "Viridian" is only available on x64 versions of Windows Server 2008. 

So, now that we've got all that out of the way, here's how you install it.

  1. Install Windows Server 2008 RC0 Full (I have no idea what we're calling the non-Server Core version, so I refer to it as "Full").
  2. In Explorer, navigate to %SystemRoot%\WSV.  You should find two MSU files.
  3. Double-click on Windows6.0-KB939854-X64.MSU.  This will install the Windows Server virtualization Management Tools in the Administrative Tools program group.
  4. Double-click on Windows6.0-KB939853-X64.MSU.  This will stage Windows Server virtualization for installation on your server, and allow it to show up in the Role Management Tool.
  5. Reboot the server.
  6. If it's not already open, click the Server Manager icon from the Quick Launch bar. 
  7. The Roles Summary section should tell you how many Roles you have installed and how many Roles are available for installation. 
    If you have 17 Roles available, press the F5 key to refresh the list.  If you have 18, click Add Roles.
  8. From the list of available Roles, put a checkmark in the box that corresponds to Windows Server virtualization, and click Next.
  9. From here, the Role wizard should guide you through the rest of the process, and reboot your server when necessary.

Comments

  • Anonymous
    September 24, 2007
    PingBack from http://www.artofbam.com/wordpress/?p=2651

  • Anonymous
    September 24, 2007
    Windows Server 2008 Release Candidate 0 was officially announced today and will be available for everyone

  • Anonymous
    September 25, 2007
    Welcome back everybody. I hope that you found yesterday’s post on how to install the “Viridian” CTP to

  • Anonymous
    September 26, 2007
    thanks for the info.  BTW, it is called the "Full" installation in the install choice window.

  • Anonymous
    September 26, 2007
    Earlier this week, I posted instructions on how to install the "Viridian" CTP on Windows Server 2008

  • Anonymous
    October 02, 2007
    I thought Viridian was a bare-metal solution or will run alongside a lite version of Windows Server.  Why is it that a "Full" install of Windows Server 2008 is required?  Will this change with the final product?

  • Anonymous
    October 02, 2007
    Hi Roy - "Viridian" is a Role in Windows Server 2008, similar to IIS or Active Directory.  For the current CTP, "Viridian" only installs on the Full edition of Windows Server.  We will be supporting installation on Server Core as well as Server Full later in the release cycle.

  • Anonymous
    October 04, 2007
    Jag har installerat Windows Server 2008 RC0 och Viridian på 192.168.0.100 Den är installerad på den locala

  • Anonymous
    October 07, 2007
    Roy, Viridian is not really a bare metal solution like the main competition. Windows Server is still wrapped around it. All I/O goes through drivers in Windows Server. Thus the virtualization engine does not have its own drivers. The advantage is that Windows drivers can be used. The disadvantage is that the kernel is rather large compared to the main competition. Which is better? You be the judge. Certainly Viridian is force to be reckoned with.

  • Anonymous
    October 07, 2007
    If like me you have tried to install the WSV CTP on an Acer Ferrari 1000 or 5000, both sport an AMD Turion 64 X2 processor, you have probably encountered a problem starting a virtual machine after a successful installation of WSV...

  • Anonymous
    October 10, 2007
    Can you expand on the AMD F2 stepping issue? I'm at a loss of how to frame a request to the machine manufacturer for a BIOS upgrade without being able to explain the issue.

  • Anonymous
    October 10, 2007
    Janique - Unfortunately, no.  The BIOS update contains some updates for hardware virtualization, so it's required for F2 processors.  Processors with an F3 or greater revision already have the necessary updates.  Sorry I can't provide a greater amount of information.

  • Anonymous
    October 12, 2007
    We are trying to install Viridian on new AMD Barcelona NPT machine and we got error "hypervisor is not running". This processor is with F2 and updated to the latest BIOS driver. Does anybody know whether one can run Viridian on new AMD Barcelona NPT machines?

  • Anonymous
    October 19, 2007
    The comment has been removed

  • Anonymous
    October 19, 2007
    Virtual Dev - I don't have the answers to your questions right now - let me do some research and I'll post the answers when I can.