VBox.log is the log produced by trying to boot with two attached partitions from the host drive, and VBox.log.2 is the log produced by the vm crashing trying to load the data on a separate disk.
Since it's a Linux guest, I mount the separate drive, but as soon as I try to access the data on that drive, the guest hangs. If I detach the offending vmdk, and boot with the vmdk to access a separate hard drive, the vm boots fine, as long as I do not access the separate hard drive. (VERR_ACCESS_DENIED).ĪHCI: Failed to attach drive to Port3 (VERR_ACCESS_DENIED).
VD: error VERR_ACCESS_DENIED opening image file 'C:\Users\user\VirtualBox VMs\debian 64\systemdrive.vmdk' (VERR_ACCESS_DENIED).įailed to open image 'C:\Users\user\VirtualBox VMs\debian 64\systemdrive.vmdk' in read-write mode (VERR_ACCESS_DENIED).įailed to attach driver below us! Access denied. VD: error VERR_NOT_SUPPORTED opening image file 'C:\Users\user\VirtualBox VMs\debian 64\systemdrive.vmdk' (VERR_NOT_SUPPORTED). The boot process fails immediately if I try to boot with the vmdk to access the two partitions on my Windows drive, with the following error messages:įailed to open a session for the virtual machine debian 64. I had setup two vmdks, one to access two partitions on my system drive (the one Windows is on), and a separate one to access the partition on a separate hard disk (there is only one partition on that disk, Windows doesn't use that disk at all). Using VirtualBox 5.0.x revision 101957 on a Windows 10 amd64 Professional host, I cannot get raw access to some of the partitions on my hard disk, which I was able to get access to on Windows 7 圆4 Ultimate, with VirtualBox 4.3.? (a recent 4.3.x build).
0 kommentar(er)
