Oh no, you're thinking, yet another cookie pop-up. Well, sorry, it's the law. We measure how many people read us, and ensure you see relevant ads, by storing cookies on your device. If you're cool with that, hit “Accept all Cookies”. For more info and to customize your settings, hit “Customize Settings”.

Review and manage your consent

Here's an overview of our use of cookies, similar technologies and how to manage them. You can also change your choices at any time, by hitting the “Your Consent Options” link on the site's footer.

Manage Cookie Preferences
  • These cookies are strictly necessary so that you can navigate the site as normal and use all features. Without these cookies we cannot provide you with the service that you expect.

  • These cookies are used to make advertising messages more relevant to you. They perform functions like preventing the same ad from continuously reappearing, ensuring that ads are properly displayed for advertisers, and in some cases selecting advertisements that are based on your interests.

  • These cookies collect information in aggregate form to help us understand how our websites are being used. They allow us to count visits and traffic sources so that we can measure and improve the performance of our sites. If people say no to these cookies, we do not know how many people have visited and we cannot monitor performance.

See also our Cookie policy and Privacy policy.

This article is more than 1 year old

Windows Server 2016's VM migration tools broken by a patch

Good job almost nobody's had time to put it into production

Microsoft's had to hurry out a fix for a problem that breaks live VM migration. And it's a problem Redmond brought upon itself with an Update Rollup to System Center 2016 Virtual Machine Manager.

Update Rollup 1 for that tool has the unintended side effect of making it impossible to migrate live VMs between different versions of Windows Server 2016 on different hosts.

When attempting live migrations, users are instead presented with the following error:

Unable to migrate or clone the virtual machine VM_name because the version of virtualization software on the host does not match the version of virtual machine's virtualization software on source version_number. To be migrated or cloned, the virtual machine must be stopped and should not contain any saved state.

Which is so not the point of live migrations, which are supposed to just happen.

Interestingly, the problem doesn't manifest when moving VMs between Windows Server 2016 and Windows Server 2012.

Redmond's therefore issued a Hotfix for the Update Rollup, yours for the downloading here. Details of the problem are here.

It's early days for Windows Server 2016 and production implementations will be few and far between, so not many will need to worry about this problem. Other than Microsoft, which surely isn't thrilled to have a glitch like this come along so soon after launch. ®

 

Similar topics

Similar topics

Similar topics

TIP US OFF

Send us news


Other stories you might like