O site de referência é o http://technet.microsoft.com/en-us/library/dd744338(WS.10).aspx – Walkthrough: Deploy a Virtual Hard Disk for Native Boot. É o processo conhecido como Native Boot. Neste link é apresentado um step-by-step do procedimento.

Bons testes.

[]s
Tiago Souza

Pesquisando nos kbs pela internet encontrei o mesmo “problema” apresentado como Ping Negativo.

Segue o link onde encontrei a resolução:

http://blogs.technet.com/b/latam/archive/2009/02/16/hyper-v-e-ping-negativo.aspx

Depois de aplicar a alteração no arquivo boot.ini o ping voltou ao normal:

Resumindo:

“A causa deste fenômeno está no TSC (Time Stamp Counters). Essas estruturas do processador são usadas como fonte de manutenção de tempo para alguns tipos de operação do sistema operacional, como operações de rede. Em uma situação de multicore/multiprocessor podemos encontrar uma falta de sincronismo entre estas estruturas (TSC drift) levando a problemas de comunicação de rede e monitoramento de performance, pois cada core terá um Time Stamp próprio.”

[]s
Tiago Souza

http://virtualizationbrazil.wordpress.com/

[]s
Tiago Souza

http://blogs.technet.com/b/askcore/archive/2008/10/24/configuring-pass-through-disks-in-hyper-v.aspx

Mas lembre-se que você perde a funcionalidade de Live Migration:

http://www.windowsitpro.com/article/virtualization/q-can-a-hyper-v-guest-use-pass-through-disks-and-still-use-live-migration-.aspx

Mais uma consideração sobre pass-through disks:

Pass-through Disks
Fonte: http://www.virtualizationadmin.com/articles-tutorials/microsoft-hyper-v-articles/installation-and-deployment/virtual-machine-disk-options.html

“Besides VHDs, Hyper-V supports pass-through disks, which allow virtual machines to access a physical disk mapped to the Hyper-V host, but that does not have a volume configured on it. Pass-through disks can be physically connected to the Hyper-V host or through a LUN on a SAN. An advantage of pass-through disks is that they are not subject to the 2 TB size limit that is imposed on virtual hard disks. In terms of limitations, pass-through disks do not support dynamically expanding virtual hard disks, differencing disks, or virtual machine snapshots. To ensure that a virtual machine has exclusive access to the physical disk, it must be configured offline on the Hyper-V host.

If you plan to use a pass-through disk to boot a virtual machine guest operating system, the virtual machine configuration file must also be stored on a different storage location. In contrast to virtual hard disks that are only files stored on physical disks, the entire pass-through disk is dedicated to the virtual machine guest operating system. Additionally, if you want to use a pass-through disk to boot a virtual machine guest operating system, it must be attached to a virtual IDE controller. In Hyper-V, the virtual SCSI controller is implemented as a synthetic device whose driver is loaded only after the virtual machine boot phase. Conversely, a pass-through disk that contains only application or data files can be connected to either a virtual IDE controller or virtual SCSI controller.”

[]s
Tiago Souza

Guia para Virtualização de Controladores de Domínio no Hyper-V

Best Practices Analyzer for Hyper-V

Hyper-V and pagefile settings « Jaap Wesselius Virtualization Info

[]s
Tiago Souza

• Active Directory in Hyper-V environments, Part 1
• Active Directory in Hyper-V environments, Part 2
• Active Directory in Hyper-V environments, Part 3

[]s
Tiago Souza

Segue o link: http://www.jonathancusson.com/tag/virtualization-stencil/

[]s
Tiago Souza

Uma leitura legal pra quem pretende virtualizar controladores de domínio no Hyper-V:

• http://technet.microsoft.com/pt-br/library/virtual_active_directory_domain_controller_virtualization_hyperv(WS.10).aspx

Não tem muito segredo, mas sim algumas observações interessantes no documento. Pra não ter dor de cabeça futuramente vale a pena seguir as boas práticas do link.

[]s

Tiago Souza