Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I just installed Windows2008 in my debian OS with kvm. And i install virtIO nic. I just wanna config virtIO nic with vlan. But after search many times. There seems no solution here. So, Is someone here can resolve my problem?

share|improve this question
up vote 1 down vote accepted

Tagging is something Windows cannot do

From what I have seen, VirtIO does not allow setting a VLAN tag in the guest, however, you can try and use the e1000 NIC emulation instead of virtIO, and install the Intel provided drivers and the PROSet utility, which should be bale to handle dot1q.

I wouldn't recommend following this path, and instead would set up a separate bridge for this VM on top of a tagged interface on the host

Would be great to hear why you must do the tagging in the guests and not on the hosts, like everyone else does

EDIT: Just tried it - PROSet wouldn't install, because it doesn't recognise the emulated e1000 adapter as an Intel adapter, so there goes this chance :)

share|improve this answer

There is no native support for vLANs in Windows (any version). You have to install 3rd party software.

That said, the usual way to pass a vLAN to a VM is to create the vLAN pseudo-nic in the host OS and bridge it into a VM NIC (with VirtIO or emulated NIC). If you need more specific instructions on how to do this just say so and I'll dig something up for you.

share|improve this answer
No kidding? I thought for sure I'd seen VLAN tag options somewhere in windows before, but perhaps that was in third-party NIC drivers. – EEAA Jun 6 '12 at 3:39
thanks for your answer. And thanks for rnxrx. So i understand.And I will follow your advice. – altman Jun 6 '12 at 3:41
@ErikA, yep not built in; most good NIC drivers have options as you note. Same with link aggregation. – Chris S Jun 6 '12 at 4:15

What are you trying to accomplish? You can simply create additional interfaces in kvm and tie them to tagged VLAN's on the host's NIC.

share|improve this answer
This is fit for my work. We must use vlan in the vms. – altman Jun 6 '12 at 3:28

ok if you using an e1000 NIC for tagged-VLANs a little work-a-round follows:

  1. download the software from
  2. start the setup, but do not continue!
  3. go to the Device Manager and update the Windows driver to the Intel driver (you can find the unpacked package under %temp%\rarXXX)
  4. close the Device Manager and continue the setup

now setup will find the NIC and installs Intel ProSet

share|improve this answer


You probably should create networks on your VM host and attach a virtual interface on that network to your guest.

With libvirt, you probably should create a bridge with a vlan interface. Then, create a new virtual interface on that bridge.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.