pkvmw's Posts

No. not supported - see the interoperability matrix: https://interopmatrix.vmware.com/#/Interoperability?isHideGenSupported=true&isHideTechSupported=true&isHideCompatible=false&isHideIncompatible=fal... See more...
No. not supported - see the interoperability matrix: https://interopmatrix.vmware.com/#/Interoperability?isHideGenSupported=true&isHideTechSupported=true&isHideCompatible=false&isHideIncompatible=false&isHideNTCompatible=false&isHideNotSupported=true&isCollection=false&col=2,3457&row=1,3495,4275,5087
"Storage Accelerator" is not a vSAN feature - it's a Horizon feature which caches VM data to reduce the load on the storage under high boot-storms or so: see https://docs.vmware.com/en/VMware-Horizon... See more...
"Storage Accelerator" is not a vSAN feature - it's a Horizon feature which caches VM data to reduce the load on the storage under high boot-storms or so: see https://docs.vmware.com/en/VMware-Horizon-7/7.13/horizon-console-administration/GUID-FE046913-1555-4957-9EBD-B0FF86AC6525.html This feature caches VM data in RAM, but I'm not sure how big the memory pool is. That's being set on Horizon. As you mention instant clones: Horizon makes a template and a replica when a Desktop Pool is created. Then the replica (IIRC) of the golden image is put into RAM to allow the quick creation of VMs, as it simply duplicates the VM in RAM. So, might the load just come from ESXi, Storage Accelerator and the fact you have Instant Clones? How many RAM does your golden image have? Regards, Patrik
Hi @actyler555. From a personal perspective I can totally understand your frustration - I really do. But being basically a small wheel in GS, there's not really much I can do nor change. I leave that... See more...
Hi @actyler555. From a personal perspective I can totally understand your frustration - I really do. But being basically a small wheel in GS, there's not really much I can do nor change. I leave that up to other people here at VMware. I'm just reading and writing in the forums here and there, trying to help in my free-time when possible. Feel free to communicate your thoughts to your TAM or other appropriate channels you might have. Can't be of more help in this regard - sorry! Regards, Patrik
The update is on the way.  The release notes for VMware ESXi Update 7.0 U2c - with the sdcard-issue fixed - already were published: https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-esxi-70u... See more...
The update is on the way.  The release notes for VMware ESXi Update 7.0 U2c - with the sdcard-issue fixed - already were published: https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-esxi-70u2c-release-notes.html Also: https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-vcenter-server-70u2b-release-notes.html https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-esxi-vcenter-server-7-vsphere-with-tanzu-release-notes.html  
Just a few hours away!  The release notes for VMware ESXi Update 7.0 U2c - with the sdcard-issue fixed - already just has been published: https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-es... See more...
Just a few hours away!  The release notes for VMware ESXi Update 7.0 U2c - with the sdcard-issue fixed - already just has been published: https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-esxi-70u2c-release-notes.html Also interesting bits: https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-vcenter-server-70u2b-release-notes.html https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-esxi-vcenter-server-7-vsphere-with-tanzu-release-notes.html  
The release notes for VMware ESXi Update 7.0 U2c - with the sdcard-issue fixed - just has been published: https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-esxi-70u2c-release-notes.html Also... See more...
The release notes for VMware ESXi Update 7.0 U2c - with the sdcard-issue fixed - just has been published: https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-esxi-70u2c-release-notes.html Also: https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-vcenter-server-70u2b-release-notes.html https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-esxi-vcenter-server-7-vsphere-with-tanzu-release-notes.html    
Do you have vSAN running? Is Storage Accelerator (in Horizon) enabled (if so, how much memory is set there?)?
Okay, so you've installed ESXi U1c with Cisco's customized image and you're trying to update via VLCM. Understood. By any chance, have you opened a SR on this issue? (NOT saying you should, just won... See more...
Okay, so you've installed ESXi U1c with Cisco's customized image and you're trying to update via VLCM. Understood. By any chance, have you opened a SR on this issue? (NOT saying you should, just wondering if you did)
That's most likely one of the reasons we in GS are not allowed to provide dates when specific releases come out. The patch was re-scheduled from July to a later date, which is not far away anymore. A... See more...
That's most likely one of the reasons we in GS are not allowed to provide dates when specific releases come out. The patch was re-scheduled from July to a later date, which is not far away anymore. Also there's a Patch Release (P03) coming out - NOT an update, which also leads to some confusion from what I've heard.
What does exactly your update path look like? Are you updating from Plain/Vanilla ESXi 7.0 U1 with a Cisco Image? And to which exact version you want to update to? (to 7.0 U1d?)
An alternative would be: 1. Taking a configuration backup of ESXi 2. Reinstall ESXi with the same build version on the SSD 3. Restore the configuration backup To backup and restore the configurat... See more...
An alternative would be: 1. Taking a configuration backup of ESXi 2. Reinstall ESXi with the same build version on the SSD 3. Restore the configuration backup To backup and restore the configuration see https://kb.vmware.com/s/article/2042141
Hi, 7.0 Update 3 will take longer time, as it's a bigger release than just a patch. However the SD-card fix you're looking for will be in the next upcoming patch release, which comes before Update 3... See more...
Hi, 7.0 Update 3 will take longer time, as it's a bigger release than just a patch. However the SD-card fix you're looking for will be in the next upcoming patch release, which comes before Update 3. As official release dates are not publicly communicated, please be a bit patient. Thanks. Regards, Patrik
Hi, I'd kindly ask you to provide more background, questions or notes for your log excerpts in the future. IMHO it's not really polite to quickly just throw a few log lines in a forum and letting ev... See more...
Hi, I'd kindly ask you to provide more background, questions or notes for your log excerpts in the future. IMHO it's not really polite to quickly just throw a few log lines in a forum and letting everyone, who's replying in their free-time, to guess what you want to tell us. From what the messages tell I guess you want to deploy/create some YAML files for using it for a GitLab CI. The WCP/SupervisorCluster is not intended for this and best-practise (and the only way to get this working) is to deploy a TKC/GuestCluster for this. See: https://docs.vmware.com/en/VMware-vSphere/7.0/vmware-vsphere-with-tanzu/GUID-B1034373-8C38-4FE2-9517-345BF7271A1E.html Regards, Patrik  
Hi @LuisjaEve , yes, that's normal. The SupervisorCluster/WCP (basically where you deploy vSphere Pods) has some restrictions and doesn't allow changing everything as you could do in "normal" Kubern... See more...
Hi @LuisjaEve , yes, that's normal. The SupervisorCluster/WCP (basically where you deploy vSphere Pods) has some restrictions and doesn't allow changing everything as you could do in "normal" Kubernetes clusters, and this is intended. The SupervisorCluster is used to deploy so called TKC (Tanzu Kubernetes Cluster) or also known as "Guest Cluster", where you have a fully Kubernetes-compatible cluster. In this TKC you can do whatever you want to, also changing clusterroles or rolebindings as you wish. Creating TKCs is also best-practise. You can find more information how to deploy TKCs here: https://docs.vmware.com/en/VMware-vSphere/7.0/vmware-vsphere-with-tanzu/GUID-B1034373-8C38-4FE2-9517-345BF7271A1E.html Hope this helps! Regards, Patrik @vcitrainer Based on your very limited log excerpt https://communities.vmware.com/t5/VMware-vSphere-Discussions/vSphere-With-Tanzu/m-p/2860677/emcs_t/S2h8ZW1haWx8Ym9hcmRfc3Vic2NyaXB0aW9ufEtSWENaQVE4QlRFR0dLfDI4NjA2Nzd8U1VCU0NSSVBUSU9OU3xoSw#M39876 you have a different issue.
Hi, as you correctly noticed, ESXi 7.0 requires a new license key and a ESXi 6.x license key does not work. When you upgrade an activated ESXi 6.x installation, the license key will be removed and t... See more...
Hi, as you correctly noticed, ESXi 7.0 requires a new license key and a ESXi 6.x license key does not work. When you upgrade an activated ESXi 6.x installation, the license key will be removed and the ESXi will continue in evaluation mode. So in any way, you either need to stick with ESXi 6.x or get a new license key for ESXi 7.0. Regards, Patrik
@hlo58 Unfortunately I don't remember which version caused this particular behavior nor to which version the customer updated their ESXi's to solve the issue. The latest 6.7 U3 release however should... See more...
@hlo58 Unfortunately I don't remember which version caused this particular behavior nor to which version the customer updated their ESXi's to solve the issue. The latest 6.7 U3 release however should be fine. (Which might be recommended due to security fixes anyway)
Hi, for vSphere 6.0 the "General Support" ended on 12nd of March of 2020 and does not receive any security patches or bug fixes. So concerning the lack of security updates and therefore unpatched se... See more...
Hi, for vSphere 6.0 the "General Support" ended on 12nd of March of 2020 and does not receive any security patches or bug fixes. So concerning the lack of security updates and therefore unpatched security vulnerabilities, ransomware mitigation (with this specific option) for your ESXi 6.0 hosts are most likely your least problems. The "End of Technical Guidance" is already in March 2022. You might want to update your hosts as soon as possible to be fully supported and receive security updates. See more here: https://lifecycle.vmware.com/ https://www.vmware.com/support/policies/lifecycle.html And as the Veeam newsletter notes, the option is not supported for vSphere 6.x. So you can try it on your ESXi and check if it works. If so, then you're lucky. Regards, Patrik
@scott28tt @paulvz  For ESXi 5.0 the "End Of General Support" was 24th of August 2016, where "End of Technical Guidance" ended on 24h of August 2018. There is no support provided for this very old r... See more...
@scott28tt @paulvz  For ESXi 5.0 the "End Of General Support" was 24th of August 2016, where "End of Technical Guidance" ended on 24h of August 2018. There is no support provided for this very old release anymore, hence no official support is provided anymore. So I'd recommend getting newer, supported hardware and ESXi version. @paulvz Also you might want not to post internal hostnames in a public community forum. What is the missing datastore and how was it presented to the ESXi host? If it was via iSCSI, I'd recommend checking the iSCSI configuration from the ESXi host as well as from the storage underneath.
Hi @DerekPease , the error occurs during the upgrade pre-check and also doesn't allow to proceed, hence there's no real destination VCSA at this point. So to answer your question: You'll need to cha... See more...
Hi @DerekPease , the error occurs during the upgrade pre-check and also doesn't allow to proceed, hence there's no real destination VCSA at this point. So to answer your question: You'll need to change the PNID/FQDN on the source VCSA, before initiating the upgrade. Regards, Patrik
Hi, Enable EVC by doing: 1. Shutting down all VMs in this cluster 2. Enabling EVC in the cluster settings 3. Startup all VMs and add new hosts Regards, Patrik