![vmware 6.0 image profile vmware 6.0 image profile](http://docs.cloudstack.apache.org/en/4.14.1.0/_images/vmware-nexus-port-profile.png)
#Vmware 6.0 image profile software
The root cause is a specific version of the elxiscsi Emulex driver, but the doc says only when you enable the hardware or software iSCSI. To resolve this issue, see VMware vSphere 6.5.x on Dell EMC PowerEdge Servers Release Notes. Changing the ScratchConfig.CurrentScratchLocation does not persist between reboots.Recommended scratch partition size is MiB.” ( = /scratch/log). You see these warnings: System logs on host are stored on non-persistent storage.And No scratch partition has been configured.
![vmware 6.0 image profile vmware 6.0 image profile](https://vmblog.ru/wp-content/uploads/2019/03/word-image-12.jpeg)
The ScratchConfig.CurrentScratchLocation is set to /scratch.If you are using the Dell EMC Customized image ESXi 6.5 A04 (but I’ve got the same issues with other Dell’s customized images, still with 6.5), after upgrading or also installing the ESXi host, you experience these symptoms: VMware KB 2151209 (ScratchConfig.CurrentScratchLocation is set to /scratch after upgrading to ESXi 6.x) describe this issue, with a tricky and not always easy solution. The second issue is specific only for ESXi 6.5 and only with Dell customized ISOs. To work around this issue, follow the steps provided in KB 2003322 (Configuring syslog on ESXi) and configure the advanced setting with a datastore in the format: DirectoryName. The default value of ScratchConfig.CurrentScratchLocation is /tmp/scratch. In this case the advanced setting ScratchConfig.ConfiguredScratchLocation for persistent scratch location is reverted to the default value after ESXi 6.x host reboot. The first issue is described in KB 2151270 (“ScratchConfig.ConfiguredScratchLocation” for persistent scratch location is reverted to the default value after ESXi 6.x host reboot) and it’s related both to ESXi 6.0 and 6.5 and actually it hasn’t yet a resolution.
#Vmware 6.0 image profile install
If you install ESXi on a USB connected mass storage (like the SD cards), then this partition is usually skipped and the ramdisk will be used instead.īut with ESXi 6.5 there are some issues on how scratch will be managed. If you install ESXi on a local hardware disk (or also if you are using a remote LUN in “boot from SAN” mode), this partition is built during the installation phase (it’s 4 GB Fat16 partition created on the target device during installation, if there is sufficient space). Scratch space is configured automatically during installation or first boot of an ESXi host and is not required to be manually configured. In the VMware ESXi 6.x partitions layout, usually, there is a partition called “scratch” that hosts the log, the updates, and other temporal files.