W2016 Hyper-V/shielded VMs causing log spam

[doktornotor]

Testing Veeam ONE on W2016 with Shielded VMs (not the complicated HGS infrastructure setup, just "standalone" shielded VMs (see the howto here in case you need a way to reproduce). We are getting literally thousands of these errors logged daily on the Hyper-V host (Source: Hyper-V-Integration, Event ID: 4134), one every minute per each of the shielded VMs.

Code: Select all

'Machine Name': The Data Exchange integration service does not support this operation for a VM running in a shielded context. (Virtual machine ID ABCDEFGH-A123-B456-C789-0123456789)

It's perfectly understandable that the monitoring capabilities will be restricted in such environment due to restrictions on Hyper-V integration services in such environment, however we need to stop this logspam. Any hints which tasks does this come from and how to disable/mute those?

[Shestakov]

Hello and welcome to the community.
Do you mean Veeam ONE alarms spam?
If yes, you can either place the object in the maintenance mode or exclude the object from that particular alarm.
Thanks!

[doktornotor]

Hi, thanks. As noted above, I mean the Windows event log spam. Not Veeam notifications/alarms.

[Shestakov]

Thanks for clarification.
Not sure if we can disable Windows event log. I'll discuss it with R&D team and write back.

[doktornotor]

Thanks. Thinking about it, perhaps a better way would be to detect shielded VMs and not run the tasks there are bound to fail there at all. (You can use Get-VMSecurity on the Hyper-V host to get the info, probably WMI as well but I have not checked...)

[Shestakov]

Indeed the events are generated because of Veeam ONE request to all VMs.
R&D team can make a fix for the case. Contact support team to get it.

[Dvorf]

Hi,
Is it possible to get this fix for Veeam ONE Free users?

[Shestakov]

Hi Georgy and welcome to the community.
Yes, users with free license may also contact support team. You will be helped on the best effort level.
Thanks!

[doktornotor]

Indeed the events are generated because of Veeam ONE request to all VMs.
R&D team can make a fix for the case. Contact support team to get it.

Thanks for posting, I'll get in touch with them next week.

[Shestakov]

Once you do, please post a support case number here for later reference.
Thanks!

[doktornotor]

Once you do, please post a support case number here for later reference.
Thanks!

Thanks, case #02749060.

[doktornotor]

Issue fixed with a patched VeeamDataProviderHyperV.dll provided by Veeam Support.

Good job, guys!

[Shestakov]

Good to know, thanks for the update!

[doktornotor]

Well, the fix apparently did not get included in B&R 9.5 Update 4...

[Shestakov]

Hello,
As a rule all fixes are included in the consecutive release. I will check if this one is exception.
Did the problem appear again after an upgrade?

[doktornotor]

Just to revive this - this unfortunately is still an issue even with latest 11 release and Server 2019/2022. Apparently has never been merged.

[RomanK]

Hello Doktornotor,

Could you please open an independent support case and provide case ID in this thread so we could collect all the details and investigate it accordingly?

Thanks

[doktornotor]

Well, the (previous) case ID was #02749060 as noted in this thread. Apparently still the same issue.

[RomanK]

Hello Doktornotor,

As far as I know, this issue mentioned in this thread has been already fixed. If you are facing a similar behavior we recommend opening a new support case for investigation. We would appreciate it if you could share the case ID so we could keep an eye on it.

Thanks