Unsolved
This post is more than 5 years old
3 Posts
0
2676
October 28th, 2011 21:00
vWorkspace VMWare linked clones dvSwitch issue
Hello,
I'm experiencing an issue with vmware linked clones and our dvswitch. When creating vmware linked clones in a pool all of our linked clones are not connected to the dvswitch. I've set the port group that the master vm is attached to "Ephemeral - no binding". I've also installed MR1 for vWorkspace 7.2 on all of our connection brokers located here https://support.quest.com/Search/SolutionDetail.aspx?ID=SOL75656 which descibes fixing a similar problem with ESX 4.1 (defect ID 150465) but it still isn't working.
The vm that these linked clones are being generated from has no issue connecting to the portgroup and getting an ip address from dhcp.
Any help would be greatly appreciated. Thank you.
DELL-David Y
228 Posts
0
November 2nd, 2011 10:00
Hello Joseph,
I have been looking further into the problem that you have detailed. We have discovered, since releasing vWorkspace 7.2 MR1 that the fix for defect ID 150465 did not fully correct the problem. I can provide you with an updated dll that will correct the issue, can I ask you to open a support case so that I can send you the file.
Best Regards
David
nykad
3 Posts
0
November 2nd, 2011 15:00
David,
Great news. I already opened a support case with tech support and have been working with them the last couple of days on this...no progress. Case number is: 970455. Thank you!
nykad
3 Posts
0
November 3rd, 2011 16:00
Just a follow up on this issue if anyone else is experiencing it. I recieved the latest PNVmLinkedClone.dll from tech support and the problem worsened. I can now no longer create linked clones from vWorkspace 7.2 at all now. Under tasks it just says "in progress" and it eventually just times out and hangs there.
DELL-David Y
228 Posts
0
November 15th, 2011 13:00
Thanks Jose,
After our webex yesterday I already put a note in the support case that Joseph has open with us to notify the other engineer of this test fix.
Regards
David
josegerez1
12 Posts
0
November 15th, 2011 13:00
Hello Joseph,
We had the same issue and yesterday support has provided a hotfix that solved the problem. The file name is Hotfix150483_x64_72MR1.exe.
Maybe you could request this file to your support engineer?