Importing XML Files into Hyper-V on Windows 8 / Windows Server 2012; Hyper-V Supported Client OS List; Microsoft Plant to Leverage Power of the Microsoft Ecosystem with Connected Car Platform

Microsoft also talked about the Live Migration and Storage Migration in Windows Server 2012. "In Windows 8 / Windows Server 2012 we've done a lot of work on import and export to address all of the complaints that we heard in this area," Microsoft stated."One of the biggest complaints that we heard from users was […]

Microsoft also talked about the Live Migration and Storage Migration in Windows Server 2012. "In Windows 8 / Windows Server 2012 we've done a lot of work on import and export to address all of the complaints that we heard in this area," Microsoft stated.

"One of the biggest complaints that we heard from users was the simple fact that we required you to export a virtual machine from one computer before you could import it on another computer. Often people would find themselves with a collection of virtual machine files (.XML, .VHD and .AVHD files) but without a running system that could be used to export them. They just needed to connect these files to a new instance of Hyper-V. And while this was technically possible to do with Windows Server 2008 R2; it was very tricky / problematic and was definitely not supported."

With Windows 8 / Windows Server 2012, Microsoft allow to just connect raw virtual machine files to Hyper-V without the need to export them first (we still have an "Export" button in the UI - but all it does now is to create a copy of the files that you need).

What is really cool here is that we also allow you to use raw virtual machine XML files from Windows Server 2008 R2.

More than that - we will take a bunch of meaningless XML files like this:

And figure out the virtual machine names and details for you, so you can quickly and easily import the right virtual machine when you need it:

Microsoft has also released Windows Server 2012 Hyper-V - List of Supported Client OS as shown in the table below:

Guest operating system (server)

Notes

Windows Server 2012

Integration services do not require a separate installation because they are built-in.

Windows Server 2008 R2 with Service Pack 1 (SP 1)

Datacenter, Enterprise, Standard and Web editions. Install the integration services after you set up the operating system in the virtual machine.

Windows Server 2008 R2

Datacenter, Enterprise, Standard and Web editions. Upgrade the integration services after you set up the operating system in the virtual machine.

Windows Server 2008 with Service Pack 2 (SP 2)

Datacenter, Enterprise, Standard and Web editions (32-bit and 64-bit). Install the integration services after you set up the operating system in the virtual machine.

Windows Server 2008

Datacenter, Enterprise, Standard and Web editions (32-bit and 64-bit). Install the integration services after you set up the operating system in the virtual machine.

Windows Home Server 2011

Edition information is not applicable. Install the integration services after you set up the operating system in the virtual machine.

Windows Small Business Server 2011

Essentials and Standard editions. Install the integration services after you set up the operating system in the virtual machine.

Windows Server 2003 R2 with Service Pack 2 (SP2)

Standard, Web, Enterprise, and Datacenter editions (32-bit and 64-bit). Install the integration services after you set up the operating system in the virtual machine.

Windows Server 2003 with Service Pack 2

Standard, Web, Enterprise, and Datacenter editions (32-bit and 64-bit). Install the integration services after you set up the operating system in the virtual machine.

CentOS 6.0 - 6.2

Download and install Linux Integration Services v3.2.

Red Hat Enterprise Linux 6.0 -6.2

Download and install Linux Integration Services v3.2.

SUSE Linux Enterprise Server 11 SP2

Integration services do not require a separate installation because they are built-in.

Guest operating system (client)

Notes

Windows 8 Release Preview

Integration services do not require a separate installation because they are built-in.

Windows 7 with Service Pack 1 (SP 1)

Ultimate and Enterprise editions (32-bit and 64-bit). Upgrade the integration services after you set up the operating system in the virtual machine.

Windows 7

Ultimate and Enterprise editions (32-bit and 64-bit). Upgrade the integration services after you set up the operating system in the virtual machine.

Windows Vista with Service Pack 2 (SP2)

Business, Enterprise, and Ultimate, including N and KN editions. Install the integration services after you set up the operating system in the virtual machine.

Windows XP with Service Pack 3 (SP3)

Professional. Install the integration services after you set up the operating system in the virtual machine.

Windows XP x64 Edition with Service Pack 2 (SP 2)

You can find more information here.

In other Windows 8 news, Microsoft in a recent job listing, given some hints about what it wants to add to the next version of its Connected Car Platform i.e. the ability to link up to Windows 8 and other Microsoft products and services.

Microsoft's job listing for a new Software Development Engineer offers up a highly ambitious feature list for the future of that Embedded Automotive platform and says that Microsoft wants to have car drivers link with their vehicles with voice, gestures, and face tracking. It adds, "Through a growing catalogue of applications, it will inform and entertain them, and keep them connected with the people and information they care about. The possibilities are endless."

For the next generation of the Connected Car Platform, we plan to leverage the full power of the Microsoft ecosystem including Kinect, Windows 8, Windows Phone, Windows Live, Bing, Azure, and Tellme. The combination of rich local sensing, user identification, cloud access, and data mining will transform tomorrow's cars from passive objects into intelligent assistants for both the driver and their passengers.