question

CannonChris-5226 avatar image
5 Votes"
CannonChris-5226 asked BrendonHolt-7726 commented

Problems with Hyper-V on Server 2019 (1809) after August 2020 patches

We've been having problems after installing August 2020 Patches on our 2019 HyperV hosts. We have multiple hyper-v clusters across Dell VRTX and UCS blades w/ ISCSI backend SANS. Both environments have seen backup times double. Additionally loading a VMs settings in HyperV or Failover cluster manager is taking a very long time. We are not using a 3rd party AV but defender managed by SCCM. Usually when i see issues like this it feels like a storage performance issue but i'm seeing the issue across the board with iscsi as well as direct attached.

Patches applied
KB4566424
KB4565349
KB4569776

our change log indicates no other changes. Our hyperv hosts have no other roles.

I'm going to try roll back the august patching and do a quick A/B test to see if that remediates the issue, but thought i'd post to see if anyone else has seen this issue.

Chris

windows-server-2019windows-server-hyper-v
· 26
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

We are also seeing delays on our 2019 Cluster. This manifests in slow "Get-VM" commands on the nodes and slowness opening settings for any of the VMs. It also seems to be causing delayed stats coming into Veeam One - sometimes these can be 15 minutes behind.

I don't like the idea of uninstalling updates to fix the issue - essentially if Microsoft is aware of the issue, they need to fix it! It could also affect anyone that has ISO compliance requiring fixes to be applied within a particular time window.

Does anyone have a link or reference to the Hotfix (Hotfix ID?) which solves the issue? I don't mind opening a case with Microsoft, if I need to go down that route to receive the fix, but it will be quicker if I can point them in the right direction.

2 Votes 2 ·

I don't think there is a public hotfix yet, only a private hotfix created ad hoc. You'll have to wait for a general release.
Alex

1 Vote 1 ·

I'm not sure i feel comfortable sharing the hotfix MS provided me as i'm not sure it was anywhere close to a finished product. I should add that I am not comfortable putting this on any of our production 2019 Hyper V servers.; I'm waiting on the general release.

1 Vote 1 ·
Show more comments

Add us to the mix, this weekend (Thanksgiving) we decided to update the Hardware Platform. Installation of Server 2019 went fine and updates were applied, up until November.

We experienced VERY SLOW Hyper-V Manager to Create or to Manage Settings on the Two New Super Powerful Computers just installed. Testing showed that during Hyper-V Manager could slow Guests down so much login to RDS servers was slow/failed. Was just taking forever to work in settings. Sunday we re-installed 2019 Server on one Machine and it was fine until updates were applied.

We decided to apply updates and deal with this issue because we provide this platform to end users, and the Legal/Financial Liability from Zero Net Logon outweighs the speed of IT Management. NOTE WE CANNOT WORK IN HYPER-V MANAGER IN PRODUCTION HOURS, 11PM to 2AM.

This BUG NEEDS TO BE FIXED and it is a SEVERE LIMITATION. I understand we all work in a complex and dangerous world, but hopefully we get a Fix SOON for this issue.

2 Votes 2 ·

Hi,

Yes, you can roll back to the previous version to see if the question still exists. And you can update your result here.

And if anyone has the same issue, welcome to post your question here.

Best Regards,
Daniel

1 Vote 1 ·

I removed only KB4565349 from a 5 node cluster (150 vms) on UCS blade chasssis and from a smaller 2 node cluster (dell vrtx) with around a dozen VMs. With the larger cluster, i was previously waiting on the window to open for a VM settings from FCM was taking between 20-40 seconds. I'm loading them now between 3 - 5. I do not yet have statistics on backups; I had to pause backups on the larger cluster b/c the job was running past the maintenance window. I'm re-enabling that back up now. With the smaller cluster, i made the change after backups had completed so i don't have a comparison.

With it being a longer holiday weekend i'll likely let things sit as they are over the weekend. If backups seem back to normal, i'm open to do some more testing with a couple other clusters (brand new UCS blades). To my knowledge, we're not seeing any VM performance issues at this point.

Thanks Chris







1 Vote 1 ·

Sounds good.

Please let me know if you have any other questions.


1 Vote 1 ·

This is certainly happening on clusters we run. We have not yet rolled back (more complicated than removing a single update) and inherently puts our environment in risk by running on an old rollup if we do.

Very frustrating to not have Microsoft already patched this, so we'll likely burn a support case to get a hotfix.

Can you provide any estimate on resolution or acknowledgment that Microsoft has even identified this?

1 Vote 1 ·

I just heard back. The update is scheduled for inclusion in January.

3 Votes 3 ·
Show more comments

Its been a month since i've heard from them. I pinged them a moment ago to see if there is a schedule for it to be included in the normal rollup. Believe me... I share your frustration. It took several calls/screen shares with multiple teams to get anyone to really acknowledge the issue. I'm still waiting on it to be rolled into the monthly cumulative. I'll respond if i hear back.

Chris

1 Vote 1 ·
Show more comments

On a 6 Nodes Win2019 SCVMM managed FailOverCluster, that we use for Automated Testing , which heavily relies on CheckPoints we have these findings:

  • Win2019/SCVMM2019 has double duration, when operations are performed on Non SCV owner, whereas Win2016/SCVMM2016 has no measureable difference.

  • Win2019+KB4586793 doubles Hyper-V Restore on Non owner. SCVMM Restore is four times slowere, mostly affected by prolonged Refresh durations

  • Win2019+KB4598230 adds 30% to Hyper-V Restore. Doubles SCVMM Restore duration,

  • Eventually MigrateVm AWAY from SCV Owner ends up lasting 6 – 14 minutes

Measurements when Restoring a complex CheckPoint (Numbers are seconds):

56592-image.png

56439-image.png

56440-image.png

So January Update was even worse!

0 Votes 0 ·
image.png (5.4 KiB)
image.png (5.6 KiB)
image.png (5.7 KiB)

BTW: Due to lots of SCVMM Error ID 2606 From the superslow Refresh(*), we have added 'Retry' SCVMM Command' for ERRORID:2606 to our Test Automation Execution , but are still severely down on Test Thrioughput.. We are still on KB4586793!


Unable to acquire a 'Delete' lock on object '52112b4e-3c4c-42b0-a2d9-0e708231d1c5' of type 'VirtualHardDisk' because it is locked by task 'ec55c407-f8dc-4900-9f3a-ce570d4a5d02' 'Refresh host cluster' with a 'Write' lock. (Error ID: 2606)

0 Votes 0 ·

For completeness, we changed VmDatStore.dll back to the latest available in WinSxS before August 2020, an got these numbers - so no relief compared to August, but sime relief compared to the Jan 2021 results (We have only tried this on a Staging environment!)

.56671-image.png


0 Votes 0 ·
image.png (19.7 KiB)

Hello Jens.
Have you been in talk with Microsoft regarding this issue? :)

0 Votes 0 ·
Show more comments

We opened a ticket with MS and referenced this post and the case# CannonChris-5226 provided. We were provided a private hotfix that is time limited which they stated they have had for a few months. It was time stamped in October 2020. Installing this hotfix requires using bcdedit to put and leave the server in test mode until the patch is removed and replaced with the public version. They also make accept a bunch of warnings that the hotfix is provided as-in and may cause other issues.

Given the impact on our environment and that there were no issues encountered in our test environment we have put this into production and it immediately resolved the IO performance issue. It did not solve the issue with VM settings taking a long time to load or the right click menu in cluster manager disappearing when you try to select something.

0 Votes 0 ·
Show more comments
CannonChris-5226 avatar image
0 Votes"
CannonChris-5226 answered CannonChris-5226 commented

kb4586793 file list includes both Vmdatastore.dll and Vmwp.exe. Going to check if the file revs match up to what was in the hotfix now.

Chris

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Nope. the file list must include the previous files b/c of the rollup status. HATE that they moved to only rollups...what a pita. The fix doesn't seem to be in Nov 2020.

1 Vote 1 ·
Hyper-Z-7856 avatar image
0 Votes"
Hyper-Z-7856 answered Hyper-Z-7856 edited

Similar to Cannon, We too are running Cisco UCS blades on iSCSI storage and experience much worse behavior than just slow performance.

If you are running Server 2019 1809 Hyper-V in a failover cluster and you apply any monthly update listed below from August till current, your Hyper-V servers may become slower or worse completely freak out and stop responding to simple management requests.

The RHS will fail randomly on all hosts. This will cause your VMs to reboot and attempt to run on another physical server as it will assume the server is unavailable.
"The cluster Resource Hosting Subsystem (RHS) process was terminated and will be restarted. This is typically associated with cluster health detection and recovery of a resource. Refer to the System event log to determine which resource and resource DLL is causing the issue."

August 2020 Update KB4565349
September 2020 Update KB4570333
October 2020 Update KB4577668
November 2020 Update KB4586793

Uninstall these updates as a workaround until Microsoft resolve this issue.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

JacquesMagne-9224 avatar image
0 Votes"
JacquesMagne-9224 answered

Be careful, KB4565349 fix zero netlogon vulnerability (CVE-2020-1472)

Sorry for my poor English

Jacques

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

HansvanDeursen-8777 avatar image
0 Votes"
HansvanDeursen-8777 answered JensKlarskovJensen-7178 commented

Hi All,

Had the same issue with new installed 2019 servers and SAS storage. Then updated with KB4592440 and the problem was solved. Both Live Migrating and Quick migration works fine now.

· 10
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi, the KB4592440 Update doesn't appear to fix the issue with performance (in relation to Vmdatastore.dll and Vmwp.exe). Running 'Get-VM -name *' on a host can still take up to 3 to 4 minutes.

Hanging out for the January CU to be released! This is causing a major heading in our datacentre.

0 Votes 0 ·

Hi, just got info from our MS support tech that the public hotfix is now scheduled for the 2021.02 C update. Not quite January either... Alas.

0 Votes 0 ·

Hi - is there any way to get the hotfix before the public release?

0 Votes 0 ·
Show more comments
CannonChris-5226 avatar image
0 Votes"
CannonChris-5226 answered CannonChris-5226 commented

I've reached back out to the tech that worked my incident. (it was closed btw) I also pinged my sales rep. Not sure when I'll hear back.

If you haven't opened a ticket about this problem, i'd suggest doing that. More most attention to the problem may expedite the solution.

Chris

· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Chris, would you mind sharing your MS case number? We have been waiting for the patch since you first mentioned the promised January release. Now with this being pushed back I want to open another MS ticket on the issue. Referencing your ticket would help cut through the nonsense that is MS support bring direct attention to this issue.

1 Vote 1 ·

120091424007097

0 Votes 0 ·
CannonChris-5226 avatar image
0 Votes"
CannonChris-5226 answered JoshHargense-9068 commented

I was told that the release was delayed and is now set for March 2021...FYi

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Good grief, March!!! I don't think we can wait that long. Similar to DaxtechIT-4864, if you could provide the MS case number we will raise our own hotfix request.

0 Votes 0 ·
CannonChris-5226 avatar image
0 Votes"
CannonChris-5226 answered MenkWolfgang-8763 commented

I was told that the release was delayed and is now set for March 2021...FYi

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Just got confirmation from MS that the hotfix is indeed not included in the 2021.02C update. The "new" scheduled release date is 2021.03C - as Chris told all along... Anyway, it's truely a shame.

0 Votes 0 ·
StewartMyles-4293 avatar image
0 Votes"
StewartMyles-4293 answered

We are experiencing the same issues on a 4 node cluster but have a 6 node DR cluster and that appears to be OK, same software revision and similar hardware. I have received a hotfix KB900246-x64 from Microsoft and this appears to have resolved the issue, I need to deploy the patch to the rest of the nodes but its looking very hopeful.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

JosephWSmith-7761 avatar image
0 Votes"
JosephWSmith-7761 answered ColeT-7986 edited

I am having the same issue here. Can anyone tell me where I can download the hotfix KB900246-x64 or version 10.1.17763.348 VmDataStore.dll?

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

I'm also having the same issue on multiple Windows Server 2019 clusters and standalone servers. Same issue regardless of server or storage hardware.

I thought waiting over 2 years to migrate to 2019 for production would have been long enough.

Can't even get through to Microsoft partner support. Voicemail says, "Dear Valued Partner were currently experiencing delays and responding to support requests. Thank you for the patience and understand good bye." It has been like that for 10 hours.

Can someone please provide the hotfix? It would be much appreciated.

Thanks.

0 Votes 0 ·
PaulWebb-5946 avatar image
0 Votes"
PaulWebb-5946 answered

It's very poor Microsoft seem to be holding off releasing the fix as part of a CU when it is affecting so many end users - have Microsoft given any reason as to why they are dragging their feet? Can't say I would want to be dropping an unsupported hotfix into our production environment, especially when you have to start changing the boot options.
Cheers

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.