VMware Cloud Community
KSALinville
Contributor
Contributor
Jump to solution

What happened to KB 2151749?

I noticed this morning that the KB article titled "ESXi host fails with PSOD after upgrading to 6.5" is blank/missing.  Has this issue been resolved?  Was it some sort of false positive?  Can we stop being worried about upgrading our hosts to ESXi 6.5 Update 1 even if they have 10Gb NICs in them?

Here's the link to the original KB:

https://kb.vmware.com/kb/2151749

Thanks!

1 Solution

Accepted Solutions
Finikiez
Champion
Champion
Jump to solution

Hi!

It could be marked as internal only. Usually this happens when VMware has to verify solution or edit article itself.

You need to contact VMware support to get clarification on this.

View solution in original post

Reply
0 Kudos
7 Replies
Finikiez
Champion
Champion
Jump to solution

Hi!

It could be marked as internal only. Usually this happens when VMware has to verify solution or edit article itself.

You need to contact VMware support to get clarification on this.

Reply
0 Kudos
rcporto
Leadership
Leadership
Jump to solution

The KB is available for me, see:

kb2151749.JPG

---

Richardson Porto
Senior Infrastructure Specialist
LinkedIn: http://linkedin.com/in/richardsonporto
Reply
0 Kudos
KSALinville
Contributor
Contributor
Jump to solution

I guess they were just updating it... it is back now.

Reply
0 Kudos
suhaakin
Contributor
Contributor
Jump to solution

kb is updated now.

Reply
0 Kudos
Peter32
Contributor
Contributor
Jump to solution

Are there any news on this post ?


Thanks

Peter

Reply
0 Kudos
Finikiez
Champion
Champion
Jump to solution

KB is available, opened it successfully.

Reply
0 Kudos
jsprinkleISG
Enthusiast
Enthusiast
Jump to solution

The article definitely needs some more precise details.

They've removed "Update 1" from the KB title, which indicates the issue is not specific to Update 1.

pastedImage_0.png

Also, in the Resolution section, it lists "Downgrade ESXi to 6.0 U2" as a workaround. This is additional confirmation the issue is known to exist in 6.5 prior to U1. The presence of "U2" here makes me wonder if the issue also exists in ESXi 6.0 U3, although there's nothing else to indicate that.

pastedImage_1.png