Jason Yoder, MCT

In Hyper-V R1, we had the option to export out a VM and then later import it back in again.  For many in testing environments, this created large export files when only the VM with a specific snapshot was needed.  With Hyper-V R2 we can now create a new VM from a snapshot of another one.  This is advantageous because now you can create an entire new VM without all the extra files from other snapshots that you may not want.  Take a look at my screen shot below of my snapshot tree. Let’s say that I want to create a new VM from this one. Apply the snapshot that you want to use as the base for the new VM. Right click the VM and select Export.  Give it a location and click Export . One thing that I do not like about this process is that you will not see any progress bars or other indicators to let you know when the export is finished.  Your VMs will not be able to start until the export is completed.  If you look in the destination that you specified, ...

VMQ allows for packets destined for a virtual network adapter to be delivered directly to that adapter instead of first being copied from the management operating system to the virtual machine.  When a VMQ is created, all the data directed for the VM is placed in the queue for delivery to the VM.  Multicast and broadcast traffic is still routed through the default queue.   The requirements for VMQ: The management OS must be running Windows Server 2008 R2 The physical NIC must support VMQ. The virtual machine must be running Windows 7 or Windows Server 2008 R2.  Windows Vista and Windows Server 2008 will support WMQ if the Integration Services are installed.   To configure VMQ, open System Center Virtual Machine manager. Select the VM that you want to configure VMQ and open the properties. Click the Hardware Configuration tab. Check Enable virtual network optimizations . Click OK