VBoxManageCrash when creating raw vmdk

[sinecure]

I'm seeing a crash when attempting to list the partitions on a rawdisk on Windows 8 Professional 64-bit.

Clean install of Windows 8, clean install of VBox 4.2.8.

If I run

Code: Select all

"c:\Program Files\Oracle\VirtualBox\VBoxManage.exe" internalcommands listpartitions -rawdisk \\.\PhysicalDrive0

as a normal user I get the following error.

Code: Select all

VBoxManage.exe: error: Cannot open the raw disk: VERR_ACCESS_DENIED

That is as expected. However, if I run the same command in an Administrator command prompt, then I get the following.

Code: Select all

VBoxManage.exe: error: Failed to create the VirtualBox object!
VBoxManage.exe: error: Code CO_E_SERVER_EXEC_FAILURE (0x80080005) - Server execution failed (extended info not available)
VBoxManage.exe: error: Most likely, the VirtualBox COM server is not running or failed to start.

Knowing that the partition I want is partition 1 (the second partition - and I may be wrong about the numbering scheme) I try the following command.

Code: Select all

"c:\Program Files\Oracle\VirtualBox\VBoxManage.exe" internalcommands createrawvmdk -filename \Users\dave\VirtualBox-VMs\osx-raw-disk0p1.vmdk -rawdisk \\.\PhysicalDrive0 -partitions 1

Which results in a crash of VBoxManage. I can provide the log files generated by Windows 8 if they would be useful. Basically, I'm looking for any suggestions on how to create a raw disk image on Windows 8 Professional 64-bit at this point.

[sinecure]

Ok, I've just duplicated (or at least experienced) a crash using Windows 7 64-bit Professional. It crashes this time whenever I try to list the raw partitions or create a vmdk to directly access the partitions. Any suggestions?

If not, I guess I'll submit a bug report.

[sinecure]

More information along with strange results. I gave up on OSX, wiped the hard drive (which had been using a GPT and Hybrid MBR partitioning scheme), and replaced all that with three FreeBSD partitions, and one Windows partition using the standard MBR partitioning scheme.

After booting into windows, I was able to create raw disk vmdk's for whole disk and individual partitions. It seems that VirtualBox may have problems creating rawdisk access vmdk's when accessing a disk with GPT partitions. However, checking those results will have to wait, as my laptop had a fight with a cup of coffee and lost. As soon as I can check, if there are still problems using GPT partitions, I'll file a bug report.