vmdk file to your VirtualBox Virtual Machine and make sure that you can boot to it. Then all you should have to do is to add the. Take ownership of the new file: sudo chown $USER:$USER ~/usb.vmdk Note: Some people have had issues of ownership of the newly created file. Then you should see something similar to this: RAW host disk access VMDK file /home/ravan/usb.vmdk created successfully. Or sudo VBoxManage internalcommands createrawvmdk -filename ~/usb.vmdk -rawdisk /dev/sdb vmdk file that points to the USB drive: sudo vboxmanage internalcommands createrawvmdk -filename ~/usb.vmdk -rawdisk /dev/sdb Next, type in the following from a terminal window to create the. So, the physical drive would be /dev/sdb. We are going to assume that your drive is mounted as /dev/sdb1. Not every situation is the same so this may not work for every case.įirst, you need to have your USB you created in your system, and determine what the physical drive is. This can be helpful if there is persistence on the USB that you want to keep. This also does not copy the USB drive to the hard drive and uses the USB directly. You MUST also add your account to the disk group as well, or you cannot add the. NOTE: You MUST add your user account to the vboxusers group for VirtualBox to see your USB. vmdk file that points to your USB drive for booting to it. Since VirtualBox does not boot to USB drives, you can create a.
I am looking into if the raw disk can be created from the UUID of the drive instead as that will not change.
When you reboot your computer for any changes please remove the USB drive prior to rebooting. It was /dev/sdi before I rebooted, after reboot it was /dev/sdc. Leaving the USB drive in the computer when you reboot can change the /dev/sd drive letter designation causing the raw usb.vmdk file to point to the incorrect drive so it does not boot in VirtualBox.
0 kommentar(er)
