Yesterday I ran Parallels Beta 4 on/off virtually all day long as I installed WinXP and got a Delphi compiler environment installed. The machine environment yesterday was MacBookPro 2.16ghz, 2gb RAM. I was using the MacBook display, keyboard, and a Microsoft USB mouse. No kernel panics. No problems. To be safe I kept saving the VM after each successful step. MacBook was using Wireless networking. This morning I'm at work, I have the MacBookPro connected to a USB keyboard, USB mouse (Microsoft Desktop Elite). I installed the drivers for this keyboard and mouse which seem to work just fine for the intel OS X. At work I have to use wired LAN. I also installed Microsoft Remote Desktop. I had CiscoVPN, Entourage, Remote Desktop all open. I opened Parallels and booted the WinXP VM. It booted but warned of no connection on LAN. So I stopped the VM. (powered it off... XP had not yet booted) and I changed the VM to have the network point to the wired LAN. I rebooted the VM. It booted fine, no messages about LAN. One annoying thing about VM boot up is that it starts in the center of the display. Because I have WinXP in a fairly large window it goes off the bottom of screen so on every boot up I have to drag it back up. I think the VMs should remember their screen position when shutdown. If on boot up they can restore to that position without being off screen they should. That would help. This is the second time this has done this but as I was dragging the VM window which had the XP display with background and start button in it, when I let go of the mouse after the drag the VM window resized to the small one and went black. This was being done as Windows XP was playing it's wonderful "I'm here to annoy you brrrrring" sound. When the window resizes like this I have not figured out how to get the VM display back. So I powered it off. Without restarting parallels I rebooted the VM. Thinking this was due to dragging the window at a bad time. I waited until the VM fully booted into XP and then drug the window. It was fine this fime. I had to copy a zip file over to finish my compiler install. I connected to the machine via LAN which worked nice, copied the zip. Right clicked on it and started to unzip it. The Mac did the wonderful slow screen fade with the messages in every possible language to reboot by pressing the power button. That was my first Kernel panic on this MacBookPro and under Beta 4. I would bet it was probably caused somehow by all the reboots and window drags etc etc. I find when I quit Parallels and run the VM fresh it is much more stable. I rebooted the Mac and luckily everything seems to be ok. I powered up Parallels and the VM was pretty hosed. Files looked ok but were truncated (source files). It would have made me REAL nervous to try and use anything produced in there from that session. So I just drug my archive of the VM over and will try it again. I've attached the panic log below. So far I'm impressed. It seems to work well but I am nervous yet about using it for real work. I hope we can continue to get it more and more stable. On the networking thing, both wireless and wired work however you have to select which one you want in the VM settings. I would like to see the VM on boot BEFORE the OS is initiated check the LAN connections and ask you to change them BEFORE the boot of the OS. This shouldn't be hard. Just check the LAN setting for a connection, if not active then pop up a dialog allowing you to select the desired one. I will be going between wired and wireless A LOT! I think my kernel panic was mainly caused by having to stop the VM and the window drag issue. Not sure. Hopefully the log will help you guys. Mark panic.log: Description: Panic (system crashes) log Size: 1.05 KB Last Modified: 4/21/06 7:15 AM Location: /Library/Logs/panic.log Recent Contents: Fri Apr 21 07:15:29 2006 panic(cpu 0 caller 0x0019CAEF): Unresolved kernel trap (CPU 0, Type 14=page fault), registers: CR0: 0x8001003b, CR2: 0x00000000, CR3: 0x00e05000, CR4: 0x000026e0 EAX: 0x00000000, EBX: 0x03797230, ECX: 0x03797230, EDX: 0x00000020 ESP: 0x00000000, EBP: 0x2519bf14, ESI: 0x03071268, EDI: 0x03797244 EFL: 0x00010012, EIP: 0x00190841, CS: 0x00000008, DS: 0x25190010 Backtrace, Format - Frame : Return Address (4 potential args on stack) 0x2519bd94 : 0x128b5e (0x3bbeb8 0x2519bdb8 0x131bbc 0x0) 0x2519bdd4 : 0x19caef (0x3c1340 0x0 0xe 0x3c10f8) 0x2519be84 : 0x197b53 (0x2519be98 0x2519bf14 0x190841 0x190048) 0x2519be90 : 0x190841 (0x190048 0x10 0x10 0x25190010) 0x2519bf14 : 0x19092e (0xcade 0x20 0x2519bfb4 0x194f61) 0x2519bf34 : 0x178e6f (0xcade 0x445f80 0x8 0x19cb02) 0x2519bfb4 : 0x179102 (0x194756 0x1 0x0 0x4a1000) 0x2519bfd4 : 0x197a21 (0x0 0x0 0x4461f8 0x3797230) Backtrace terminated-invalid frame pointer 0x0 Kernel version: Darwin Kernel Version 8.6.1: Tue Mar 7 16:55:45 PST 2006; root:xnu-792.9.22.obj~1/RELEASE_I386 *********
I should mention that when I go to work I have the MacBookPro in lid closed mode using an external DV monitor, a Dell 21" at 1600x1200. I just restarted Parallels, let it fully boot XP. The window resized and displayed the XP background and toolbar I let it sit without touching it for a few moments. The windows XP sound played then suddenly on it's own it resized to the smaller black window. I tried going to full screen and back, no luck. When this happens I seem to have no choice but to power off the VM (which maybe corrupts it?). M
Is this the right place to post the kernel panic? How do I know if you guys at Parallels got this? Mark
Hello guys, From the 4th post on the forum We've made a serious work with recent three betas. Thanks to everyone experiencing kernel panics and sending them to us. They really do help us progress, without you there wouldn't be any beta4 possible. We do expect beta4 to be much more stable than previous betas. And we badly need your help in hunting for kernel panics left. If you experience one, please share the logs with us. You'll only need to 1. Open Applications->Utilities->System Profiler. In System Profiler find Software->Logs->panic.log. This is the file containing necessary technical information about the panic. 2. And send us the log file as well as the desription of what you were doing that time. Any special actions? Any other info you think might be important? Please send this staff to [email protected]. Use this mailbox for kernel panic reports only please. Last edited by Tim Surgent : 04-18-2006 at 04:58 PM
