Jump to content
EduGeek EdSec 2026 is Go! 27th Oct in Derby! Join us for a day of EdTech security focused talks, networking, and an evening social ×

KVM Host as HyperV Guest (yes really.) Come a Cropper on Networking?


Recommended Posts

Posted (edited)

Hello all, title says it all really but I'll give the summary.

 

Moving from KVM to HyperV and some of the older or odder Linux VMs (Varnish, chillispot, RT helpdesk) aren't moving over nicely. So, as their lives are limited (most of this will be replaced next year) I decided IN MY WISDOM to make a KVM guest in HyperV and just run those 3 VMs in a KVM standalone, itself a HyperV machine. They're "appliances" anyway and just sit there, so no biggie really.

 

So, I set up a KVM head, all works fine and ran the powershell script that lets you run KVM that way, all fine. What I can't get however is my guests to see any networking.

 

My setup for networking is all tagged packets on all VLANs go to the HyperV heads, which have a teamed NIC. This then appears as a virtual switch for HyperV and VLAN identifiers are used within each virtual machine, depending on the VLAN I want them in. Of course, this is ALSO what I want the KVM head to be doing, so I have three virtual NICs for it; one is for management of it and it's tagged in the servers VLAN and the other two are bonded (probably cack-handedly) with NO VLAN identifier, my thinking being it can then pass tagged packets to the VMs hosted within KVM and I can select the virtual NICs for them.

 

If you're still with me, here's a config for one of the working, hardware KVM heads I'm replacing:

# This filedescribes the network interfaces available on your system
# and how toactivate them. For more information, see interfaces(5).


source/etc/network/interfaces.d/*


# The loopbacknetwork interface
auto lo
iface lo inetloopback


# Primary IF
auto eth0
iface eth0 inetstatic    
   address 10.108.1.33
   netmask255.255.255.0
   network 10.108.1.0
   broadcast10.108.1.255
   gateway 10.108.1.1
   dns-nameservers10.108.1.200 10.108.1.201
   dns-searchmyplace.sch.uk


#Oh boy, here we go.Trying for bonds for guests...
auto enp0s10f0
iface enp0s10f0 inetmanual
   bond-master bond0


auto enp0s10f1
iface enp0s10f1 inetmanual
   bond-master bond0


#Bond to CORE
auto bond0
iface bond0 inetmanual
   bond-mode 802.3ad
   bond-miimon 100
   bond-lacp-rate 1
   bond-slaves none


#Think this one isjust for hotspot
auto xenbr2101
iface xenbr2101 inetmanual
   bridge_portsbond0.2102
   bridge_stp off
   bridge_fd 0
   bridge_waitport off


#Think this one isalso just for hotspot now
auto xenbr2102
iface xenbr2102 inetmanual
   bridge_portsbond0.2102
   bridge_stp off
   bridge_fd 0
   bridge_waitport off


#Regular serversVLAN
auto xenbr10
iface xenbr10 inetmanual
   bridge_portsbond0.10
   bridge_stp off
   bridge_fd 0
   bridge_waitport off

 

 

And here is the config from the new KVM in HyperV:

 

# This filedescribes the network interfaces available on your system
# and how toactivate them. For more information, see interfaces(5).


source/etc/network/interfaces.d/*


# The loopbacknetwork interface
auto lo
iface lo inetloopback


# Primary IF
auto eth0
iface eth0 inetstatic    
   address 10.108.1.33
   netmask255.255.255.0
   network 10.108.1.0
   broadcast10.108.1.255
   gateway 10.108.1.1
   dns-nameservers10.108.1.200 10.108.1.201
   dns-searchmyplace.sch.uk


#Oh boy, here we go.Trying for bonds for guests...
auto enp0s10f0
iface enp0s10f0 inetmanual
   bond-master bond0


auto enp0s10f1
iface enp0s10f1 inetmanual
   bond-master bond0


#Bond to CORE
auto bond0
iface bond0 inetmanual
   bond-mode 802.3ad
   bond-miimon 100
   bond-lacp-rate 1
   bond-slaves none


#Think this one isjust for hotspot
auto xenbr2101
iface xenbr2101 inetmanual
   bridge_portsbond0.2102
   bridge_stp off
   bridge_fd 0
   bridge_waitport off


#Think this one isalso just for hotspot now
auto xenbr2102
iface xenbr2102 inetmanual
   bridge_portsbond0.2102
   bridge_stp off
   bridge_fd 0
   bridge_waitport off


#Regular serversVLAN
auto xenbr10
iface xenbr10 inetmanual
   bridge_portsbond0.10
   bridge_stp off
   bridge_fd 0
   bridge_waitport off

 

Can anyone see what I'm messing up here? Can ping the HyperV KVM head fine, but the VMs (although the options appear in virtual machine manager for KVM) don't get any network and can't ping anything.

 

Thanks for any help! Feel like I'm dividing by zero a bit...

Edited by JRA

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...