Setup simulator with VMware » History » Version 2
  Anchi Cheng, 10/07/2014 09:26 PM 
  
| 1 | 1 | Anchi Cheng | h1. Setup simulator with VMware Fusion | 
|---|---|---|---|
| 2 | |||
| 3 | 2 | Anchi Cheng | You can get tem and camera simulator from manufactures and setup virtual machines for development. | 
| 4 | |||
| 5 | I set up 2 virtual machines on my MacBook with VMware and can run all the tcp transporter tests and image acquisition using a few specific settings as follow: | ||
| 6 | 1 | Anchi Cheng | |
| 7 | On the mac, find out the hostname known by python socket module. In python command line | ||
| 8 | <pre> | ||
| 9 | import socket | ||
| 10 | socket.gethostname() | ||
| 11 | </pre> | ||
| 12 | My mac is called anchi3.local | ||
| 13 | |||
| 14 | For each virtual machine | ||
| 15 | |||
| 16 | # Open Network Adopter settings through menu VMware Fusion/Virtual Machine\Network Adopter\Network Adopter Settings... | ||
| 17 | # Select to use "Private to my Mac" and activate "Connect Network Adaptor" if not already chosen. | ||
| 18 | # Follow [[Windows_Installation_Al#Add-the-IP-address-and-matching-hostname-of-the-microscope-and-digital-camera-computer-in-your-host-file-on-the-main-Leginon-computer,-and-vice-versa.]] to make all parties on this private network know each other by hostname | ||
| 19 | # ** Note: the virtual machine knows the real machine as "anchi3", not "anchi3.local"*. You should associate both names with the private network IP (127.xx.xx.1) | ||
| 20 | |||
| 21 | On the mac, the /etc/hosts should include assignment to each virtual machine as well as its own private network IP. I have | ||
| 22 | <pre> | ||
| 23 | 127.xx.xx.128 virtual1 | ||
| 24 | 127.xx.xx.129 virtual2 | ||
| 25 | 127.xx.xx.1 anchi3 anchi3.local | ||
| 26 | </pre> |