KVM networking & teaming
-
I have a Fedora 30 KVM host. I would like to have 2 NICs in a team, acting in an active/failover mode. This is no problem, and I can do it all through Cockpit. Works perfect.
But, I am stuck on the KVM virtual switch. How do I create a virtual switch for KVM so that my VM on the KVM host has direct access to the physical network (NIC team) ? I thought I needed to just create a new virual switch in routed mode, and assign it to the "physical device", which is the NIC team I just created. But it is not allowing me to do that, saying that the device is already in use.
Am I completely missing a simple concept here, not making this possible, or am I going about this the wrong way?
Do I need more coffee?
-
@fuznutz04 said in KVM networking & teaming:
I have a Fedora 30 KVM host. I would like to have 2 NICs in a team, acting in an active/failover mode. This is no problem, and I can do it all through Cockpit. Works perfect.
But, I am stuck on the KVM virtual switch. How do I create a virtual switch for KVM so that my VM on the KVM host has direct access to the physical network (NIC team) ? I thought I needed to just create a new virual switch in routed mode, and assign it to the "physical device", which is the NIC team I just created. But it is not allowing me to do that, saying that the device is already in use.
Am I completely missing a simple concept here, not making this possible, or am I going about this the wrong way?
Do I need more coffee?
By not allowing do you mean that NIC team isn't listed as a physical network, or something's grayed out in Virtual Machine Manager?
-
Nothing is grayed out, but when I finish the setup wizard, it says, "That network is already in use by interface "some other network team that I have configured for something else"
-
@fuznutz04 said in KVM networking & teaming:
Nothing is grayed out, but when I finish the setup wizard, it says, "That network is already in use by interface "some other network team that I have configured for something else"
Is the default network using it?
-
@fuznutz04 said in KVM networking & teaming:
Am I completely missing a simple concept here, not making this possible, or am I going about this the wrong way?
You cannot do this through cockpit at this time.
You have to use Virtual Machine Manager or CLI (virsh).
-
@JaredBusch said in KVM networking & teaming:
@fuznutz04 said in KVM networking & teaming:
Am I completely missing a simple concept here, not making this possible, or am I going about this the wrong way?
You cannot do this through cockpit at this time.
You have to use Virtual Machine Manager or CLI (virsh).
Ah! That's what I was missing then. You are saying that you do not need to create a new virtual switch at all on KVM. You simply specify it in the guest VM network settings?
-
@fuznutz04 no he's saying you can only assign it in VM or via CLI. You still create your team.
-
@DustinB3403 said in KVM networking & teaming:
@fuznutz04 no he's saying you can only assign it in VM or via CLI. You still create your team.
I think he is actually saying, you can create the NIC team in Cockpit. (You can, I did it already), but you then just assign that team, via the VM Guest settings. ...I think.
-
@fuznutz04 said in KVM networking & teaming:
@DustinB3403 said in KVM networking & teaming:
@fuznutz04 no he's saying you can only assign it in VM or via CLI. You still create your team.
I think he is actually saying, you can create the NIC team in Cockpit. (You can, I did it already), but you then just assign that team, via the VM Guest settings. ...I think.
But not in Cockpit. You cannot choose it if you are creating the VM in cockpit.
-
@fuznutz04 said in KVM networking & teaming:
@DustinB3403 said in KVM networking & teaming:
@fuznutz04 no he's saying you can only assign it in VM or via CLI. You still create your team.
I think he is actually saying, you can create the NIC team in Cockpit. (You can, I did it already), but you then just assign that team, via the VM Guest settings. ...I think.
For what's it's worth, that is what I said.
