Using Windows Bootcamp Partition with VirtualBox?

Discussions related to using VirtualBox on Mac OS X hosts.
mildred
Posts: 3
Joined: 29. Nov 2010, 02:45
Primary OS: Mac OS X Leopard
VBox Version: OSE Debian
Guest OSses: Vista

Re: Using Windows Bootcamp Partition with VirtualBox?

Post by mildred »

Thanks for the advice mk.. I have gone into the disk settings and tried the following but it still doesn't work.
Image

Is this what you meant?

Regards,
Pedro
mildred
Posts: 3
Joined: 29. Nov 2010, 02:45
Primary OS: Mac OS X Leopard
VBox Version: OSE Debian
Guest OSses: Vista

Re: Using Windows Bootcamp Partition with VirtualBox?

Post by mildred »

Another thing I forgot to mention. If I enable IO APIC with ACPI it will load as far as the windows boot screen but then you get the blue screen of death..
Image
If I disable ACPI but keep IO APIC enabled, I get the following:
Image
belum2aj
Posts: 2
Joined: 27. Oct 2010, 19:28
Primary OS: Mac OS X other
VBox Version: OSE other
Guest OSses: Windows 7

Re: Using Windows Bootcamp Partition with VirtualBox?

Post by belum2aj »

ninjoblio wrote:re:belum2aj

I had to remove the SATA drive from the list to get around the error you're getting.

My problem after that though is I can 'start' my windows 7 partition in VB, and it gets to the 'loading files' screen/bar from Windows 7... but then bumps me back to the virtual box loading screen and starts all over. I looked in the log files for VB and I see this when the files are loading...
00:00:07.306 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=1a7a1000 w=1024 h=768 bpp=24 cbLine=0xC00

When the bar is full and you'd normally see the windows login screen, I get this in the log...
00:00:37.679 Changing the VM state from 'RUNNING' to 'RESETTING'.

Anyone seen this before. It just loops and loops and loops through this forever. It looks like I'm getting some kind of error requiring a restart, but VB isn't really telling me a whole lot about what went wrong.

I'm running VB 3.2.10, Windows 7 64 with bootcamp, mac osx 10.6.5. MPB 13", unibody 2.4 ghz
the same problem here
jay1078
Posts: 1
Joined: 21. Jan 2011, 23:10
Primary OS: Mac OS X Leopard
VBox Version: OSE Debian
Guest OSses: Windows Vista - 64bit

Re: Using Windows Bootcamp Partition with VirtualBox?

Post by jay1078 »

@mildred & SonicEarth: I also got the same blue screen of death. I could resolve the error and could successfully boot into Vista-64bit by changing following,

- Remove winvistaraw.vmdk from SATA controller
- Add winvistaraw.vmdk to IDE Controller
- Set IDE Controller type to PIIX4
- Enable "Use host I/O cache"
- Make sure winvistaraw.vmdk is to IDE Primary Master

After these changes start Virtual Machine....
diders
Posts: 1
Joined: 16. Jun 2014, 08:20

Re: Using Windows Bootcamp Partition with VirtualBox?

Post by diders »

Hi everyone I didnt have any issues, maybe because the newer versions of VIrtualBox have fixed it? This is what I did:

1) Eject my windows disk/partition from desktop (right click eject)
2) Open terminal and type $ diskutil list (The reason for this is a lot of the instructions referred to partition 3 and this command on my setup revealed it should be partition 4. Output below:
10-76-16-200:~ diders$ 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            230.0 GB   disk0s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
   4:       Microsoft Basic Data                         20.1 GB    disk0s4
3) $ sudo chmod 777 /dev/disk0
4) $ sudo chmod 777 /dev/disk0s4
5) VBoxManage internalcommands createrawvmdk -rawdisk /dev/disk0 -filename win8_raw.vmdk -partitions 4

NOTE: I have used the number from the diskutil Microsoft partition with the VBoxManage command

6) Started VirtualBox and choose the correct type and version. In my case it had to be 64 bit because the first time I did it failed upon boot because I choose the wrong version.

Yes it is also spinning the CPU up to 95-100% but I didnt need to use VMWare or do anything fancy.
Post Reply