[ltp] VMware 4.0 serial port problem

[Kang Tin LAI]

Thanks for your information, I just finished some tests on vmware 4.0:

My TP600E:
1) 2.4.20 kernel, XP pro guest.
2) 2.4.20, w2k guest installed from scratch.

Brand C laptop:
1) 2.4.18, XP pro, with new config and reused the vmdk drive files.
2) 2.4.18, w2k

All above the serial port access are not working on high speed (>4800 baud), 
receiver buffer overrun, not sure the transmitter OK or not. :(

Switched back to vmware 3.2, all are OK.

-- 
---
Kang Tin LAI <ktlai@hk.net>
-----

Ted Johansson wrote:
> Kang Tin LAI wrote:
> 
>> Hi,
>>
>> My system:
>>
>> 600E
>> kernel 2.4.20 (slackware 9.0)
>> vmware 3.2 w2k guest
>>
>> The serial port was working fine from w2k guest.
>>
>>
>>
>> After vmware upgraded to 4.0, connected a modem to serial port, and 
>> open the Hyperterminal, set speed to 2400 and send an AT command, AT&V 
>> for example, OK, change speed to 4800, OK but not very stable. For 
>> higher speed, for example 9600, totally not working, an overrun 
>> phenomenon found. I have tried to change the flow control, but no 
>> improvement. I have to spend time to revert to vmware 3.2, then OK, 
>> including 115200. Under linux, serial port is working fine with seyon.
>>
>> Anybody here with different system and experienced the same problem? 
>> Is it a bug of vmware or just my system's problem.
>>
> 
> Had the same problem on the desktop machine (MDK9.1, WinME guest). From
> searching google, it appears to be a bug in vmware 4.0.
> 
> I added some parameter, as suggest on google, concerning the serial port
> in the .vmx configuration file for the VM. I am not 100% sure, but I
> think this is the entry:
> serial1.yieldOnMsrRead = "TRUE" (for com1).
> This reduced the problem to an acceptable level, but it is still
> noticable and loads the VM considerably (WinME on 1800+ Athlon). There
> were other parameters suggestions on goggle, but with no effect for me.
> 
> 
> Regard,   Ted
> 
> 
> 
> 
>