VMware Communities
icthy
Contributor
Contributor

guest has lost networking: can't open vmnet device

Hi, I'm running VMware-Workstation-Full-7.1.4-385536.x86_64, on a Fedora 14 x64 computer, using kernel 2.6.35.6-45.     I had a hard drive failure, installed Fedora 14 from scratch, Workstation 7, and then copied my virtual machine over from a backup drive.   Workstation 7 (running Windows 7), runs fine, but I have lost my internet connection.   I've attached my vmware.log, file, and here are some (hopefully) salient lines from it:

        [lots of other stuff]

Jun 29 10:03:22.154: vcpu-0| VNET: MACVNetPortOpenDevice: Ethernet0: can't open vmnet device (No such device or address)
Jun 29 10:03:22.154: vcpu-0| VNET: MACVNetPort_Connect: Ethernet0: can't open data fd
Jun 29 10:03:22.154: vcpu-0| Msg_Post: Warning
Jun 29 10:03:22.154: vcpu-0| [msg.vnet.connectvnet] Could not connect Ethernet0 to virtual network "/dev/vmnet8". More information can be found in the vmware.log file.
Jun 29 10:03:22.154: vcpu-0| [msg.device.startdisconnected] Virtual device Ethernet0 will start disconnected.

[lots of other stuff]

Jun 29 10:03:15.311: vmx| DICT         ethernet0.present = TRUE
Jun 29 10:03:15.311: vmx| DICT  ethernet0.connectionType = nat
Jun 29 10:03:15.311: vmx| DICT      ethernet0.virtualDev = e1000
Jun 29 10:03:15.311: vmx| DICT   ethernet0.wakeOnPcktRcv = FALSE
Jun 29 10:03:15.311: vmx| DICT     ethernet0.addressType = generated

[lots of other stuff]

When I installed vmware, I don't recall any question about setting up my guest internet or vmnet, and I am guessing Workstation is trying to use the old settings that are not appropriate any more.    Can you please tell me what needs to be changed and how to do it?

Also, out of curiosity, could I ask how one best backs up a virtual machine to a remote drive?   I was copying the whole vmware directory, which is probably excessive.

Thanks.

0 Kudos
2 Replies
icthy
Contributor
Contributor

I found the command vmware-netcfg in /usr/bin, and used that to switch the VM networking from "Bridged" to "NAT", and that has gotten the network going.    Thanks to anyone that read my post and pondered it.

0 Kudos
nrapopor
Contributor
Contributor

I've had a similar problem with ubuntu 17.10 and Workstation 14.0.0.

I've migrated a bunch of VMs to this box that were originally created on windows.  Each of the machines had two network adapters; one NAT (vmnet8), one host only (vmnet1). Host only (vmnet1) would refuse to connect with the same messages as mentioned above. I've deleted and recreated the vmnet1 adapter with different subnet using the  "sudo  vmware-netcfg" command.  that seems to have fixed the problem. I need two adapters so VMs can still talk to each other when the host is not connected to the network.

HTH

Nick

0 Kudos