It may be the virtual network card on the host (the host software emulating
the network card) is really working hard.  Phindows is pretty network
intensive (depending how much things change on your screen) and since you
are using fake network hardware, it is a lot of work for the host.
Just a thought.

Rick..

On Wed, Jun 17, 2009 at 1:46 PM, Ernesto Juarez
<community-noreply@qnx.com>wrote:

> Hi
>   I am testing QNX4.25 on VMware esix4. I installed it and everything seems
> to be working ok. I have been testing different applications and all of them
> perform just as is they were running on physical machines. The problem I
> have is when remote clients connect to the QNX host using phindows to use
> some data display applications. The connections feel very slow in comparison
> to running the host on a physical machine. The host for the virtual machines
> is has much better hardware but still it feels very slow. Does anyone has an
> idea why this happens? Is it maybe the video driver (I am using a vmware
> video driver)? One thing I notice is when the clients connect the cpu on the
> virtual host starts working really hard.
>
>  Thanks in advance for your help
>
> _______________________________________________
> General
> http://community.qnx.com/sf/go/post32006
>
>


-- 
Rick Duff
rgduff@gmail.com

George Carlin<http://www.brainyquote.com/quotes/authors/g/george_carlin.html>;
- "Electricity is really just organized lightning."

How did you managed it to install QNX4.25 into ESX4?
I made it with ESX3.5 and it was a pain with uploading manually changed *.vmx and *.vmdk files.
Actually I can use my QNX4.25 in the ESX-Server but I cannot change the settings using the VMWare Infrastructure GUI.