Second network interface - internal
This is probably something answered many times over, so I'm pretty much expecting to just be pointed to the right documentation...
But, what I am attempting is to create a second network interface which can be used for internal traffic between KVM systems on the same underlying server.
I'm running RHEL5 KVM servers. RHEL5 readily builds eth0 and I have configured that to connect with my overall network interface. But I would like to create a second virtual network interface which could shuttle some internal network traffic between a couple of different virtual servers. My ultimate goal will be to install HA clustering software on each server, so isolating cluster traffic on a separate network is important for this type of setup.
How can I get this done? The virtual device only has one network interface out of the box, so I would have to build at least one more and configure it to do "internal" networking.
Thanks in advance for any pointers or assistance that you might give,
Tom Hanstra
I was looking for the same thing myself and found that the easiest way to enable private network connectivity between virtual guests was to create a virtual "isloated" network.
This can be done surprisingly easily through Virtual Machine Manager. If you're using the command line only, I'm afraid you'll have to search out the syntax.
1. In the Edit menu, click "Connection Details"
2. Click the "Virtual Networks" tab
3. Click the plus sign "+" in the bottom left
4. Follow the wizard
a. You can use the defaults for most things but in the "Connecting to a physical network" page, ensure you choose "Isolated virtual network" not "Forwarding to physical network" which is the default.
Then create an interface for each guest on the isolated network you created
Unfortunately after finding this, I realised that I infact want a private network which my physical host can also access. I don't think this will do it, although I'm about to give it a try anyway!
David
Post new comment