Hey everyone,
Please checkout our NEW VMware User’s Group for the Baton Rouge, Louisiana area: http://www.brvmug.org - This is an officially sponsored Group by VMware. We’ll have having regular meetups, involving vendors, sponsors, etc. — So please check it out.
Thanks,
Will
Let’s just say first: I VMware vCloud Director ROCKS! I have been using it for about 2 weeks; and, this product is going to make IT administration/automation really easy…
However, here is one of the issues that threw me off when trying to login to my newly created vCloud VM guest:
Problem: I cannot login into the OS (Linux, Windows, etc) of my newly created VMware vCloud guest.
Solution: By default, when a new vCloud Director VM is provisioned, the default “administrator” or “root” user ID is auto-generated by vCloud Director. This is part of the VM guest’s customization settings after provisioning. You can find the new password by choosing the properties on the new guest. Make sure you go to the properties of the VM guest — and not the vApp. See Below:
Hope this helps…
Thanks,
Will
http://twitter.com/wsellers
http://communities.vmware.com/people/wsellers
Last week I was having problems creating a Provider vDC in VMware’s vCloud Director… Here’s the error I was getting
Even though the installation was followed step-by-step from documentation, I was still getting this error… After working with VMware Cloud Technical Support, we were able to resolve the issue. The problem is that when I initially named the VCD System Name I gave it the “exact” name of the VM guest running VCD.
The VCD Installed ran fine — and the installation was successful, — with the exception of errors when creating Provider vCD’s.
So, when you are naming your vCD, give it a unique name—- that will never conflict with the name of a VM guest that exists — or would ever exist…
I will post an update here— once the VMware KB article is created and published.
Happy vClouding,
Will
Here’s a handy PDF, showing a step-by-step procedure for resizing the “/” root partition on a Linux VM guest. Please note, that the guest was running a Red Hat based OS.
http://www.lavmug.org/wp-content/uploads/2010/04/Resize-root-partition-with-LVM.pdf
Thanks,
Will
Checkout this great VMware Communities Podcast, regarding ESXi — hosted by @jtroyer. Here’s the links for DOWNLOAD and to LISTEN NOW.
John Troyer (http://twitter.com/jtroyer) runs the VMware Communities Podcast at: http://www.talkshoe.com/tc/19367 – Please stop by and participate in these live podcasts, hosted at Talkshoe.
Enjoy,
Will
Greetings,
In order to better maintain this site, we’ve moved to a new web/blogging software. Please be patient while we update the site back to a usable format. If you are interested in participating in this site, please login with a new account you create here — or use the facebook connect feature.
Thanks for your patience,
Will
Thanks,
Will
I’ve found that from time to time, “Deploy virtual machine from this template” will be grayed-out and prevents me from deploying a new VM from template.
This is a known issue: http://www.vmware.com/community/thread.jspa?threadID=51923&start=0&tstart=0
Quick fix:
Right click on your orphaned template
Select “Remove from Inventory”
From the host you would like the template to reside on…
Select you host
Select the “Configuration” tab
Select “Storage” under the Hardware pane
Double click on the storage device in the right pane..this will bring up the “Datastore Browser”
Browse to your orphaned template’s location
Right click on the template file..it will have a “.vmtx” extention with the Type displayed as “Template VM”
Choose “Add to Inventory”
Go through and answer the wizard information to complete the “fix”
Thanks,
Will
I’ve run into an issue where from time to time, Red Hat Linux servers will start getting the following errors at console: “EXT3-fs error (device sdxx) in Start_transaction: Journal has aborted” This is due to an issue with the scsi driver and the file system becoming read-only.
Here is a link to a VMware KB article that fixed my problem:
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=51306
Here is a link to the patch:
http://ftpsite.vmware.com/download/RHEL4mptscsiRPM/mptscsi-rhel4gos-3.02.62.01-0vmw.i386.rpm
I would say it is best practice to patch your Linux servers at install time.
Thanks,
Will
