Not able to open VM using console- connection attempt failed because the connected party did not properly respond

I renamed host which has been migrated from different location but after rename user were not able to connect to virtual machine using VC.
1. Disconnected and removed the host from Virtual Center. Restarted hostd and vpxd service.
2. I also connected the host directly using VC thinking that it might be VC issue but still it did not helped. I was getting error
“error connecting: can not connect to host x.x.x.x: a connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.”

I even rebooted host but still did not helped. Some were it was suggested to modify config file for host which worked for me

L ogin to ssh by i.e. putty, and edit the following line : /etc/vmware/config (type #nano /etc/vmware/config)

Add this following line : vmauthd.server.alwaysProxy = “TRUE” at the end of the file.
This resolved the issue

Another Milestone Implementing Harware ISCSI initiator HBA

Publish at Scribd or explore others: School Work How-to-Guides & Manu Books hardware ISCSI

Destination Exists,cannot overwrite

We were doing V2V for moving one vm from one esx host to other at the same time retaining the copy of it on source. We started getting error message “Destination Exists, Cannot overwrite”.

I checkedthe source host it exist there. I restarted service mgmt-vmware and tried it again . We got same error message.

I repeatedthe same steps for destination esx host but with no luck. For somereason convertor was thinking that VM got converted.

So I did V2V using different name ,which went fine. Once this V2V completed I rename the VM on ESX host using following

-bash: fork :resource temporarily unavailable

I was getting -bash: fork :resource temporarily unavailable on of the ESX host. I was not able to issue reboot/vmotion or anything with this ESX host.
I found huge memory error under hostd log

[2009-05-11 04:54:31.645 'Memory checker' 21138352 warning] Current value 127776 exceeds soft limit 122880.

[2009-05-11 04:55:01.664 'Memory checker' 126815152 warning] Current value 127776 exceeds soft limit 122880.

[2009-05-11 04:55:31.684 'Memory checker' 131939248 warning] Current value 127776 exceeds soft limit 122880.

[2009-05-11 04:56:01.702 'Memory checker' 37694384 warning] Current value 127776 exceeds soft limit 122880.

It was indication that service console is running out of memory. I checked my service console and it had 272MB. I looked at messages and found that HPSIM related messages.

I have recently deployed HPSIM on these ESX host. In the past I do know that HP SIM agent can create lots of problem

Deploying windows using MDT and WDS

For a while I was working on solution for deploying windows using WDS (Windows Deployment service ) and MDT (Microsoft Deployment Toolkit.). I came across many interesting issue everyday.
Like you should have desperate VLAN for server build purpose. Only this server should have "iphelper " enabled.

Going forward I will keep sharing my experience with MDT and WDS

Deploying server using MDT and WDS

Publish at Scribd or explore others: