Replace /dev/sdc with the path to the img file. vmdk conf file with correct configuration. dev/sdc should be the partiton of the device/usb the raw. Note that you don't need any particular commands to make a VMDK, but as others have stated, VBoxManage internalcommands createrawvmdk can create one for you as well, which you may find easier or harder depending on what you're trying to do.Īlso note that VMDKs can point to actual partitions or disks as well ( \\.\PhysicalDriveN on Windows, etc.), but the caveat is that VirtualBox doesn't lock the volumes using those disks, so you'll get write errors and/or corruption depending on your OS and whether the volume is mounted.Ĭreate mbr file: sudo install-mbr -force WinXP.mbrĪfter that create a vmdk file like so: sudo VBoxManage internalcommands createrawvmdk -filename myUSB.vmdk -rawdisk /dev/sdc -partitions 1 -relative -mbr WinXP.mbr The other bits about the disk geometry seem irrelevant as far as I can tell. As far as I know, it can be any random GUID, but I'm not sure.ġ234 is the number of sectors in the Image.raw file that you want to map to the diskĥ678 is the sector offset inside the Image.raw file where you want the mapping to begin XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX is the ID of your disk. When the virtual disk is created, it's a random hexadecimal 32-bit value as far as you're concerned. The important bits to fill in are the following: Here's the format one of my VMDK files had (read more here): # Disk DescriptorFile Otherwise, a VMDK file will do what you need, because it's just a text file (with LF line endings at least in my case, but maybe CRLF will work too) that can reference other files to use as the chunk.
Raw image make virtualmachine code#
However, I have found a copy of the source code & binary that the license apparently permits the redistribution of, so if you're looking for it, let me know.Īlternatively, there are probably other tools that could do the same, or you could make a different image of the same size and transfer the appended sector (wasteful, but gets the job done). There used to be a tool called VHDTool by Microsoft which could instantly append the extra sector of metadata to turn a raw image into a VHD, but it's hard to find a copy online now. Since I’m messing with disks a lot, I used the first option (that’s why my commands start with $ not #), but I think running just VirtualBox as root is the safer/better solution for most users.īoth of the answers here get you most of the way there, but here's what I ended up finding helpful:įirst of all, note that a fixed-size VHD file only contains 1 sector of metadata at the end of the file, which is a lot easier to deal with than a file with metadata the beginning.įor booting Linux partition images, a VHD would work just fine. This means either adding your user to a group that has access to disks (on my Ubuntu machine, this is group “disk”), or you need to run VirtualBox as root. Warning: In order for this to work, VirtualBox needs to be able to access the loop device you created.
The virtual machine will access the virtual disk, which now is linked to /dev/loop0, which in turn is linked to the disk image file. Step 3: Attach the virtual disk to a virtual machine and start it. $ VBoxManage internalcommands createrawvmdk -filename /path/to/usb.vmdk -rawdisk /dev/loop0
Step 2: Create a virtual disk and register it with VirtualBox. Step 1: Associate the disk image with a loop device.
0 kommentar(er)
