You are here: welcome » wiki » virtualbox

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision		Previous revision
wiki:virtualbox [2011/04/18 07:25] – external edit 127.0.0.1wiki:virtualbox [2013/09/23 06:56] (current) – add 'troubleshooting': sync mouse pointer asashnov
Line 1: Line 1:
-If you are a Windows user, have you ever wondered how difficult it is to work with or experiment with tinycore?+If you are a Windows user, have you ever wondered how difficult it would be to work with or experiment with tinycore?
  
-This is bacause many people would find it inconvenient to boot into tinycore every time they need to make a small change, cook up a package, or simply experiment.+This is because many people would find it inconvenient to boot into tinycore every time they need to make a small change, cook up a package, or simply experiment.
  
-I have a great suggestion that would ease your pains. You can actually boot tinycore within a virtual machine like Sun VirtualBox. This will allow you to boot TinyCore as a "window" within your existing OS,  and even works on Windows!+I have a great suggestion that would ease your pains. You can actually boot tinycore within a virtual machine like Oracle VirtualBox. This will allow you to boot TinyCore as a "window" within your existing OS,  and even works on Windows!
  
 There are 3 ways of doing this, of which the last one I like best. There are 3 ways of doing this, of which the last one I like best.
Line 12: Line 12:
 ===== Windows Host Os ===== ===== Windows Host Os =====
 ==== Method 1: VBox Boot from Mounted Tinycore ISO ==== ==== Method 1: VBox Boot from Mounted Tinycore ISO ====
-The tutorial here will be focused on getting you up and running the simplest way.+ 
 +Download the ISO of your choice (TinyCore, CorePlus, or Core). Start VirtualBox, click on **New**, which will start the New Virtual Machine Wizard, and click **Next**. Enter a VM name, and select OS Type **Linux** version **Linux 2.6**. Select how much memory you want to use, remembering that TinyCore caches everything in memory, so the more memory, the better.  The next step allows you to create a virtual hard disk. If you will want to install TinyCore to disk, go ahead and create one. The default minimum of 8 gigabytes is fine.  Otherwise, uncheck the checkbox, and click **Next**.  At the last screen, click **Create**. You will be sent back to the VirtualBox main screen. Select your new VM, and click on **Start**, this will start the First Run Wizard. Click **Next** and at the Select Installation Media screen, click on the directory browsing icon, and navigate to the location of the ISO you downloaded earlier. Select the ISO, click **Next** and click **Start**. The new VM should boot, and you should see the TinyCore boot prompt. 
  
 ==== Method 2: VBox Boot from Tinycore Virtual Disk ==== ==== Method 2: VBox Boot from Tinycore Virtual Disk ====
Line 26: Line 28:
 Part A Part A
   - EUSEAS Partition Manager Home (freeware) is used to shrink the existing NTFS partition by a meager 2GB. Other partition managers like gparted can be used. Then, a new unformatted partition is created in the free space.   - EUSEAS Partition Manager Home (freeware) is used to shrink the existing NTFS partition by a meager 2GB. Other partition managers like gparted can be used. Then, a new unformatted partition is created in the free space.
-  - The VBox Partition Pointer file (.vmdk) is created with ^VBoxManage internalcommands createrawvmdk -filename PhysicalDrive0-Partition2.vmdk -rawdisk \\.\PhysicalDrive0 -partitions 2 -mbr C:\grub.mbr -register^ (grub.mbr here is an empty "notepad" file we created.) (Win Vista: console/cmd with Administrator access is required for this step) [[http://www.virtualbox.org/manual/UserManual.html#id2528616 | Read more on VBoxManage]]+  - The VBox Partition Pointer file (.vmdk) is created with ''VBoxManage internalcommands createrawvmdk -filename PhysicalDrive0-Partition2.vmdk -rawdisk \\.\PhysicalDrive0 -partitions 2 -mbr C:\grub.mbr -register'' (grub.mbr here is an empty "notepad" file we created.) (Win Vista: console/cmd with Administrator access is required for this step) [[http://www.virtualbox.org/manual/UserManual.html#id2528616 | Read more on VBoxManage]]
  
 Part B Part B
Line 32: Line 34:
  
   - We then boot Tinycore in VirtualBox from the Mounted Tinycore ISO. (Win Vista: Start VirtualBox as Administrator)    - We then boot Tinycore in VirtualBox from the Mounted Tinycore ISO. (Win Vista: Start VirtualBox as Administrator) 
-  - And do ^fdisk /dev/sda^ to delete & recreate partition 2, then ^mkfs.ext3 /dev/sda2^ +  - And do ^fdisk /dev/sda^ to delete & recreate partition 2, then ''mkfs.ext3 /dev/sda2'' 
-  - Grub extension is first installed from the Appbrowser. Boot files are then copied from /mnt/hdc/boot to /mnt/sda2/boot. Grub special files also. The /mnt/sda2/boot/grub/menu.lst is created. You can also add the xvesa option to the kernel option of grub to set the desktop resolution ^kernel    /boot/bzImage quiet xvesa=800x600x24^ so when it runs in a window it fits on the screen. The vga option only affects the terminal.+  - Grub extension is first installed from the Appbrowser. Boot files are then copied from /mnt/hdc/boot to /mnt/sda2/boot. Grub special files also. The /mnt/sda2/boot/grub/menu.lst is created. You can also add the xvesa option to the kernel option of grub to set the desktop resolution ''kernel /boot/bzImage quiet xvesa=800x600x24'' so when it runs in a window it fits on the screen. The vga option only affects the terminal.
   - Grub is initialized with root (hd0,1) and setup (hd0,2) and setup (hd0).   - Grub is initialized with root (hd0,1) and setup (hd0,2) and setup (hd0).
-  - Lastly, the grub MBR is extracted with ^dd if=/dev/sda2 of=/home/tc/grub.mbr bs=512 count=1^.+  - Lastly, the grub MBR is extracted with ''dd if=/dev/sda2 of=/home/tc/grub.mbr bs=512 count=1''.
  
 Part C Part C
Line 41: Line 43:
   - Finally, we edit boot.ini (WinXp) or use bcdedit (Vista) or [[http://neosmart.net/dl.php?id=1 | EasyBCD]] to create a record in Windows Bootloader to allow us to boot into grub when in the "Choose your operating System" Screen. Read [[http://port25.technet.com/archive/2006/10/13/Using-Vista_2700_s-Boot-Manager-to-Boot-Linux-and-Dual-Booting-with-BitLocker-Protection-with-TPM-Support.aspx | this link]] to find out how.   - Finally, we edit boot.ini (WinXp) or use bcdedit (Vista) or [[http://neosmart.net/dl.php?id=1 | EasyBCD]] to create a record in Windows Bootloader to allow us to boot into grub when in the "Choose your operating System" Screen. Read [[http://port25.technet.com/archive/2006/10/13/Using-Vista_2700_s-Boot-Manager-to-Boot-Linux-and-Dual-Booting-with-BitLocker-Protection-with-TPM-Support.aspx | this link]] to find out how.
   - Shiretoko, Xfe, Xfw extensions are installed to give the common user some ease.   - Shiretoko, Xfe, Xfw extensions are installed to give the common user some ease.
 +
 +==== Troubleshooting ====
 +
 +If you have a problem with mouse pointer try to uncheck System' -> 'Motherboard' -> 'Enable absolute pointing device' in the VM configuration (tested on VirtualBox-4.2). As an alternative you can install Xorg-7.6 and virtualbox-ose-additions in order to sync your mouse pointer between host machine and VM properly.
 +
  
  
Print/export
QR Code
QR Code wiki:virtualbox (generated for current page)