Cannot Start VBox described Win7 Bootcamp partition
Posted: 7. Mar 2012, 20:25
Have there been changes to the createrawvmdk internal vboxmanage command in the past year or so? I recently upgraded my Macbook Pro laptop to Lion. I have been running A VirtualBox Windows 7 Virtual Machine on a Bootcamp partition for almost a year now on my Snow Leopard installed Macbook. The bootcamp partition had originally been setup as partition 3 on my hard disk. After upgrading to Lion, I tried to bring up the virtual machine view of this bootcamp partition, but it failed miserably, with a message something like “No Operating System Found”, or some such. Upon investigating, I found that when Lion was installed the Hard disk partitioning had been shuffled and partition 3 was now the MacOS Recovery partition and the bootcamp partition had been moved to partition 4:
JBs-MacBook-Pro:~ Jim$ sudo vboxmanage internalcommands listpartitions -rawdisk /dev/disk0
Number Type StartCHS EndCHS Size (MiB) Start (Sect)
1 0xee 1023/254/63 1023/254/63 200 1
2 0xaf 1023/254/63 1023/254/63 274167 409640
3 0xab 1023/254/63 1023/254/63 619 561903832
4 0x07 1023/254/63 1023/254/63 30258 563173376
After seeing this, I setup my startup disk for the bootcamp partition and rebooted to make sure the Windows 7 contents did not get mangled. It booted up with no problems. So I rebooted to MacOS Lion and thought that it would be a simple matter of rerunning the createrawvmdk command again, specifying partition 4 instead of 3 as the bootcamp partition:
JBs-MacBook-Pro:BC6 Jim$ sudo vboxmanage internalcommands createrawvmdk -rawdisk /dev/disk0s4 -filename BC6.vmdk
RAW host disk access VMDK file BC6.vmdk created successfully.
JBs-MacBook-Pro:BC6 Jim$ ls -l
total 8
-rw------- 1 root Jim 540 Mar 7 07:58 BC6.vmdk
As you can see, the command ran fine, but it only created the vmdk file. In the past when I have run this (last June, with a current version of VirtualBox at the time), a 2nd file which would have been named BC6-pt.vmdk was also created. This essentially was an MBR template description file which which denoted the partition type of each partition.
After setting open permissions on the BC6.vmdk and /dev/disk0s4 files, I tried creating a new virtual disk with just the one vmdk file, but it did not work. It seems to be created OK, but I get “A disk read error occurred. Press Ctrl+Alt+Del to restart” in the Win7 window. I am running VBox version 4.1.6.
Am I missing something here or has the createrawvmdk command been broken? Here is the VBox configuration:
JBs-MacBook-Pro:~ Jim$ sudo vboxmanage internalcommands listpartitions -rawdisk /dev/disk0
Number Type StartCHS EndCHS Size (MiB) Start (Sect)
1 0xee 1023/254/63 1023/254/63 200 1
2 0xaf 1023/254/63 1023/254/63 274167 409640
3 0xab 1023/254/63 1023/254/63 619 561903832
4 0x07 1023/254/63 1023/254/63 30258 563173376
After seeing this, I setup my startup disk for the bootcamp partition and rebooted to make sure the Windows 7 contents did not get mangled. It booted up with no problems. So I rebooted to MacOS Lion and thought that it would be a simple matter of rerunning the createrawvmdk command again, specifying partition 4 instead of 3 as the bootcamp partition:
JBs-MacBook-Pro:BC6 Jim$ sudo vboxmanage internalcommands createrawvmdk -rawdisk /dev/disk0s4 -filename BC6.vmdk
RAW host disk access VMDK file BC6.vmdk created successfully.
JBs-MacBook-Pro:BC6 Jim$ ls -l
total 8
-rw------- 1 root Jim 540 Mar 7 07:58 BC6.vmdk
As you can see, the command ran fine, but it only created the vmdk file. In the past when I have run this (last June, with a current version of VirtualBox at the time), a 2nd file which would have been named BC6-pt.vmdk was also created. This essentially was an MBR template description file which which denoted the partition type of each partition.
After setting open permissions on the BC6.vmdk and /dev/disk0s4 files, I tried creating a new virtual disk with just the one vmdk file, but it did not work. It seems to be created OK, but I get “A disk read error occurred. Press Ctrl+Alt+Del to restart” in the Win7 window. I am running VBox version 4.1.6.
Am I missing something here or has the createrawvmdk command been broken? Here is the VBox configuration: