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 need to buy a nic that I want to eventually (~3 months) re-use for a VM server deployment that will need to support heavy network I/O. Server is a Xeon Gulftown/Westmere-EP.

Intel has server NICs that support VMDc, VMDq, or both.

Which is the difference?

Which do I want? They both seem to deal with the problem of doing per-VM segmentation at the NIC level, but I don't know which technology better.

See VMDc:

See VMDq:

Thank you

share|improve this question
up vote 3 down vote accepted

VMDc is for assigning a single VM its own personal NIC, which breaks all the fun stuff of VMs like live migrations.

VMDq is an extension of processing offload and buffering, often called NetQueue. Go ahead and get that, though it's not going to be a huge boost unless you have some major workloads on the NICs.

share|improve this answer
I do intend to run heavy network I/O in these VM's. For VMDc do you mean a full physical nic per VM, or a single "virtual" nic? For VMDq, how benifit does that bring to a VM? – nonot1 Mar 23 '11 at 20:15
VMDc - full physical NIC assigned to a VM (a la VT-d). VMDQ - The NIC will pre-route the data packets to take the overhead off of the hypervisor. This doesn't really become an issue until you have 10Gbit NICs, though. – Hyppy Mar 23 '11 at 20:23
See Almost seems like VMDc can do 1+ VM per NIC. Can you clarify? How is this different from VMDq? – nonot1 Mar 23 '11 at 21:58

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.