Bdtyktl

On newer MacBook Pro's the SD card slot is no longer exposed as a USB device. Because of this you'll need to attach the raw device to the VM in order to gain raw access to the whole card. Full documentation is in the Advanced Storage Configuration section of the VirtualBox documentation.

As clearly stated in the docs:

Warning - Raw hard disk access is for expert users only. Incorrect use or use of an outdated configuration can lead to total loss of data on the physical disk. Most importantly, do not attempt to boot the partition with the currently running host operating system in a guest. This will lead to severe data corruption.

As a quick guide these are the steps to attach the device to a linux VM:

1. 
   

   Identify the raw disk block device on your host system

   
   
   
   
   
   1. Insert the SD card into the slot
   
   
   2. 
      

      Open a Terminal and type "mount". You'll see output identifying the mounted volume from your SD card. On my system I get the following

      
      
      

      $ mount
      
      /dev/disk1 on / (hfs, local, journaled)
      
      devfs on /dev (devfs, local, nobrowse)
      
      map -hosts on /net (autofs, nosuid, automounted, nobrowse)
      
      map auto_home on /home (autofs, automounted, nobrowse)
      
      /dev/disk2s1 on /Volumes/NO NAME (msdos, local, nodev, nosuid, noowners)`
      
      

      
      
   
   

   3. In my case the "NO NAME" volume is the SD card, so I take note of the /dev/disk2s1 part. In this particular case the s1 part represents a partition (slice) on the raw device, so the part we'll use later is just the /dev/disk2 part.

   
   
   
   


2. Open Disk Utility and "Unmount" the volume. Do not "Eject" it. Note that you may need to unmount the volume once in a while during the next steps as I found OSX would automatically remount it at random.


3. 
   

   Now we set up VirtualBox to be aware of the raw device with the following command in the Terminal.

   
   
   
   
   
   1. Note that the /path/to/file.vmdk can be put anywhere, though it's a good idea to store this in the guest VM folder such as ~/VirtualBox VMs/guest-vm/sdcard.vmdk
      
   
   
   2. 
      

      Note that the -rawdisk we use doesn't reference the partition (slice) but only the block device as a whole.

      
      
      

      $ VBoxManage internalcommands createrawvmdk -filename /path/to/file.vmdk -rawdisk /dev/disk2
      
      

      
      
   
   
   
   


4. 
   

   Next we attach the raw disk to a guest VM within the VirtualBox UI

   
   
   
   
   
   1. Ensure the guest VM is not running.
   
   
   2. Open the settings area for the guest VM
   
   
   3. Click on "Storage" in the toolbar
   
   
   4. Next to the controller click on the icon to "Add Hard Disk"
   
   
   5. Select "Choose existing disk"
   
   
   6. Navigate to the /path/to/file.vmdk you used in step 3 and select it
   
   
   7. You should now be returned to the Storage tab and see your file.vmdk in the list.
   
   
   
   


5. Start the VM


6. Depending on whether you have a GUI or not the SD card may or may not automatically mount. If you need to mount is manually it is simply exposed as another standard block device, so on my guest this was exposed as /dev/sdb.

Update

It seems some people may have trouble with accessing the raw device in step 3.2 or 4.6. Attempts to run some of the commands with sudo won't help as VirtualBox will be running as your logged in user and still won't be able to access the raw device correct or the generated vmdk file.

The following steps should help, though I haven't tested them.

1. Check the account you're using on OSX has Admin privileges in the System Preferences/Users section. There's a good chance it should also be the primary account on the system for raw device access to work.


2. 
   

   Check the raw disk permissions

   
   
   

       $ ls -l /dev/disk2
   
       brw-r----- 1 jinn staff    14,  5 Aug 26 15:33 /dev/disk2
   
   

   
   
   

   These permissions must match your current logged in user account:

   
   
   

       $ id
   
       uid=501(jinn) gid=20(staff) ...snip...
   
   

   
   
   

   The permissions on the device should also permit your usual user account to both read (r) and write (w) to this device. DO NOT CHANGE PERMISSIONS ON THE DEVICE UNLESS YOU ABSOLUTELY KNOW WHAT YOUR'RE DOING.

   
   

Update #2

Turns out OSX Mountain Lion created the device with "root:operator" privileges and 0640 permissions. Unfortunately for now the only way to gain access to this device is to "sudo chown $USER" it to your current user each time you insert the device, however this is not recommended unless you really understand what you're doing. Hopefully either Apple or VirtualBox will find a more suitable solution.

Answer for Windows users

1. 
   

   Get the DeviceID of your SD card reader.

   
   
   

   You'll need a card in the drive, mounted by windows.

   
   
   

   Enter this command

   
   
   

   wmic diskdrive list brief
   
   

   
   
   

   It should look something like this:

   
   
   

   C:UsersSandy Scott>wmic diskdrive list brief
   
   Caption                      DeviceID            Model                        Partitions  Size
   
   WDC WD7500BPKT-75PK4T0       \.PHYSICALDRIVE0  WDC WD7500BPKT-75PK4T0       3           750153761280
   
   O2Micro SD SCSI Disk Device  \.PHYSICALDRIVE1  O2Micro SD SCSI Disk Device  1           3964584960
   
   

   
   
   

   The last device is the SD card reader, so the DeviceID is \.PHYSICALDRIVE1

   
   


2. 
   

   Create the link file to the SD card

   
   
   

   Open a command windows as Administrator

   
   
   

   "C:Program FilesOracleVirtualBoxVBoxManage" internalcommands createrawvmdk -filename "%USERPROFILE%/Desktop/sdcard.vmdk" -rawdisk "\.PHYSICALDRIVE1"
   
   

   
   
   

   This assumes the default installation path - change it if you need to. (Ensure quotes are around the rawdisk argument.)

   
   
   

   The .vmdk file is a link to the SD card, you can put it anywhere on your host system, but this command just puts it on your desktop for convenience.

   
   



3. Follow steps 4-6 in JinnKo's answer, the only minor tweak is that you need to start VirtualBox as an Administrator

1. Next we attach the raw disk to a guest VM within the VirtualBox UI
   
   
   
   
   1. Ensure the guest VM is powered off.
   
   
   2. Ensure VirtualBox is not running
   
   
   3. Start VirtualBox by right-clicking on it and choosing "Run as administrator"
   
   
   4. Open the settings area for the guest VM
   
   
   5. Click on "Storage" in the toolbar
   
   
   6. Next to the controller click on the icon to "Add Hard Disk"
   
   
   7. Select "Choose existing disk"
   
   
   8. Navigate to the /path/to/file.vmdk you used in step 3 and select it
   
   
   9. You should now be returned to the Storage tab and see your file.vmdk in the list.
   
   
   
   


2. Start the VM


3. Depending on whether you have a GUI or not the SD card may or may not automatically mount. If you need to mount is manually it is simply exposed as another standard block device, so on my guest this was exposed as /dev/sdb.

You are most likely missing the extensions if your SD reader is using your USB controller.

Under File > Preferences, follow the pic. Add and point to the downloaded extension.

Restart your Virtual Machine and you should have access to USB devices.

I'm using Kubuntu 15.04, VirtualBox 4.3.26

This assumes that the sd card device is /dev/mmcbl0 , and the output .vdk will be sd-card.vmk :

sudo VBoxManage internalcommands createrawvmdk -filename ./sd-card.vmdk -rawdisk /dev/mmcblk0

Not sure this is the best way to fix permissions, but it worked:

sudo chmod 777 /dev/mmcblk0

sudo chmod 777 ./sd-card.vmdk

Now go to the VM Settings, select Storage, click on Controller:Sata, click on the icon for Add Hard Disk, select your .vdk (sd-card.vmdk in this case)

I had a lot of troubles getting the solution by JinnKo to work, mostly due to my being on Mountain Lion (OS X 10.8) ... But with his kind assistance, I've solved the issues.

The full solution is detailed here.

However, the essence of my solution--for Mountain Lion users--is as follows (use JinnKo's steps above, but insert my step here before running the 'VBoxManage internalcommands createrawvmdk [...]' command (that is, in between his steps 2 & 3):

** Particularly for Mtn Lion ** Make sure you are the owner of this device. On 10.8 Mtn Lion, you will probably find that you aren't. Check it by doing:

ls -l /dev/disk*

With the '*' you will see ALL your disk devices, you can also do: ls -l /dev/diskX to just see 'X', for instance, I did:

ls -l /dev/disk5

On Mtn Lion ( 10.8.x ) you will see something like:

brw-r----- 1 root operator 1, <today's date/time> /dev/diskX

Where 'X' is your device number, like the '5' in /dev/disk5 ...

On Lion ( 10.7.x ), Snow Leopard (10.6.x ), or perhaps earlier versions of OS X, you will--if your username is 'brad'--likely see something like:

brw-r----- 1 brad operator 1, <today's date/time> /dev/diskX

Where 'X' is your device number, like the '5' in /dev/disk5 ...
If you are the owner, then all's good, nothing to do here, go to the next step, that is, the createrawvmdk step (in @JinnKo 's great instructions above).

If you are not the owner (but 'root' or some other user is), then either (a) login as that admin user or (b) do the following (again, be very sure you are using the correct device number/letter here!):

* CAUTION * The below is only for those who want to risk permanently destroying data on their hard drive or flash storage drive. DO NOT DO THIS if you aren't sure you know what you're doing:

sudo chown <your username> /dev/disk5

sudo chown <your username> /dev/disk5s1

* CAUTION * DO NOT DO THIS if you aren't sure you know what you're doing. The above is only for those who want to RISK permanently destroying data on their hard drive or flash storage drive.

You will need to do it for ALL of your slices (s1, s2, s3, ... however many there are).
For example, my username is 'brad', so I did: sudo chown brad /dev/disk5, then sudo chown brad /dev/disk5s1, then for s2, and s3 (since I had 3 existing partitions or slices already).

If you haven't partitioned the SD card, then you may only need to do the sudo chown <your username> /dev/diskX once (without doing any of the slices/partitions)

Hope this helps some other poor Mtn Lion users out there!

On newer MacBook Pro's the SD card slot is no longer exposed as a USB device

To overcome this problem you can simply use an external Usb Memory Card Reader (i.e. sd card to usb adapter) instead of built-in card reader. It will expose your sd card as a USB device so that you can mount it easily just like any usb device. They're cheap devices and would be an acceptable solution considering all the hassle in the other way.

I've so far failed in finding a way to do this directly, even with a USB card reader (it put the card on /dev/dm-1 rather than the expected /dev/mmcblk1).

My workround was to create a 4 GB virtual drive in VirtualBox. This could then (as /dev/sdb) take an install of BeagleBoard Ubuntu as documented.

I then shut down the VM, converted it to a RAW DD file and used DD to put it on the card:
(on the host Mac):

VBoxManage clonehd UbuntuBeagleImage.vdi UbuntuBeagleImage.dd --format RAW

sudo dd if=UbuntuBeagleImage.dd of=/dev/rdisk(NUMBER) bs=1m

(/dev/disk2 in my case, but triplecheck as getting it wrong could bork your hard disk drive).

The dd command took about 1 hr 20 min!

I hope this helps. I'm still working towards an easier and quicker way - we shouldn't need to transfer 4 GB of data for 600 MB of OS.

For me the solution was to turn-on USB device with SD card, using
Devices -> USB devices ->My card reader,

and after few seconds new disks appear in my VM.

I have installed VirtualBox Extensions Pack before that.

I installed the "Virtual Box Guest Additons CD" files, but my SD card reader was not showing in my Windows XP Virtual Machine. I was able to get mine working by enabling the USB device in Virtual Box and then re-starting the Virtual Machine.

As kobaltz mentioned. To support the USB 2.0 and 3.0 versions you need to install the Virtual Extension Pack, I installed the 5.2.22 Oracle VM VirtualBox Extension Pack, and you can download it from the Virtual Box download page. Once you download the file, you can directly go ahead and install it, the same will be added to your Virtual Box extensions.

You should also add your SD card to the device filters in our Virtual Box, please go to Settings – > USB -> Click on the Add SD card Attached option.

Now you will be able to your SD card in the Filters.

Go to the Files and see the see the SD card folders (I use Ubuntu Linux Distribution)