Hi,
When starting Ubuntu on VM workstation I get the following error: piix4_smbus 0000:00:07.3: Host SMBus controller not enabled!
I've tried reinstalling the whole product, reinstalling VM tools and repairing VM workstation but to no avail; after the error, I keep getting a black display with nothing on it.
Here's an image of the error I get: https://prnt.sc/gv4l0m
Hopefully, someone could help me out.
Thank you
I get on my VMplayer error 1075: the dependency service does not exist or has been marked for deletion how to fix it? I try looking for the service file can not find services folder
I get on my VMplayer error 1075: the dependency service does not exist or has been marked for deletion how to fix it? Try looking for services folder not there.
I am using WMware Workstation Player 12. I am trying to configure my lab servers to communicate with each other. One has the DHCP/DNS role installed and needs a static ip. The other will be a client which will receive the IP addresses. I need to cofigure the client with the static IP from the server but cannot get the two guest servers to communicate with each other. They are both on the same subnet. I have tried disabling the firewalls and allowing ICMP. The guest cannot ping each other. They can ping the host, but the host cannot ping the guests.
I have tried all variation of the network settings. My questions are; will WMware Workstation Player allow guest-to-guest communication? If so, does anyone have any ideas on the configuration?
Hi,
I'm using Workstation Player 12.5.2 build-4638234 (latest?) on an Ubuntu 16.04 (4.4.0-57-generic), with an Ubuntu 16.04 (same) guest. The wifi network I'm connecting to has a small (5 mins) DHCP lease time. (This setting is out of my control.) As a result, the host renews the DHCP config quite often (2-5 mins), and every time it does, the guest experiences a small network disconnect. This causes, for instance, a web browser running on the guest to often report pages as unavailable. This is very annoying, and it's something that doesn't happen with a browser running on the host. I'm trying to understand if there's a way to avoid such "hiccups". Specifically, why does the guest network adapter have to go down&up for every such event?? Thanks!
My detailed network settings are below:
- The host uses a wifi connection, managed by NetworkManager, with DHCP.
- The VM has 2 virtual network adapters, one NAT and one host-only. Both are set to use fixed IPs. The host-only adapter has no issues. Here is the config for the NAT adapter:
# /etc/vmware/vmnet8/dhcpd/dhcpd.conf
allow unknown-clients;
default-lease-time 1800; # default is 30 minutes
max-lease-time 7200; # default is 2 hours
subnet 192.168.71.0 netmask 255.255.255.0 {
range 192.168.71.128 192.168.71.254;
option broadcast-address 192.168.71.255;
option domain-name-servers 192.168.71.2;
option domain-name localdomain;
default-lease-time 1800; # default is 30 minutes
max-lease-time 7200; # default is 2 hours
option netbios-name-servers 192.168.71.2;
option routers 192.168.71.2;
}
host vmnet8 {
hardware ethernet 00:50:56:C0:00:08;
fixed-address 192.168.71.1;
option domain-name-servers 0.0.0.0;
option domain-name "";
option routers 0.0.0.0;
}
- In the guest, both adapters are set to use static IPs through NetworkManager:
# /etc/NetworkManager/system-connections/NAT\ Network
...
[ipv4]
address1=192.168.71.10/24,192.168.71.2
dns=192.168.71.2;
dns-search=
method=manual
...
- Here is what I see in syslog during DHCP renewal, apart from other NM-related messages:
On host:
Jan 3 10:51:23 daemon.info vmnet-natd: RTM_NEWADDR: index:3, addr:192.168.100.183
Jan 3 10:53:27 daemon.info vmnet-natd: RTM_NEWADDR: index:3, addr:192.168.100.183
Jan 3 10:55:52 daemon.info vmnet-natd: RTM_NEWADDR: index:3, addr:192.168.100.183
Jan 3 10:57:56 daemon.info vmnet-natd: RTM_NEWADDR: index:3, addr:192.168.100.183
On guest:
Jan 3 10:51:25 kern.info kernel:[286522.503468] e1000: ens33 NIC Link is Down
Jan 3 10:51:31 kern.info kernel:[286528.515317] e1000: ens33 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
Jan 3 10:53:29 kern.info kernel:[286646.747963] e1000: ens33 NIC Link is Down
Jan 3 10:53:33 kern.info kernel:[286650.756319] e1000: ens33 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
Jan 3 10:55:53 kern.info kernel:[286791.025117] e1000: ens33 NIC Link is Down
Jan 3 10:55:57 kern.info kernel:[286795.059015] e1000: ens33 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
Jan 3 10:57:57 kern.info kernel:[286915.279562] e1000: ens33 NIC Link is Down
Jan 3 10:58:01 kern.info kernel:[286919.287363] e1000: ens33 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
Hello,
I have created a VM runing on windows 7, my OS is Windows7 PRO.
Starting the VM I got those messages:
This host supports Intel VT-x, but Intel VT-x is disabled.
Intel VT-x might be disabled if it has been disabled in the BIOS/firmware settings or the host has not been power-cycled since changing this setting.
(1) Verify that the BIOS/firmware settings enable Intel VT-x and disable 'trusted execution.'
(2) Power-cycle the host if either of these BIOS/firmware settings have been changed.
(3) Power-cycle the host if you have not done so since installing VMware Player.
(4) Update the host's BIOS/firmware to the latest version.
This host does not support "Intel EPT" hardware assisted MMU virtualization.
This host does not support virtualizing real mode. The Intel "VMX Unrestricted Guest" feature is necessary to run this virtual machine on an Intel processor.
Module 'CPUIDEarly' power on failed.
Failed to start the virtual machine.
As I am new user of VMWARE I hope I can receive from you some help and recommandations.
I use a Laptop DELL LATITUDE D830 (not anew one I know) with INTEL CORE (TM) 2 DUA CPU, T8300, 2.4 GHZ and 4M0 RAM.
Thanks for your help
I have just upgraded VMware player to version 14.0.0. I want to run a virtual system i have BSoD where the error causes \SystemRoot\system32\DRIVERS\vmx86.sys
Version 12.5.7 works without problems. My processor is Pentium Dual Core E2180 2 Ghz. OS Win 64 bit.
All my VM´s created with previous versions of VMware Workstation Player, also 12.5.7 worked fine and started them all without any issue. Today I updated to Workstation Player 14 and now VM can not be opened. I just receive the message that my Computer suports AMD-V but must be enabled in BIOS.
Or: I must update my BIOS version and other messages.
But why I get this probelm just with v14? So, I turned back to 12.5.7 and everything is working.
Why does this happen?
I´m using Windows 10 Fall Update (1709) 64-Bit fully updated.
I don't see where I can set the virtual disk type to SATA when creating a new virtual machine in VMware Workstation 14 free edition. It just defaults to SCSI. Is this a Pro only feature?
I just installed Ubuntu 17.10 Linux and VMware Player 14 prompts me with:
"Before you can run VMWare, several modules must be compiled and loaded into the running kernel."
I click "Install", enter my password, and the program immediately exits. Any ideas how to troubleshoot this?
Thanks!
when I create a virtual machine it doesn't display in the player. After I open a virtual machine it doesn't display in the player. Any suguestions?
After approx. 1 hour of use, the VM inside VMware freezes hard. Same image was working perfectly on Kubuntu 17.04, VMware player 12. Can't close the player, kicks out "The virtual machine is busy." error.
I cannot kill the vmplayer process, gives same error, "The virtual machine is busy." I can issue a kill -9 on it.
After it's dead, relaunching vmplayer does not give an option to power on the VM anymore.
Hi all,
since the latest update of Windows 10 (1709), the resolution of the virtual machine is no longer automatically set.
I reinstalled the VMWare tools, but the feature is still missing.
Anyone observed something similar?
Ciao
Manuel
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?
