Skip to content
/ Michaël Hompus

, , , ,
Today the Microsoft Virtualization Team announced the availability of the new beta version of the Linux Integration Services for Hyper-V. In this post I will try the new features.

Today the Microsoft Virtualization Team announced the availability of the new beta version of the Linux Integration Services for Hyper-V. There are three big changes in this version:

  • Virtual machines will be able to use up to 4 virtual CPUs.
  • Virtual machines will be able to synchronize their time with the parent partition.
  • Virtual machines will be able to shutdown gracefully from the Hyper-V manager.

In this post I will try the new features.

Linux Integration Services for Hyper-V 2.0

First, I got a Virtual Machine (VM) installed as described in my previous post “Running CentOS 5.x on Hyper-V”. I used the current released stable version of the Linux Integration Services (LIS): Version 2.0.

Screenshot displaying the VMBUS information on booting the virtual machine. Build Date=Jun 29 2009 and Build Description=Version 2.0.
On boot time, VMBUS displays 'Version 2.0'

My Hyper-V host only has a dual-core CPU. So, it is impossible for me to test the 4 CPU support. I could not find any differences with 2 CPUs.

Shutdown from Hyper-V Console

With the current version of the LIS when I press the shutdown button, I get the following error:

Screenshot displaying the Hyper-V console showing the error text: "The application encountered an error while attempting to change the state of 'BlogDemo'. Failed to shut down the virtual machine.".
Hyper-V Console shows the error 'Failed to shut down the virtual machine'.

Time synchronization

With the current version of the LIS I had a lot of trouble with the clock of the VM getting out of sync very fast. I did a post to fix this: “Correcting time drift with CentOS on Hyper-V”.

I did not implement the mentioned fix on the VM I created for this post, to demonstrate the problem:

Screenshot displaying the Hyper-V console showing the VM gets a time difference of multiple=
The VM gets an offset of multiple seconds within minutes.

Linux Integration Services for Hyper-V 2.1 Beta

To get the beta drivers you need to download them from the Microsoft Connect website.

I installed the new drivers in exact the same way as the 2.0.

Screenshot displaying the VMBUS information on booting the virtual machine. Build Date=Mar 23 2010 and Build Description=Version 2.1.2.
On boot time, VMBUS displays Version 2.1.2

Not only the new version number is displayed, also the new Shutdown and Timesync channels are mentioned!

Shutdown from Hyper-V Console

Pressing the shutdown button now gives a more expected result:

Screenshot displaying the virtual machine has received the shutdown command and starts the power-off sequence.
The VM receives the signal to shut down and calls `/sbin/poweroff`
Screenshot displaying the Hyper-V console with the message: "The virtual machine is turned off".
The VM is gracefully turned off.

Time synchronization

With the new LIS the time is pretty much stable, nothing the NTP service cannot handle. There is no need to change the boot command in grub anymore.

Screenshot displaying the Hyper-V console showing the VM shows minimal time difference over the course of minutes.
The VM only shows a minimal time difference over the course of minutes.
Filed under Hyper-V
Last update:
/ Michaël Hompus

, , , , , , , , , ,
I wanted to use the new REST services in SharePoint 2010. But when I navigated to the ListData.svc service. I got the following error: “Could not load type 'System.Data.Services.Providers.IDataServiceUpdateProvider' from assembly 'System.Data.Services, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'.”

I wanted to use the new REST services in SharePoint 2010. But when I navigated to the ListData.svc service. I got the following error:

Screenshot displaying SharePoint 2010 showing the following error: "Could not load type 'System.Data.Services.Providers.IDataServiceUpdateProvider' from assembly 'System.Data.Services, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'."

First, I checked if there was a System.Data.Services entry in the GAC (Global Assembly Cache). There was one with version 3.5.30729.1. So, it was not a missing file.

Searching the web on the error…

Could not load type ‘System.­Data.­Services.­Providers.­IDataServiceUpdateProvider’ from assembly ‘System.­Data.­Services, Version=3.5.0.0, Culture=­neutral, PublicKeyToken=­b77a5c561934e089’

…does not provide many hints to what is causing this error.
Most sites suggest to install ADO.NET Data Services v1.5 CTP2, but I already had.

I finally found the page REST and SharePoint 2010 Quick Start Guide by Scott Currier. He suggests to install the ADO.NET Data Services Update for .NET 3.5 SP1. As it turns out, this is the final release of the ADO.NET Services v1.5!

The update comes in two flavors.

For Windows 7 AND Windows Server 2008 R2

Download the ADO.NET Data Services Update for .NET Framework 3.5 SP1 for Windows 7 and Windows Server 2008 R2.

After installing the version of the System.Data.Services.dll file is 3.5.30729.5004.

For Windows 2000, Windows XP, Windows Vista, Windows Server 2003 AND Windows Server 2008

Download the ADO.NET Data Services Update for .NET Framework 3.5 SP1 for Windows 2000, Windows Server 2003, Windows XP, Windows Vista and Windows Server 2008.

After installing the version of the System.Data.Services.dll file is 3.5.30729.4466.

Testing

After I installed the update, I browsed to the ListData.svc service.

Screenshot displaying the service description of a SharePoint 2010 Team Site as an atom feed.
The service description of a SharePoint 2010 Team Site as an atom feed.
Filed under SharePoint
Last update:
/ Michaël Hompus

, , , ,
Today the news broke Microsoft has extended the support for installations of Windows SharePoint Services 3.0 SP1, Microsoft Office SharePoint Server 2007 SP1 and Project Server 2007 SP1.

As I wrote in “WSS 3.0, SharePoint 2007 and Project Server SP1 support ends soon”. But today I discovered Microsoft has extended the support for installations of Windows SharePoint Services 3.0 SP1, Microsoft Office SharePoint Server 2007 SP1 and Project Server 2007 SP1.

read more…
/ Michaël Hompus

, , , , , , , ,
The Microsoft Surface is a Windows Vista computer running the Microsoft Surface Shell. This shell is by default localized for US English. It is possible to localize for other locales, but there is no configuration screen to set the desired localization. This post will summarize the different steps to localize the Surface shell.

The Microsoft Surface (the table, not the tablet) is a Windows Vista computer running the Microsoft Surface Shell. This shell is by default localized for US English.

It is possible to localize for other locales, but there is no configuration screen to set the desired localization.

This article will summarize the different steps to localize the Surface shell.

read more…
Filed under Surface
Last update:
/ Michaël Hompus

, , , , ,
If you want to develop for the Microsoft Surface you need a Surface device, but using the device to develop is not always practical, specially when there are more developers than Surface devices. The solution for this is to install the Surface SDK on you local development machine. This post will address some limitations you have to work around.

If you want to develop for the Microsoft Surface (the table, not the tablet) you need a Surface device. But using the device to develop is not always practical, especially when there are more developers than Surface devices.

The solution for this is to install the Surface SDK Workstation Edition on your local development machine. This article will address some limitations you have to work around.

read more…
Filed under Surface
Last update: