Error validating hyper v machine name

Well as it turns out it was the Jumbo Frame setting on the CSV and LM NICs. The Mellanox NICs allow for MTU Sizes up to 9614 in their Jumbo Frame property.

Those servers had been connected to a couple of DELL Force10 S4810 switches. Now super sized jumbo frames are all cool until you attach the network cables to another switch like a Power Connect 8132 that has a max MTU size of 9216.

I also modified the script to give me the option to only show updates that are missing or both.

This is achieved by setting the variable to show installed and missing.

That moment your network won’t do what it’s supposed to and you see errors like those above.

But when I try to add a client by browsing the virtuel guests running on the cluster I simply can't see any... But when I run the backup it fails immidiately with error code 48 ("client hostname could not be found(48)"). Log Name: Microsoft-Windows-Hyper-V-VMMS-Admin Source: Microsoft-Windows-Hyper-V-VMMS Date: 10/8/2013 AM Event ID: 22038 Task Category: None Level: Error Keywords: User: SYSTEM Computer: SRV1. COM Description: Failed to send data for a Virtual Machine migration: An existing connection was forcibly closed by the remote host. Log Name: Microsoft-Windows-Hyper-V-VMMS-Admin Source: Microsoft-Windows-Hyper-V-VMMS Date: 10/8/2013 AM Event ID: 21018 Task Category: None Level: Error Keywords: User: SYSTEM Computer: SRV1. COM Description: Planned virtual machine creation failed for virtual machine ‘Didier Test01’: An existing connection was forcibly closed by the remote host. (Virtual Machine ID 41EF2DB-0C0A-12FE-25CB-C3330D937F27). Log Name: Microsoft-Windows-Hyper-V-VMMS-Admin Source: Microsoft-Windows-Hyper-V-VMMS Date: 10/8/2013 AM Event ID: 22040 Task Category: None Level: Error Keywords: User: SYSTEM Computer: SRV1. COM Description: Failed to receive data for a Virtual Machine migration: An existing connection was forcibly closed by the remote host. Log Name: Microsoft-Windows-Hyper-V-VMMS-Admin Source: Microsoft-Windows-Hyper-V-VMMS Date: 10/8/2013 AM Event ID: 21024 Task Category: None Level: Error Keywords: User: SYSTEM Computer: srv1com Description: Virtual machine migration operation for ‘Didier Test01’ failed at migration source ‘SRV1’.(Virtual machine ID 41EF2DB-0C0A-12FE-25CB-C3330D937F27) There is something wrong with the network and if all checks out on your cluster & hosts it’s time to look beyond that.After running the script again against the host, the result was only 4 missing hotfixes The script will show a warning if the host is installed with an older version of windows 2012 or some critical updates are missing.I also updated the script which checks all the nodes in a cluster.

Search for error validating hyper v machine name:

error validating hyper v machine name-77error validating hyper v machine name-80

Leave a Reply

Your email address will not be published. Required fields are marked *

One thought on “error validating hyper v machine name”