Hi, After upgrading open-vm-tools to version 10.3.0-1, after every boot I get a notification that vmtoolsd has crashed. abrt can not file a bug report, saying that it can not process the problem: Server responded with an error: 'uReport data is invalid.' ('report_uReport' exited with 1) These are the only relevant lines that appear in my logs: Aug 05 00:29:53 audit[2025]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=2 subj=unconfined_u:unconfined_r:vmtools_t:s0-s0:c0.c1023 pid=2025 comm="vmtoolsd" exe="/usr/bin/vmtoolsd" sig=11 res=1 Aug 05 00:29:53 kernel: traps: vmtoolsd[2025] general protection ip:7f9f094e6bb0 sp:7ffd7228e328 error:0 in libvmtools.so.0.0.0[7f9f094b9000+8b000] Aug 05 00:29:54 systemd-coredump[2120]: Process 2025 (vmtoolsd) of user 1000 dumped core. #0 0x00007f9f094e6bb0 Backdoor_InOut (libvmtools.so.0) Aug 05 00:30:04 abrt-notification[2369]: Process 2025 (vmtoolsd) crashed in Backdoor_InOut()
It looks as if the coredump was captured by systemd-coredump, so you should be able to get a stack trace by doing: # coredumpctl list # coredumpctl gdb [ID] (gdb) t a a bt
Is this helpful? # coredumpctl gdb 2073 PID: 2073 (vmtoolsd) UID: 1000) GID: 1000 Signal: 11 (SEGV) Timestamp: Mon 2018-08-06 12:08:06 CEST (11min ago) Command Line: /usr/bin/vmtoolsd -n vmusr Executable: /usr/bin/vmtoolsd Control Group: /user.slice/user-1000.slice/session-2.scope Unit: session-2.scope Slice: user-1000.slice Session: 2 Owner UID: 1000 Boot ID: 525c399acb1c4bbe9008298b59cf6821 Machine ID: b2b3969566eb4f199427fd512847dd35 Storage: /var/lib/systemd/coredump/core.vmtoolsd.1000.525c399acb1c4bbe9008298b59cf6821.2073.1533550086000000.lz4 Message: Process 2073 (vmtoolsd) of user 1000 dumped core. Stack trace of thread 2073: #0 0x00007f66eadf5bb0 Backdoor_InOut (libvmtools.so.0) #1 0x00007ffd80878db8 n/a (n/a) #2 0x0918c02000005592 n/a (n/a) GNU gdb (GDB) Fedora 8.1.1-3.fc28 Copyright (C) 2018 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/bin/vmtoolsd...Reading symbols from /usr/lib/debug/usr/bin/vmtoolsd-10.3.0-1.fc28.x86_64.debug...done. done. [New LWP 2073] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `/usr/bin/vmtoolsd -n vmusr'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00007f66eadf5bb0 in Backdoor_InOut (myBp=0x770000007c) at backdoorGcc64.c:78 78 __asm__ __volatile__( Thread 1 (Thread 0x7f66eb24aec0 (LWP 2073)): #0 0x00007f66eadf5bb0 in Backdoor_InOut (myBp=0x770000007c) at backdoorGcc64.c:78 #1 0x00007ffd80878db8 in ?? () #2 0x00007f66eae1d139 in VmCheck_GetVersion (version=0x7ffd80878d50, version@entry=0x7ffd80878db8, type=type@entry=0x7ffd80878dbc) at vmcheck.c:219 #3 0x00007f66dd3f0d31 in ToolsOnLoad (ctx=0x5592083ad100 <gState+96>) at hgfsPlugin.c:1096 #4 0x00005592081a8050 in ToolsCore_LoadPlugins (state=state@entry=0x5592083ad0a0 <gState>) at pluginMgr.c:730 #5 0x00005592081a6c9c in ToolsCoreRunLoop (state=0x5592083ad0a0 <gState>) at mainLoop.c:291 #6 0x00005592081a6047 in main (argc=3, argv=<optimized out>, envp=0x7ffd80879038) at mainPosix.c:283
Yes, that's interesting. The "Backdoor" functions are related to where it makes the lowest level I/O call into the hypervisor, and as you can see it's failing at almost the first thing it does -- trying to get the version of the hypervisor. https://github.com/vmware/open-vm-tools/blob/3a0205478e242bd672356d4eab6272d3b901fe6e/open-vm-tools/lib/vmCheck/vmcheck.c#L205 Very strange, I'll leave it up to Ravindra to work out what any of this means.
Of course an obvious question: Are you actually running this in a VMware VM, or is it baremetal or a guest on another type of hypervisor?
(In reply to Richard W.M. Jones from comment #4) > Of course an obvious question: Are you actually running this in a > VMware VM, or is it baremetal or a guest on another type of hypervisor? This is on a couple of laptops which occasionally run KVM/QEMU VMs through virt-manager. No VMs are started on boot, just libvirtd.
Alexander, thanks for reporting this issue. My understanding is vmtoolsd is running on bare metal and you were not running into this crash with earlier versions? Please confirm.
(In reply to Ravindra Kumar from comment #6) > Alexander, thanks for reporting this issue. My understanding is vmtoolsd is > running on bare metal and you were not running into this crash with earlier > versions? Please confirm. Yes, exactly.
Thanks. I will have a fix today.
open-vm-tools-10.3.0-2.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-7152c16d7e
open-vm-tools-10.3.0-2.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-66fd8b027d
(In reply to Ravindra Kumar from comment #8) > Thanks. I will have a fix today. 10.3.0-2 fixed the problem, thanks Ravindra!
open-vm-tools-10.3.0-2.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-66fd8b027d
open-vm-tools-10.3.0-2.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-7152c16d7e
open-vm-tools-10.3.0-2.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.
open-vm-tools-10.3.0-2.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.