Parallels 10 - Win XP on Yosemite - Network Issues

[Ben_Backhouse]

I've recently upgraded to OSX10.10 Yosemite with initially Parallels 9 and i had some issues with the network just stopping in XP and locking up Sage (reason for using Parallels). They is no issue with the network within OSX. I upgraded to Parallels 10 to see if that cured the issue but its made no difference. What would be the next steps to sorting the issue? Create a new virtual XP machine and reinstall Sage? I'm reluctant to do that after the issues we had to get it working initially. But i May have no choice.

 

[spiderkarma]

I have Windows XP in Parallels 9.0.24251 running in Yosemite 10.10. The network is bridged over Ethernet. I can ping the OS X host, but syslog traffic no longer arrives there as it did with Mavericks. Console shows the following upon startup of an app in Windows XP that should generate syslog traffic:

10/21/14 4:05:55.630 PM WinAppHelper[1136]: WARNING: The Gestalt selector gestaltSystemVersion is returning 10.9.0 instead of 10.10.0. Use NSProcessInfo's operatingSystemVersion property to get correct system version number.
Call location:
10/21/14 4:05:55.630 PM WinAppHelper[1136]: 0 CarbonCore 0x00007fff8d4b5dc3 ___Gestalt_SystemVersion_block_invoke + 113
10/21/14 4:05:55.630 PM WinAppHelper[1136]: 1 libdispatch.dylib 0x00007fff955d6c13 _dispatch_client_callout + 8
10/21/14 4:05:55.630 PM WinAppHelper[1136]: 2 libdispatch.dylib 0x00007fff955d6b26 dispatch_once_f + 117
10/21/14 4:05:55.630 PM WinAppHelper[1136]: 3 CarbonCore 0x00007fff8d45e4da _Gestalt_SystemVersion + 987
10/21/14 4:05:55.631 PM WinAppHelper[1136]: 4 CarbonCore 0x00007fff8d45e0c7 Gestalt + 144
10/21/14 4:05:55.631 PM WinAppHelper[1136]: 5 QtCorePrl 0x0000000103acfc16 QtCorePrl + 15382
10/21/14 4:05:55.631 PM WinAppHelper[1136]: 6 ??? 0x00007fff6f18aceb 0x0 + 140735057276139

 

[Ben_Backhouse]

Seems to be similar issue to me. Im also bridged over Ethernet. Issue arose after upgrade from Mavericks to Yosemite in both Parallels 9 and 10. The general performance of the VM has taken a nose drive because if this issue too.