A: A VM can have between 1 and 64 virtual CPUs in Windows Server 2012 and later. Typically, VMs are given 1, 2, 4, 8 and so on virtual processors. This matches many physical server configurations.
Q: Can I perform a Live Migration from a Hyper-V host with an Intel processor to a Hyper-V host with an AMD processor in Windows Server 2012?
Second, and still related to storage, is the actual space the log files consume. Normally the log files are sent to the replica every five minutes. After confirmation that the log file has been played into the replica VM, the log file is deleted from the primary. However, if there's a large amount of change on the source VM (also called churn), the log file could grow large, and any interruption in the transmission of the log file would result in multiple log files queuing up on the source server, consuming more disk space.
Third, the log files have to be sent over the network, and depending on the workload of the VM, the log files could be large and require network bandwidth to be sent. The more VMs enabled for Hyper-V Replica, the more bandwidth required. If the network bandwidth between the primary and the replica isn't sufficient, the log files will start to queue up and the replica will start to creep further out of synchronization.
Initially, you select the number of logical (virtual) processors that the VM can see, from one to four (assuming the physical host has at least four cores). You can then set various Resource control options, as shown below.