Opened 14 years ago
Closed 10 years ago
#8567 closed defect (obsolete)
VERR_NOT_SUPPORTED error when trying to add RAW vmdk disk on VBox 4.0.4 running on Windows
Reported by: | audrunas | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 4.0.4 |
Keywords: | vmdk raw VERR_NOT_SUPPORTED | Cc: | |
Guest type: | other | Host type: | Windows |
Description (last modified by )
Hello,
I know that this bug has been reported before and has a status of being fixed (tickets #7811 and #7251), but it is definitely present in version 4.0.4 , so this is not a duplicate.
I have the following problem running VBox on Windows 7 Host:
- I created a raw vmdk disk using the following command:
VBoxManage internalcommands createrawvmdk -filename D:\VirtualPC\Physical_Ubuntu\disk.vmdk -rawdisk \.\PhysicalDrive0 -partitions 5,6 RAW host disk access VMDK file D:\VirtualPC\Physical_Ubuntu\disk.vmdk created successfully.
- Then I tried to add it to a virtual machine and I got the following error message:
Failed to open the hadr disk D:\VirtualPC\Physical_Ubuntu\disk-pt.cmdk . Result Code: VBOX_E_IPRT_ERROR (0x80BB0005) Component: Medium Interface: IMedium {9edda847-1279-4b0a-9af7-9d66251ccc18} Callee: IVirtualBox {d2de270c-1d4b-4c9e-843f-bbb9b47269ff}
I hope this helps you. Thank you for such a great product! I am enjoying using VirtualBox.
Attachments (2)
Change History (5)
by , 14 years ago
by , 14 years ago
Attachment: | disk-pt.vmdk added |
---|
comment:1 by , 14 years ago
comment:2 by , 13 years ago
I can confirm that this same issue is happening to me as of 4.1.8 on a Windows 7 host. Using the same VMDK in VMware works just fine, so I believe it's a problem with the media manager since it won't allow me to attach the drive at all.
comment:3 by , 10 years ago
Description: | modified (diff) |
---|---|
Resolution: | → obsolete |
Status: | new → closed |
Closing as obsolete, please reopen if still relevant and attach a VBox.log.
Sorry, the file in the error message was supposed to be D:\VirtualPC\Physical_Ubuntu\disk-pt.vmdk (I was copying the first line of the error message by typing it manually)