Unsolved Help me understand KVM Networking
-
So working, but lots of packet loss for a while.
It seems solid now.
Nevermind.. while it was trying to communicate out to get the base repo info, the pings failed. Once that timed out, the pings worked. Just tried it a couple times...
-
@stacksofplates said in Help me understand KVM Networking:
I also usually just use macvtap. If I need host to guest communication I just set up a private network for them to communicate on.
So how do you setup a private connection?
I have no issues with using macvtap on the team.
-
@jaredbusch said in Help me understand KVM Networking:
@stacksofplates said in Help me understand KVM Networking:
I also usually just use macvtap. If I need host to guest communication I just set up a private network for them to communicate on.
So how do you setup a private connection?
I have no issues with using macvtap on the team.
You can just create it in Virt-Manager. I'll jump on my laptop and take a screenshot.
-
Just click on your connection and go to edit -> connection details and click on the Virtual Networks tab.
Click the plus
Then run through the wizard.
If you choose NAT instead it will still work but is kind of pointless since you will already have an address through the macvtap.
You can do this through virsh as well. The host uses dnsmasq to configure everything so you can also add reservations and all of the other goodies as well. For reservations you can just add it in after the range line:
<host mac='de:ad:be:ef:ca:fe' name='test-vm' ip='192.168.30.50'/>
-
Works perfectly.
-
Too bad ovs isnt in the repos for RHEL/CentOS. You can set up these private networks and connect them through a VXLAN with ovs. That way you can have something like a separate dev network on the same hosts and they can communicate between hosts.
-
@stacksofplates said in Help me understand KVM Networking:
Too bad ovs isnt in the repos for RHEL/CentOS. You can set up these private networks and connect them through a VXLAN with ovs. That way you can have something like a separate dev network on the same hosts and they can communicate between hosts.
Not available in the epel repo?
-
@black3dynamite said in Help me understand KVM Networking:
@stacksofplates said in Help me understand KVM Networking:
Too bad ovs isnt in the repos for RHEL/CentOS. You can set up these private networks and connect them through a VXLAN with ovs. That way you can have something like a separate dev network on the same hosts and they can communicate between hosts.
Not available in the epel repo?
That is apparently the case unless my google--fu isn't up to snuff
-
@jaredbusch said in Help me understand KVM Networking:
I will have easy access to the VM, but not the host, because of "reasons" that have nothing to do with IT.
You can't access the host externally, as in you will only be able to access the host via one of it's guests? That seems like a weird requirement.
-
@tim_g said in Help me understand KVM Networking:
@jaredbusch said in Help me understand KVM Networking:
I will have easy access to the VM, but not the host, because of "reasons" that have nothing to do with IT.
You can't access the host externally, as in you will only be able to access the host via one of it's guests? That seems like a weird requirement.
Yes it is. Yet, if I drive 5 hours to be on site, I can have all the local console I want.
As I stated, not IT related reasoning.
-
@wirestyle22 said in Help me understand KVM Networking:
@black3dynamite said in Help me understand KVM Networking:
@stacksofplates said in Help me understand KVM Networking:
Too bad ovs isnt in the repos for RHEL/CentOS. You can set up these private networks and connect them through a VXLAN with ovs. That way you can have something like a separate dev network on the same hosts and they can communicate between hosts.
Not available in the epel repo?
That is apparently the case unless my google--fu isn't up to snuff
Nope. It is available in Fedora though. If you want to install it you have to manually build the RPMs. While not hard to build it would be a pain to maintain updates.
-
@stacksofplates said in Help me understand KVM Networking:
@wirestyle22 said in Help me understand KVM Networking:
@black3dynamite said in Help me understand KVM Networking:
@stacksofplates said in Help me understand KVM Networking:
Too bad ovs isnt in the repos for RHEL/CentOS. You can set up these private networks and connect them through a VXLAN with ovs. That way you can have something like a separate dev network on the same hosts and they can communicate between hosts.
Not available in the epel repo?
That is apparently the case unless my google--fu isn't up to snuff
Nope. It is available in Fedora though. If you want to install it you have to manually build the RPMs. While not hard to build it would be a pain to maintain updates.
OVS is used by oVirt so maybe the centos ovirt repo has it (or the ovirt stable repo)
-
@matteo-nunziati said in Help me understand KVM Networking:
@stacksofplates said in Help me understand KVM Networking:
@wirestyle22 said in Help me understand KVM Networking:
@black3dynamite said in Help me understand KVM Networking:
@stacksofplates said in Help me understand KVM Networking:
Too bad ovs isnt in the repos for RHEL/CentOS. You can set up these private networks and connect them through a VXLAN with ovs. That way you can have something like a separate dev network on the same hosts and they can communicate between hosts.
Not available in the epel repo?
That is apparently the case unless my google--fu isn't up to snuff
Nope. It is available in Fedora though. If you want to install it you have to manually build the RPMs. While not hard to build it would be a pain to maintain updates.
OVS is used by oVirt so maybe the centos ovirt repo has it (or the ovirt stable repo)
I'm assuming it's just building the RPM since it's not in the normal repo.
