Date: Tue, 01 May 2018 18:57:14 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 227906] emulators/open-vm-tools: vmguestd stops communicating with host randomly Message-ID: <bug-227906-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D227906 Bug ID: 227906 Summary: emulators/open-vm-tools: vmguestd stops communicating with host randomly Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: jpaetzel@FreeBSD.org Reporter: prj@rootwyrm.com Assignee: jpaetzel@FreeBSD.org Flags: maintainer-feedback?(jpaetzel@FreeBSD.org) Separate bug requested by John Wolfe. This build does not appear to fully address a repeating issue I have been running into. No error is reported by host or guest, but guestd appears to stop communicating, resulting in the classic 'VMware Tools Not Installed' message in vCenter. There isn't any cl= ear trigger, and restarting guestd seems to fix it.=20 Reproduces on three guests now, with the hosts running 6.5.0 7388607. This problem began with open-vm-tools-nox11-10.2.0 from portsnap and SVN, packag= es built on my in-house poudriere cluster and straight from ports. Since no cl= ear trigger has been found, it's VERY difficult to test port-build vs poudriere built package, but it has reproduced with both. Versions prior to 10.2.0 did not exhibit this behavior. This has occurred from about FreeBSD 11.1-RELEASE through -p11, exclusive to amd64 guests (I have not been able to reproduce on i386.) I had hoped to possibly find a commonality between guests such as high VMDK count or frequ= ent normal high CPU or RAM, but no such luck. It shows up on 1vC/1GB/2 VMDK as = well as 4vC/4GB/10 VMDK.=20 In all guests, bouncing vmguestd with /usr/local/etc/rc.d/vmware-guestd res= tart will resolve it temporarily. Sometimes vmware-kmod also needs a restart, ev= en though kernel modules are already loaded. 10.2.5 does seem to resolve it a = bit longer - about 24-36 hours - but 10.2.0_2,2 will lose communications again usually after a few hours (generally less than 4.)=20 All guests are using the same boot start in rc.conf: vmware_guest_vmblock_enable=3D"YES" vmware_guest_vmhgfs_enable=3D"YES" vmware_guest_vmmemctl_enable=3D"YES" vmware_guest_vmxnet_enable=3D"YES" vmware_guestd_enable=3D"YES" This does also occur with both open-vm-tools and open-vm-tools-nox11 so it's not related to any X components. Since there's no clear trigger and I can't reproduce at will, this has proven extremely difficult to debug. There are = no indications of problems on either guest or host side in the logs either. It just stops communicating. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-227906-7788>