Created attachment 308841 [details]
Working vmware.service Unit
I have attached a vmware.service unit that I created using /etc/init.d/vmware. I am currently using it without issue.
I'm curious about what the status on this is. Summer has already come and gone.
@systemd: please have a look, does the file make sense?
Some sense, yes. It's against all systemd policies but I guess vmware doesn't really care and I don't really understand what is happening there. One thing I can say is that thing thing becomes totally stateless and horribly fragile.
It seems like it might be better to break this into 3 unit files.
Created attachment 351626 [details]
I use these services downloaded from
apparently also available on github https://github.com/kriation/systemd-vmware
*** Bug 477000 has been marked as a duplicate of this bug. ***
TODO: compare the attached files from bug 477000 with the files from https://github.com/kriation/systemd-vmware
(In reply to Andreas K. Hüttel from comment #7)
> TODO: compare the attached files from bug 477000 with the files from
The files are mostly identical with path fixes.
Need license declaration, see https://github.com/kriation/systemd-vmware/issues/1
I would also be good if we could include a vmware.scope unit file for starting vmware workstation more in the way systemd manages virtual machines. I have been experimenting with starting vmware with:
sudo systemd-run --scope --unit=vmware --slice=machine /opt/vmware/bin/vmware
Running as unit vmware.scope.
I end up after starting a vm with:
│ ├─10130 /opt/vmware/bin/vmware
│ ├─10262 /opt/vmware/lib/vmware/bin/vmware-tray poweredOn
│ ├─10283 /opt/vmware/lib/vmware/bin/vmware-unity-helper --daemon
│ ├─10326 dbus-launch --autolaunch=d95f715e390a4d5b5874f8840006d101 --binary-syntax --close-stderr
│ ├─10327 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
│ └─10448 /opt/vmware/lib/vmware/bin/vmware-vmx -s vmx.stdio.keep=TRUE -# product=1;name=VMware Workstation;version=9.0.2;buildnumber=1031769;licensename=VMware Workstation;licenseversion=9.0; -@ duplex=3;msgs
The vm seems to be running faster but I have no tests to verify.
Anyway the only downside seems to be that vmware is running with root privileges which I assume can be fixed.
The scope unit file documentation is hard to come by be I assume a vmware.scope unit file could be written at specifies slice and permissions.
Anyone know how to do this?
(In reply to Harris Landgarten from comment #9)
> I would also be good if we could include a vmware.scope unit file for
> starting vmware workstation more in the way systemd manages virtual
> machines. I have been experimenting with starting vmware with:
> sudo systemd-run --scope --unit=vmware --slice=machine /opt/vmware/bin/vmware
> Running as unit vmware.scope.
> Anyone know how to do this?
No, but let's do this one step at a time.
+ 24 Jul 2013; Andreas K. Huettel <email@example.com>
+ Add experimental systemd unit files, bug 411901