Hi,
If I understand you correctly then your host runs on Ubuntu kernel 4.15.0-44-generic, so that would normally be Ubuntu 18.04
I suppose that you also updated the host, because I don't see how that would run VMware Workstation 12.x without some manual patching.
Your problem could be due to a number of reasons.
If you have the same problem when creating a new VM then at least it is not due to a lock file not being there.
Are you certain that you have read/write access to the folders where the VM is located? If the user-id changed then this might cause this type of problem.
Another thing you might try, is to remove the virtual USB controller on that new VM you created and see if it boots then.
I suppose that there are no hidden windows so that it is waiting for input from you?
FYI, for attaching images, there is an attach "button" in the bottom right part of the screen where you type the reply.
--
Wil
Hi,
Oh, seems I misunderstood, your host OS is running Elementary OS, not the guest.
That is not a supported host operating system.
But that does not mean it cannot work, it seems to me that both WS14 and WS15 should run on El. OS4 and I would expect WS15 to work on El. OS5.
At this moment I would need more information to be able to give more help.
Please provide the support bundle as generated via menu -> Help -> Support -> Collect Support Data and attach it to your reply here.
You can find an attach link at the bottom right area when posting a reply.
--
Wil
Hi,
If your VM only boots when you are root then my best guess is that the files in your VM do not have the correct permissions.
IOW, your user is probably not allowed to read/write to the VM.
-
Wil
It's not the installer bundle, it is the VM.
eg.
run
ls -alh /path/where/your/vm/lives
and post the output back here.
--
Wil
Hi,
Use the chown command to change the owner of your VM to the user under which you run VMware Workstation.
eg:
chown -Rf username: /path/of/yourVMs
--
Wil
Hi,
First things first. I understand it can be frustrating if things don't work as expected, or if you don't know why something does not work that way.
Beware though that I do not work for VMware and -like many others here- am helping out users as a VMware Workstation user myself on a voluntary bases.
When communication gets frustrating I tend to step aside as I then think my time is better spent elsewhere.
In the past I asked for the output of the details on the folder that your VM lives.
I never got an answer, so gave you general steps that _should have_ worked.
Not getting answers for questions I ask is another reason I will stop spending my time as I can't help when I don't know what the details are.
Eg. you failed to answer and give me the output of the command:
ls -alh /path/where/your/vm/lives
The "Shared VM" parts you are now going down have nothing to do with the problem of having to start Workstation as a root user.
This is a feature for being able autostart/autostop VMs with the host
Yes you can control which users can access that VM, but it does not run the VM under that user account.
edit: Oh.. there was two users with similar problems in this thread. Actually I asked you for the support bundle... that never came either.
--
Wil
Hi,
That's the main VM folder where all your VMs are stored.
It would a lot more helpful if you showed the contents of one of the VMs you are trying to start.
A VM that does not run under the user account.
--
Wil
Hi,
Ok, that looks just fine.
The chmod 777 should not be needed, but I think you know and you just tried that in order to exclude things.
So when you say "Always same problem" then you mean that you are getting the "waiting for connection" error?
One of the differences when running as root is that you can open ports under 1024. It is possible that that is part of the reason why it works.
Does your host have a firewall enabled?
If so can you try with the firewall disabled?
If that doesn't help... how about sharing a support bundle? The logs might have more details on why you are getting a waiting for connection error.
--
Wil