By default, when virtual machine is created on Hyper-V host, its clock is "bound" to the virtualization host operating system clock via Hyper-V integration services. If there are two or more virtualization hosts in the same network, it may happen the operating system time on one of the hosts to be different comparing to another host.
Just finished some quick but rather indicative tests of VMware vSphere with View 5 and MS Windows 2008 R2 SP1 Hyper-V
We are long time looking for virtualization platform that would allow decent quality of 3D graphics and modeling applications.
To enable or to disable hyper-threading on virtualization hosts?
There are many articles, documents and discussions in Internet and there is no definitive answer about the hyper-threading usage in virtualized environment.
A processor architecture feature that allows a single processor to execute multiple independent threads simultaneously.
Quick check list and brief instructions on hyper-V RemoteFX set up
- Processors must support Second-Level Address Translation (SLAT). Intel-based processors, Extended Page Tables (EPT) == SLAT. AMD-based processors, Nested Page Tables (NPT) == SLAT.
Installing HP DL370 G6 server with 4 integrated network cards and following the HP recommendation about the installation sequence as specified:Host OS: Windows Server 2008 R2 Enterprise with SP1
(1) install Hyper-V and all updates without virtual network
Article on Microsoft Tech Net with the latest information for the supported number of virtual processors and integration services when running different guest operating systems (virtual machines) on Windows Server 2008 R2 Hyper-v
Hyper-V hardware requirement1. 64-bit (x64) processor and 64 bit Windows 2008 (R2) server2. Hardware Virtualization Assists
Enable in the system BIOS:- Intel VT-x (initially codenamed Vanderpool)
- AMD AMD-V (also called SVM and initially codename Pacifica)
3. Hardware Data Execution Prevention
Enable in the system BIOS:- Intel Execute Disable (XD)
- AMD No Execute (NX).
4. SLAT hardware - required for using RemoteFX, highly recommended for traditional server virtualization
Install and configure the microphone on the local PC and set redirection at Remote Desktop Connection
Remote Desktop Connection microphone redirectionAllow audio recording at hostHKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-TcpfDisableAudioCapture REG_DWORD 0x00000000
Allow audio recording at G
Virtualization and CAD software (AutoCAD and similar) at the end of year 2012.
Recently tested XenApp, XenDesktop and Server 2012 with Hyper-V + Nvidia Quadro 4000 and Windows 8 virtual machines.
XenApp is OK with AutoCAD. However AutoCAD LT is not compatible with XenApp - limited to 2 Acad instances only.