VirtualBox

Opened 8 years ago

Last modified 8 years ago

#14854 new defect

regression: failed to open session VD: error VERR_NOT_SUPPORTED opening image file

Reported by: Chris Murphy Owned by:
Component: virtual disk Version: VirtualBox 5.0.10
Keywords: Cc:
Guest type: Linux Host type: Mac OS X

Description

I have a VM that uses raw disk function for an SSD partition, with the proper permissions to do so on OS X. There is a .vmdk file created to point to this partition. The VM works without error using VirtualBox 5.0.0 but somewhere between 5.0.1 and 5.0.8 this now results in an error. I'm using 5.0.10 for this bug report.

Host: Mac OS X 10.9.5 Guest: Fedora 23 (but the VM fails before I even get to the emulated firmware)

Attachments (4)

VBox.log.1 (39.1 KB ) - added by Chris Murphy 8 years ago.
vbox.log
sda.vmdk (737 bytes ) - added by Chris Murphy 8 years ago.
sda.vmdk
Fedora UEFI.vbox (10.7 KB ) - added by Chris Murphy 8 years ago.
VM.vbox
VBox.log (117.9 KB ) - added by Chris Murphy 8 years ago.
vbox.log 5.0.0 bug NOT reproducible

Download all attachments as: .zip

Change History (8)

by Chris Murphy, 8 years ago

Attachment: VBox.log.1 added

vbox.log

by Chris Murphy, 8 years ago

Attachment: sda.vmdk added

sda.vmdk

by Chris Murphy, 8 years ago

Attachment: Fedora UEFI.vbox added

VM.vbox

comment:1 by Chris Murphy, 8 years ago

OK I've reinstalled 5.0.2 and it fails. And there is no 5.0.1 so the first version it fails in is 5.0.2 and the failure persists through 5.0.10. This also used to work just fine in all 4.x series virtualboxes, so I don't understand the problem and the error message doesn't help shed any light on what the problem or solution should be.

by Chris Murphy, 8 years ago

Attachment: VBox.log added

vbox.log 5.0.0 bug NOT reproducible

comment:2 by liberize, 8 years ago

I can confirm this. In fact this bug exists for months. I've tested multiple versions through 4.3.x to 5.0.x. As @murphyc described, the last version that works is 5.0.0. There are some other people who have run into this bug, but reported in another ticket: https://www.virtualbox.org/ticket/14425

comment:3 by Chris Murphy, 8 years ago

The same problem occurs even if I only give my user ownership of the specific partition I want to use in the guest OS, which is not used by the host OS; and use internalcommand to create a vmdk for just that partition. So I don't think the error is related to some attempt of concurrent use of the entire block device, since this should restrict it.

comment:4 by liberize, 8 years ago

I think https://www.virtualbox.org/ticket/14613 refers to the same issue.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use