macOS High Sierra on MBP, VMware Fusion 8.5.8 and Windows 7.

After doing a clean install High Sierra, and not doing a migration, preferring instead to enter all data, I installed VMware Fusion 8.5.8, and restoring the Documents folder, I choose the Import an  Existing VM, when in Finder, I open the Virtual Machines folder, the VM bundle is greyed out.

If I try to activate the bundle directly, I get the following errors.

"Could not open /dev/vmmon: No such file or directory."

"Failed to initialize monitor device."

I've noticed that in a Linux guest, it's possible to mount specific shared folders using the 'mount' command, like:

mkdir /test

mount -t vmhgfs .host:/shared_folder /test

The contents of shared_folder shows up at the root of /test.

On OS X, using mount is still possible, but not to access a specific share:

mkdir /test

mount -t vmhgfs .host:/shared_folder /test

/test instead contains shared_folder (and any other shared folders that might be defined). They are mounted, but it seems like any path given to mount via ".host:/path" basically creates the equivalent of "/Volumes/VMware Shared Folders" at the given path.

Is there any option or capability that might make this possible without having to resort to symlinks?

getting this error

i uninstalled manually all the various Application Support, preference files etc and reinstalled.

any ideas?

mac OS X 10.13 High Sierra on a 10,1 MacBook Pro.

I'm trying to set up NAT networking in my VMware Fusion 8.5.6 Pro environment using a hard-coded IP address in the DHCP settings along with port forwarding in the NAT configuration settings.  In general, I am attempting to follow the process described at https://medium.com/@tuweizhong/how-to-setup-port-forward-at-vmware-fusion-8-for-os-x-742ad6ca1344 which seemed to provide the best documentation on how to set this up.

I first tried creating a new, custom network configuration (which showed up as vmnet3), but I abandoned that and just tried getting the existing vmnet8 NAT adapter to work.

I first edited (via sudo nano) my vmnet8 dhcpd.conf file (located in /Library/Preferences/VMware Fusion/vmnet8) to add a fixed IP address.  I made sure the address was outside the reserved IP range within the "DO NOT CHANGE" section of the dhcpd.conf file.

# Configuration file for ISC 2.0 vmnet-dhcpd operating on vmnet8.
#
# This file was automatically generated by the VMware configuration program.
# See Instructions below if you want to modify it.
#
# We set domain-name-servers to make some DHCP clients happy
# (dhclient as configured in SuSE, TurboLinux, etc.).
# We also supply a domain name to make pump (Red Hat 6.x) happy.
#




###### VMNET DHCP Configuration. Start of "DO NOT MODIFY SECTION" #####
# Modification Instructions: This section of the configuration file contains
# information generated by the configuration program. Do not modify this
# section.
# You are free to modify everything else. Also, this section must start
# on a new line
# This file will get backed up with a different name in the same directory
# if this section is edited and you try to configure DHCP again.


# Written at: 04/26/2017 11:39:58
allow unknown-clients;
default-lease-time 1800;                # default is 30 minutes
max-lease-time 7200;                    # default is 2 hours


subnet 192.168.110.0 netmask 255.255.255.0 {
  range 192.168.110.128 192.168.110.254;  option broadcast-address 192.168.110.255;  option domain-name-servers 192.168.110.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.110.2;  option routers 192.168.110.2;
}
host vmnet8 {  hardware ethernet 00:50:56:C0:00:08;  fixed-address 192.168.110.1;  option domain-name-servers 0.0.0.0;  option domain-name "";  option routers 0.0.0.0;
}
####### VMNET DHCP Configuration. End of "DO NOT MODIFY SECTION" #######
host R9NoBIM {
hardware ethernet 00:50:56:3E:44:20;
fixed-address 192.168.110.50;
}

My VM name is R9NoBIM.  Per the instructions on the first URL above, I set the host to the name of my VM.  (Is this what it should be?  I also tried using vmnet8 as the host here, thinking that this section would override the "DO NOT MODIFY" section above, but that didn't work, either.)

I quit, then restarted Fusion.

I then edited my nat.conf file to add the port, 8001 (http) that I wished to have forwarded, using the IP address I designated in the dhcpd.conf file above:

# VMware NAT configuration file


[host]


# NAT gateway address
ip = 192.168.110.2
netmask = 255.255.255.0


# VMnet device if not specified on command line
device = vmnet8


# Allow PORT/EPRT FTP commands (they need incoming TCP stream ...)
activeFTP = 1


# Allows the source to have any OUI.  Turn this on if you change the OUI
# in the MAC address of your virtual machines.
allowAnyOUI = 1


# Controls if (TCP) connections should be reset when the adapter they are
# bound to goes down
resetConnectionOnLinkDown = 1


# Controls if (TCP) connection should be reset when guest packet's destination
# is NAT's IP address
resetConnectionOnDestLocalHost = 1


# Controls if enable nat ipv6
natIp6Enable = 0


# Controls if enable nat ipv6
natIp6Prefix = fd15:4ba5:5a2b:1008::/64


[tcp]


# Value of timeout in TCP TIME_WAIT state, in seconds
timeWaitTimeout = 30


[udp]


# Timeout in seconds. Dynamically-created UDP mappings will purged if
# idle for this duration of time 0 = no timeout, default = 60; real
# value might be up to 100% longer
timeout = 60


[netbios]
# Timeout for NBNS queries.
nbnsTimeout = 2


# Number of retries for each NBNS query.
nbnsRetries = 3


# Timeout for NBDS queries.
nbdsTimeout = 3


[incomingtcp]


# Use these with care - anyone can enter into your VM through these...
# The format and example are as follows:
#<external port number> = <VM's IP address>:<VM's port number>
#8080 = 172.16.3.128:80
8001 = 192.168.110.50:8001


[incomingudp]


# UDP port forwarding example
#6000 = 172.16.3.0:6001

After this I stopped, then restarted my networking by running the following commands in Terminal:

sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli --stop
sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli --start

I confirmed that the networking file within the /Library/Preferences/VMware\ Fusion directory reflected the NAT entry:

VERSION=1,0
answer VNET_1_DHCP yes
answer VNET_1_DHCP_CFG_HASH 946E9174153882B15F5D274344959525D511212F
answer VNET_1_HOSTONLY_NETMASK 255.255.255.0
answer VNET_1_HOSTONLY_SUBNET 192.168.37.0
answer VNET_1_VIRTUAL_ADAPTER yes
answer VNET_8_DHCP yes
answer VNET_8_DHCP_CFG_HASH F171831A724DDD8020D6584939B78429F35D4E1D
answer VNET_8_HOSTONLY_NETMASK 255.255.255.0
answer VNET_8_HOSTONLY_SUBNET 192.168.110.0
answer VNET_8_NAT yes
answer VNET_8_VIRTUAL_ADAPTER yes
add_nat_portfwd 8 tcp 8001 192.168.110.50 8001
add_bridge_mapping en0 2

I've tried various configurations, using different adapters, etc., but I came back to the simplest approach of modifying the vmnet8, default NAT adapter.  After making my first attempt, and ever since then, the Networking settings for both the general Fusion Preferences > Networking, as well as the Network Settings pane for my VM are all grayed out, not allowing me to change them.  I've seen this posted elsewhere (as in  Network Settings options greyed out in Fusion Pro 7.1.0 ), but I haven't been able to get the ability to change the settings via the GUI to be restored, even after following a variety of tips that seemed to work for others.

Here is the general Fusion Network Settings pane. Even though I've unlocked the settings at the bottom, the settings pane remains grayed out:

Here is the Network Settings pane for my specific VM, also completely grayed out an uneducable:

I am able to change the network adapter via the Virtual Machine > Network Adapter menu, but when I select NAT, the VM client (Windows 2012) just reports that the Media State of the adapter is "Media disconnected".

I found a post that recommended checking the vnetlib log for errors.  Here is the section at the end of the log that gets written after restarting the vmware networking:

##multiple lines consisting of the following two lines##
Apr 26 11:37:03 VNLAdapterStatus - ioctl: SIOCGIFFLAGS failed, error: Device not configured
Apr 26 11:37:04 VNLAdapterStatus - ioctl: SIOCGIFFLAGS failed, error: Device not configured
Apr 26 11:37:04 VNL_EnableNetworkAdapter - Successfully enabled hostonly adapter on vnet: vmnet1
Apr 26 11:37:04 VNL_StartService - Started "DHCP" service for vnet: vmnet1
Apr 26 11:37:04 VNLNetCfgLookupNATPortFwd - List of NAT forwarded ports is empty
Apr 26 11:37:04 VNLNATReadPortForward - Failed to read TCP port forward config info.
Apr 26 11:37:04 VNL_StartService - Started "NAT" service for vnet: vmnet8
Apr 26 11:37:04 VNLAdapterStatus - ioctl: SIOCGIFFLAGS failed, error: Device not configured
Apr 26 11:37:04 VNL_EnableNetworkAdInternet Software Consortium DHCP Server 2.0
Copyright 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium.
All rights reserved.


Please contribute if you find this software useful.
For info, please visit http://www.isc.org/dhcp-contrib.html


Configured subnet: 192.168.110.0
Setting vmnet-dhcp IP address: 192.168.110.254
Opened: `J,Qˇ
Recving on     VNet/vmnet8/192.168.110.0
Sending on     VNet/vmnet8/192.168.110.0
apter - Successfully enabled hostonly adapter on vnet: vmnet8
Apr 26 11:37:04 VNL_StartService - Started "DHCP" service for vnet: vmnet8
Apr 26 11:37:04 VNL_Unload - Vnetlib unloaded.

The Bridged networking adapter works without any problem.  But in the setup I'm needing to establish I need to use NAT with an IP address that doesn't change, so I can rely on my port forwarding rules to work.

Any help on this would be greatly appreciated!

The SD Card Slot of my MAC Mini is unusable in my windows VM for Fusion 8.x. How can I allow the Virtual Machine to connect to the SD Card?

Hello everyone!

I want to purchase a 27 inch iMac with an SSD. I am confused about which configuration to buy. I will be running windows 10 on a virtual machine (VMware Fusion) on the Mac OS. Inside the windows on the virtual machine, I will install and run Matlab and Matlab related executables.

Could someone please suggest what would be the right RAM, GPU and processor configuration for my needs.

Thanks

OS X 10.11.6   Fusion Pro 8.1.1 (3771013)

I've set up a custom vmnet configure as follows

With ipconfig -L on the host I get the following

vmnet6: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500

  ether 00:50:56:c0:00:06

  inet 172.16.245.1 netmask 0xffffff00 broadcast 172.16.245.255

  nd6 options=1<PERFORMNUD>

Seems odd that there is no IPv6 info but *shrug*

Static IPv6

There are two guest VMs running CentOS 7 (minimal install)

Box 1 : IPV6ADDR=fd15:4ba5:5a2b:1007::3

Box 2 : IPV6ADDR=fd15:4ba5:5a2b:1007::5

ping6 between them shows 100% packet loss, ssh times out. ssh from the host gives no route to host

Time to experiment with routing.

Added an IP to vmnet6 on the Host with 'sudo ifconfig vmnet6 inet6 fd15:4ba5:5a2b:1007::1 prefixlen 64'which gives me an ifconfig of

vmnet6: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500

  ether 00:50:56:c0:00:06

  inet 172.16.245.1 netmask 0xffffff00 broadcast 172.16.245.255

  inet6 fe80::250:56ff:fec0:6%vmnet6 prefixlen 64 scopeid 0xe

  inet6 fd15:4ba5:5a2b:1007::1 prefixlen 64

  nd6 options=1<PERFORMNUD>

Added the default GW to the guest machines (DEFROUTE did not work). IPV6_DEFAULTGW=fd15:4ba5:5a2b:1007::1%en16777736 to the ifcfg-en16777736

Still nothing between the guest machines however the host now shows ping6 fd15:4ba5:5a2b:1007::3

PING6(56=40+8+8 bytes) fd15:4ba5:5a2b:1007::1 --> fd15:4ba5:5a2b:1007::3  and a ping6 from guest to fd15:4ba5:5a2b:1007::1 works.

So we have do have a route there now. Progress! However it is not being picked up. Lets try advertising it.

sudo sysctl -w net.inet6.ip6.use_tempaddr=1

sudo sysctl -w net.inet6.ip6.forwarding=1

sudo rtadvd -sfD vmnet6  (-f for non-daemon, D for full debug)

Pings all around! Guests can ping each other, I can ssh into them from the host and ping that GW.... for about 100 seq numbers. Then the SSH pipe breaks, pings stop and everyone is unhappy again. If I restart rtadvd I get another success for about 100 seq numbers

Things seem to break right around the prefix check...

Aug 11 13:24:21  rtadvd[6744] <Info>: <getconfig> vmnet6 isn't defined in the configuration file or the configuration file doesn't exist. Treat it as default

Aug 11 13:24:21  rtadvd[6744] <Debug>: <get_prefix> add fd15:4ba5:5a2b:1007::/64 to prefix list on vmnet6

Aug 11 13:24:21  rtadvd[6744] <Debug>: <ra_timer_update> RA timer on vmnet6 is set to 0:0

Aug 11 13:24:21  rtadvd[6744] <Debug>: <ra_timeout> RA timer on vmnet6 is expired

Aug 11 13:24:21  rtadvd[6744] <Debug>: <ra_output> send RA on vmnet6, # of waitings = 0

Aug 11 13:24:21  rtadvd[6744] <Debug>: <ra_timer_update> RA timer on vmnet6 is set to 16:0

Aug 11 13:24:21  rtadvd[6744] <Debug>: <main> set timer to 16:0. waiting for inputs or timeout

Aug 11 13:24:21  rtadvd[6744] <Debug>: <ra_input> RA received from fe80::250:56ff:fec0:6 on vmnet6

Aug 11 13:24:21  rtadvd[6744] <Debug>: <main> set timer to 15:999740. waiting for inputs or timeout

Aug 11 13:24:37  rtadvd[6744] <Debug>: <ra_timeout> RA timer on vmnet6 is expired

Aug 11 13:24:37  rtadvd[6744] <Debug>: <ra_output> send RA on vmnet6, # of waitings = 0

Aug 11 13:24:37  rtadvd[6744] <Debug>: <ra_timer_update> RA timer on vmnet6 is set to 16:0

Aug 11 13:24:37  rtadvd[6744] <Debug>: <main> set timer to 16:0. waiting for inputs or timeout

Aug 11 13:24:37  rtadvd[6744] <Debug>: <ra_input> RA received from fe80::250:56ff:fec0:6 on vmnet6

Aug 11 13:24:37  rtadvd[6744] <Debug>: <main> set timer to 15:999108. waiting for inputs or timeout

Aug 11 13:24:38  rtadvd[6744] <Debug>: <ra_input> RA received from fe80::250:56ff:fec0:2222 on vmnet6

Aug 11 13:24:38  rtadvd[6744] <Info>: <nd6_options> unknown ND option(type 24)

Aug 11 13:24:38  rtadvd[6744] <Info>: <prefix_check> preferred lifetime for fd15:4ba5:5a2b:1007::/64 inconsistent on vmnet6: 14400 from fe80::250:56ff:fec0:2222, 604800 from us

Aug 11 13:24:38  rtadvd[6744] <Info>: <prefix_check> valid lifetime for fd15:4ba5:5a2b:1007::/64 inconsistent on vmnet6: 86400 from fe80::250:56ff:fec0:2222, 2592000 from us

Aug 11 13:24:38  rtadvd[6744] <Debug>: <main> set timer to 15:295751. waiting for inputs or timeout

Anyone able to give any help in regards to this? The RA from fe80 is odd, and I have tried setting explicit pltime 14400 vltime 86400 to no effect.

Update : If I leave things alone (with rtadv running) Every once in a while about 20 pings will succeed, then start failing again)

I currently use Fusion 8.5.8 to run Win 7 on my iMac running MacOS Sierra.

I would like to export this VM to an iMac running Mac OS X 10.6.8 (Snow Leopard).  Is this possible ?  I assume that an earlier version of Fusion would be required, but are there any other differences between VMs created in different versions of Fusion ?

Hi guys

I've recently upgraded to Mac OS High Sierra v10.13, and VMware Fusion v10.0.1.  Since upgrading I'm having issues with my virtual install of Windows 10 as it won't pick up any wireless networks.  Presumably there's a setting I need to change, can anyone clue me in as to what it is ?

Thanks

UEFI support for both linux and windows?

moderator edit: Discussion moved from Fusion Pro Tech Preview to VMware Fusion® (for Mac)

Resuming a CentOS 7 guest went up from seconds to minutes. I have an APFS SSD. Is there a known issue?

I just migrated my old VMware Fusion version 5.0.5 from my old Mavericks OS to a new computer running High Sierra. I get a message saying to "Please make sure that the kernel module 'vmmon' is loaded". I realize that this is an old version, but I only use it about twice a year to run Windows 7 to update a URC remote control unit, so I would like to avoid buying a new version if possible. Thanks for any help.

My OS is Sierra 10.12.6. I have several Windows VMs in Fusion 8.5.8 working without any problems. I need to create a new VM with macOS or at least with OSX El Capitan. I have tried many times now and VMware is always failing me when starting the VM for the first time before the installation, or on the VM creation process. If I use the .app file from the Apple Store dropping it into the Create a New Virtual Image window I just get this error message: "Unable to create the installation medium". If I use the InstallESD.dmg from inside the package contents from the .app file, and use it as a DVD source for starting the new VM from it, the VM simply cannot boot from it. I have tried with both macOS Sierra and El Capitan and the same is happening.

I have googled this problem and found that it was present on the Fusion 8 beta but it supposed to be fixed long time ago via updates on Fusion.

Any help is greatly appreciated.

Hi All,

I have a brand new mac mini with High Sierra on it and wanted to try out vmware fusion with windows 10.  I can't get unity mode to work, it's completely grayed out.  It is a trial version of pro, does that have anything to do with it?

Thanks,

Eddie

After upgrade my MAC book to MAC OS high sierra, I tried open the windows on VMware it show Cannot find a valid peer process connect to. How to solve that?

vmware.log show this

2017-10-07T11:37:36.221+08:00| vmx| I125: USBIO:  000: 00 00 88 34 df 06 00 00                         ...4....      

2017-10-07T11:37:36.223+08:00| vmx| I125: USBIO: Down dev=1 'usb:0' endpt=81 stream=0 datalen=8 numPackets=0 status=0 0

2017-10-07T11:37:36.230+08:00| vmx| I125: USBIO: Up dev=1 'usb:0' endpt=81 stream=0 datalen=8 numPackets=0 status=0 0

2017-10-07T11:37:36.230+08:00| vmx| I125: USBIO:  000: 00 00 11 32 a4 02 00 00                         ...2....      

2017-10-07T11:37:36.232+08:00| vmx| I125: USBIO: Down dev=1 'usb:0' endpt=81 stream=0 datalen=8 numPackets=0 status=0 0

2017-10-07T11:37:36.237+08:00| vmx| I125: USBIO: Up dev=1 'usb:0' endpt=81 stream=0 datalen=8 numPackets=0 status=0 0

2017-10-07T11:37:36.237+08:00| vmx| I125: USBIO:  000: 00 00 25 2d 1a 00 00 00                         ..%-....      

2017-10-07T11:37:36.239+08:00| vmx| I125: USBIO: Down dev=1 'usb:0' endpt=81 stream=0 datalen=8 numPackets=0 status=0 0

2017-10-07T11:37:40.768+08:00| mks| I125: SWBWindow: Number of MKSWindows changed: 1 rendering MKSWindow(s) of total 2.

2017-10-07T11:37:42.609+08:00| mks| I125: SWBWindow: Number of MKSWindows changed: 0 rendering MKSWindow(s) of total 2.

2017-10-07T11:39:35.589+08:00| vmx| I125: SOCKET creating new socket, connecting to /var/run/vmware/usbarbitrator-socket

2017-10-07T11:39:35.589+08:00| vmx| I125: SOCKET connect failed, error 2: No such file or directory

2017-10-07T11:41:35.590+08:00| vmx| I125: SOCKET creating new socket, connecting to /var/run/vmware/usbarbitrator-socket

2017-10-07T11:41:35.590+08:00| vmx| I125: SOCKET connect failed, error 2: No such file or directory

2017-10-07T11:43:35.589+08:00| vmx| I125: SOCKET creating new socket, connecting to /var/run/vmware/usbarbitrator-socket

2017-10-07T11:43:35.590+08:00| vmx| I125: SOCKET connect failed, error 2: No such file or directory

2017-10-07T11:45:35.589+08:00| vmx| I125: SOCKET creating new socket, connecting to /var/run/vmware/usbarbitrator-socket

2017-10-07T11:45:35.590+08:00| vmx| I125: SOCKET connect failed, error 2: No such file or directory

2017-10-07T11:47:35.589+08:00| vmx| I125: SOCKET creating new socket, connecting to /var/run/vmware/usbarbitrator-socket

2017-10-07T11:47:35.590+08:00| vmx| I125: SOCKET connect failed, error 2: No such file or directory

2017-10-07T11:49:35.589+08:00| vmx| I125: SOCKET creating new socket, connecting to /var/run/vmware/usbarbitrator-socket

2017-10-07T11:49:35.589+08:00| vmx| I125: SOCKET connect failed, error 2: No such file or directory

I was able to manage my ESXi 6.5 and ESXi 6.0 servers using 8.5.3 - connect to server. Very handy, as the web interface of 6.5 still leaves much to be desired, taking over the screen of the guest using my fusion app is sometimes simply necessary to get things done. In fact I run NO virtual machines in my fusion app, I just use it to have an additional management tool for my lab ESXi servers.

Now I see in 10. Fusion that I cannot connect anymore to those ESXi server, and I need some FLEX license all of a sudden. I'm not interested in FLEX, I just want to manage these servers.

This makes Fusion 10.1 unusable for me.

Luckily, I was able to download Fusion 8.5.3 and install it again.

What gives? Is this a bug in the new Fusion version, are is vmware going to force me to use their still rather buggy ESXi web interface all the time to manage an ESXi server?

When I created a Windows 10 virtual machine in Sierra today I selected the option to use the existing bootcamp installation rather than create a new copy.  After using the W10 VM for a while I needed to shutdown my Mac and that's when the question arose: can I put the VM in Pause or might that affect the state of (or corrupt) W10 if I were to boot to the Bootcamp partition next session? For now I selected Shutdown in Windows but I prefer to use Pause if possible.

Thank you.

Originally using Fubon 8.5.8 and meets blue screen in our VM after upgrade to High Sierra.

Then try to upgrade to Fubon 10.0.1 the problem still exists. Anybody meets this problem ?

I report this problem the same reported here:  keyboard issues PD12 and Win10 | Parallels Forums

I try the suggested solution and it work for me.

1. Press CMD+ R (to open Run )
2. Copy and paste "C:\Windows\system32\ctfmon.exe" then press enter, it brings back the language bar 3. After executing the run command, proceed to these steps-
   • Navigate to the folder C:\Windows\System32
   • Locate ctfmon (Application)
   • Right-click > Send to > Desktop (Create shortcut)
   • Open run > type ' shell:startup ' (without quotes)
   • Drag & drop the ctfmon shortcut placed in the Desktop to the Startup folder.