Running Boot Camp partition via a VM?

Can someone comment on their experiences running Boot Camp through their VM software?
Does it prevent you from booting into the Boot Camp partition?
I know you have to install the tools for your VM onto the Boot Camp partition to keep your activation active? What happens if one uninstalls the VM? Can the tools be uninstalled to and the Boot Camp partition work like normal again?
Most importantly, can running the Boot Camp partition through a VM cause any damage?

It seems to be hanging, it's actually listed as Not Responding by the force quit menu.
Though I did just check the HD in Disk Utility, and it seems like there is a Windows Partition of the correct size, so I am starting to think BCA just crashed after successfully partioning.

Similar Messages

Access Boot Camp Partition via Fusion or Parallels

I already have a 20gb Vista partition on my Mac is it possible to access that via Fusion or Parallels without rebooting?

I use Fusion with a boot camp partition containing Windows Vista. No issues when running both Leopard and Fusion with Windows.
One thing to note though and that is if you are planning to play Windows based games via Fusion then forget it. It will be very slow and in most cases unplayable due to speed. Now, if you are running productivity software (MS Office for Windows etc) then you will love this convenience.
Axel F.

Help: Windows XP on MacBook Pro Boot Camp Partition via Target Disk Mode

Firstly, let me lay out my situation. I have an old MacBook Pro (2,2) with a broken disk drive. It was dropped in its youth and can no longer read from or write to CDs or DVDs of any kind. I have just recently bought a new MacBook Pro to replace it (6,2) and am currently trying to convert the old computer into an XP machine through Boot Camp. I'd like to be able to do so without having to buy an external disk drive.
After a clean install of OS X (10.6.3) onto the old machine, I successfully partition 85GB of space (although I previously attempted the same with a 32GB file system to no avail as well) for XP to be installed upon. Because I cannot boot my XP install disk directly from the broken disk drive, I then close Boot Camp Assistant and shut down the computer. I start it up in Target Disk Mode to be accessed from the new MacBook (6,2).
Once the old MacBook is connected, I insert my XP install disk into the new MacBook (6,2) and boot from the disk. After allowing the XP (Professional) boot to load the install files, I arrow-key down to my 85GB partition (FAT32, named standard as "BOOTCAMP") on the old MacBook (2,2)'s hard drive and select it as the partition I would like to install to. This is where I am directed to a new boot window that tells me in a series of paragraphs that the XP installer cannot reach the selected partition for what seems to be a number of reasons. What it seems to be trying to say to me is that it cannot do a remote install of XP on a Target Disk Mode-connected machine, while not "knowing" that I am trying to do so. It's a similar message to the one that Boot Camp Assistant shows when one tries to create a Boot Camp partition on a machine that is being accessed via Target Disk Mode (Apple puts it much more clearly than Microsoft).
I'd be perfectly content, albiet slightly vexed, to conclude here that it is not possible, shuttle over to the nearest Best Buy, and purchase an external disk drive if it weren't for one thing: I tried the same thing two weeks ago with Ubuntu 10.10 and it installed perfectly on the Boot Camp partition I had created then (I have since wiped all and installed OS X cleanly on the laptop).
Here comes the point/questions:
If the Ubuntu boot disk can access the partition, why can't the XP boot disk?
Is there some way to convince the boot system that the drive is local, rather than being accessed via Target Disk Mode?
Is there an easy solution that doesn't even require that, and will allow me to install to the disk over a firewire connection?
If anyone's knowledgeable and/or brave enough to tackle this one, I'll be eternally grateful. Heck, I'll be grateful if anyone even attempts to tackle it.
Thanks,
-Alec Page

Windows XP will only install from the optical drive. Target Disk Mode does not work with Windows volumes. Windows will not install from any external device.

Possible to RAID 0 and run Boot Camp partition?

I have a mid-2010 MacBook Pro (13"). I have a stock 250 GB hard drive and I just got a SanDisk 256 GB SSD.
I'm running Windows (through Boot Camp) on a small partition of my stock 250 GB hard drive. I want to install the SSD in my optical drive and RAID the two hard drives (250 GB and 256 GB). I also want to wipe my Windows partition and make it bigger (around 50-100 GB).
My question is: is it possible to RAID 0 and have a Windows parition at the same time? What's the best way to do it if it's possible?
Thanks

If you are planning on setting them up in a Raid Array, it doesn't really matter. The performance is going to be poor no matter what. I see your plan as spending money for little or no gain.
Have you considered just removing the current disk drive and replacing it with a larger one. I think that would give you the best performance for the least money and the fewest headaches getting it set up.
Your need for Windows is preventing me from making any other suggestions. Windows has so many lkimitations built into it.
Allan

Run Boot Camp Partition alongside Leopard

Hello everyone,
I have Boot Camp with Vista running on my Mac. It works perfectly fine. I was wondering if I could run it alongside Leopard (with a program like VMWare Fusion or Parallels) at certain times, but boot into it with Boot Camp at other times.
Thanks,
Noam.

Yes, I have this setup on a Mac Pro (using VMWare Fusion). Fusion will enable your Bootcamp-installed Windows to be run in a virtual environment within Leopard. You will still be able to boot the computer directly into Windows when necessary.
bd

BSOD every 20 minutes running windows XP in boot camp partition

Has anyone else had this problem? Everything was running fine for a couple of months on my new mac OS X until around the time I installed the recommended updater to Boot Camp 2.1, then Windows XP started crashing every 20 minutes exactly, BCCode : 1000007f. One line of discussion suggests it's a boot camp problem but uninstalling the update hasn't helped. Others seemed to think it might be a graphics card incompatibility. I've now been advised that it's a Norton 2008 problem and I should uninstall that although I haven't tried yet. But the every 20 minutes must be some clue to what's going on. Does anyone have any ideas?

Thanks Axel. I removed Norton 2008 with the uninstall tool and hey presto no more BSODs so far (24 hours). I've also replaced Norton with Kaspersky. I guess this is really a Norton/Boot Camp compatibility problem but it's weird that Norton ran without problems on my system for five months until I installed the Boot Camp 2.1 updater. Having said that, I now see that there are a couple of discussions on this in the Boot Camp > Installation and Storage topic list ...
In one of these, Mark Davidson3 resolved the problem by completely uninstalling/reinstalling his Boot Camp partition and is now running Norton again with no problem but I wonder if that's because he must have uninstalled/reinstalled Norton in the process. Like me, the crashes had started for him only after he installed the Boot Camp 2.1 updater. Presumably Norton would run again on my system now too if I reinstalled it.
Has anyone out there talked to the Norton/Boot Camp people about this?

How to partition in order to run Boot Camp

I have an iMac 9.1 Intel Core 2 Duo running Mac OS X 10.6.8.
I have also downloaded the correct version of Boot Camp and saved to an external USB formatted for MS-DOS (FAT32).
I am running Boot Camp Assistant. Problem is when I get to the option where I am to download the software to install the Boot Camp drivers (I select "Download the Windows support software for this Mac" because I do not have the Mac OS X installation disc that came with my iMac), it tells me the following:
"The startup disk cannot be partitioned or restored to a single partition. The startup disk must be formatted as a single Mac OS Extended (Journaled) volume already partitioned by Boot Camp Assistant for installing Windows."

It is not giving you that message because you do not have the original start up disc for your Mac. It is giving you that message because you have more than one partition on the boot drive in your Mac. The way that BootCamp works is that it creates the required partitions on your Mac boot drive. Due to limitations of Windows, you can only have up to 4 primary partitions on your drive, and the Boot Camp installation process wants to use at least 3 of those. If you already have more than one partition on the drive, they can't guarantee that you will be able to access all your partitions properly, so it tells you that you need to re-create a single partition on your boot drive.
If you have a good system clone, you should still be able to use the Disk Utility to restore the drive back to a single partition. Doing this could cause corruption if not done properly, that is why I suggest having a good clone before you try.

Parallel runs slow on Boot Camp partition and other questions...

Hi all,
I have had my MBP santa rosa for about 3 weeks. I love it. Everything is super fast and responsive on this thingy. I have parallel running on Boot Camp partition and it is slow. I mean its not awfully slow but when I click start (the play button of Parallel), I see the spinning beachball for 0.5 to 1 min. When I get to Windows XP or Vista (I tried both of them), there is no way parallel could perform up to "near native" speed, I get a lot of sand-clock and it takes 1 mins or so to boot up MS SQL server 2005. When i tried to open lots of windows at once, it freezes for a while then all the windows pop up. I dedicated 1gb of ram for parallel. I am thinking of removing boot camp and use parallel virtual drive on which to install windows. Would that make the performance any better?
I have another question. I bought Disk Warrior 4 but my lovely cousin broke the disc into half coz he thought it was a cheap toy. Is there anyway I can make another bootable CD for disk warrior? I know BootCD only works on Panther. Can I use SuperDuper to clone my MBP and put the image file on a PC-formated external hard drive to bootup from there to run Disk Warrior?
Thank you so much for your help. I gotta say this MBP is the best laptop I have ever used in my entire life. VEry happy with the purchase so far. Thank you Apple.
MacNo0b
p/s: Any recommendation on how to keep the Mac running well without slowing down? Cheers

I have to say, I have never used Parallels in a system with 2GB. I don't feel that it's worth it given Boot Camp is available. That said, if you run nothing else it should run quite happily.
If you're having problems getting through the installation try setting it up with a virtual environment that has no drive. That way you should be able to get through the installation/setup and then you can add your Boot Camp partition after that.
As for transferring files, I will either use Parallels folder sharing else a 1GB DOS formatted USB flash drive.
PS You're right, I certainly can't complain about the equipment I get to play with. I've had to fork out quite a bit of money for the privilege but it's all been worth it.

Boot Camp repair via Hybrid MBR fix after 5+ partitions

With the understanding that Boot Camp only formally supports a Windows boot upon creation from a single Mac OSX data partition, I'm trying to determine if a fix exists for the following boot setup. The end result I'm pursing is a triple boot mac setup with Mavericks, Win7, and Ubuntu. This applies to the bootcamp subject because it is not possible to install Windows 7 without Bootcamp due to USB3 drivers at install on this model [2014 Macbook Pro]. Thus making the Win7 Boot Camp task a required first step. The partition edits after this to make room Linux end up messing with the hybrid MBR boot setup that Boot Camp created - resulting in no available Windows boot option. A bit of research tells me that this Boot Camp partition can be repaired with some manual hybrid MBR work as long as a total of 4 partitions are present.
My question is can an alternate (or new) hybrid MBR approach support a fix for an already existing Boot Camp partitions while 5+ partitions exist on the same disk? If at all possible, what are the risks involved?
Current State:
As of now, I have the bootcamp hybrid MBR set up properly with Win 7 working -- though knowing any partition edit will mess this up. Using rEFInd boot manager already, and plan to incorporate that for the final setup. Would be hesitant to drop the Apple Recovery Partition if at all possible.
$ diskutil list
/dev/disk0
   #:      TYPE NAME                                      SIZE                IDENTIFIER
   0:      GUID_partition_scheme                    *251.0 GB       disk0
   1:      EFI EFI                                              209.7 MB        disk0s1
   2:      Apple_HFS Macintosh HD                 210.1 GB        disk0s2
   3:      Apple_Boot Recovery HD                  650.0 MB        disk0s3
   4:      Microsoft Basic Data BOOTCAMP      40.0 GB          disk0s4
The additional that will put me past the supported 4:
5. Ubuntu 14.04
6. Ubuntu SWAP [may be able to avoid this with swap file instead]
7. Shared FAT32 space ~4GB [can also toss this if it puts me one partition over from a resolution]
Thanks in advance, appreciate any input.

sudo gpt -r -vv show disk0
gpt show: disk0: mediasize=251000193024; sectorsize=512; blocks=490234752
gpt show: disk0: Suspicious MBR at sector 0
gpt show: disk0: Pri GPT at sector 1
gpt show: disk0: Sec GPT at sector 490234751
      start       size index contents
          0          1         MBR
          1          1         Pri GPT header
          2         32         Pri GPT table
         34          6
         40     409600      1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
     409640 410430536      2 GPT part - 48465300-0000-11AA-AA11-00306543ECAC
410840176    1269536      3 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
412109712       1136
412110848   78123008      4 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
490233856        863
490234719         32         Sec GPT table
490234751          1         Sec GPT header
Is this the MBR readout you're looking for? Have this fdisk one as well:
sudo fdisk /dev/disk0
Disk: /dev/disk0 geometry: 30515/255/63 [490234752 sectors]
Signature: 0xAA55
         Starting       Ending
#: id cyl hd sec - cyl hd sec [     start -       size]
1: EE 1023 254 63 - 1023 254 63 [         1 -     409639] <Unknown ID>
2: AF 1023 254 63 - 1023 254 63 [    409640 - 410430536] HFS+
3: AB 1023 254 63 - 1023 254 63 [ 410840176 -    1269536] Darwin Boot
*4: 07 1023 254 63 - 1023 254 63 [ 412110848 -   78123008] HPFS/QNX/AUX
Edit: Having trouble pasting/quoting plaintext

Parallels can now run your boot camp partition!

Having seen this question many times in this forum, I thought I'd let people know that the new beta of parallels can boot from your existing boot camp partition. It also has a few other features with some major cool factor. Check it out here.
MacBook Pro - 2.0 GHz - 2GB RAM Mac OS X (10.4.7)

unforunately it won't work if your bootcamp partition is fat32, however they said it will be fixed in the next release!

Boot Camp Partition no longer shows in StartUp Control Panel

My Boot Camp partition no longer shows in StartUp Control Panel, but does show up using Option Key at startup. This started soon after the latest Parallels update. The Boot Camp partition seems normal and healthy in the finder. Once started via the Option Key, Windows XP-SP3 runs fine. Upgrading to BC 3.0 did not have any affect.
I've tried LOTS of troubleshooting strategies, including completely deinstalling Parallels. Deleting obvious preferences, etc.. No joy.
Any suggestions?

Hi,
if I remember correctly Parallels installs some kind of file system driver to OSX to access NTFS files system partitions.
The 'case of the missing Windows partition' is widely spread when using these NTFS file system drivers in OSX.
(Others are NTFS-3G; Paragons NTFS for Mac and Tuxera NTFS for Mac).
To my knowledge there is no other remedy to this phenomenon then to deinstall the NTFS drivers.
But as long as the Option-key is working maybe you can live with it.
Or use rEFIt http://refit.sourceforge.net/ as a Boot-Menu.
Regards
Stefan

Can you run Boot Camp and Fusion at the same time?

Hi,
I had boot camp installed on my mac pro and loved it. I decided to get greedy and install Fusion using the boot camp partition. The Fusion install went ok but then Microsoft started to get fussy. Every time I would do something on Fusion it would ask me to "Re-activate Windows" when I logged into boot camp. Maybe if I saw Fusion fully working I wouldn't want to run boot camp any more but I think I want to have the option to run either. Right now I only have 1 gig real memory on my mac pro and Fusion seems a little slow compared to native boot camp. Can I run both boot camp and fusion without having to buy two native copies of Windows XP pro? I don't want a "sensible" answer, I want an answer that takes into account how Microsoft treats this re-activation situation.
I guess Leopard might make this all obsolete, but until then .....
... Flash Gordon

You need to make sure to install VMware Tools into your virtual machine (while booted into Windows via Fusion). Once you do this you shouldn't have to continually activate Windows when going back and forth from Boot Camp to Fusion. I've seen this discussed over on the VMware Fusion discussion boards, so you may want to look there for more details.
Also, if Windows starts telling you it's been activated too many times, you can call Microsoft and they'll give you an alternate activation key. The phone number is listed on the Windows error screen. I had to do it and they were very accommodating. I just told them I was running Windows in a virtual machine, and there were almost no questions asked.
You don't need to buy 2 copies of Windows to run both Boot Camp and VMFusion.

10.5.8 updated killed Write/Update permissions on my Boot camp partition.

I can't figure this one out. I regularly "reach over" to my boot camp partition to move files from XP to my mac, and have automator scripts that also do that. Since the update, it no longer works either manually or via automator. I can read and copy stuff, but not move or delete. I've tried disk utilities, permission fixing, re-running the update with the combo updater instead of the "normal" way, and even reinstalling the OS and re-applying the patches, but its still broken. Kind of a hassle. Not sure what to try next. I've also run chkdsk from XP.

Still broken on 10.5.8, but 10.6 fixed it

Boot Camp Partition Limited to 99GB on 3GB Fusion?

I have a new (refurbished) 27" iMac with a 3TB Fusion drive. I am attempting to install Boot Camp. When attempting to setup the Boot Camp partition, I am presented with a default of 20 GB but CANNOT extend above 99GB. Again, the internal drive is 3TB which has seen no activity outside of a time machine restore.
I have run a series of terminal commands and have included the information below. Is it possible that it's only allowing me to partition the Disk0? I thought that was the flash drive and would be exempt from the Boot Camp process? Any help would be appreciated.
-Dan
Mac:~ User$ diskutil list
/dev/disk0
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *121.3 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:          Apple_CoreStorage                         120.5 GB   disk0s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
/dev/disk1
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *3.0 TB     disk1
   1:                        EFI EFI                     209.7 MB   disk1s1
   2:          Apple_CoreStorage                         3.0 TB     disk1s2
   3:                 Apple_Boot Boot OS X               134.2 MB   disk1s3
/dev/disk2
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                  Apple_HFS Macintosh HD           *3.1 TB     disk2
Mac:~ User$
Last login: Mon Nov 24 14:55:37 on console
Mac:~ jUser$ sudo gpt -vv -r show /dev/disk0
Password:
gpt show: /dev/disk0: mediasize=121332826112; sectorsize=512; blocks=236978176
gpt show: /dev/disk0: PMBR at sector 0
gpt show: /dev/disk0: Pri GPT at sector 1
gpt show: /dev/disk0: Sec GPT at sector 236978175
      start       size index contents
          0          1         PMBR
          1          1         Pri GPT header
          2         32         Pri GPT table
         34          6
         40     409600      1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
     409640 235298960      2 GPT part - 53746F72-6167-11AA-AA11-00306543ECAC
235708600    1269536      3 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
236978136          7
236978143         32         Sec GPT table
236978175          1         Sec GPT header
Mac:~ User$ sudo gpt -vv -r show /dev/disk1
gpt show: /dev/disk1: mediasize=3000592982016; sectorsize=512; blocks=5860533168
gpt show: /dev/disk1: PMBR at sector 0
gpt show: /dev/disk1: Pri GPT at sector 1
gpt show: /dev/disk1: Sec GPT at sector 5860533167
       start        size index contents
           0           1         PMBR
           1           1         Pri GPT header
           2          32         Pri GPT table
          34           6
          40      409600      1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
      409640 5859861344      2 GPT part - 53746F72-6167-11AA-AA11-00306543ECAC
5860270984      262144      3 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
5860533128           7
5860533135          32         Sec GPT table
5860533167           1         Sec GPT header
Mac:~ User$ sudo fdisk /dev/disk1
Disk: /dev/disk1 geometry: 97451/255/63 [1565565872 sectors]
Signature: 0xAA55
         Starting       Ending
#: id cyl hd sec - cyl hd sec [     start -       size]
1: EE 1023 254 63 - 1023 254 63 [         1 - 4294967294] <Unknown ID>
2: 00    0   0   0 -    0   0   0 [         0 -          0] unused
3: 00    0   0   0 -    0   0   0 [         0 -          0] unused
4: 00    0   0   0 -    0   0   0 [         0 -          0] unused

I worked with Apple Support. Something appeared to be incorrect in the partitions of the Fusion drive as shipped from the factory. We deleted the drive via Terminal and Disk Utility was then able to recognize a damaged Fusion volume and correct it. After a new install of Yosemite I was able to partition Boot Camp as desired and install Windows.

The Invisible Boot Camp Partition

Basically, my Windows partition does not show up on my Mac side of things.
It shows up in Disk Utility as "disk0s3" but is not mountable. It cannot be mounted if I use the MacFuse and NTFS-3G solution. It cannot be mounted with Paragon's NTFS for Mac OSX. If I open up VMWare Fusion it detects a Boot Camp partition but cannot run it saying instead there is not mountable device. Also, in System Profiler, the partition does not show up under the Serial-ATA section where my OS X partition does.
That being said, Windows runs fine with no issues that I've found.
The way I had to install it was via a work-around since I'm another one of those people who could not format my partition during the installation process. Instead I partitioned via Boot Camp, then used an Ubuntu disk to format the volume to NTFS and install Windows, which worked perfectly sans the OS X side of trouble.
Does anyone know what I can do to fix this problem be it either reinstalling Windows another way or may figuring out why OS X can't see it?

Solution: Remove the volume and reinstall windows via another method. Hopefully 10.5.2 will fix the Boot Camp issues...

Running Boot Camp partition via a VM?

Similar Messages

Maybe you are looking for