Posts Tagged ‘vSphere’
Each time a VM is powered on, a new log file is created in the main directory of the VM. These files all have a ".log" extension and the active log file is named vmware.log (though this can be defined in the VMX configuration file.)
VMware records the key events affecting each VM in the log files.
At VM start, the oldest log file is deleted, the vmware.log file is renamed by appending a "-##" sequence and a new vmware.log file is created. For example, here are some of the files in a VM before starting. Note the vmware.log file has a size of 487,490 bytes and is date stamped Jun 18.
The VM is started and you can see that the old vmware.log file is now called vmware-19.log. Also, vmware-13.log is gone.
If we restarte the VM, the same thing happens: vmware-14.log is gone and a new one is begun.
You can find more about VMware files that make up a VM at this link.
Running SBS 2008 migration on a virtual server takes us on a detour down memory lane
Working on a migration of Windows Small Business Server (SBS) 2003 to SBS 2008, I had jumped thru the previous 283 migration hoops (I exaggerate, but just a little) and was ready to boot the 2008 installer DVD with my handy SBSAnswerFile which Microsoft wants me to put on “…the root of a USB drive, floppy disk or a partition on the destination server.” Hmmm….
– USB drive is a no-go on the ESX server.
– Let’s put it on a 2nd virtual hard disk. No, the migration installer didn’t “see” it.
– OK, let’s put it on a virtual CD drive. No. It didn’t see it again.
– Finally, I went to the extra hassle of putting it on a virtual floppy. Success!
The blow by blow follows: