Not too long ago a client (you know who you are and thanks!) asked a perfect question regarding the XenClient Enterprise (XCE) Synchronizer server and Hyper-V:
“Do I need more than one NIC to use Hyper-V on the Synchronizer?
We are only testing on a few machines and making a change request for additional NICs plus drops could take a while…”
The long answer: Ehhh, NO. Especially not in a production sense.
For production environments this is not supported nor recommended as any form of best practice! This blog is meant for personal/business test environments, contained POC (proof of concept), or …. general “tinker” environment.
Also… if your XCE server only has a single 100MiB NIC then I would limit testing to no more than 3 engines.
If you have a 1-10GiB NIC then I would limit testing to no more than 5-10 engines.
This all comes from personal and professional testing, so please trust me!
The short answer: YES!
For test purposes (even mine) – YES – you can only use one (non-wireless) physical network interface for the XenClient Enterprise Synchronizer that supports:
– Web Interface management
– SQL Server (Express)
The philosophical question: Why?
Because it is good to test and experiment technology!
The technical question: How?
Well, my answer below was provided under non-production standards and was proclaimed as “not supported under production or circumstances where bandwidth and management become a concern”.
So, disclaimers being said here is how you can use XenClient Enterprise Synchronizer and Hyper-V with one physical network card. This comes from my personal experience and testing and here goes:
Lauch Hyper-V Manager from the Start Menu:
Connect to the Hyper-V Host:
Specify the Local or Remote computer to connect to Hyper-V
Select the Virtual Network Manager:
Select New Virtual Network:
Define the External Virtual Network:
Define the Name as “External Network”:
After completion, a new “External Network” should appear:
From here, you can now save changes and start the XenClient Enterprise web interface. This will support the local (web) interface as well as Hyper-V.
Now, you should be able to utilize the web interface as well as create virtual images through Hyper-V for publishing to test Engines!