Antsle Forum

Welcome to our Antsle community! This forum is to connect all Antsle users to post experiences, make user-generated content available for the entire community and more. 

Please note: This forum is about discussing one specific issue at a time. No generalizations. No judgments. Please check the Forum Rules before posting. If you have specific questions about your Antsle and expect a response from our team directly, please continue to use the appropriate channels (email: [email protected]) so every inquiry is tracked. 

Forum breadcrumbs - You are here:ForumGeneral: GeneralSDN interface for Windows 10
Please or Register to create posts and topics.

SDN interface for Windows 10

What is the proper method to add a Windows 10 antlet to a software defined network VLAN?  The antlet picks up the virtual interface but there is no corresponding interface in the zpool antlet-libvirt.xml for the antlet (I guess that's expected), since this is a KWM antlet I do see it in the /etc/libvirt/qemu XML file for the antlet but the <model type> is listed as virtio instead of e1000.  Is the correct 'fix' for this to install the virtio drivers, such as has been eluded to in other forum posts, from the stable ISO file on or Github and "update" the driver for the unseen interface?  Or, would it be more appropriate to just perform the edit in /etc/libvirt/qemu for the appropriate antlet XML configuration?

Since this would be a common problem with SDN VLANs for Windows antlets, I'd imagine, is there a canonical method that should be used?  Is this something that can be done in swagger?

Hi infobro:

The easiest approach would be to:  Using antMan, delete the network interface (defined as VirtIO) in your antlet, and then re-create new one using E1000 driver.

For our Linux templates and Windows templates that have "StdGui", they come with with VirtIO drivers pre-installed.

You can feel free to install the VirtIO drivers yourself by following these instructions:

You can download the Fedora windows virtio drivers - from within the windows antlet
This link takes you to the web page
This link will download the stable .iso

Right click and mount the .iso. Then install the Balloon\WIN_VER\amd64\ballon.inf driver to take care of the unknown device in device manager.
Install the viostor\WIN_VER\amd64\viostor.inf driver for storage
Install the NetKVM\WIN_VER\amd64\netkvm.inf driver for the NIC

You will need to edit the xml for the antlet from the antsle's command line/terminal

EDITOR=nano virsh edit ANTLET_NAME

Look for the <disk... section and replace the target bus='e1000' with 'virtio'
and delete the <address... line. This will be recreated by virsh

<disk type='file' device='disk'>
<driver name='qemu' type='qcow2'/>
<source file='/antlets/w10instVirtio/Win10.qcow2'/>
<target dev='sda' bus='virtio'/>

Next Look for the <interface... section and replace the model type='e1000' with 'virtio'
and delete the <address... line. This will be recreated by virsh

<interface type='network'>
<mac address='b2:61:6e:73:6c:19'/>
<source network='bblv'/>
<model type='virtio'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>

You must stop then start the antlet in antMan so it can read the changes.

Yes, the XML files are located in /etc/libvirt/qemu directory but you should use virsh edit command edit your antlet's XML.


Thanks.  I found that installing the VirtIO drivers is the quickest way to get that interface and the memballoon drivers up and running after adding the SDN using antMan.  The only caveat there is that you have to select the right Intel driver, the exact one that is on the E1000 interface that in the Win10 template.

Hi infobro:

Glad that you got it running.

Thanks for sharing.