Either support Linux domain member servers or clients with AD domain policies through a new integration service or make sure that the Windows server eventlogs aren't flooded with events complaining about this matter.

The solution or workaround at the moment for this is clearing the AD attribute DNSHostName contents with powershell or adsiedit on the computer object of the in the event log mentioned Linux host inside the residing container. As long as the (make sure it's static anyway) DNS entry for the Linux hosts exists it will not give any problems, but much less system event log errors.

As for now we have no option to trace events like kernel panic or storage faiulure and restart vms.