I have my ESXi hypervisors upgraded to 6.5.0 update 1 build 7526125 and it seems this has been redacted?
Is this a bad patch?
-Thanks
VMware released KB article https://kb.vmware.com/s/article/52345 for details about this.
André
VMware released KB article https://kb.vmware.com/s/article/52345 for details about this.
André
6.5.0 update 1 build 7526125 and it seems this has been redacted?
Yes, ESXi 6.5 U1e Builds number 7526125 has been Released on 2018-01-09.
Is this a bad patch?
This ESXi patch provides part of the hypervisor-assisted guest remediation of CVE-2017-5715 for guest operating systems. For important details on this remediation, see VMware Security Advisory VMSA-2018-0004
more information see below KB
Regards,
Randhir
If you found my answers useful please consider marking them as Correct OR Helpful
Yes, I am aware of it being released on 2018-01-09. I installed it on my ESXi hypervisors that same day. I wanted to find out because I have had some problems since the patch and now the site https://esxi-patches.v-front.de/ESXi-6.5.0.html has removed the patch listed.
I know the site is not official. But wanted to ask the community if it knew anything around this build.
Did you see my previous post?
André
I think the ESXi-6.5.0-20180104001-standard may have been redacted. I can't install it from a terminal. I get a response from the server "no image profile found". I even went into the logs of my ESXi 6.5 servers that I previously installed the patch on 2018-01-09 and made sure the name was correct.
the ESXi-6.5.0-20171204001-standard is the latest I am able to install.
The commands I used
This does not find the 2018-01-09 patch
esxcli software profile update -p ESXi-6.5.0-20180104001-standard -d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml
This is for the 2012-12 and it worked.
esxcli software profile update -p ESXi-6.5.0-20171204001-standard -d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml
Do I understand correctly that edit config file and restart every VM and after that it will be works?
I use 6.5
Yes. And this whole ordeal is a huge mess, not just for VMWare but everyone