VBoxManage internalcommands createrawvmdk -filename "/home/lizzias/virtualdrives/windows10.vmdk" -rawdisk /dev/sda
VBoxManage: error: Cannot open the raw disk '/dev/sda': VERR_ACCESS_DENIED
VBoxManage: error: The raw disk vmdk file was not created
VBoxManage internalcommands createrawvmdk -filename "/home/lizzias/virtualdrives/windows10.vmdk" -rawdisk /dev/sda
VBoxManage: error: Cannot open the raw disk '/dev/sda': VERR_ACCESS_DENIED
VBoxManage: error: The raw disk vmdk file was not created
i have used these commands on my manjaro mate installation of linux and it works great but for some reason the command isnt working in arch linux mate installation
in both cases i can mount the drive either to a mount point in fstab or in a file manger to access the drive AND in manjaro the virtual drive works and i can boot into my windows 10 from within manjaro no problem
i have chowned /run/media/lizzias/uudi number of the drive as well as the fstab mount point of /home/lizzias/Windows
i am missing something here that it works in manjaro, an arch derviative but not in arch itself.... someone has a good idea please?
[solved] Virtualbox internal commands throwing errors VERR_ACCESS_DENIED
[solved] Virtualbox internal commands throwing errors VERR_ACCESS_DENIED
Last edited by LizziAS on 26. May 2020, 14:35, edited 1 time in total.
Re: Virtualbos internal commands throwing errors VERR_ACCESS_DENIED
Nevermind... it was a group permissions issue with my new install.
-
scottgus1
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows, Linux
Re: [solved] Virtualbox internal commands throwing errors VERR_ACCESS_DENIED
Thanks, LizziAS, for letting us know what you found.
With the "VERR_ACCESS_DENIED"s, I figured it was a permissions problem, but being a Windows guy and this being Linux so you couldn't "right-click run as Administrator" I didn't know what to suggest.
Glad you're up and running!
With the "VERR_ACCESS_DENIED"s, I figured it was a permissions problem, but being a Windows guy and this being Linux so you couldn't "right-click run as Administrator" I didn't know what to suggest.
Glad you're up and running!