如何在不同计算机上运行的虚拟机上运行客户端服务器应用程序？

从网络角度来看，您有两个选择：

1. 很多NAT。默认情况下，我假设您的VM在任何虚拟化解决方案中都设置为使用NAT模式，这使操作起来有些棘手。可行，但棘手。

2. 虚拟机也“桥接”到主机系统所在的实际网络上，这消除了NAT的麻烦。这是更简单的选择。

---

---

选项1：NAT模式下的VM网络

注意：我从没有使它可靠地工作过，我一直使用桥接模式，这种方式要可靠得多。

VMware和VBox都设置为允许NAT和端口转发。这一切都很好，很花哨，但这带来了一些麻烦。

---

虚拟机

除非您具有VMware Workstation Pro，否则无法轻松设置NAT端口转发。这是因为用于NAT端口转发的虚拟网络编辑器未随Workstation Player或较早的VMware Player软件版本一起提供。

假设您具有虚拟网络管理器/编辑器，但是在具有将作为“服务器”的VM的系统上执行以下操作：

（1）打开“虚拟网络管理器/编辑器”，然后选择一个带有“ NAT”的适配器作为“外部连接”列表。它看起来像此图所示：

（2）选择“ NAT设置”，您将获得一个类似这样的窗口：

（3）在“端口转发”区域下，单击“添加”。您会看到一个像这样的窗口：

设置信息如下：

Host Port: Likely to be the same port you're having the Server listen on in the VM, but it can be something else if you want.

Type: TCP or UDP is dependent on your server and how it listens. Safe to assume TCP here, though, most active-connection server things are TCP.

IP Address: The IP address of the VM. You can get this with ip -4 addr list from inside the VM on the command line.

Virtual Machine Port: The port that the server application will be listening on.

Description: A description of what this port forward is for.

You'll probably have to shut off your VM temporarily, and restart the VMware services with sudo systemctl restart vmware so it reloads all the port forwarding/bridging rules.

(4) Start up the VM with the server on it. From the Client VM, make sure you tell the Client to connect to the IP Address of the computer that is running the Server VM (so if the laptop with the Server VM on it has IP address of 192.168.250.20, the Client VM's application should try and connect to 192.168.250.20.)

Note that this will not work in all cases, and I strongly recommend the use of Bridged mode instead.

---

VirtualBox

I have never gotten VBox NAT network port forwarding to behave. If you are using VBox, I strongly suggest you use Bridged mode instead of NAT. (While this doesn't clearly answer for VBox, I tried testing these Port Forwards from VBox and couldn't get it to work at all).

Not that I didn't try, but on 16.04, VirtualBox was not able to connect outbound to anything, and never set up any virtual network interfaces for NAT capabilities; I assumed then that it can't work right without Bridged but I can't find why it never brought up NAT capacity.

---

---

Option 2: VM Networking: Bridged Mode

You will need to run the VMs in "Bridged" mode and then use IP addresses from your own LAN/Wifi network that are assigned to the VMs (as a result of "bridged" allowing the VMs to connect to and look like they're on the actual network of the host computers).

Firstly, configure the VMs on both systems to use the "Bridged Network" mode. How this shows will be different from VM solution to VM solution, but it'll always say "Bridged" or similar (at least, in VMware or VBox). Make sure the device that you're "bridged" to is your preferred network card (wifi or ethernet), so you're properly going out to the right network with the VM for an IP address.

Secondly, reboot the VMs if they're already online. This should get them a brand new IP address from the same network as the host machines. (It should be in the same subnet range even).

Thirdly, point the client of the one VM to the IP of the server on the other VM. Because the networking is Bridged, it should just connect. You may have to tweak the VMs on the guests to make sure it permits connections though.

对于VM，就应该如此，并且它们应该能够互连而不会出现问题。