![How To Install Micro Xp With Virtualbox Linux How To Install Micro Xp With Virtualbox Linux](http://4.bp.blogspot.com/-nt97LwGGP1o/T1_At3fp-JI/AAAAAAAAAF0/BhVyJ44JiZs/s1600/Screenshot+at+2012-03-03+18:40:01.png)
VirtualBox itself does not support booting from a USB device. In order to boot from a USB device, another bootloader is required. The steps below provide one possible way to accomplish this:. Download (currently v5.0.15). Extract the file plpbt.iso from the ZIP archive and save it somewhere.
A Basic Guide To The Linux Operating System Share Pin. That users need to know before they install Linux. Machine by using a tool called Virtualbox. Apr 5, 2014 - I'm trying to install Windows XP Service Pack 1 from an original. Installed the latest VirtualBox. OSX, Linux and Windows Hosts & Guests.
Open the settings for the virtual machine and attach the ISO file:. Add a filter for the USB device:. Boot the VM and select the 'USB' option in the menu: If all went well, the machine should now boot from the USB device. I wanted to add that Plop Boot Manager only officially supports EHCI. If you're like me, and you're trying to use a USB 3.0 drive with Plop Boot Manager, it won't work. You could try to use the method mentioned in the other post, but VirtualBox also doesn't seem very fond of working with raw vmdks from USB 3.0 devices. If you only have USB 3 ports on your computer, you can order a USB 2.0 hub and connect the drive through that.
It will behave essentially like a USB 2.0 drive. – Mar 21 '16 at 0:02. EDIT: 7 Mar 2018 Something to note here. 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. As a test I left one in my system. It was /dev/sdi before I rebooted, after reboot it was /dev/sdc.
When you reboot your computer for any changes please remove the USB drive prior to rebooting. I am looking into if the raw disk can be created from the UUID of the drive instead as that will not change.
Since VirtualBox does not boot to USB drives, you can create a.vmdk file that points to your USB drive for booting to it. NOTE: You MUST add your user account to the vboxusers group for VirtualBox to see your USB. You MUST also add your account to the disk group as well, or you cannot add the.vmdk file to your Virtual Machine. Added instructions below in EDIT.
This also does not copy the USB drive to the hard drive and uses the USB directly. This can be helpful if there is persistence on the USB that you want to keep. Not every situation is the same so this may not work for every case.
First, you need to have your USB you created in your system, and determine what the physical drive is. We are going to assume that your drive is mounted as /dev/sdb1. So, the physical drive would be /dev/sdb. Next, type in the following from a terminal window to create the.vmdk file that points to the USB drive: sudo vboxmanage internalcommands createrawvmdk -filename /usb.vmdk -rawdisk /dev/sdb Or sudo VBoxManage internalcommands createrawvmdk -filename /usb.vmdk -rawdisk /dev/sdb Then you should see something similar to this: RAW host disk access VMDK file /home/ravan/usb.vmdk created successfully. Note: Some people have had issues of ownership of the newly created file. Take ownership of the new file: sudo chown $USER:$USER /usb.vmdk Then all you should have to do is to add the.vmdk file to your VirtualBox Virtual Machine and make sure that you can boot to it.
EDIT: To add your user to the vboxusers group, run the following command: sudo usermod -a -G vboxusers username To add your user to the disk group, run the following command: Note: Adding your user to the disk group can be dangerous and a security risk. It is as dangerous as having sudo access to write to a raw disk. Sudo usermod -a -G disk username Then you MUST REBOOT your system in order for the changes to take effect. Before reboot: After reboot: Hope this helps! I came to this post just few days ago. I don't want to use Plop Boot Manager, because my USB stick is already bootable.
So I tried to point the USB stick to a VMDK disk (as in Terrance answer) by creating vboxmanage internalcommands createrawvmdk -filename /usb.vmdk -rawdisk /dev/sdb Unfortunately, this refused to work. I chmod and chown the usb.vmdk disk, and so I was able to attach it to a VM but it simply didn't work. Finally, I tried another solution and this one has worked flawlessly. Here it is (thanks to Gean Santos for the research):. Insert USB stick and identify it (mine is /dev/sdb, running Sabayon Linux);. Create a.vmdk disk by converting the raw device (i.e.
The USB stick) to a VirtualBox disk sudo VBoxManage convertfromraw /dev/sdb./usb.vmdk -format vmdk. Now you have a usb.vmdk disk created from your bootable USB stick. I tried also dd the USB stick to an image file and create the.vmdk disk from the image file. It works, as well as.vdi disks created the former way (or from the image file).
Now, give permissions to the created disk in order VirtualBox can access the file. It just means change the file owner to an user that are in vboxusers group. If your VirtualBox install is running OK, than this owner would be, probably, you: sudo chown `whoami`:`whoami`./usb.vmdk. Now, you just have to attach the usb.vmdk disk to a Virtual Machine. But it must be attached to an IDE controller.
I tried SATA with no success. At this point, you're OK. Just boot the new VM, press F12 and choose the bootable drive. I did not want to run Virtualbox as root. I did not want my user to be of the disk group, having full permissions to all disks.
So here is what I got to work: Find out what sd the memory stick is. In the following instructions it's sdc. Unmount memory Stick su chmod 666 /dev/sdc1 chmod 666 /dev/sdc VBoxManage internalcommands createrawvmdk -filename usb.vmdk -rawdisk /dev/sdc chmod 777 usb.vmdk chmod 666 /dev/sdc. Attach usb.vmdk virtualbox machine chmod 666 /dev/sdc. Start virtualbox machine. After done, reset sdc1 permission for security: chmod 660 /dev/sdc1 In the above you can see that I had to reset the permissions for the memory stick a few times, because it would get set back to root each time.
I'm using Mandriva Linux, but it should be about the same in Ubuntu.