vxprthu's Accepted Solutions

Hi,  There was significant file system changes in vSphere 7. If you are using SD card or USB key for boot, you need to provide additional HDD / SDD disk for the ESX-OSDATA partition, which usually contains the ROM data (coredumps, configs etc...) I this case the OS DATA partition should be extended or additionally created on physical disk device. More info here: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.esxi.upgrade.doc/GUID-474D003B-C6FB-465D-BC1B-5FD30F8E2209.html https://kb.vmware.com/s/article/77009?lang=en_US If you don't want to see the warning, it can be disabled by this: Select the ESXi Host >  Click Configuration > Advanced Settings Search for UserVars.SuppressCoredumpWarning Then locate the string and and enter 1 as the value  Cheers,

Hi All, We are talking about different things. What we have here is 3 different layer: 1, Guest os 2, vmdk 3, storage lun To reclaim unused space the following order should be followed: 1, If you delete something in the guest os, that something will be deleted only logically. Your guest os will be aware about those logically deleted items but on vsphere level its invisible. That is why necessary to write zeroed out all the unused blocks. In windows vms, this could be the sdelete command. Once its complete, and the deleted/unused space is zeroed, then we can jump to point 2. 2, Shrink the vmdk: this can be happen with the vmkfstools. 3, Once vmdks are shrinked or in other cases deleted, can the lun reclaim the space on storage level, this is called unmap. With vmfs v6 unmap can be automated but also there are esxcli commands to do that. Now. if you have thin disk then its maximum size cannot be larger (just a little bit) than what you set.  If you create a think disk as large of 700GB, then it is its maximum size. The initial size could be between 0-700. Of course if you utilize all of the space then its will be 700gb at the beginning. Regards,        

HI,) It's my bad, i wasn't clear. You need to edit /etc/vmware-syslog/syslog.conf instead of rsyslog.conf Where i said @Syslogserversip:port; you have to update to yours (if it's not already there, but im sure its there.) Probably you will see something like this in /etc/vmware-syslog/syslog.conf:       *.* 192.168.1.1:514;RSYSLOG_SyslogProtocol23Format       and that needs to be updated to this one:       *.warn;*.err;*.crit;*.alert 192.168.1.1:514;RSYSLOG_SyslogProtocol23Format       Then reboot rsyslog service. And don't forget to change back the rsyslog files to their original one. Cheers,    

HI @gmerideth  If i understand correctly the VMs are powered off, when they didn't use the VMotion network right? The migration of powered off vms called as cold migration. By default the data for cold migration, snapshots or cloning are using the management interface. This traffic called provisioning traffic. You can have dedicated interface(s) for provisioning traffic, then that interface will be used. Regards,  

If the vibs are not in use (you can check based on the KB), they can be removed, then continue the installation, but they may have further dependencies..   However if you are not aware about the source, then you could try do download the latest HP custom iso and update with that. If you have the same result (vib dependencies), then I recommend to reinstall the host due the missing drivers which are required for the specified hardware.