8 พฤษภาคม 2555 12:00
We have a Win2008 R2 server running HyperV. I have created an external HyperV network adaptor for all our VM's on the host machine because we would like other servers except the host server to communicate with the VM's. My headache is as follow, Is it possible to assign internal IP's(192.168.16.xx) for all our VM's and have our webserver communicate to the SQL port on the VM's with the internal IP's.
Basically, will a server on the same range and workgroup as the host server be able to communicated with the VM's if I assign internal IP's to the VM's
8 พฤษภาคม 2555 13:34ผู้ดูแลHi,
If you attach the network adapters of the virtual machines to the External Virtual Network, the virtual machines will get IP address from your router or DHCP(if there is) like a physical computer. So you can let the virtual machines get IP addresses automatically, or you can assign them static IP addresses.
8 พฤษภาคม 2555 13:43Hi Thank you for the answer but I think I explained a little bit wrong. I dont want to assign the VM's an external IP, I want them all to have an internal range binding to the external adapter I created on the HOST machine. Is it possible for my other physical servers to connect to the internal IP and ports from the VM's or do I need to assign a public IP like my physical servers.
8 พฤษภาคม 2555 14:45ผู้ดูแล
The VMs must be routable in some way.
It appears as if you want to NAT your public into your private (manually assigned) range. The easiest way to handle this is to put a VM in the middle that is a router or firewall (Vyatta, VPX, F5, etc.)
Then it is this VM that has 2 vNICs - a public that is attached to an external virual switch and an private attached to the Private virutal switch with your VMs. Then you establish your routing rules in the routing software of this VM.
Otherwise any hypervisor only gives you physical isolation.
With Win8 it will be possible to do what you want with Virtual Networking - however, it is not trivial to set up (I know).
Learn. Apply. Repeat.
Disclaimer: Attempting change is of your own free will.
8 พฤษภาคม 2555 16:37
If I understand you correctly you have created an external vSwitch on the host that is also shared by the host?
So, host IP = 192.168.16.200 (example for all IPs)
Bind the vSwitch to each of your VMs. Once this is done the vNIC _in_ the VM OS must be assigned an IP address just as any server OS would be whether via DHCP or static.
VM1 vNIC: 192.168.16.201
VM2 vNIC: 192.168.16.202
Does that cover what you are asking?
Philip Elder SBS MVP Blog: http://blog.mpecsinc.ca
9 พฤษภาคม 2555 15:24
On my laptop, I added a loopback adapter and I bind Hyper-v to that. Then I use ICS to share my wireless connection with the loopback. I give the loopback the static IP of 192.168.1.1, however when I am sharing it's automagically assigned the same IP. All the VMs get DHCP assigned 192.168.1.0/24 addresses when I have ICS turned on. This sounds sort of what you're trying to do.
9 พฤษภาคม 2555 16:25ผู้ดูแล
Check the following post to see whether you have the same concern.
- ทำเครื่องหมายเป็นคำตอบโดย Vincent HuModerator 14 พฤษภาคม 2555 6:05