Now go in to your Mac System Preferences and configure the second network card for a private subnet (i.e. Sudo /Library/Application\ Support/VMware\ Fusion/boot.sh -restart "$LIBDIR/vmnet-bridge" -d /var/run/vmnet-bridge-vmnet2.pid vmnet2 en1 "$LIBDIR/vmnet-bridge" -d /var/run/vmnet-bridge-vmnet0.pid vmnet0 en0 Note you can not use vmnet1 or vmnet8 as those are for NAT and Host-only connections. "$LIBDIR/vmnet-bridge" -d /var/run/vmnet-bridge-vmnet0.pid vmnet0 ''Īnd then add 2 lines directly below that line, which tells vmware to bind the en0 physical device to the vmnet0 virtual device, same for en1 to vmnet2. Sudo vi /Library/Application\ Support/VMware\ Fusion/boot.sh Edit the file /Library/Application Support/VMware Fusion/boot.sh To fix this you will need to go and edit some files that VMWare Fusion uses. None of which will work if I want a private network for the Sun Ray’s. I gave the VM 2 nics (the Mac Pro has 2), however the only options that VMWare Fusion let you do is NAT, Host-Only, and Bridged. The kicker was getting VMWare Fusion to actually allocate the network cards the way I needed them. The Mac Pro is more than suited to handle it and had plenty of free memory/processor/storage to use so there was no contention (I gave the VM 4 processors and 8 gig of ram).
#Add vmnet2 vmware fusion mac install#
So I decided to install it in a VMWare image on my Mac Pro. But I did not want to test the software on the current working server. Now my current setup probably should not be used for any type of test more than simple single/dual user testing. I finally got time again to start playing with Sun Ray 5 Early Access software.
0 kommentar(er)
