One of cloud doesn't work in failover with Event ID 1205 and 1069 and unable to move services and application another node

Question

Any one please respond.
I've been working on creating a windows server 2008 R2 cluster for about a month now and I keep getting an error whenever I try to add a 2nd node. I keep
getting The cluster node is not reachable. However, when I validate the configuration, everything goes through success. I created and destroyed the cluster a couple of times, but no luck. I even re-installed Windows Server 2008 R2 on both servers, re-configured
the iSCSI, and the same warning keeps coming up. 
I installed a new a new SQL Server 2008R2 Named Instance on an exisiting SQL Server cluster node (Node 1 &Node2). When I try to manually fail
over 
the Services and applications  to another node (Node1 to node2) using Failover Cluster Manager, I get the errors
The cluster has these Events:
Event ID
1069: Cluster resource 'IP Address xx.xx.xx.xx' in clustered service or application 'ClusterDtc' failed.
Event ID 1205:The Cluster service failed to bring clustered service or application 'ClusterDtc' completely online
or offline. One or more resources may be in a failed state. This may impact the availability of the clustered service or application..
Why the cloud server doesn’t move to node2? you can see screen shorts below.
1.
in system configuration-
3. in
system configuration---->warning--->Validate All Drivers Signed
after creating cluster I got below errors.
Any info you might know would be really helpful.

Answer 1

Dear Ravikumar
From clone support they given reply mail...
mail from Ramu...
That would be a typical work around in this situation. But what we intend to do cannot be accomplished through this work around as we need the validations to complete successfully.
 We are looking for an option either to get the driver signed or use a different signed adapter for the same. Could you please suggest us something on that line. 
Mail from Support....
Hello,
Unfortunately this is not something that we would be able to do in a virtual environment; You are welcome to try different drivers however we would not be able to provide any support 
for untrusted drivers. The only true solution would be to upgrade from a VM to a dedicated server where you would have control of all the drivers as there is no virtualization layer to
 contend with. Stepping into the territory of untested drivers for a custom configuration in a virtual environment will certainly prove to be an uphill battle.
 I would advise contacting Microsoft's support for additional assistance as they will be able to provide the most accurate information regarding this concern. 
Regards
Systems Administrator