Adjusting the amount of hostd log files

There was a question posted on the VMware Community Forums regarding the ability to increase the number of hostd log files.  Here is the solution I provided:

To change the max amount of log files for hostd you will need to edit /etc/vmware/hostd/config.xml. In the file you will find the following section:

   <log>

      <directory>/var/log/vmware/</directory>

      <name>hostd</name>

      <outputToConsole>false</outputToConsole>

      <level>verbose</level>

   </log>

You will want to add <maxFileNum>numberLogs</maxFileNum> like so:

   <log>

      <directory>/var/log/vmware/</directory>

      <name>hostd</name>

      <outputToConsole>false</outputToConsole>

      <level>verbose</level>

      <maxFileNum>10</maxFileNum>

   </log>

Your logs, however, should have multiple gzipped versions or rotated logs in /var/log/vmware. You will probably see /var/log/vmware/hostd-#.log.gz in there. If you do then you can view those logs with the following command:

# zless /var/log/vmware/hostd-1.log.gz

VCP-410 Study Guide Posts

As I start gearing up for my VCP-410 exam I decided I would post my progress and information regarding each objective as I go through them.  I know that there is plenty of information online for others but would it really hurt to see more?  My hopes are that I can get this information out for others who will be attempting their VCP-410 exams soon as well.  I hope that everyone will find this information useful!  Look for the first objective posts to come this weekend as I sit down and run through Objective 1 for the VCP-410!

vCenter 4.1 and SQL Express Gardening

Cody Bunch over at ProfessionalVMware posted yet another good article for us vGeeks.  I, personally, have not run into this yet but I imagine I will soon.  Cody ran into an issue where the vCenter service wouldn’t start…

Last night, I ran into an issue where the vCenter service would not start, in fact, it was quite angry.

Click over to the article and check out the issue, the resolution…make notes…put Post-Its all over your monitor with this information!  :)

Sourced from: ProfessionalVMware.com

Holy VMFS3 Batman!

“Robin, go carve me out a new LUN for our new Batworks Monitoring System!”, says Batman.  Robin replies, “It is ready for you Batman, let’s get monitoring the Batwork.”

**POW** **BOOM**  **SPLAT**

My P2V has failed…”Failed to create virtual disk: There is not enough space on the file system for the selected operation.” What will Gotham do now!?!?

I am sure that many of you have run into the issue where your Storage Guy gives you a new LUN and you create a VMFS datastore and find out you somehow don’t have enough space.  Although, you know for fact that you were given 1TB or more on the LUN.  What happened?

Well, a lot of people tend to click right on through accepting any and all defaults that are presented to you.  One thing you missed was the wonderful block size selection.  You are presented with the Disk/LUN Formatting section and you see you actually had choices you could make:  small (1MB), medium (2MB), large (4MB), and super size (8MB).

If you were presented with 1TB then you would need to make sure that you select the appropriate block size to enable the use of that ever-so-expensive disk space.  For example-sake, if you need to provision a VMFS datastore of a size less than 256GB you need to select 1MB blocks, if you need to provision 512GB then use 2MB blocks, 1TB would require at least 4MB blocks, and 2TB requires 8MB blocks.

Now one asks, “Why and what causes this?”

The answer is simple…filesystem limitations of VMFS3.  Word has it that VMFS4 will not have these limitations.  It will supposedly follow ext4 limitations which enable 16TB.  Sound off in the comments regarding your thoughts and experiences with VMFS3 and the future of VMFS!

« Previous Entries Next Entries »