VMware Cloud Community
Gr33nEye
Enthusiast
Enthusiast

Experience with 6.7U1 ?

Hi,

Just after some peoples feed back. Has anyone done the 6.7U1 update? Any issues yet or bugs?

Reply
0 Kudos
11 Replies
GayathriS
Expert
Expert

I haven't heard much bugs on 6.7 u1, probably going forward we may.

However release notes is the best one to get a glance of issues which are fixed and known issues with 6.7 u1 as well:

https://docs.vmware.com/en/VMware-vSphere/6.7/rn/vsphere-vcenter-server-671-release-notes.html

regards

Gayathri

Reply
0 Kudos
MikeStoica
Expert
Expert

In case you have Veeam Backup, there were reported some issues.

Reply
0 Kudos
Gr33nEye
Enthusiast
Enthusiast

I've had a read through the release notes. I was just after more of a first hand experience. How did the upgrade go, any cert issues, services not starting up, or ect.

MikeStoica

I thought that bug was in 6.5U2 and the 6.7U1 was supposed to include the fix. Are you talking about where it crashes the host/proxy?

Reply
0 Kudos
MikeStoica
Expert
Expert

Reply
0 Kudos
cernyj
Enthusiast
Enthusiast

Hello, if you had 6.7 without issues, than U1 will be ok.

There is one really nasty bug for 6.7:
https://kb.vmware.com/s/article/55650

VMware Knowledge Base

Sadly it looks like unresolved id 6.7 U1. Discussed here:https://www.reddit.com/r/vmware/comments/9mpqrz/psa_dont_upgrade_to_esxi_67_if_you_are_using_vsr/

https://www.reddit.com/r/vmware/comments/9mpqrz/psa_dont_upgrade_to_esxi_67_if_you_are_using_vsr/

ESXi 6.7 kernel panic during Heap_Free in dlmalloc

ESXi 6.7 Keep Getting PANIC bora/vmkernel/main/dlmalloc.c: 4924 - Usage error in dlmalloc

I'm waiting for answer form support, but as gun on Reddit said, fix is planned to U2.

So if you are using vSphere replication, you have to stay on 6.5 series.

Reply
0 Kudos
Gr33nEye
Enthusiast
Enthusiast

cernyj

That looks fun. There was no mention on VC version though. Would it be safe to assume that there is no issue if only the VC is only 6.7.

Reply
0 Kudos
cernyj
Enthusiast
Enthusiast

Problem is, probably, only with ESXi. So you can have vCenter 6.7(U1), latest vRA and SRM (8.1), but for smooth errorless replication you have to stay on ESXi 6.5U2.

From my experience, PSOD happens only if replicating large VM (about 2TB of disks, but I have to do more testing to find out details which configuration causes the crash). But I am not able to verify my presumptions on production HW and VM with our company ERP system.

What I know, it's:

- not related to HW vendor, our systems are Huawei, but I know about guys with same problem on HP and Dell servers

- maybe something with Qlogic FC HBA's; support doesn't want to confirm that's replication problem only

Reply
0 Kudos
Gr33nEye
Enthusiast
Enthusiast

For the moment we have no plans to upgrade the hosts to 6.7+ so it would only be the vCenter. We do have a large number of VM's with individual disks larger than 2TB. It would definitely be good to know if the mix of vC 6.7,vRA 8.1 and 6.5 hosts would cause the issues.

VMware's KB on this is rather vague on the cause of the PSOD ,there is no mention that it is caused by replication action. If we contact VMware, will they know about this issues?

Reply
0 Kudos
cernyj
Enthusiast
Enthusiast

Yes, they know.

I have info from them, that they have problems with reproducing this issue in their lab.

They recommended me to use ESXi 6.5.

So it's hypervisor related bug, so combination vC 6.7, vRA 8.1 and ESXi 6.5 shoud be stable.

Reply
0 Kudos
Howiedog
Enthusiast
Enthusiast

Hey...I have just installed 6.7U1 and now this post says its NOT READY EITHER? Maybe U2?? OMG.

VMware should really get out of the toilet buisness.

Not only that....I cannot even find the "reboot" "shutdown" button for this appliance.?? Where did VMware hide this?

or can I NOT reboot vcsa67u1 from the web client?

Reply
0 Kudos
daphnissov
Immortal
Immortal

Not at all hard to find.

pastedImage_0.png

Reply
0 Kudos