Real Time Anti-Virus on Hyper V server

I found a lot of people facing problem with hyper V servers and getting those errors.

Hyper-V-VMMS 18160
Hyper-V-Worker 12030,12010

These events indicate that the Virtual machine couldn’t start due to  another process is accessing the same file.

Actually this error mostly due to running anti-virus application
on the Hyper-V server as it interrupters the VM process.

As running anti-virus application is an essential thing, you must consider exclude those folders on your Hyper-V server

·         Default VM Config Directory

[C:\ProgramData\Microsoft\Windows\Hyper-V]

·         Default VM VHD Directory

[C:\Users\Public\Documents\Hyper-V\Virtual Hard Disks]

·         Custom VHD Directory

[The directory that you store the VHD file]

·         Snapshot Directory

[C:\ProgramData\Microsoft\Windows\Hyper-V\Snapshots]

·         The follow two processes for Hyper-V

1.      Vmms.exe

2.      Vmwp.exe

Can I run my Hyper V VM in Virtual PC ?

Is it possible to run a virtual machine created or running on Hyper V using Virtual PC 2007?

Actually moving from VPC to hyper V is easy process as all you have to do is removing the VM additions and copy the VHD and mount it during creating new virtual machine.

Yesterday I tried the reverse way, I have a virtual machine windows 2003 SP2 running on my Hyper V server. I removed the integrated services and copy the VHD to another machine and tried to run it with VPC.

I failed to start, after loading the BIOS configurations I got a black screen.

I tried to restart it again and get the same results :S

after having some search, I found that John Huang answered to a similar question.

This is because most operating system will detect the presence of an  IO-APIC in the virtual machine environment and install an appropriate HAL in the operating system image. Once that image is started on Virtual Server or Virtual PC where an IO-APIC is not present, the image will fail to boot.

In theory it is possible to swap the HAL, but not in a Microsoft supported.
So the answer remains no.

If you install the Integration Components (and let’s stick to Windows Server 2003 for the example), then we swap the HAL to an APIC HAL as the first part of the installer. At this point, the VHD will no longer boot under Virtual PC and Virtual Server.

For more information about this, please view the article below:

Are VHDs compatible between Hyper-V and Virtual Server and Virtual PC?

http://blogs.technet.com/jhoward/archive/2008/02/28/are-vhds-compatible-between-hyper-v-and-virtual-server-and-virtual-pc.aspx

Hyper-V Virtual Machine Connection

Each virtual machine is opened in a separate Virtual Connection Manager interface (vmconnect.exe)

The Virtual machine Connection client application (VMconnect.exe) uses the Remote Desktop Protocol (RDP).

The Single Port Listener for RDP in the Virtual Machine Management Service listens for incoming connection requests on TCP port 2179 on the parent partition.

The Virtual Machine Connection client application uses the Terminal Services ActiveX control, mstscax.dll  to make the connection to TCP port 2179 when it is launched.

This ActiveX control is the same ActiveX control that is used by the Remote Desktop Connection (RDC) client application, mstsc.exe.

The Virtual Machine Connection client application is simply a shell that utilizes the Terminal Services ActiveX control. This becomes most evident when the Virtual Machine Connection client application is set to the full screen view.

When the Virtual Machine Connection client application connects to port 2179, the Virtual Machine Management Service routes the communication to the worker process for the specified virtual machine.

At the current situation, it only allow one session when you connect to the Virtual Machine.