Virtual Machine couldn't ping each other

[guest]

The issue is that after you configure the
Virtual Server host clustering, the Virtual Machine couldn't ping each
other and the Failover fails.

So let's divide this issue into two parts and we will troubleshoot this
issue one by one.

- VM couldn't ping each other
- Cluster failover fails

Let's start from the first issue, Virtual Machines couldn't ping each
other. To troubleshoot this issue, please let me know the following:

1. How many NICs are there on the host computer?

2. Which NIC is attached to the Virtual Machine? The physical NIC or the
Virtual NIC you created?

3. If the same Virtual NIC is attached for these two Virtual Machines.

Also please try to remove the Virtual NIC on these Guest OS and then attach
it to the Guest OS again and see if the issue still exists.

[guest]

I think I was able to figure out my issue with Guests not being able to ping
each other. Its related to them being originally setup on different host
systems and using different VNC files. When the two guests were both running
on the same server the two Virtual NICs didn't pass traffic between them even
though the associated guest NICs were configured on the same subnet. My
solution will be to remove the individiual VNC files for each guest's SAN
volume and create a single identical VNC directly on each Host which all
Guests will use.
Does this sound correct to you?

To answer your questions:
1,2) Three NICs on each Host, one for public, one private (cluster), one
iSCSI. Only Public has Virtual Machine Network Services enabled.
3) The same Virtual NIC wasn't attacked to both, as noted above. I think
that was my issue.

[guest]

I would like to suggest that you install the
hotfix below and see if the issue still exists:

The Virtual Server service may stop responding when the service is starting
if one or more of the virtual machines are configured to automatically
start when the Virtual Server service starts
<http://support.microsoft.com/kb/941125/en-us>