Upgraded To 4.0 Today / Won't Startup

D

dmfh

Bit poster
Folks:

I've been having this problem that's appeared in other threads, where after upgrading to Parallels 4.0, I now have a product that will not start with the "can't connect" error. I'm going to provide all the details I think you could possibly need to diagnose this, but I need to place a cautionary comment or two in this thread since I haven't been impressed with the way Parallels has responded to this problem in other threads. Here's my thinking:

- I will provide any and all diagnostics you want to help fix this, and the community.
- Be aware that this bug defect(s) have wasted half a day of my valuable time.
- I'm already engaged with your Sales department to use you as an alternative to VMware commercially.
- My support experience here will directly affect my purchase choices as a CTO.
- If I have a negative support experience here, I will "close the loop for you" by copying responses directly to sales to explain to them why things are not going to proceed forward, or why they are.
- Moving me to another posting, burying my request for help, will have me assume that you really don't want to help me work my problem.
- Parallels needs to be aware that people do not configure their machines just so Parallels can run. People use firewalls, and other software that are part of the "ecosystem" on our machines. VMware works fine on my machine. Other software does too. Your software has to play nicely with others.
- Asking me to delete my Network Preferences is unacceptable, unless Parallels is willing to pay me an hourly rate for my time in reconfiguring my machine and refund my upgrade price.
- I'm an experienced network engineer, supercompute designer & a bit of a coder for Wall St. - talking technical to me is cool and welcome.
- I'm reasonable, and I think your technology is very cool. Working with me means more business for your company. Lets work together.

Now that the ground rules are clear, here's the diagnostic information.

I have tried installing and un-installing 4.0 several times, including disabling the Application firewall and any other firewall software that could have / might have been running, I've also verified on a secure private network that my machine is completely open with a security network auditing tool in our lab, and installing from scratch again - this is not the issue.

I've noticed that Parallels chose to use "en4" and "en5" for the virtual interfaces it defines, whereas they were "en2" and "en3" before under Parallels 3.0


I'm running a MacBook Pro, here's the information about the machine, without the serial number:

Model Name: MacBook Pro
Model Identifier: MacBookPro4,1
Processor Name: Intel Core 2 Duo
Processor Speed: 2.6 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache: 6 MB
Memory: 4 GB
Bus Speed: 800 MHz
Boot ROM Version: MBP41.00C1.B03
SMC Version: 1.28f1


Here's the process table output (prl_disp_service doesn't crash):

somehosts:~ someuser$ ps auxww |grep Parallel
root 244 0.0 0.2 112444 9448 ?? S 4:33PM 0:00.71 /Library/Parallels/Parallels Service.app/Contents/MacOS/prl_disp_service -e --logfile /var/log/prl_disp_service_server.log --pidfile /var/run/prl_disp_service.pid
root 224 0.0 0.1 92140 2848 ?? Ss 4:33PM 0:00.17 /Library/Parallels/Parallels Service.app/Contents/MacOS/prl_naptd
root 69 0.0 0.0 600172 736 ?? Ss 4:32PM 0:00.02 /bin/sh /Library/Parallels/Parallels Service.app/Contents/Resources/ParallelsDispatcherService start


Here's the netstat output (I'm aware of the self-assigned IP address, it didn't work either with an assigned one, has nothing to do with anything anyway):

Luxovius:~ CKMS$ netstat -lan |grep LISTEN
tcp4 0 0 169.245.0.5.110 *.* LISTEN
tcp4 0 0 169.245.0.5.25 *.* LISTEN
tcp4 0 0 169.245.0.4.25 *.* LISTEN
tcp4 0 0 169.245.0.4.110 *.* LISTEN
tcp4 0 0 169.245.0.3.59022 *.* LISTEN
tcp4 0 0 169.245.0.3.59000 *.* LISTEN
tcp4 0 0 169.245.0.3.548 *.* LISTEN
tcp4 0 0 169.245.0.3.80 *.* LISTEN
tcp4 0 0 169.245.0.3.5902 *.* LISTEN
tcp4 0 0 169.245.0.3.5901 *.* LISTEN
tcp4 0 0 169.245.0.3.5900 *.* LISTEN
tcp4 0 0 169.245.0.3.65534 *.* LISTEN
tcp4 0 0 169.245.0.3.110 *.* LISTEN
tcp4 0 0 169.245.0.3.25 *.* LISTEN
tcp4 0 0 169.245.0.3.119 *.* LISTEN
tcp4 0 0 169.245.0.3.1080 *.* LISTEN
tcp4 0 0 169.245.0.2.1080 *.* LISTEN
tcp4 0 0 *.31416 *.* LISTEN
tcp4 0 0 *.64000 *.* LISTEN
tcp4 0 0 127.0.0.1.1313 *.* LISTEN
tcp4 0 0 127.0.0.1.47807 *.* LISTEN
tcp4 0 0 127.0.0.1.631 *.* LISTEN
tcp6 0 0 ::1.631 *.* LISTEN



Since you limit posts to 10,000 characters, see a follow-up post for the rest. Please increase this limit in the future.
 
Part 2 - Upgraded To 4.0 Today / Won't Startup

... (continuing) ...

Here's the lsof output of everything related to Parallels:

bash-3.2# lsof |grep prl_disp
prl_disp_ 244 root cwd DIR 14,2 1462 2 /
prl_disp_ 244 root txt REG 14,2 8029104 99532766 /Library/Parallels/Parallels Service.app/Contents/MacOS/prl_disp_service
prl_disp_ 244 root txt REG 14,2 297056 860623 /usr/lib/libpam.1.dylib
prl_disp_ 244 root txt REG 14,2 901504 705320 /System/Library/Frameworks/OpenAL.framework/Versions/A/OpenAL
prl_disp_ 244 root txt REG 14,2 508368 99532068 /Library/Parallels/Parallels Service.app/Contents/MacOS/libQtXml.4.dylib
prl_disp_ 244 root txt REG 14,2 9627968 99532065 /Library/Parallels/Parallels Service.app/Contents/MacOS/libQtGui.4.dylib
prl_disp_ 244 root txt REG 14,2 842036 99532066 /Library/Parallels/Parallels Service.app/Contents/MacOS/libQtNetwork.4.dylib
prl_disp_ 244 root txt REG 14,2 2034208 99532064 /Library/Parallels/Parallels Service.app/Contents/MacOS/libQtCore.4.dylib
prl_disp_ 244 root txt REG 14,2 148736 676054 /System/Library/Extensions/AudioIPCDriver.kext/Contents/Resources/AudioIPCPlugIn.bundle/Contents/MacOS/AudioIPCPlugIn
prl_disp_ 244 root txt REG 14,2 123056 41454763 /System/Library/Extensions/AppleHDA.kext/Contents/PlugIns/AppleHDAHALPlugIn.bundle/Contents/MacOS/AppleHDAHALPlugIn
prl_disp_ 244 root txt REG 14,2 10235872 41458428 /usr/share/icu/icudt36l.dat
prl_disp_ 244 root txt REG 14,2 1059776 860298 /usr/lib/dyld
prl_disp_ 244 root txt REG 14,2 133242880 75297337 /private/var/db/dyld/dyld_shared_cache_i386
prl_disp_ 244 root 0r CHR 3,2 0t0 113056260 /dev/null
prl_disp_ 244 root 1w CHR 3,2 0t60 113056260 /dev/null
prl_disp_ 244 root 2w CHR 3,2 0t60 113056260 /dev/null
prl_disp_ 244 root 3r CHR 8,1 0t2224 113760132 /dev/urandom
prl_disp_ 244 root 4 PIPE 0x6d13324 16384
prl_disp_ 244 root 5 PIPE 0x6d12f3c 16384
prl_disp_ 244 root 6 PIPE 0x6d13388 16384
prl_disp_ 244 root 7 PIPE 0x6d13004 16384
prl_disp_ 244 root 8u KQUEUE count=0, state=0
prl_disp_ 244 root 9 PIPE 0x6d14328 16384
prl_disp_ 244 root 10 PIPE 0x6d1438c 16384
prl_disp_ 244 root 11u KQUEUE count=0, state=0x2
prl_disp_ 244 root 12 PIPE 0x6d139c8 16384
prl_disp_ 244 root 13 PIPE 0x6d14968 16384
prl_disp_ 244 root 14u unix 0x6d112a8 0t0 ->(none)
prl_disp_ 244 root 15 PIPE 0x6d12b54 16384
prl_disp_ 244 root 16 PIPE 0x6d12af0 16384
prl_disp_ 244 root 17 PIPE 0x6d13194 16384
prl_disp_ 244 root 18 PIPE 0x6d12c1c 16384
prl_disp_ 244 root 19u IPv4 0x6f0e66c 0t0 TCP *:64000 (LISTEN)
prl_disp_ 244 root 20u IPv4 0x69cd0f8 0t0 UDP localhost:64000
prl_disp_ 244 root 21 PIPE 0x6d12a28 16384
prl_disp_ 244 root 22 PIPE 0x6d12898 16384
prl_disp_ 244 root 23r DIR 14,2 816 530484 /Library/Logs/CrashReporter
prl_disp_ 244 root 24 PIPE 0x6d128fc 16384
prl_disp_ 244 root 25 PIPE 0x6d12bb8 16384
prl_disp_ 244 root 26 PIPE 0x6d12834 16384
prl_disp_ 244 root 27 PIPE 0x6d127d0 16384
prl_disp_ 244 root 28 PIPE 0x6d1276c 16384
prl_disp_ 244 root 29 PIPE 0x6d12708 16384
prl_disp_ 244 root 30u unix 0x7215a18 0t0 ->0x7215908
prl_disp_ 244 root 31 PIPE 0x6d126a4 16384
prl_disp_ 244 root 32 PIPE 0x6d12640 16384
prl_disp_ 244 root 33u unix 0x7f3e660 0t0 ->(none)
bash-3.2#
bash-3.2# lsof |grep Para
sh 69 root 255r REG 14,2 6279 99532102 /Library/Parallels/Parallels Service.app/Contents/Resources/ParallelsDispatcherService
prl_naptd 224 root txt REG 14,2 818620 99532086 /Library/Parallels/Parallels Service.app/Contents/MacOS/prl_naptd
prl_naptd 224 root txt REG 14,2 508368 99532068 /Library/Parallels/Parallels Service.app/Contents/MacOS/libQtXml.4.dylib
prl_naptd 224 root txt REG 14,2 842036 99532066 /Library/Parallels/Parallels Service.app/Contents/MacOS/libQtNetwork.4.dylib
prl_naptd 224 root txt REG 14,2 2034208 99532064 /Library/Parallels/Parallels Service.app/Contents/MacOS/libQtCore.4.dylib
prl_disp_ 244 root txt REG 14,2 8029104 99532766 /Library/Parallels/Parallels Service.app/Contents/MacOS/prl_disp_service
prl_disp_ 244 root txt REG 14,2 508368 99532068 /Library/Parallels/Parallels Service.app/Contents/MacOS/libQtXml.4.dylib
prl_disp_ 244 root txt REG 14,2 9627968 99532065 /Library/Parallels/Parallels Service.app/Contents/MacOS/libQtGui.4.dylib
prl_disp_ 244 root txt REG 14,2 842036 99532066 /Library/Parallels/Parallels Service.app/Contents/MacOS/libQtNetwork.4.dylib
prl_disp_ 244 root txt REG 14,2 2034208 99532064 /Library/Parallels/Parallels Service.app/Contents/MacOS/libQtCore.4.dylib
bash-3.2#

telnet'ing to the tcp/64000 port proves the prl_disp is alive and there is no firewall on any interface:

bash-3.2# telnet 127.0.0.1 64000
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
PRLT4.0.3522.205912 (Sat, 08 Nov 2008 11:44:50)^]
telnet> close
Connection closed.
bash-3.2# telnet 169.245.0.3 64000
Trying 169.245.0.3...
Connected to nexus6.priv.dmfh.cx.
Escape character is '^]'.
PRLT4.0.3522.205912 (Sat, 08 Nov 2008 11:44:50)^[close
^]
telnet> close
Connection closed.
bash-3.2#


Last, the extensions output related to Parallels:

bash-3.2# kextstat |grep para
79 0 0x54ee7000 0x4000 0x3000 com.parallels.kext.prl_usb_connect (4.0 3522.205912) <36 7 6 5 4>
115 0 0x5ba59000 0x3000 0x2000 com.parallels.kext.prl_hid_hook (4.0 3522.205912) <7 6 5 4 2>
117 0 0x6b513000 0x8d000 0x8c000 com.parallels.kext.prl_hypervisor (4.0 3522.205912) <12 7 6 5 4 2>
125 0 0x5c101000 0x5000 0x4000 com.parallels.kext.prl_vnic (4.0 3522.205912) <92 5 4>
126 0 0x5c106000 0x7000 0x6000 com.parallels.kext.prl_netbridge (4.0 3522.205912) <6 5 4 2>
bash-3.2#


I need a solution to this problem, fast.

Many thanks in advance, any requests by you for information will be responded to promptly. Working on this over the weekend is recommended.
 
Hi.

Sorry to hear that you have such issues with our new product. Could you to do following things:

1. Attach here /Library/Logs/parallels.log file
2. Try to monitor TCP activity through tcpdump:

startup tcpdump with command "sudo tcpdump -i lo0" and then startup Parallels Desktop. Please post here result of monitoring (actually you can open ticket at support.parallels.com and post there results in order to prevent to public any private info on forum; just notify me with ticket id and i'll get it to myself).
 
Information Requested

Thank you.

I'll post what you need here, I can "sanitize" the data and remove IP addresses / user login accounts as needed, etc.

Here's the TCPDUMP output, I first filtered out the normal traffic there to try to capture Parallels traffic if there was any, but I didn't see any, so I just used "tcpdump -n -i lo0" as you'd asked (the -n just prevents DNS resolution) and here's the result. I'm pretty sure no traffic was seen.

tcpdump -n -i lo0
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on lo0, link-type NULL (BSD loopback), capture size 96 bytes
14:35:45.639182 IP 127.0.0.1.49213 > 127.0.0.1.31416: P 3046429588:3046429655(67) ack 2591160144 win 6944 <nop,nop,timestamp 1008522551 1008522541>
14:35:45.639210 IP 127.0.0.1.31416 > 127.0.0.1.49213: . ack 67 win 6943 <nop,nop,timestamp 1008522551 1008522551>
14:35:45.639369 IP 127.0.0.1.31416 > 127.0.0.1.49213: P 1:583(582) ack 67 win 6944 <nop,nop,timestamp 1008522551 1008522551>
14:35:45.639386 IP 127.0.0.1.49213 > 127.0.0.1.31416: . ack 583 win 6935 <nop,nop,timestamp 1008522551 1008522551>
14:35:45.639737 IP 127.0.0.1.49213 > 127.0.0.1.31416: P 67:132(65) ack 583 win 6944 <nop,nop,timestamp 1008522551 1008522551>
14:35:45.639750 IP 127.0.0.1.31416 > 127.0.0.1.49213: . ack 132 win 6943 <nop,nop,timestamp 1008522551 1008522551>
14:35:45.639857 IP 127.0.0.1.31416 > 127.0.0.1.49213: P 583:6666(6083) ack 132 win 6944 <nop,nop,timestamp 1008522551 1008522551>
14:35:45.639871 IP 127.0.0.1.49213 > 127.0.0.1.31416: . ack 6666 win 6849 <nop,nop,timestamp 1008522551 1008522551>
14:35:46.296381 IP 127.0.0.1.1313 > 127.0.0.1.49259: P 3338914314:3338914493(179) ack 3751764065 win 6944 <nop,nop,timestamp 1008522558 1008522508>
14:35:46.296410 IP 127.0.0.1.49259 > 127.0.0.1.1313: . ack 179 win 6941 <nop,nop,timestamp 1008522558 1008522558>
14:35:46.639167 IP 127.0.0.1.49213 > 127.0.0.1.31416: P 132:199(67) ack 6666 win 6944 <nop,nop,timestamp 1008522561 1008522551>
14:35:46.639203 IP 127.0.0.1.31416 > 127.0.0.1.49213: . ack 199 win 6943 <nop,nop,timestamp 1008522561 1008522561>
14:35:46.639298 IP 127.0.0.1.31416 > 127.0.0.1.49213: P 6666:7248(582) ack 199 win 6944 <nop,nop,timestamp 1008522561 1008522561>
14:35:46.639348 IP 127.0.0.1.49213 > 127.0.0.1.31416: . ack 7248 win 6935 <nop,nop,timestamp 1008522561 1008522561>
14:35:46.639900 IP 127.0.0.1.49213 > 127.0.0.1.31416: P 199:264(65) ack 7248 win 6944 <nop,nop,timestamp 1008522561 1008522561>
14:35:46.639929 IP 127.0.0.1.31416 > 127.0.0.1.49213: . ack 264 win 6943 <nop,nop,timestamp 1008522561 1008522561>
14:35:46.640034 IP 127.0.0.1.31416 > 127.0.0.1.49213: P 7248:13331(6083) ack 264 win 6944 <nop,nop,timestamp 1008522561 1008522561>
14:35:46.640048 IP 127.0.0.1.49213 > 127.0.0.1.31416: . ack 13331 win 6849 <nop,nop,timestamp 1008522561 1008522561>
14:35:47.582916 IP 127.0.0.1.1313 > 127.0.0.1.50592: P 3752569000:3752569179(179) ack 412364217 win 6944 <nop,nop,timestamp 1008522570 1008522520>
14:35:47.582956 IP 127.0.0.1.50592 > 127.0.0.1.1313: . ack 179 win 6941 <nop,nop,timestamp 1008522570 1008522570>
14:35:47.639141 IP 127.0.0.1.49213 > 127.0.0.1.31416: P 264:331(67) ack 13331 win 6944 <nop,nop,timestamp 1008522571 1008522561>
14:35:47.639177 IP 127.0.0.1.31416 > 127.0.0.1.49213: . ack 331 win 6943 <nop,nop,timestamp 1008522571 1008522571>
14:35:47.639282 IP 127.0.0.1.31416 > 127.0.0.1.49213: P 13331:13913(582) ack 331 win 6944 <nop,nop,timestamp 1008522571 1008522571>
14:35:47.639306 IP 127.0.0.1.49213 > 127.0.0.1.31416: . ack 13913 win 6935 <nop,nop,timestamp 1008522571 1008522571>
14:35:47.640003 IP 127.0.0.1.49213 > 127.0.0.1.31416: P 331:396(65) ack 13913 win 6944 <nop,nop,timestamp 1008522571 1008522571>
14:35:47.640025 IP 127.0.0.1.31416 > 127.0.0.1.49213: . ack 396 win 6943 <nop,nop,timestamp 1008522571 1008522571>
14:35:47.640256 IP 127.0.0.1.31416 > 127.0.0.1.49213: P 13913:19996(6083) ack 396 win 6944 <nop,nop,timestamp 1008522571 1008522571>
14:35:47.640297 IP 127.0.0.1.49213 > 127.0.0.1.31416: . ack 19996 win 6849 <nop,nop,timestamp 1008522571 1008522571>
14:35:48.639131 IP 127.0.0.1.49213 > 127.0.0.1.31416: P 396:463(67) ack 19996 win 6944 <nop,nop,timestamp 1008522581 1008522571>
14:35:48.639157 IP 127.0.0.1.31416 > 127.0.0.1.49213: . ack 463 win 6943 <nop,nop,timestamp 1008522581 1008522581>
14:35:48.639231 IP 127.0.0.1.31416 > 127.0.0.1.49213: P 19996:20578(582) ack 463 win 6944 <nop,nop,timestamp 1008522581 1008522581>
14:35:48.639267 IP 127.0.0.1.49213 > 127.0.0.1.31416: . ack 20578 win 6935 <nop,nop,timestamp 1008522581 1008522581>
14:35:48.639555 IP 127.0.0.1.49213 > 127.0.0.1.31416: P 463:528(65) ack 20578 win 6944 <nop,nop,timestamp 1008522581 1008522581>
14:35:48.639595 IP 127.0.0.1.31416 > 127.0.0.1.49213: . ack 528 win 6943 <nop,nop,timestamp 1008522581 1008522581>
14:35:48.639706 IP 127.0.0.1.31416 > 127.0.0.1.49213: P 20578:26661(6083) ack 528 win 6944 <nop,nop,timestamp 1008522581 1008522581>
14:35:48.639745 IP 127.0.0.1.49213 > 127.0.0.1.31416: . ack 26661 win 6849 <nop,nop,timestamp 1008522581 1008522581>
14:35:49.639186 IP 127.0.0.1.49213 > 127.0.0.1.31416: P 528:595(67) ack 26661 win 6944 <nop,nop,timestamp 1008522591 1008522581>
14:35:49.639212 IP 127.0.0.1.31416 > 127.0.0.1.49213: . ack 595 win 6943 <nop,nop,timestamp 1008522591 1008522591>
14:35:49.639287 IP 127.0.0.1.31416 > 127.0.0.1.49213: P 26661:27243(582) ack 595 win 6944 <nop,nop,timestamp 1008522591 1008522591>
14:35:49.639300 IP 127.0.0.1.49213 > 127.0.0.1.31416: . ack 27243 win 6935 <nop,nop,timestamp 1008522591 1008522591>
14:35:49.639841 IP 127.0.0.1.49213 > 127.0.0.1.31416: P 595:660(65) ack 27243 win 6944 <nop,nop,timestamp 1008522591 1008522591>
14:35:49.639853 IP 127.0.0.1.31416 > 127.0.0.1.49213: . ack 660 win 6943 <nop,nop,timestamp 1008522591 1008522591>
14:35:49.640049 IP 127.0.0.1.31416 > 127.0.0.1.49213: P 27243:33326(6083) ack 660 win 6944 <nop,nop,timestamp 1008522591 1008522591>
14:35:49.640071 IP 127.0.0.1.49213 > 127.0.0.1.31416: . ack 33326 win 6849 <nop,nop,timestamp 1008522591 1008522591>
14:35:50.639339 IP 127.0.0.1.49213 > 127.0.0.1.31416: P 660:727(67) ack 33326 win 6944 <nop,nop,timestamp 1008522601 1008522591>
14:35:50.639430 IP 127.0.0.1.31416 > 127.0.0.1.49213: . ack 727 win 6943 <nop,nop,timestamp 1008522601 1008522601>
14:35:50.639566 IP 127.0.0.1.31416 > 127.0.0.1.49213: P 33326:33908(582) ack 727 win 6944 <nop,nop,timestamp 1008522601 1008522601>
14:35:50.639630 IP 127.0.0.1.49213 > 127.0.0.1.31416: . ack 33908 win 6935 <nop,nop,timestamp 1008522601 1008522601>
14:35:50.640208 IP 127.0.0.1.49213 > 127.0.0.1.31416: P 727:792(65) ack 33908 win 6944 <nop,nop,timestamp 1008522601 1008522601>
14:35:50.640234 IP 127.0.0.1.31416 > 127.0.0.1.49213: . ack 792 win 6943 <nop,nop,timestamp 1008522601 1008522601>
14:35:50.640425 IP 127.0.0.1.31416 > 127.0.0.1.49213: P 33908:39991(6083) ack 792 win 6944 <nop,nop,timestamp 1008522601 1008522601>
14:35:50.640455 IP 127.0.0.1.49213 > 127.0.0.1.31416: . ack 39991 win 6849 <nop,nop,timestamp 1008522601 1008522601>
14:35:51.296804 IP 127.0.0.1.1313 > 127.0.0.1.49259: P 179:358(179) ack 1 win 6944 <nop,nop,timestamp 1008522607 1008522558>
14:35:51.296895 IP 127.0.0.1.49259 > 127.0.0.1.1313: . ack 358 win 6941 <nop,nop,timestamp 1008522607 1008522607>
14:35:51.639319 IP 127.0.0.1.49213 > 127.0.0.1.31416: P 792:859(67) ack 39991 win 6944 <nop,nop,timestamp 1008522611 1008522601>
14:35:51.639357 IP 127.0.0.1.31416 > 127.0.0.1.49213: . ack 859 win 6943 <nop,nop,timestamp 1008522611 1008522611>
14:35:51.639468 IP 127.0.0.1.31416 > 127.0.0.1.49213: P 39991:40573(582) ack 859 win 6944 <nop,nop,timestamp 1008522611 1008522611>
14:35:51.639497 IP 127.0.0.1.49213 > 127.0.0.1.31416: . ack 40573 win 6935 <nop,nop,timestamp 1008522611 1008522611>
14:35:51.639948 IP 127.0.0.1.49213 > 127.0.0.1.31416: P 859:924(65) ack 40573 win 6944 <nop,nop,timestamp 1008522611 1008522611>
14:35:51.639974 IP 127.0.0.1.31416 > 127.0.0.1.49213: . ack 924 win 6943 <nop,nop,timestamp 1008522611 1008522611>
14:35:51.640193 IP 127.0.0.1.31416 > 127.0.0.1.49213: P 40573:46656(6083) ack 924 win 6944 <nop,nop,timestamp 1008522611 1008522611>
14:35:51.640218 IP 127.0.0.1.49213 > 127.0.0.1.31416: . ack 46656 win 6849 <nop,nop,timestamp 1008522611 1008522611>
^C
62 packets captured
62 packets received by filter
0 packets dropped by kernel

The Parallels log file is attached as parallels.txt
 

Attachments

Same here?

I'm also only getting the error message "Unable to connect to Parallels Desktop. You may experience a connection problem or your Mac may be down. Contact the Parallels support team for assistance." After installation.

Edit:
Parallels-Desktop-4.0.3522.205912.dmg (trial)
Clean install, no bootcamp or previous versions.

I'm not that good with Unix command line, but i'll try to post the same info here...


Model Name: MacBook Pro
Model Identifier: MacBookPro3,1
Processor Name: Intel Core 2 Duo
Processor Speed: 2.4 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache: 4 MB
Memory: 2 GB
Bus Speed: 800 MHz
Boot ROM Version: MBP31.0070.B07
SMC Version: 1.16f8
Serial Number: W87307C6X92
Sudden Motion Sensor:
State: Enabled

Process table


Js-MacBook-24:~ jukarttu$ ps auxww |grep Parallel
jukarttu 9250 1.0 0.0 75492 344 s000 R+ 10:15PM 0:00.00 grep Parallel
root 8944 0.0 0.4 112392 9324 ?? S 9:41PM 0:00.95 /Library/Parallels/Parallels Service.app/Contents/MacOS/prl_disp_service -e --logfile /var/log/prl_disp_service_server.log --pidfile /var/run/prl_disp_service.pid
root 8917 0.0 0.1 92140 2816 ?? Ss 9:41PM 0:00.27 /Library/Parallels/Parallels Service.app/Contents/MacOS/prl_naptd
root 8771 0.0 0.0 75884 736 ?? Ss 9:40PM 0:00.02 /bin/sh /Library/Parallels/Parallels Service.app/Contents/Resources/ParallelsDispatcherService start

Netstat output

Js-MacBook-24:~ jukarttu$ netstat -lan |grep LISTEN
tcp4 0 0 *.64000 *.* LISTEN
tcp4 0 0 127.0.0.1.10993 *.* LISTEN
tcp4 0 0 127.0.0.1.10995 *.* LISTEN
tcp4 0 0 127.0.0.1.14444 *.* LISTEN
tcp4 0 0 127.0.0.1.15190 *.* LISTEN
tcp4 0 0 127.0.0.1.10143 *.* LISTEN
tcp4 0 0 127.0.0.1.10110 *.* LISTEN
tcp4 0 0 127.0.0.1.10587 *.* LISTEN
tcp4 0 0 127.0.0.1.10025 *.* LISTEN
tcp4 0 0 127.0.0.1.9000 *.* LISTEN
tcp4 0 0 127.0.0.1.631 *.* LISTEN
tcp6 0 0 ::1.631 *.* LISTEN
 
Last edited:
Not really sure how to do that other stuff...

Log file attached.
I have tried installing, reinstalling, uninstalling, restarting, and fixing file permissions.
Sometimes installation / uninstallation freezes, and the computer stops responding, and i need to hard reset the machine by keeping power button pressed down for 10 seconds.

Disk utility seems to find some permissions to fix regarding the Parallels log files.

Edit:
Parallels-Desktop-4.0.3522.205912.dmg (trial)
Clean install, no bootcamp or previous versions.
 

Attachments

Last edited:
Guys, thanks for provided info. Unfortunately situation still not clear. Could you please to do follow experiment:

1. Open Terminal
2. Perform there follow commands:

prlctl list -a
prlctl list -a -l youruserlogin@localhost:64000

prlsctl it's Parallels command line utility. First version of command should do local login (actually the same as Parallels Desktop doing) and list all VMs at current VM directory. The second command form let to specify host and port for connection establishment.

dmfh please also use tcpdump on lo0 in order to check whether some TCP activity present from prlctl side.
 
Hi,

Unfortunately I cannot do that anymore.

The good news is that now I succeeded in installing Parallels 4.0
I formatted the hard drive, did clean Mac OS X 10.5 install, ran software update multiple times, and then installed Parallels 4.0 successfully.
 
dmfh

One more idea. If you won't get any significant results with prlctl could you please also do same things under root account (just perform "sudo su -" command from Terminal to get root session).
 
Last edited:
I just received this information and will try this tomorrow and report back the results to this thread. I was expecting the forums would report to me if there were responses to this thread, but I haven't gotten such e-mails, it's like they stopped coming, I'll make a point to check now once each day.
 
Hmm, very strange. Actually it should notify.

Our administrator just checked and determined that system sent you letter about 25 min ago. So you should to receive at least this one letter. If not then please check SPAM filter on your side.
 
Last edited:
Here's the data you wanted, and I'm sure none of this produced activity on lo0, obvious from looking at it:

bash-3.2# prlctl list -a
Login failed: Unable to connect to Parallels Desktop. [-2147483063]

bash-3.2# prlctl list -a -l xxxxxxx@localhost:64000
xxxxxxx@localhost's password:
Login failed: Unable to connect to Parallels Desktop. [-2147483063]

That error code, " -2147483063 ", is suspicious, because it's a "magic number" - if you take the max (negative) value of a 32-bit integer, 4294967296, divide by two, and add 16 (power of two!), you'll get this error number.

And yes, your daemon on port 64000 is definitely running, see below:

bash-3.2# telnet 127.0.0.1 64000
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
PRLT4.0.3522.205912 (Sat, 08 Nov 2008 11:44:50)

prctl is producing no traffic on loopback
 
dmfh

Thank you very much for investigation. Whether you tried to do same things (prlctl commands) under root account?
 
Fixing /etc/hosts Worked.

Cool - so, adding the /etc/hosts entry worked, and I'm now running Parallels and converting my virtual machines over. I've had one crash at the beginning of a conversion though, but it seems to have recovered fine and is proceeding forward. The crash report ID was 14907, sent in a few minutes ago from your bug-submission utility to that server @ port 8080 - I doubt that has anything to do with the original subject of this thread, but I mention here for completeness.

I have downloaded and installed the latest version you indicated from the prior response, so I am running Build 4.0.3540.

I'd like to note for this thread that Parallels is working with the following "security features" enabled in OSX:

- Explicit list of applications allowed to accept incoming connections enabled in the Security System Prefs pane.
- The use of "Little Snitch", the OSX application-sensitive firewall.

So, these shouldn't be a problem for other users.

No worries if the bug was "dumb", the important this is now I, and hopefully many more people are able to use the product, I can develop again, and this got done within the week.

Thanks very much.

I have a new minor issue, which is, Parallels had decided to make "en4" and "en5" it's two new Ethernet interfaces. Why didn't it "recycle" "en2" & "en3" from the prior version of Parallels? I sometimes would care to use Parallels to safely test security issues, like watching machines infecting each other from the safety of a virtual interface disconnected from any network, and scripts for that can be coded with those two interface names - is there any way to fix this?
 
dmfh said:
I've had one crash at the beginning of a conversion though, but it seems to have recovered fine and is proceeding forward. The crash report ID was 14907.
Click to expand...
Thanks for your report - all problem reports with crashes are being processed and are fixed with highest priority.

dmfh said:
I have a new minor issue, which is, Parallels had decided to make "en4" and "en5" it's two new Ethernet interfaces. Why didn't it "recycle" "en2" & "en3" from the prior version of Parallels?
Click to expand...
Decision of interfaces naming is done by MacOS itself - we just "register" new interfaces without specifying any predefined interfaces names. It's not clear if we can guarantee any naming - so far it looks like you'll have to dynamically detect interfaces names in your script.

Regards,
Max
 
Parallels Deleted My Directory!

I just turned in a crash report with the ID# of 14907 about an hour ago, which was the result of Parallels beginning to convert one of my Windows XP Parallels 3 machines. I should note that one such conversion has gone successfully. What happened with this conversion was very disturbing.

I keep my Parallels machines not in one directory, but in many directories, and sometimes, on an encrypted sparseimage (I've done this with Parallels 3 for years) which is a requirement for some of my commercial and government work.

When Parallels converted this machine, and crashed, it took the entire directory with the PVS file, the disk image file, and the "Windows Applications" directory and turned it into a single file. I'm not joking - I couldn't believe what I saw. The directory was gone, and there was literally, a single file on the disk and no more directory.

I keep regular backups, so I'm restoring the directory now, but you need to check if 4.0 makes "assumptions" about things - your product cannot just delete directories on my host because it thinks it is the correct thing to do!

When the machine booted and was converted, it was damaged, showing a default XP installation background screen and some default prompts like "Take A Tour Of XP" - weird, really weird, but I know it was the right machine because of some of the utilities I have in that XP installation that only are in that specific install.

Folks @ Parallels, please listen - the point of making user software is not nice looking widgets and slick screens and helpful install screens - it's to produce a consistent result over and over again. Someone inside of Parallels seems to have decided that features were more important than stability.

I also realize that you have a deal with Kapersky for Anti-Virus and such? But my reaction to it is one of annoyance - it's not a big deal to say "no" to your offer, but guys, I didn't buy your software to pay to look at your advertising, OK? As a user, this makes me feel like I've paid money to be a marketing opportunity. Take this out of the product.
 
dmfh,

None of your files are gone. What Parallels Desktop 4.0 did - it simply converted
your virtual machine folder into Bundle (*.pvm).
Bundle is still a folder - but it looks in Finder as a single entity - you can always
click "Show Contents" on it and see all your files.

As for your VM that showed only "take a tour of XP" - can you please expain
what exactly happened? Upgrade process does not erase any data - it just
upgrades your VM to support SMP/ACPI hardware.

Regards,
Max
 
Directory Still There, New Problem.

OK, I found that my folder hadn't been deleted, indeed, but this process of de-registering and re-registering a virtual machine was a little cumbersome, and in order to get the process started I had to move the files to another folder and start the conversion process again.

What was strange about the conversion process is that when the Parallels Tools installer starts going, which needed me to allow it to access the Internet (I use the ZoneAlarm firewall on that Windows XP installation), it shows the default XP "sky and grass" background with none of my Desktop icons until it has finished, reboots, and then things come back again. You might want to consider replacing that screen (if you are setting it) with something that says "Installing Tools - Please Wait For Reboot".

Now after the conversion, I keep getting prompted to insert my XP CD, it keeps looking for at least this file : acpiec.sys - where can I find this and now manually install it?
 
You must log in or register to reply here.
Back
Top