virtualbox: the vmdk made in debian 8 cannot be read - error VERR_ACCESS_DENIED

Issues related to applications and software problems
Post Reply
hopefulp
Posts: 25
Joined: 2018/07/29 12:41:54

virtualbox: the vmdk made in debian 8 cannot be read - error VERR_ACCESS_DENIED

Post by hopefulp » 2018/07/29 13:05:09

I have recently changed OS from debian 8 to centos 7.
Previously I used virtual box for virtual machine which was made by VMware so the extension is .vmdk.
In reading .vmdk file from virtualbox (centos 7) makes error.

Error:
Could not open the medium '/home/joon/vmware/Windows10_x64/Wind7_x64_new.vmdk'.
VD: error VERR_ACCESS_DENIED opening image file '/home/joon/vmware/Windows10_x64/Wind7_x64_new.vmdk' (VERR_ACCESS_DENIED).

Is it possible to modify .vmdk file and it is read in centos?

kernel: 3.10.0-862.9.1.el7.x86_64
Window10 has its own bootable separate disk in sdc
sda partition was changed from (debian: /, /home, swap with primary) to (centos: /boot, /, /home, swap where / and /home was LVM) though I am not sure this will affect.
The Window10 is still sdc. ( there is 4 hard disk)
the previous, it means, the present vmdk file is,
----------------------------------------------------------------------------
# Disk DescriptorFile
version=1
encoding="UTF-8"
CID=04fa0f21
parentCID=ffffffff
isNativeSnapshot="no"
createType="fullDevice"

# Extent description
RW 3907029168 FLAT "/dev/disk/by-id/wwn-0x5000c500870adc70" 0

# The Disk Data Base
#DDB

ddb.adapterType = "lsilogic"
ddb.geometry.biosCylinders = "243201"
ddb.geometry.biosHeads = "255"
ddb.geometry.biosSectors = "63"
ddb.geometry.cylinders = "16383"
ddb.geometry.heads = "16"
ddb.geometry.sectors = "63"
ddb.longContentID = "1768532b85f549e646af64f404fa0f21"
ddb.toolsInstallType = "1"
ddb.toolsVersion = "10250"
ddb.uuid = "60 00 C2 91 7d 41 50 f4-1e e2 8c f6 b8 17 da be"
ddb.uuid.image = "2345a952-d619-4a51-b3bf-1b1b430ba7c9"
ddb.uuid.modification = "c42be796-6be0-4f31-b484-8a5c38803df1"
ddb.uuid.parent = "00000000-0000-0000-0000-000000000000"
ddb.uuid.parentmodification = "00000000-0000-0000-0000-000000000000"
ddb.virtualHWVersion = "12"
-------------------------------------------------------------------------------------------------------

The present info of /deb/disk/by-id is
ata-HL-DT-ST_DVDRAM_GH24NSD1_KEXH55A3559
ata-Samsung_SSD_850_PRO_256GB_S258NWAG304532T
ata-Samsung_SSD_850_PRO_256GB_S258NWAG304532T-part1
ata-Samsung_SSD_850_PRO_256GB_S258NWAG304532T-part2
ata-Samsung_SSD_850_PRO_256GB_S258NWAG304532T-part3
ata-ST2000DM001-1ER164_Z4Z3MSXQ
ata-ST2000DM001-1ER164_Z4Z3MSXQ-part1
ata-ST2000DM001-1ER164_Z4Z3MSXQ-part2
ata-ST2000DM001-1ER164_Z4Z3MSXQ-part3
ata-ST2000VX003-1HH164_W523GVGJ
ata-ST2000VX003-1HH164_W523GVGJ-part1
ata-WDC_WD20EFRX-68EUZN0_WD-WCC4M1FUCXCS
ata-WDC_WD20EFRX-68EUZN0_WD-WCC4M1FUCXCS-part1
dm-name-centos_chi-home
dm-name-centos_chi-root
dm-uuid-LVM-08yDaAPl3kmczdDgp6hYO78ZxJKK8ax1AqETDyH4ZTQsbqwq2o0ta64Uh21LfQ3n
dm-uuid-LVM-08yDaAPl3kmczdDgp6hYO78ZxJKK8ax1zPsZqFmFWUtUoMjiNyUSfL9WNqTcG9KO
lvm-pv-uuid-1qQLmz-vKJx-4IKO-AKjI-DvY5-D3nk-TfMEIi
wwn-0x5000c500870adc70
wwn-0x5000c500870adc70-part1
wwn-0x5000c500870adc70-part2
wwn-0x5000c500870adc70-part3
wwn-0x5000c5009c4321bd
wwn-0x5000c5009c4321bd-part1
wwn-0x5001480000000000
wwn-0x50014ee2614eeb9a
wwn-0x50014ee2614eeb9a-part1
wwn-0x50025388700b9604
wwn-0x50025388700b9604-part1
wwn-0x50025388700b9604-part2
wwn-0x50025388700b9604-part3

User avatar
TrevorH
Site Admin
Posts: 33202
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: virtualbox: the vmdk made in debian 8 cannot be read - error VERR_ACCESS_DENIED

Post by TrevorH » 2018/07/29 13:25:15

It is complaining about being unable to read '/home/joon/vmware/Windows10_x64/Wind7_x64_new.vmdk' so this looks like a linux permissions issue. The user you are using to run vbox will need to have read/write access to the file itself and at least traverse (+x) access to all directories leading down to the file. In addition, on CentOS, the selinux context will need to be correct to allow the user access but this is less likely than just plain old permission problems. If you still have problems then post the output from namei -mol /home/joon/vmware/Windows10_x64/Wind7_x64_new.vmdk as well as the output from ls -laZ /home/joon/vmware/Windows10_x64/Wind7_x64_new.vmdk
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke

hopefulp
Posts: 25
Joined: 2018/07/29 12:41:54

Re: virtualbox: the vmdk made in debian 8 cannot be read - error VERR_ACCESS_DENIED

Post by hopefulp » 2018/07/30 02:28:56

The id is "joonho" which I have changed slightly in previous writing.
Sometimes the authority bothers me but I am not sure this is the same case

joonho@chi:~$ namei -mol /home/joonho/vmware/Windows10_x64/Wind7_x64_new.vmdk
f: /home/joonho/vmware/Windows10_x64/Wind7_x64_new.vmdk
dr-xr-xr-x root root /
drwxr-xr-x root root home
drwxr-xr-x joonho joonho joonho
drwxr-xr-x joonho joonho vmware
drwxr-xr-x joonho joonho Windows10_x64
-rwx------ joonho joonho Wind7_x64_new.vmdk

joonho@chi:~$ ls -laZ /home/joonho/vmware/Windows10_x64/Wind7_x64_new.vmdk
-rwx------ joonho joonho ? /home/joonho/vmware/Windows10_x64/Wind7_x64_new.vmdk

hopefulp
Posts: 25
Joined: 2018/07/29 12:41:54

Re: virtualbox: the vmdk made in debian 8 cannot be read - error VERR_ACCESS_DENIED

Post by hopefulp » 2018/07/30 04:11:58

@ TrevoH: You are right. That was permission issue. Window 10 is on the different disk, that is, sdc.
So I need to add my id to group disk.
It works now. Thank you very much.

Post Reply