hi
on Workstation 12 Player
Porteus 3.2.2
i'm able to run Porteus Linux on VMWare no problem.
porteus.org
vmware tools installed no problem, no error.
but, when i try to run
/usr/bin/vmware-config-tools.pl
i get
Unable to copy to source file
/usr/lib/vmware-tools/configurator/pam.d/vmtoolsd to the destination file
/etc/pam.d/vmtoolsd.
Execution aborted.
i notice the pam.d directory does not exist.
any help?
thx!
I just upgraded to Workstation Player 14 on Linux and now all my existing VMs are missing their virtual floppy drive.
They had one virtual floppy drive assigned to B: (Floppy 2 in the VM's preferences) but it just doesn't appear anymore in the Win VMs. The VM's toolbar reports that the drive is connected, no messages/problems show up whatsoever. The floppy's image file still exists in the proper spot and is readable for the current user.
Further investigation revealed that in the VM's BIOS, both floppy drives are set to Disabled and the option is grayed out, so I cannot change it back to 1.44MB 3.5" drive. Am I missing anything? Can anyone reproduce this? All the VMs ran fine on 12.5.4
I have two Windows 10 Virtual Machines running on a Windows 7 host. This started with Player version 12.5.7. First VM was a fresh install of Windows 10 version 1709 (Fall Creators Update). Once VM tools were installed, all functionality, including resizing of the VM's window, worked with no issue. The second VM was a current version of Windows update with version 1709 upgraded. After the upgrade, VMware tools was re-installed, but would no longer allow screen size adjustments. It would only allow the Windows Default resolutions. Upgraded to Wmware Workstation Player 14, no change. Uninstalled and reinstalled VMware Tools multiple times, no change. The VM does show VMware SVGA 3D in device manager.
Do you have any idea why this VM won't allow screen size changes after the Windows 10 update?
Host machine in a Lenovo with Intel Core i7 3720QM, Intel HD Graphics 4000, and NVIDIA Quadro K1000M
Thank you.
I am attempting to install VMWare Player but can't discover what I am missing. I have gotten through the gcc install, make install, etc but hit the brick wall when I get to the VMWare Kernel module updater. I googled the problem and did see some references to Debian with a workaround of "Use another supported OS". Well, CentOS7 is definitely supported but I don't see what the problem is.
I did install kernel-devel, gcc, kernel-3.10.0-514.el7.src.rpm, linux-headers-3.10.0-514.el7.x86_64 (after a dpkg-query -s linux-headers-$(uname -r). To open a support case with VMWare I guess I have to solve this on my own because I have not gotten far enough to register for the 30 day email complimentary support.
Oddly enough I did have this running on a Debian box but switched to CentOS due to some video driver issues
Any ideas?
Hello guys. Good Morning!
I am new user in VMware and I have a problem to create a VM in the Debian 9 environment.
After selecting the ISO click on next, however, VMware closes and does not go to the next step.
I opened the Linux terminal and the error message is as follows:
NOT_IMPLEMENTED bora / lib / unicode / unicodeSimpleBase.c: 741.
Can someone help me?
now where to start. i installed Virtual box as the vm i was trying to use was not supported, then bridged mode started to brake on vmware. i couldn't connect and it started coming up that it couldn't connect to the vmnet0. then i ensure that the Bridge Protocol was installed. so then i try to repair the program and it spits out an error stating how it cant make a temp file, so then i go to uninstall it and yeah...it wont let me delete this thing no matter what i do. it wont let me use vmware anymore and i am stuck here with a useless but of software that is clogging up my laptop wasting my time.
Guys,
Is it possible, to connect virtual machines installed in vmware player from different physical amchines?
Example:
laptop A, a HP, has 2 vm's installed in vmwareplayer
Laptop B, a Lenovo, has 3 vm's installed in vmware player.
Can i connect these 5 vm's as if they are in the same subnet?
The Host is a Windows machine with 1709 and a Dell P2415Qb monitor. The guest is a P2V version of my former Windows installation that could not be updated to 1709. I ma running VMWare Player 14 and in the guest the current Tools. How do I enable portrait in the guest too?
Hello,
I've VMware Workstation 14 Player (without licence) on Linux Mint 18.2 (64bit) and CPU Intel Core i7-4702MQ with enabled virtualization in Bios, but when I trying to create new virtual machine on VMware Player, I cann't to enable "Virtualize Intel VT-x ...". This option is grayed.
What special is required ?
Thanks
Okay, so, I tried to install the VMWare 12 player, but, in the "Starting services" step, the VMWare Authorization Service did not start, I did everything, since deleting the registry, and the ProgramData folders.
Now, when I tried to reinstall, the "Installing Parallel Port" step doesn't complete, and the "Rolling Back Action" starts, deleting every progress. What did I do wrong?
I'm currently using Workstation Player 14.0.0 on a Windows 7 Pro host and running Windows 10 Version 1709 in the player.
I've updated from Workstation Player 12.5.5 to 14.0.0 the same time the new Windows 10 update was made available.
Previously when I disconnected the Huawei E3276 HiLink modem from the host in order to access and use it inside the VM it would open the modem's website http://192.168.1.1 on the VM (windows 10).
But after the update the modem's control page is not shown anymore and I cannot connect to the internet on the VM.
I can however connect the modem to the internet on the host (windows 7) and using NAT connect the VM to the internet but that is not a workable solution since I need the VM's internet issolated from the host.
I have a smartphone that I plugged in and was given a choice to connect to the host or guest OS. I selected the host OS and ticked the checkbox to remember my choice.
How can I reassign or undo this choice so the phone is connected to the guest OS if possible?
Thanks,
I'm running VMWare Workstation Player 12. My host OS is Windows 10 and the guest OS is macOS Sierra on a laptop with a touch screen. Quite frequently when switching control from the guest to the host, the touch screen control is not relinquished. To correct this I have to switch back to the Virtual Machine, then go to the Player Menu > Removable devices > {touchscreen device} > Disconnect. After this the touch screen works normally. If I had to do this once in a while it wouldn't be a problem, but it happens several times a day and is disruptive to my workflow. If there is a fix such that the VM Player always disconnects from the touch screen when the VM is not in focus that would be awesome. However, it would be nice if there was just some way I could permanently ignore the touch screen device on the VM as macOS doesn't support it well anyway. Does anyone know how I might achieve either of these solutions?
I'm running Workstation Player 14 and I see that the VMware NAT Service is set to Disabled on my host (Windows 7 64 bit). When I enable it and try to start it, I get the following error:
Windows could not start the VMware NAT Service service on Local Computer. Error 1067: The process terminated unexpectedly.
I had the same issue with 12.5, so I upgraded to 14 hoping it would fix the issue, but it didn't.
First, I'm wondering why the service is set to Disabled (VMWare DHCP Service is also Disabled) and second, why is it crashing when I enable and start it. I checked and it is set to run the latest version of vmnat.exe in C:\Windows\SysWOW64
Any help would be greatly appreciated.
Thanks,
Rich
Please fix both products so they can be installed and run on modern Linux Distro's running current Kernels.
If you run VMware Workstation Player 14 (and probably also VMware Workstation 14) on a Linux Host running a 4.13 Kernel just after a reboot, you can start the VM and it will run for a short period of time, but then it will crash saying something like memory couldn't be allocated. If you try to start a VM after the host OS has been running for some time, it won't start and give the same error message right away. If the host is running a 4.12 Kernel, there are no issues. But PC's should run current Kernels that have been security patched, and also to support new hardware, and also VMware products should support modern Kernels. So in my opinion this is a serious issue that has to be fixed, also for future Kernels.
Since the new VMware Workstation Player 14 only supports host CPU's that support SLAT, version 12.5 still needs to be supported, as there are many PC's around that don't have SLAT support. But if you try installing Workstation Player 12.5.7 on a Linux host, the configuration fails (according to the forums it seems to have to do with vmmon and vmnet modules that must be patched. According to what I have read it may work on ancient Kernels. So please also fix version 12.5 so that it can easily be installed and used on Linux hosts running current kernels, or at least adapt version 14 so that it also supports host CPU's that don't have SLAT.
I am starting the move over to Linux, and wanted to bring my Win7 virtual machine (Win7 guest, Win7 Host) with me. For some reason, VMware 14 under Linux Mint (running 18.2, stock kernel etc) cannot open the virtual machine. If it matters, the VM was originally created with version 12 on windows, and was upgraded before migrating.
I looked at the VM converter tool, but this was not installed and I couldn't find any download links for it (nor was I even sure it would help).
I'll update this with my vmx when I get home, if it will help.
Hi,
I'm using Workstation 14 Player on a Win10 x64 host. I'm currently using two guest OS : Win10 x64 (same as host) and Ubuntu 16.04.3 LTS. VMWare Tools is installed on the Win10 guest, while the recommended open-vm-tools package is installed on the Ubuntu guest.
Copy/paste works both ways in both guests.
Drag & Drop works both ways on the Win10 guest.
However, I can only Drag&Drop from the Win10 host TO the Ubuntu guest, but when I try to drag&drop the other way around the mouse cursor "holding" the file gets stuck on the borders of the Workstation window and I can't drop the file out into the host.
I tried installing VMware Tools in Ubuntu but it hasn't solved the problem.
Has anyone else experienced this and how did you solve it ?
Hey there guys,
I'm currently trying to make a program that detects when the Guest disk will run out of space and ask the host for more disk space.
Say I have a 20GB Virtual Machine and I'm trying to send a message to the host when I reach 19GB in order for the host to possibly run a vmrun command or something similar to expand the size. I've been tinkering around with some ideas but I have not came up with something serious.
Any way to approach this problem?
hello,
I use a new laptop DELL and windows10 PRO deliver togheter.
Configuration is InteL7 32G° memory.
I need to install VmWare player and run a windows10 or better Windows System.
Once I have installed the VmWare workstation player version 12.5.7, I create a VM and selected Windows10 PRO 64.
When I try to start it I see a message NO OPERATING SYSTEM FOUND.
How can I make it working as I do not the Windows10 CD from DELL?
Thanks in advance for your help and recommandations.
Regards
please let me first say that a *working* VMware or VMplayer is absolutely te best VM for a Linux installation. Having said that, I must say that it becomes ever more complicated to get VMware working on Linux.
Traditionally (i.e. the last five or six years) we got the situation that the vmmon module would not compile. Funny, because on a similar machine with the same (K)ubuntu installation it would compile flawlessly. I have at home one Kubuntu 17.10 with a 'good' VMplayer and two 17.10's with VMplayers that won't compile vmmon. On older (K)ubuntus it would sometimes working with a few patches, but not any more.
I now downloaded VMware 14, and it had no trouble at all with starting on a Kubuntu 17.10, but now it complains about not enough memory to install an old 32-bit XP version. Now 4 Gig may not be very much these days, but it never refused to start older VMplayer versions.
Am I doing things wrong, or is it VMware that is struggling to keep up with Linux updates? If so, which Linux woud be suitable and wich corresponding VM ware or VMplayer?