** Changed in: open-vm-tools
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791220
Title:
increased crash rate since 10.3 upgrade is available
To manage notif
This bug was fixed in the package open-vm-tools -
2:10.3.0-0ubuntu1~18.04.2
---
open-vm-tools (2:10.3.0-0ubuntu1~18.04.2) bionic; urgency=medium
* d/p/ubuntu/lp-1791220-Disable-hgfsServer-not-VMware.patch: avoid crashing
with segfaults when force starting the service in non VMWa
Before Fix
root@b-vmtools:~# vmtoolsd
Segmentation fault (core dumped)
Upgrade package
(Reading database ... 28495 files and directories currently installed.)
Preparing to unpack open-vm-tools_10.3.0-0ubuntu1~18.04.2_amd64.deb ...
Unpacking open-vm-tools (2:10.3.0-0ubuntu1~18.04.2) over
(2:10.3.
Hello , or anyone else affected,
Accepted open-vm-tools into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/open-vm-
tools/2:10.3.0-0ubuntu1~18.04.2 in a few hours, and then in the
-proposed repository.
Please help us by testing this new pack
- SRU Template complete
- Cosmic fixed and confirmed (I retested on vSphere)
- Since other than the version in changelog latest -dev and LTS are kept in
sync the MP we had for cosmic essentially applies here as well.
Pushing the same fix to Bionic, now available in -unapproved for the SRU
Teams c
** Also affects: open-vm-tools (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: open-vm-tools (Ubuntu Bionic)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
This bug was fixed in the package open-vm-tools - 2:10.3.0-0ubuntu2
---
open-vm-tools (2:10.3.0-0ubuntu2) cosmic; urgency=medium
* d/p/ubuntu/lp-1791220-Disable-hgfsServer-not-VMware.patch: avoid crashing
with segfaults when force starting the service in non VMWare environments.
With the insight so far we can remove the systemd task again.
** No longer affects: systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791220
Title:
increased crash rate since 10.3 upg
** Changed in: open-vm-tools (Ubuntu)
Status: New => In Progress
** Changed in: open-vm-tools (Ubuntu)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
** Description changed:
+ [Impact]
+
+ * The new version of open-vm-tools we recently SRUed had an issue
+that if started in non-VMWare environments (protected by systemd
+condition-virtualization, but people fake VMware envs) would segfault.
+
+ * It is fine to "not work there" but s
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/open-vm-tools/+git/open-vm-tools/+merge/354555
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791220
Title:
increased
I tried backporting the upstream fix that came up in our discussion.
It fixes the crash back to how it was in Xenial (no segfault).
There still won't be much reason to run in non-VMWare envoronments, but this
isn't what this was about.
It is working just fine.
Preparing a MP to review and a cosm
I have an idea actually, these are setups faking the VMWare ID.
Systemd checks dmidecode values which could be faked in other hipervisors.
There the tool would start and then trigger the crash.
IMHO - the solution is make the tool exit, but not crash
--
You received this bug notification because
We want to fix it in open-vm-tools but I also added a sytemd bug task to
get more opinions.
@systemd
As ConditionVirtualization=vmware should have prevented the issue in the first
place, is there any rumor or known issues of that not being reliable?
** Also affects: systemd (Ubuntu)
Importan
Oh well we can.
Debugging from what I learned off the ASM I found the following TL;DR that I
put on the upstream bug:
TL;DR:
- the bug is trying to run vmtoolsd on non vmware systems
- it is stupid and ConditionVirtualization=vmware should prevent that issue
from existing
- Old versions (10.2) o
Code isn't generated:
open-vm-tools/lib/backdoor/backdoorGcc64.c
Backdoor_InOut(Backdoor_proto *myBp) // IN/OUT
{
uint64 dummy;
__asm__ __volatile__(
#ifdef __APPLE__
/*
* Save %rbx on the stack because the Mac OS GCC doesn't want us to
* clobber it - it erroneousl
Not bad:
https://www.thezdi.com/blog/2017/8/1/pythonizing-the-vmware-backdoor
https://sites.google.com/site/chitchatvmback/backdoor
I think VMWare can reconstruct the actual call, lets add them the full
regs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
>From the upstream bug:
Can someone who has seen this and make this happen obtain tools logs with the
HGFS server logging enabled?
How to set up the logging is as follows:
Create the following file:
/etc/vmware-tools/tools.conf
Edit it with the following details (modified to your file location o
Tagged regression update as that is what it seems.
I still lack a reproducer of any kind, so if one affected by this bug
finds this bug while searching for it, please help to fix this by
sharing what exactly was done before hitting this issue.
--
You received this bug notification because you ar
19 matches
Mail list logo
