HowTo

Host Disconnects from vCenter in a vCloud Director Environment

So I ran into an issue the other day regarding host disconnects within vCenter in a vCD environment.  SSH’d into the host and noticed right off the bat that vmkernel.log was showing the following error:

WARNING: VisorFSObj: 893: Cannot create file tmp:/current.png5557 for process vmx-mks:Cell Profiler x64 (b9d6aa64-d789-4954-bde9-f2875406c159) because the visorfs inode table is full. 2012-10-05T12:38:49.808Z cpu27:6014573)WARNING: VisorFSObj: 893: Cannot create file /etc/vmware/esx.conf.LOCK for process esxcfg-advcfg because the visorfs inode table is full.

And in hostd.log I saw this:

WARNING: VisorFSObj: 893: Cannot create file /etc/vmware/esx.conf.LOCK for process hostd because the visorfs inode table is full.
Continue reading “Host Disconnects from vCenter in a vCloud Director Environment” »

Can’t Remove vApp in vCD – Pending State

So I have run into a few issues where trying to delete a vApp with Partially Powered Off VMs live inside the vApp.  It seems to place the vApp and VM into a Pending state in vCloud Director.  When you attempt to run the delete again it says that you need to stop the VM first.  In your eyes you thought the VM was stopped but vCD seems to think otherwise.  You check in vCenter and see the VM is powered off so what now?

DISCLAIMER:  THIS WAS DONE IN A LAB ENVIRONMENT!  DO NOT ATTEMPT THIS IN PRODUCTION WITHOUT THE PROPER PRECAUTIONS!  IF YOU ARE NOT COMFORTABLE WITH DATABASE WORK THEN PLEASE STOP NOW!

Continue reading “Can’t Remove vApp in vCD – Pending State” »

Multi-Site vCenter Server Appliance Deployment

When sitting around today thinking about the grand scheme of things for my future state architecture, I was presented with a question from a co-worker about linked-mode.

Does the new 5.1 stuff allow for linked-mode in the appliance?

Knowing the short answer was easy, but explaining how it could be done now with SSO without “linked-mode” spawned a test in my home lab.  The test is to have more than one vCenter Server Appliance (VCSA) attached and manageable through the 5.1 vSphere Web Client.  In short, the answer is yes, it can be done.  Here is how:

You will first need to deploy another VCSA somewhere, in my case it was in my lab where my other VCSA was deployed.  Once the deployment of the OVF is done you will want to login to the VAMI by going to https://:5480.  Your initial login is, of course, root and the password is vmware.

Continue reading “Multi-Site vCenter Server Appliance Deployment” »

1 2 3 9  Scroll to top