PrepAway - Latest Free Exam Questions & Answers

You need to configure Hyper-V to allow higher network throughput and reduce processing overhead related to net

A company has a Windows Server 2012 R2 server that has the Hyper-V role installed. The server has a single
processor and a single 10-gigabit network interfacecard (NIC). 12 virtual machines (VMs) run on the server.
You need to configure Hyper-V to allow higher network throughput and reduce processing overhead related to
network operations. What should you do?

PrepAway - Latest Free Exam Questions & Answers

A.
Run the Windows PowerShell command Set-VMNetworkAdapter -VmqWeight 0 on the VMs.

B.
In Hyper-V Manager, disable the protected networkoption for all NICs on the VMs.

C.
in Hyper-V Manager, enable the Single Root I/O Virtualization (SR-IOV) option on the VMs.

D.
Disable Internet Protocol security (IPsec) task offloading on the VMs.

19 Comments on “You need to configure Hyper-V to allow higher network throughput and reduce processing overhead related to net

  1. Yip kc says:

    Why not answer c, by enable sr-iov?

    I don’t think disable vmq will meet the requirement “You need to configure Hyper-V to allow higher network throughput and reduce processing overhead related to network “




    0



    0
  2. MCSE says:

    VMQ provides improved networking performance to the management operating system as a whole rather than to a specific virtual machine. For the best results, treat queues as a scarce, carefully managed resource. Because queues are allocated to virtual machines on a first-come, first-served basis, making all virtual machines eligible for a queue may result in some queues being given to virtual machines with light traffic instead of those with heavier traffic. Enable VMQ only for those virtual machines with the heaviest inbound traffic. Because VMQ primarily improves receive-side performance, providing queues for virtual machines that receive the most packets provides the most benefit to overall management operating system performance.




    0



    0
  3. MCSE says:

    Bandwidth isn’t necessarily the key benefit of SR-IOV in Hyper-V. The VM Bus can saturate a 10Gb link, but that amount of traffic generates enough CPU load to occupy one core. So if low CPU utilization is a key design goal, SR-IOV is the key. If latency is a critical aspect, SR-IOV gives performance close to a physical NIC.

    On a host where you expect a lot of incoming VM traffic, Dynamic Virtual Machine Queue (dVMQ) distributes the traffic into queues for each VM based on MAC address hashes. It also distributes the interrupts across CPU cores.




    0



    0
  4. Ruben says:

    I would also have to go with answer C.

    “This is identical in functionality to VMQWeight in Windows Server 2008 R2, and expresses a desire for a hardware offload, not a guarantee. A positive number between 1 and 100 is “on”, and 0 is “off”. We do not, in Windows Server “8” use a relative weighting system. All numbers between 1 and 100 mean the same. This design allows us to add ‘weighting’ functionality in the future without needing to change APIs.”

    http://blogs.technet.com/b/jhoward/archive/2012/03/16/everything-you-wanted-to-know-about-sr-iov-in-hyper-v-part-5.aspx




    0



    0
    1. god2600 says:

      John Howard’s article confirms that issuing a VmqWeight 0 to a VM will express the desire to NOT use SR-IOV for the VM.

      If the value was any number between 1 and 100, that would be a good answer.

      That rules out the answer A. Again, C is the only to go.




      0



      0
  5. KameX says:

    Answer is C

    What is SR-IOV

    Requires support in network adapter
    Provides Direct Memory Access to virtual machines
    Increases network throughput
    Reduces network latency
    Reduces CPU overhead on the Hyper-V server
    Virtual machine bypasses virtual switch
    Supports Live Migration, even when different SR_IOV adapters are used
    =====================================================================
    Why the answer is NOT “A”:

    -VmqWeight
    Specifies whether virtual machine queue (VMQ) is to be enabled on the virtual network adapter. . The relative weight describes the affinity of the virtual network adapter to use VMQ. The range of value is from 0 through 100. Specify 0 to disable VMQ on the virtual network adapte

    Dynamic Virtual Machine Queues (D-VMQ) for Hyper-V. VMQ is a hardware virtualization technology that increases the efficiency of network processing when packets are received on a Hyper-V host. This optimizes the networking performance of the host and reduces overhead as packets are delivered to virtual machines.

    Without VMQ technology and RSS, a majority of the network processing would burden CPU0 and would ultimately limit the scale of the solution.




    0



    0
  6. Arie says:

    The correct answer is C, not A. The requirements are to allow higher network throughput and to reduce processing overhead related to network operations. Answer A expresses the desire for a hardware offload, but it is not a guarantee, as other have already pointed out. Answer C enables network traffic to bypass the software switch layer of the virtualization stack. This diminishes the I/O overhead in the software emulation layer, which results in network performance that is almost identical to that of a non-virtualized environment.




    0



    0
  7. dariowins says:

    The best answer is A.

    Exp.
    You can connect a
    virtual switch to different networks, and based on this connection, you can create a private, internal, or
    external virtual switch. If supported by server hardware, you can also use features such as single root I/O
    virtualization (SR-IOV) and Dynamic Virtual Machine Queue, which enable higher network throughput
    and lower CPU utilization.




    0



    0
  8. Samson says:

    answer c is correct. Remember question is asking allow higher network throughput and reduce processing overhead .
    VMQ is using cpu depending on number of cores .However,SR-IOV reduces CPU as well as increases network throughput




    0



    0

Leave a Reply