New Mac Pro version of Parallels Desktop causing kernel panics

I have installed the new build of Parallels Desktop and have had two kernel panics in the process of trying to set up new virtual machines (Windows XP). Machine is running 10.4.7 with 3GB of RAM. The only thing that might be a bit off is the fact that I'm putting the VM on a different hard drive than the one Parallels resides on.

Kernel panic happened when Windows XP was about to start installing.

Dumps from the KPs:

Code:

panic(cpu 1 caller 0x003A2287): getPhysicalSegment() out of 32b range 0x100000000, len 0x48000, class IOGeneralMemoryDescriptor
Backtrace, Format - Frame : Return Address (4 potential args on stack) 
0x3796b938 : 0x128cdb (0x3c99c4 0x3796b95c 0x131cdf 0x0) 
0x3796b978 : 0x3a2287 (0x3edad8 0x0 0x1 0x48000) 
0x3796ba48 : 0x3a41e5 (0x7c11580 0x1b8000 0x0 0x6b38b90) 
0x3796ba68 : 0x5597c67f (0x67e24c0 0x1b8000 0x0 0x67e24c0) 
0x3796baa8 : 0x5597c0db (0x67e2480 0x400000 0x67e2480 0x6d616769) 
0x3796bae8 : 0x5597dd72 (0x54f55000 0x400 0x0 0x54873fd5) 
0x3796bb38 : 0x5597d0a7 (0x77d9f04 0x18 0x600000 0x199103) 
0x3796bbf8 : 0x5597d383 (0x77d9f04 0x3796bec8 0x18 0x3bc94d) 
0x3796bd58 : 0x5597b5c5 (0x77d9f04 0xc0185401 0x3796bec8 0x7890010) 
0x3796bd78 : 0x1f00f7 (0xa000000 0xc0185401 0x3796bec8 0x81) 
0x3796bdb8 : 0x1e7045 (0x3796bde0 0x297 0x3796be18 0x1d09ee) 
0x3796be18 : 0x1deee9 (0x89cc000 0xc0185401 0x3796bec8 0x81) 
0x3796be68 : 0x3305b4 (0x737f580 0xc0185401 0x3796bec8 0x84785dc) 
0x3796be98 : 0x34e881 (0x737f580 0xc0185401 0x3796bec8 0x84785dc) 
0x3796bf68 : 0x378f9c (0x84785dc 0x7a7b780 0x7a7b7c4 0x0) 
0x3796bfc8 : 0x19b0ee (0x725c900 0x0 0x19e0b5 0x5e9ae50) 	Backtrace continues...
      Kernel loadable modules in backtrace (with dependencies):
         com.parallels.kext.vmmain(2.2)@0x5597a000

Kernel version:
Darwin Kernel Version 8.7.2: Tue Jul 25 23:09:54 PDT 2006; root:xnu-792.10.96.obj~3/RELEASE_I386

Model: MacPro1,1, BootROM MP11.005C.B00, 4 processors, Dual-Core Intel Xeon, 2.66 GHz, 3 GB
Graphics: NVIDIA GeForce 7300 GT, NVIDIA GeForce 7300 GT, PCIe, 256 MB
Graphics: NVIDIA GeForce 7300 GT, NVIDIA GeForce 7300 GT, PCIe, 256 MB
Memory Module: DIMM Riser A/DIMM 1, 512 MB, DDR2 FB-DIMM, 667 MHz
Memory Module: DIMM Riser A/DIMM 2, 512 MB, DDR2 FB-DIMM, 667 MHz
Memory Module: DIMM Riser B/DIMM 1, 1 GB, DDR2 FB-DIMM, 667 MHz
Memory Module: DIMM Riser B/DIMM 2, 1 GB, DDR2 FB-DIMM, 667 MHz
Network Service: Built-in Ethernet 1, Ethernet, en0
PCI Card: NVIDIA GeForce 7300 GT, Display, Slot-3
PCI Card: NVIDIA GeForce 7300 GT, Display, Slot-1
Serial ATA Device: ST3250824AS  P, 232.89 GB
Serial ATA Device: Maxtor 6H500F0, 465.76 GB
Serial ATA Device: Maxtor 6H500F0, 465.76 GB
Serial ATA Device: Maxtor 6H500F0, 465.76 GB
Parallel ATA Device: SONY    DVD RW DW-D150A, 672.13 MB
Parallel ATA Device: SONY    DVD RW DW-Q120A
USB Device: Hub, Up to 480 Mb/sec, 500 mA
USB Device: Kensington USB Keyboard, Innovace, Up to 1.5 Mb/sec, 500 mA
USB Device: Apple Optical USB Mouse, Primax Electronics, Up to 1.5 Mb/sec, 500 mA
USB Device: Microsoft Trackball Explorer®, Microsoft, Up to 1.5 Mb/sec, 500 mA
USB Device: Hub, Up to 480 Mb/sec, 500 mA
USB Device: EPSON Scanner, EPSON, Up to 480 Mb/sec, 500 mA
USB Device: Apple Cinema HD Display, Apple Computer, Inc., Up to 12 Mb/sec, 500 mA
USB Device: Hub, Up to 480 Mb/sec, 500 mA
USB Device: RadioSHARK, Griffin Technology, Inc., Up to 12 Mb/sec, 500 mA
USB Device: Plantronics Headset, Plantronics, Up to 12 Mb/sec, 500 mA
FireWire Device: eyetv 200, 0xC6C, Up to 400 Mb/sec
FireWire Device: built-in_hub, unknown_value, Unknown
FireWire Device: OXFORD IDE Device, Macpower, Up to 800 Mb/sec
FireWire Device: iSight, Apple Computer, Inc., Up to 400 Mb/sec
FireWire Device: unknown_device, unknown_value, Unknown

From #2

Code:

panic(cpu 2 caller 0x003A2287): getPhysicalSegment() out of 32b range 0x11b683000, len 0x1000, class IOGeneralMemoryDescriptor
Backtrace, Format - Frame : Return Address (4 potential args on stack) 
0x37363938 : 0x128cdb (0x3c99c4 0x3736395c 0x131cdf 0x0) 
0x37363978 : 0x3a2287 (0x3edad8 0x1b683000 0x1 0x1000) 
0x37363a48 : 0x3a41e5 (0x6e57200 0x2000 0x0 0x62694c0) 
0x37363a68 : 0xca567f (0x8932b00 0x2000 0x0 0x8932b00) 
0x37363aa8 : 0xca50db (0x8934280 0x400000 0x8934280 0x6d610010) 
0x37363ae8 : 0xca6d72 (0x3657d000 0x400 0x37363b44 0x10) 
0x37363b38 : 0xca60a7 (0x63c4f84 0x18 0x200000 0x199103) 
0x37363bf8 : 0xca6383 (0x63c4f84 0x37363ec8 0x18 0x680fcb8) 
0x37363d58 : 0xca45c5 (0x63c4f84 0xc0185401 0x37363ec8 0x0) 
0x37363d78 : 0x1f00f7 (0xa000000 0xc0185401 0x37363ec8 0x81) 
0x37363db8 : 0x1e7045 (0x37363de0 0x297 0x37363e18 0x1d09ee) 
0x37363e18 : 0x1deee9 (0x7714ef4 0xc0185401 0x37363ec8 0x81) 
0x37363e68 : 0x3305b4 (0x5b352a0 0xc0185401 0x37363ec8 0x6c05dac) 
0x37363e98 : 0x34e881 (0x5b352a0 0xc0185401 0x37363ec8 0x6c05dac) 
0x37363f68 : 0x378f9c (0x6c05dac 0x680fcb8 0x680fcfc 0x0) 
0x37363fc8 : 0x19b0ee (0x68038c0 0x0 0x10 0x68038c0) 	Backtrace continues...
      Kernel loadable modules in backtrace (with dependencies):
         com.parallels.kext.vmmain(2.2)@0xca3000

Kernel version:
Darwin Kernel Version 8.7.2: Tue Jul 25 23:09:54 PDT 2006; root:xnu-792.10.96.obj~3/RELEASE_I386

Model: MacPro1,1, BootROM MP11.005C.B00, 4 processors, Dual-Core Intel Xeon, 2.66 GHz, 3 GB
Graphics: NVIDIA GeForce 7300 GT, NVIDIA GeForce 7300 GT, PCIe, 256 MB
Graphics: NVIDIA GeForce 7300 GT, NVIDIA GeForce 7300 GT, PCIe, 256 MB
Memory Module: DIMM Riser A/DIMM 1, 512 MB, DDR2 FB-DIMM, 667 MHz
Memory Module: DIMM Riser A/DIMM 2, 512 MB, DDR2 FB-DIMM, 667 MHz
Memory Module: DIMM Riser B/DIMM 1, 1 GB, DDR2 FB-DIMM, 667 MHz
Memory Module: DIMM Riser B/DIMM 2, 1 GB, DDR2 FB-DIMM, 667 MHz
Network Service: Built-in Ethernet 1, Ethernet, en0
PCI Card: NVIDIA GeForce 7300 GT, Display, Slot-3
PCI Card: NVIDIA GeForce 7300 GT, Display, Slot-1
Serial ATA Device: ST3250824AS  P, 232.89 GB
Serial ATA Device: Maxtor 6H500F0, 465.76 GB
Serial ATA Device: Maxtor 6H500F0, 465.76 GB
Serial ATA Device: Maxtor 6H500F0, 465.76 GB
Parallel ATA Device: SONY    DVD RW DW-D150A, 672.13 MB
Parallel ATA Device: SONY    DVD RW DW-Q120A
USB Device: Hub, Up to 480 Mb/sec, 500 mA
USB Device: Kensington USB Keyboard, Innovace, Up to 1.5 Mb/sec, 500 mA
USB Device: Apple Optical USB Mouse, Primax Electronics, Up to 1.5 Mb/sec, 500 mA
USB Device: Microsoft Trackball Explorer®, Microsoft, Up to 1.5 Mb/sec, 500 mA
USB Device: Hub, Up to 480 Mb/sec, 500 mA
USB Device: EPSON Scanner, EPSON, Up to 480 Mb/sec, 500 mA
USB Device: Apple Cinema HD Display, Apple Computer, Inc., Up to 12 Mb/sec, 500 mA
USB Device: Hub, Up to 480 Mb/sec, 500 mA
USB Device: Plantronics Headset, Plantronics, Up to 12 Mb/sec, 500 mA
USB Device: RadioSHARK, Griffin Technology, Inc., Up to 12 Mb/sec, 500 mA
FireWire Device: eyetv 200, 0xC6C, Up to 400 Mb/sec
FireWire Device: built-in_hub, unknown_value, Unknown
FireWire Device: OXFORD IDE Device, Macpower, Up to 800 Mb/sec
FireWire Device: iSight, Apple Computer, Inc., Up to 400 Mb/sec
FireWire Device: unknown_device, unknown_value, Unknown

 

Here too.

It's very frustrating. We have standardized on Parallels in our company, but I'm the only one thus far wiiht a Mac Pro (trying) to run it.

I have tried 5x to install the program and Win XP Pro and I get Kernel Panic all the time now, right after Windows says the software was completed, take the disk out of drive A.

Parallels, HELP

 

And then, when the machine reboots, and I launch Parallels, I get this:



Your CPU supports Intel Virtualization Technology (VT-x) but it is currently disabled (locked by firmware). Virtual machine will be started without VT-x support (in software virtualization mode).

And can't get past it.

Help!

 

I should add that I'm trying to install Windows XP SP2

 

I'm experiencing the KP's from Parallels once Windows boots as well. It gets to the log in screen and kaboom. I'm using a Mac Pro, 3GB, 1TB RAID (Stripe) and Win2K is the OS. Hopefully the patch won't take too long.



Thu Sep 7 14:41:11 2006
panic(cpu 2 caller 0x003A2287): getPhysicalSegment() out of 32b range 0x100000000, len 0xe5000, class IOGeneralMemoryDescriptor
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x373c3938 : 0x128cdb (0x3c99c4 0x373c395c 0x131cdf 0x0)
0x373c3978 : 0x3a2287 (0x3edad8 0x0 0x1 0xe5000)
0x373c3a48 : 0x3a41e5 (0x7269c80 0x11b000 0x0 0x594b1b0)
0x373c3a68 : 0x4f77367f (0x71e80c0 0x11b000 0x0 0x71e80c0)
0x373c3aa8 : 0x4f7730db (0x71f0fc0 0x400000 0x71f0fc0 0x6d616769)
0x373c3ae8 : 0x4f774d72 (0x4602f000 0x400 0x0 0x4f767fd5)
0x373c3b38 : 0x4f7740a7 (0x6b9f804 0x18 0x400000 0x199103)
0x373c3bf8 : 0x4f774383 (0x6b9f804 0x373c3ec8 0x18 0x6628090)
0x373c3d58 : 0x4f7725c5 (0x6b9f804 0xc0185401 0x373c3ec8 0x0)
0x373c3d78 : 0x1f00f7 (0xa000000 0xc0185401 0x373c3ec8 0x81)
0x373c3db8 : 0x1e7045 (0x373c3de0 0x297 0x373c3e18 0x1d09ee)
0x373c3e18 : 0x1deee9 (0x71406b4 0xc0185401 0x373c3ec8 0x81)
0x373c3e68 : 0x3305b4 (0x5e54700 0xc0185401 0x373c3ec8 0x61d21f4)
0x373c3e98 : 0x34e881 (0x5e54700 0xc0185401 0x373c3ec8 0x61d21f4)
0x373c3f68 : 0x378f9c (0x61d21f4 0x6628090 0x66280d4 0x0)
0x373c3fc8 : 0x19b0ee (0x65a4420 0x0 0x10 0x65a4420) Backtrace continues...
Kernel loadable modules in backtrace (with dependencies):
com.parallels.kext.vmmain(2.2)@0x4f771000

Kernel version:
Darwin Kernel Version 8.7.2: Tue Jul 25 23:09:54 PDT 2006; root:xnu-792.10.96.obj~3/RELEASE_I386


*********

Thu Sep 7 15:01:26 2006
panic(cpu 3 caller 0x003A2287): getPhysicalSegment() out of 32b range 0x100000000, len 0xcc000, class IOGeneralMemoryDescriptor
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x37123938 : 0x128cdb (0x3c99c4 0x3712395c 0x131cdf 0x0)
0x37123978 : 0x3a2287 (0x3edad8 0x0 0x1 0xcc000)
0x37123a48 : 0x3a41e5 (0x67f9500 0x334000 0x0 0x594a648)
0x37123a68 : 0x4faad67f (0x614fc40 0x334000 0x0 0x614fc40)
0x37123aa8 : 0x4faad0db (0x614fc80 0x400000 0x614fc80 0x6d616769)
0x37123ae8 : 0x4faaed72 (0x5c907000 0x400 0x0 0x4f89cfd5)
0x37123b38 : 0x4faae0a7 (0x66db104 0x18 0x600000 0x199103)
0x37123bf8 : 0x4faae383 (0x66db104 0x37123ec8 0x18 0x6420628)
0x37123d58 : 0x4faac5c5 (0x66db104 0xc0185401 0x37123ec8 0x0)
0x37123d78 : 0x1f00f7 (0xa000000 0xc0185401 0x37123ec8 0x81)
0x37123db8 : 0x1e7045 (0x37123de0 0x297 0x37123e18 0x1d09ee)
0x37123e18 : 0x1deee9 (0x5ecdf78 0xc0185401 0x37123ec8 0x81)
0x37123e68 : 0x3305b4 (0x648cde0 0xc0185401 0x37123ec8 0x622a7d0)
0x37123e98 : 0x34e881 (0x648cde0 0xc0185401 0x37123ec8 0x622a7d0)
0x37123f68 : 0x378f9c (0x622a7d0 0x6420628 0x642066c 0x0)
0x37123fc8 : 0x19b0ee (0x61ebc80 0x0 0x19e0b5 0x61ebc80) Backtrace continues...
Kernel loadable modules in backtrace (with dependencies):
com.parallels.kext.vmmain(2.2)@0x4faab000

Kernel version:
Darwin Kernel Version 8.7.2: Tue Jul 25 23:09:54 PDT 2006; root:xnu-792.10.96.obj~3/RELEASE_I386


*********

 

Same thing on my MacPro 2,66 GHz. Kernel Panic during install Windows XP Pro SP2.

I also got the message about the missing VT-x support. But I know, that if you go with your mac to sleeping mode and wake it up again, VT-x support will be enabled.

Regards
Thomas

 

For those of you who are getting the kernel panics, did you previously have Parallels running using the temporary fix or are you using fresh installs of Parallels? I would like to install it on my Mac Pro, but if it's not ready, I'd rather not go through the hassle.

 

I got kernel panics with a fresh install!

Regards
Thomas

 

I installed the latest build of Parallels Desktop over the previous one.

I also just got a fatal error; at least it's not a KP this time.

 

If you have more than 3.5 gigs of ram I would wait. KP after every os reboot I try. Almost like the vm ties to some hardware that is not happy.

 

Crash

Getting kernel panics on my mac pro.
Fresh parallels install, trying to set up a VM with ubuntu linux.
I started a linux debian vm and before I could do anything i immediately get a panic.
My mac has 2gb of ram.

 

Me too, fatal error during installation of Win XP Pro SP2 after loading all drivers when I have to hit the enter key to start installing Win XP...

Regards
Thomas

 

i have a fresh 2.66 ghz mac pro that has never had parallels installed or attempted any of the workaround fixes for the previous versions. at lunch today i attempted (excitedly) to install xp sp2. my mac pro has 8gb of ram so i performed the "maxmem" fix and began the install. i use a stripped ( 0 ) raid as my boot volume (might be the issue) which then is the default volume for the virtual drive to sit on. when i install xp sp2 i consistantly get to the point of formating the drive either in ntfs full or ntfs quick. either formatting option i choose instantly causes a kernal panic. at this point i had to return to work for the afternoon and had to stop playing. when i get home this evening i am going to locate the program, virtual drive, and all other related paralells items on my ATA drive i installed under the superdrive. this may fix my problem and i will repost after i have tried it.

 

I've got a RAID 0 boot and vm drive as well. I can format the guest os, but I'm still getting kernel panics - sometimes after hitting CTRL/ALT to release the mouse, sometimes just trying to click on anything. I don't think it's the RAID. Overall it's still very buggy and not any real improvement for me - still can't run a VM.

QEMU will run a VM for me, but I can't make it a member of a domain since they don't have bridged network....back to the full out Dell box until Parallels really gets fixed.

 

glberen

you are booting from a raid 0 also? along with your vm being there too? and you are able to fully format the drives? like i stated mine panics every time i envoke the format process. have you tried to load to a different drive yet? all of this aside i will be looking foward to the vmware solution. i think that given their years of experience they may be able to provide a more stable "out-of-the-box" program. i will still update this evening when i have the chance to get back at it.

 

Yes - 4 drive raid 0. I had no problems formatting the XP/Vista drive. Used NTFS(quick).

 

I get all these freakin issues! It's frustrating. I keep having to restart my computer.

I actually kept trying over and over and fresh installing Parallels, and I finally got Win XP installed, and I was in XP workin around it and everything and then it panicked again and I restarted. When I got back it wouldn't start I get that other message people are getting about missing VT-x support.

Specs: 2.66, 2GB Ram, ATI x1900 512MB Card, 250 GB HD, Mac Pro

 

spoke too soon!

I spoke too soon in the other thread...I'm having problems as well tho no KP's. After the XP install the restart of XP gave me the grey screen "you need to restart your machine" error. once i restarted and tried to run my VM i get an "unable to communicate with hypervisor!" error.

tried everything i could think of...uninstalled parallels/re-installed, tried different VM configurations, nothing worked.

thanks for the attempt parallels team!

"rush a miracle man and what do you get??? bad miracles"

B

 

Boulie, the grey screen *is* a KP (kernel panic). :-/

One wonders how much testing this "release candidate" received, given the issues being reported in the forum.

 

in response to "how much testing".... like any?

nothing but panics on my end. i am a serial number owner of parallels and i am disapointed to say the least.

i was unable under any circumstances to get xp sp2 installed on my mac pro. kernel panic city baby....

i do feel sorry for the parallels team but still this is not aceptable. i could understand that perhaps some thing may not fully function but to not install at all? it's not like we don't know how to install it. personally i have parallels installed on my iMac 2.0 and my Macbook Pro but no dice on the mac pro. if it's acceptable to some users to have to throttle back their system memory, and apply this hack and the patch and what not... then all the more power to ya and i wish ya luck but i am not going to go through all of that this time around. if you think i am being harsh or unfair that is your opinion and your welcome to it. think about this experience in terms of other day to day things like say your car... would you accept this solution when it comes to the operation of your car. No... you would demand more and better support or your money back. i will be firing up the windows box until the parallels team can code this beast correctly or vmware comes and steals their customers away.... and i will the first in line.