Archive

Archive for the ‘Virtualization’ Category

Free eBook:Understanding Microsoft Virtualization Solutions — From the Desktop to the Datacenter

September 28, 2010 Leave a comment

Learn about the benefits of the latest virtualization technologies and how to plan, implement, and manage virtual infrastructure solutions based on these technologies.

Free eBook:Understanding Microsoft Virtualization Solutions — From the Desktop to the Datacenter

Virtualization: Top 10 Virtualization Best Practices

September 28, 2010 Leave a comment

Source:TechNet Magazine  , by Wes Miller *

Virtualization has gone from being a test lab technology to a mainstream component in datacenters and virtual desktop infrastructures. Along the way, virtualization has occasionally received a “get out of jail free” card, and has not had the same degree of efficient IT practices applied to virtual deployments as would be expected of actual physical machines. This is a mistake.

If you had an unlimited budget, would you let everyone in your organization order a new system or two and hook it up to the network? Probably not. When virtualization first appeared on the scene, unlimited and unmanaged proliferation was kept in check by the fact that there was actually a cost associated with hypervisor applications. This provided some line of defense against rogue virtual machines in your infrastructure. That is no longer the case.

There are several free hypervisor technologies available, for both Type 1 and Type 2 hypervisors. Anyone in your organization with Windows installation media and a little free time can put up a new system on your network. When virtual machines are deployed without the right team members knowing about it, that means a new system can become an unwelcome honeypot for new zero-day vulnerabilities, ready to take down other systems on your network that are business critical.

Virtual systems should never be underappreciated or taken for granted. Virtual infrastructures need to have the same best practices applied as actual physical systems. Here, we will discuss 10 key best practices that should always be on your mind when working with virtual systems.

To read to full article go to http://technet.microsoft.com/en-au/magazine/gg131921.aspx

*Wes Miller is the director of Product Management at CoreTrace (CoreTrace.com) in Austin, Texas. Previously, he worked at Winternals Software and as a program manager at Microsoft. Miller can be reached at wm@getwired.com.

New version of the Linux Integration Services for Hyper-V

September 27, 2010 1 comment
 

A new version (2.1) of the Linux Integration Services for Hyper-V have just been made available.

This new version has some significant improvements:  

  • Driver support for synthetic devices: Linux Integration Services supports the synthetic network controller and the synthetic storage controller that were developed specifically for Hyper-V.
  • Fastpath Boot Support for Hyper-V: Boot devices take advantage of the block Virtualization Service Client (VSC) to provide enhanced performance.
  • Timesync: The clock inside the virtual machine will remain synchronized with the clock on the host.
  • Integrated Shutdown: Virtual machines running Linux can be gracefully shut down from either Hyper-V Manager or System Center Virtual Machine Manager.
  • Symmetric Multi-Processing (SMP) Support: Supported Linux distributions can use up to 4 virtual processors (VP) per virtual machine.
  • Heartbeat: Allows the host to detect whether the guest is running and responsive. 
  • Pluggable Time Source: A pluggable clock source module is included to provide a more accurate time source to the guest. 

This version of the integration services for Hyper-V supports Novell SUSE Linux Enterprise Server 10 SP3, SUSE Linux Enterprise Server 11, and Red Hat Enterprise Linux 5.2 / 5.3 / 5.4 / 5.5.

 

 

DPM Roadmap for Hyper-V Protection

September 21, 2010 Leave a comment

 

image

Categories: Virtualization

Windows 7 XP Mode : hotfix if your computer does not have hardware-assisted virtualization

September 20, 2010 Leave a comment
 
 
If you receive the message “This computer does not have hardware-assisted virtualization,” your computer does not meet the hardware requirement for Windows Virtual PC, but you can still use Windows 7 XP Mode by running this hotfix.
 
Be aware that XP Mode will run much better if hardware-assisted virtualization can be enabled.
 
If you receive the message “Hardware-assisted virtualization is not enabled on this computer,” turn on hardware virtualization in your PC BIOS
 

If you receive the message “This computer is configured with hardware-assisted virtualization,”  download and install Windows Virtual PC and Windows XP Mode.

Does my DELL support hardware virtualization, and is the BIOS setting turned on?

September 20, 2010 Leave a comment
 
Turn on your DELL and :
 
  • Press the F12 key when boot menu text appears at startup
  • Select BIOS setup and press the Enter key
  • Using the mouse, expand the Virtualization Support menu item by clicking on the plus to the left of Virtualisation Support and
  • Select Virtualisation
  • Check the Enable Intel Virtualisation Technology checkbox
  • Click Apply
  • Click Exit
  • Fully shut down (power off), wait a few seconds, and restart your computer ( IMPORTANT!!!!)
Please note that if you could not find the Virtualization Support menu, either your machine does not support Hardware Virtualization or the BIOS is not updated. Go to http://www.dell.com.au and under Drivers and Downloads, using your machine service tag, check if you have the latest Bios version. Be carefull when updating your machine BIOS.

How To register the Hyper-V VSS writer with Windows Server Backup

September 18, 2010 Leave a comment
This is well documented, but as some folks are asking about this, lets post :
 
  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate the following registry key:
    HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersion
  3. Right-click CurrentVersion, point to New, and then click Key.
  4. Type WindowsServerBackup, and then press ENTER.
  5. Right-click WindowsServerBackup, point to New, and then click Key.
  6. Type Application Support, and then press ENTER.
  7. Right-click Application Support, point to New, and then click Key.
  8. Type {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}, and then press ENTER.
  9. Right-click {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}, point to New, and then click String Value.
  10. Type Application Identifier, and then press ENTER.
  11. Right-click Application Identifier, and then click Modify.
  12. In the Value data box, type Hyper-V, and then click OK

This will enable back up Hyper-V virtual machines from the parent partition on a Windows Server 2008-based computer by using Windows Server Backup.

Categories: Virtualization

Hyper-V : How to Handle Dynamic Memory using script

September 17, 2010 Leave a comment

 

With the availability of dynamic memory in Windows Server 2008 R2 SP1 there are some changes to how you need to handle memory as a scripter / developer. 

The WMI API changes are now documented here http://msdn.microsoft.com/en-us/library/cc136856(VS.85).aspx

Take a look at Ben Armstrong, Virtualization Program Manager( Virtual PC Guy) blog:
 
Categories: Virtualization

Duplicate virtual machines (VMs) may appear in the SCVMM Administrator Console window after a Hyper-V VM in a cluster fails over to another cluster node. HotFix KB2308590

September 17, 2010 Leave a comment
If you have SCVMM2008R2 installed and are experiencing the following issue :
Duplicate virtual machines (VMs) may appear in the SCVMM Administrator Console window after a Hyper-V VM in a cluster fails over to another cluster node. Additionally, the status for one of the duplicate VMs is set to Missing. If you try to remove the missing VM from the SCVMM Administrator Console window, the VM is not removed.
Microsoft released an hotfix http://support.microsoft.com/kb/2308590
 
How to obtain this SCVMM 2008 R2 hotfix rollup package: This hotfix rollup package is available on Microsoft Update.To obtain this update from Microsoft Update, follow these steps on the SCVMM server:

  1. Click Start, and then select Control Panel.
  2. In Control Panel, double-click Windows Update.
  3. In the Windows Update window, click Check Online for updates from Microsoft Update.
  4. Click important updates are available.
  5. Select Update for System Center Virtual Machine Manager 2008 R2 (KB2308590), and then click OK.
  6. Click Install updates.
Note If the Virtual Machine Manager or Virtual Machine Manager Agent service is running when this hotfix rollup package is installed on the SCVMM server, you have to restart the computer. 
How to update the SCVMM agent on the Hyper-V and Virtual Server host
This update requires updating the VMM agent on the Hyper-V and Virtual Server hosts. The hosts will have a status of Needs Attention if the agent has not been updated.

To update the SCVMM agent on multiple hosts, follow these steps:

  1. Open the SCVMM Administrator Console window. 
  2. Click Administration, and then click Managed Computers.
  3. Select the hosts, and then click Update Agent.
  4. Enter your user account credentials, and then click OK.
To manually download the hotfix rollup package from the Microsoft Update Catalog, visit the following Microsoft Web site:

 
Note The Microsoft Update Catalog has different versions of the hotfix rollup package. These different versions have the EVAL, OEM, RETAIL, and WORKGRP labels. Download the appropriate version for your installation.To install this hotfix rollup package that can be downloaded from the Microsoft Update Catalog on the SCVMM server, follow these steps: 

  1. Extract the VmmServer64Update-RETAIL.cab file to a temporary directory.
  2. Open an elevated command prompt, type the following command, and then press ENTER to install the update:
    msiexec /update vmmServer64Update-RETAIL.msp BOOTSTRAPPED=1
    Note The name of the package varies, depending on the version that was downloaded.
  3. After the hotfix rollup package is installed on the SCVMM server, update the SCVMM agent on the Hyper-V and Virtual Server hosts.
Hotfix rollup information
Prerequisites

You must have SCVMM 2008 R2 installed.

P2V Migration for Software Assurance : Beta released

September 16, 2010 Leave a comment
 
Microsoft launched the public beta of a new physical to virtual (P2V) migration tool for client operating systmes:P2V Migration for Software Assurance.
P2V Migration for Software Assurance uses automation from the Microsoft Deployment Toolkit (MDT) 2010 and P2V disk conversion from Sysinternals Disk2vhd. The Windows Installer Package for P2V Migration contains a collection of scripts and MDT 2010 task sequence templates that convert an existing operating system installation to a VHD file during a Windows 7 deployment. Then, the process creates a VM using the VHD file and publishes the applications it contains to the Windows 7 Start menu.
P2V Migration supports creating VHD files based on Windows 7, Windows Vista, and Windows XP with Service Pack 3 (SP3) operating systems. Although you can use P2V Migration when deploying the x86 or x64 versions of Windows 7, it can only create VHD files based on x86 versions of the operating system. P2V Migration is language agnostic.

For Lite Touch Installation deployments using MDT 2010 Update 1, P2V Migration for Software Assurance requires the following components:
·         A functional installation of MDT 2010 Update 1 with mapped deployment shares on the client computer targeted for P2V Migration for Software Assurance installation.
·         An Internet connection or downloadable components listed in the previous section, available in C:Program Files (x86)P2V Migration for Software AssuranceTools.
For Zero Touch Installation deployments using Microsoft System Center Configuration Manager 2007, P2V Migration for Software Assurance requires the following components:
·         A configured System Center Configuration Manager Operating System Deployment environment with MDT 2010 Update 1 add-in components installed.
·         An Internet connection or downloadable components listed in the previous section, available in C:Program Files (x86)P2V Migration for Software AssuranceTools.
The client computers targeted for VHD conversion must meet the following requirements:
·         32-bit Windows 7 Professional or Windows 7 Enterprise, Windows Vista Business or Windows Vista Enterprise with SP1 or SP2, or Windows XP Professional with SP3 installed.
·         Client computers were installed and activated using Microsoft Volume Licensing or full packaged product installation media. Installations using OEM installation media are not valid. Full packaged product installation media provide the right to transfer the installation to another computer but will require reactivation once the system has been converted to a VHD.
·         Hard disks must be 127 gigabytes (GB) or smaller in size, regardless of the amount of data stored on them. This is a limitation of Windows Virtual PC. For example, if the computer has a 160-GB hard disk consuming only 20 GB of data or is configured with multiple partitions and a Windows volume smaller than 127 GB, P2V Migration will not work in either configuration.
The client computers on which the new operating system will be installed must meet the following requirements:
·         32-bit or 64-bit Windows 7 Professional or Windows 7 Enterprise
·         Software Assurance covers the device in order to provide rights for up to four VM installations per device
·         Hardware meets the minimum requirements of Windows 7 with Windows Virtual PC (2 GB of RAM recommended).
Note   Hardware-assisted virtualization is not required with this solution

 
 
Categories: Virtualization