Parallels 5 & Windows 7 Partition

[Kobukson]

Hey Guys,

 

So I've seen a few articles on running older versions of Parallels with the Windows partition on your Hackintosh, but it seems to be outdated.

 

So, has anyone been able to get Parallels 5 to work with their Windows 7 partition on their Hackintosh successfully? I keep getting the following error when my VM tries booting:

 

boot0: GPT

boot0: testing

boot0: testing

boot0: error

 

I'm betting is due to Chameleon being the bootloader, but I can't seem to find a fix to get this to work. If anyone has any advice or tips, please let me know ^^

[pcace]

Noone any idea?

 

Im running into the same Problem...

[MrKalah]

Noone any idea?

 

Im running into the same Problem...

 

That's a tricky one. I did solve the problem but I didn't really know how. I kept playing with changing the boot flag on windows partition, unmounting the windows partition from disk utility and stop / restart parallels desktop. It eventually worked but I couldn't know with what exact conditions.

 

Next week I will do a fresh install of this type of dual boot / virtual machine, I will see how to properly solve this problem.

 

Meanwhile, I added a third partition for Linux. I had the same error and couldn't get rid of the boot0 error (no problem with the windows one though). So I added a small Linux virtual machine with an normal image, added the "boot camp" linux partition to its hardware, and configured a grub bootloader to load my Linux on the boot camp partition. That works. That could be an alternative solution to the windows problem too.

[Kobukson]

Anyone else have any luck?

[MrKalah]

Anyone else have any luck?

 

I confirm my last solution, I have been testing it for the past few weeks and it works perfectly.

 

To sum up, I am using Parallels Desktop to access my two other systems windows7 and a linux, each one having its own partition and available via chameleon. Each virtual machine starts on a local linux image acting as bootloader instead of booting directly on the drive partitions. The VM is configured with both a virtual drive, and the real partition, but boots only the first one. Then all what u have to do is to configure grub to start the second drive.

 

I have set up small archlinux systems of only a few hundreds megs, and uses the old grub version (as in not the version 2 present in recent distro). Here is the entry for the windows system:

 

title Windows 7
rootnoverify (hd1,2)
makeactive
chainloader +1

 

hd1 represents my main physical drive, which is placed in second position because I have configured the virtual drive first in the VM set up. 2 is my windows partition.

[reuben68]

MrKalah's method works very well.

 

Prior to finding his method Parallels 5 would bomb out with a boot0 error. Now, it boots just fine with this simple method.

 

Here's what I did, roughly.

 

I used TinyCore Linux. Reason I picked it was its small footprint.

Created a "Other Linux" VM with the amount of CPU and memory I wanted Win7 to use.

Created a .1GB virtual hard drive.

Installed TinyCore and configured grub to boot TinyCore

Reboot to verify all is well.

Reboot.

Add Win7 partition

Boot into TinyCore

Configure grub.

- Followed MrKalah's example.

- I also set failback to TinyCore, timeout to 5, and default to Win7.

- NOTE: Using drive numbering from fdisk -l (in TinyCore) does not match what grub sees. For example, fdisk showed my Win7 partition as hdc3 but grub needed hd1,2 (for example).

Rebooted.

Yeah it works.

Parallels boots TinyCore, Grub hands off to Win7. Win7 boots.

Parallels will popup some warning messages, notable was that it stopped the VM from resetting the active partition.

 

Two things I've come across so far. 1.) Using Parallels to suspend the VM doesn't work because the VM is using a boot camp drive (according to the Parallels message that pops up). 2.) Sound from Win7 isn't working, I haven't fiddled with it much since I had to move to other things.

 

Thanks for this suggestion MrKalah.

[Javimdq]

I'm getting the same boot:0 error with Parallels 5 and Win7.

I found the above solution too much "complicated" for something that should be easy.

 

With VMware Fusion 3, Win 7 starts with no problem.

 

Anyone had found another solution for P5?

 

Thanks!

[berry_lthird]

MrKalah's method works very well.

 

Prior to finding his method Parallels 5 would bomb out with a boot0 error. Now, it boots just fine with this simple method.

 

Here's what I did, roughly.

 

I used TinyCore Linux. Reason I picked it was its small footprint.

Created a "Other Linux" VM with the amount of CPU and memory I wanted Win7 to use.

Created a .1GB virtual hard drive.

Installed TinyCore and configured grub to boot TinyCore

Reboot to verify all is well.

Reboot.

Add Win7 partition

Boot into TinyCore

Configure grub.

- Followed MrKalah's example.

- I also set failback to TinyCore, timeout to 5, and default to Win7.

- NOTE: Using drive numbering from fdisk -l (in TinyCore) does not match what grub sees. For example, fdisk showed my Win7 partition as hdc3 but grub needed hd1,2 (for example).

Rebooted.

Yeah it works.

Parallels boots TinyCore, Grub hands off to Win7. Win7 boots.

Parallels will popup some warning messages, notable was that it stopped the VM from resetting the active partition.

 

Two things I've come across so far. 1.) Using Parallels to suspend the VM doesn't work because the VM is using a boot camp drive (according to the Parallels message that pops up). 2.) Sound from Win7 isn't working, I haven't fiddled with it much since I had to move to other things.

 

Thanks for this suggestion MrKalah.

I'm currently dual-booting with Snow Leopard and Windows 7 from the same physical disk. I already have the drive GUID partition, half for OS X and the other for Window. I now effectively have four actual partitions on the drive.

 

What are my options with TinyCore in this case?

 

Also, I am very new with Linus/Unix and terminal commands. Could you or someone here please provide a more detailed explanation of how to set-up TinyCore the way reuben68 did?

 

Thank you in advance!

[poverty]

** SOLVED **

 

The linux solution wasn't something I wanted to pursue. I was determined to make Parallels work natively. Here's what I did.

 

Uninstalled Parallels application and parallels folder from documents (or wherever you told it to make your VM) and any other supporting files.

 

Opened up terminal

 

diskutil list

find your identifier for your NTFS drive ie. (disk0s3 for me)

sudo -s

Enter Password

fdisk -e /dev/rdisk0

p

f 3 (again this will vary depending on your NTFS partition - mine was 3)

w

y

Close Terminal and reboot

 

This temporary process will no longer allow your Hackintosh to boot from your Snow Leopard partition Chameleon loader. Instead if you let it reboot it should just fire up straight into Windows 7. With this being said make sure you have your original boot CD ISO for Chameleon or boot USB key and boot from that (double check your BIOS boot order). Once the Chameleon screen comes up select your Snow Leopard partition. Boot into Snow Leopard and install Parallels. Select new virtual machine from Boot Camp Partition. This time it should configure the VM and boot right into Windows without the Boot 0 Error. Once you have confirmed Windows VM is setup and Parallels Tools has been installed shut down the machine. Open up terminal and reset your active partition back to your HFS+ (Snow Leopard Partition) or just type the following.

 

diskutil list

find your identifier for your HFS+ Snow Leopard drive ie. (disk0s2 for me)

sudo -s

Enter Password

fdisk -e /dev/rdisk0

p

f 2

w

y

Close Terminal and reboot

 

I hope this works for you please let me know because it will be my very first contribution to the community! Woohoo!!

[hisho]

hey man , thank u so much , it worked 100 % and its really easy

[Prowlerblizz]

Good solution! It managed to point Parallels to boot windows. But I keep entering start-up repair and it goes on a loop as a first time installation. I read in the Parallels forum that this is a known issue and they do not have a solution for it. as of now. Happens mostly to high end PC with 4 cores and a lot of ram T_T. Gonna try VMware instead..

[guitch]

Hi

 

I tried your solution, but for some reasons I don't understand, my HFS+ partition is now recognized as NTFS (both in fdisk and diskpart)........

Does anyone have an idea as of why ? I've searched a bit on my own, but I really don't have a clue....

 

Cheers

[guitch]

Hi

 

I tried your solution, but for some reasons I don't understand, my HFS+ partition is now recognized as NTFS (both in fdisk and diskpart)........

Does anyone have an idea as of why ? I've searched a bit on my own, but I really don't have a clue....

 

Cheers

 

Hi

 

In case anyone encounters the same problem as me, that's because of win7's diskpart. For some reasons, it changes the System Type of the partition you're marking as Active. The partition still exists and the filesystem is still HFS+ (or ext3 or whatever). The solution is to use Gparted livecd and re-set the partition type back to AF (HFS/HFS+).

 

Cheers

[guitch]

Anyway, just to let you and other readers know, after I have fixed my boot problems, your solution works great ! Now I have parallels working on my hackintosh !

 

Cheers

[valv]

Create a virtual machine into Parallels.


For disk choose Boot-camp.
 Do not run the virtual machine yet.
 when done, exit Parallels and go edit the configuration file .pvs of that virtual machine and replace Disk 0:0 image = Boot Camp with Disk 0:0 image = Boot Camp;diskXsX 
where X is the partition to load from diskX.

Greetz

[qngage]

@valv : hmm precisely, where did you put that line "Disk 0:0 image = Boot Camp;diskXsX" in the config.pvs? Please help

[savoirfaire]

** SOLVED **

 

The linux solution wasn't something I wanted to pursue. I was determined to make Parallels work natively. Here's what I did...

 

*snipped*

 

That sounds like the most promising solution, but I have my Windows XP and Snow Leopard installations on separate drives. Currently, the setup looks like this:

 

/dev/disk0

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *1.0 TB disk0

1: EFI 209.7 MB disk0s1

2: Apple_HFS Hackint0sh 992.2 GB disk0s2

3: Apple_HFS Mac OS X Install Par... 7.5 GB disk0s3

/dev/disk1

#: TYPE NAME SIZE IDENTIFIER

0: FDisk_partition_scheme *1.0 TB disk1

1: Windows_NTFS Windows XP 999.7 GB disk1s1

2: Apple_HFS CHAMELEON 542.8 MB disk1s5

/dev/disk2

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *1.0 TB disk2

1: EFI 209.7 MB disk2s1

2: Apple_HFS Terabyte 1 999.9 GB disk2s2

 

Can someone help me figure out how to get Parallels working? It is not recognizing my Windows XP installation as a Boot Camp partition.

[Sennen]

I hope this works for you please let me know because it will be my very first contribution to the community! Woohoo!!

 

Thank you for the info - your solution worked well for me.

[shijan]

valvs method is best but seems it for parallels 5 only. in version 6 config.pvs file is different. all we need is to find a right way to edit config.pvs to boot from right partition. any ideas?

[gaswirth]

reuben68, you're a lifesaver!!!

 

Works like a charm.

 

For those who might be confused (as I was), the trick is adding an additional hard drive in your VM Configuration....add it as another hardware device, and it'll pop up when you try fdisk -l. Maybe I'm just a doofus, but it took me forever to figure out why my actual hard drives weren't showing up!

 

Thanks Reuben68!!

[Z3R0-X]

I know it's an old post, but I really ran out of solutions! I just installed my fully working hackintosh with dual booting system (Lion and Win7x64 using chimera bootloader on my 1st SSD, on separate partitions). Using Parallels 7 to run win7 using its own physical partition is definitely not that easy!

 

Windows loads, then before log-in screen it fires the blue screen (BSOD) and restarts in a continuous loop!

Tried all boot options (Safe mode, recover, ...) non worked. It boots fine in safe mode and enters windows, so I think the problem is because of a driver conflict with Parallels 7... If do need ti know the cause or the conflicting driver to stop/ fix it. I am sure the fix is easy once I know the cause. I have the necessary logs generated by windows during the boot and I can access event log in safe mode to extract whatever required.

 

BTW: My PC is high-end with 16GB RAM, as somebody in this thread has mentioned that this might cause a similar infinite loop.

I'm sure that somebody has experienced the same, and I would really appreciate any kind of help. Thanks...

 

Update: When I tried to boot normally into win7 partition, I experienced the same BSOD and thought I lost my win installation, but I booted with win recovery option thrice (which couldn't solve the issue even by restoring with a restore point). Then booted again and voila, windows is working! restarted and its working. Then I rebooted into lion and deleted the Parallels bootcamp machine, created new machine with no CD and no had disk attached (deleted Disk1) then manually added the win partition, fired up the machine and it started to create/ configure/ install parallels tools then restarted to enter again into the infinite loop of blue screen + reboot

 

I still think its a parallels driver conflict with high-end hardware, may be? Please advice...

ntbtlog.txt

[Dinana]

Instead of installing a linux VM, I used Plop boot manager, here are the details:

• Download the distribution from http://www.plop.at/en/bootmanager/download.html latest at the time of writing was 5.0.14
• Unzip, you'll find an iso file inside (in my version plpbt.iso)
• Use this as the CD-ROM in your virtual machine
• Change boot order to boot from CD-ROM first
• When Plop manager appears select the partition you want to boot
• Enjoy!

 

[gils83]

 

with vt-d disable (dart=0) 

 

Intel E3-1245V2 8go ram /HD 6670 LP /OS X 10.9.3 / Parallels 9 / win7 64 / 4 thread and 3072 ram 

 

test 3DMark