Here's everything we could find about: "VirtualBox"
Posted by Derek@TheDailyLinux »
23 Comments »This is a step by step tutorial on how to get VirtualBox 3.2 up and running on Fedora 13. Specifically, this guide was written using the VirtualBox 3.2.0 (32-bit) version. It can be adapted to upcoming versions and different CPUs (64-bit). The folks at VirtualBox have made it easy to install for Fedora users and I’m going to show you how in a few easy steps. Right, open a terminal window and let’s get to it…
[Read more →]
Posted by Derek@TheDailyLinux »
Add Comment »Table of Contents
This guide will assist in loading a pre-built VirtualBox image. The example used is a pre-built Ubuntu 9.10 “Karmic Koala” guest image. Any VirtualBox image can be used however.
[Read more →]
Posted by Derek@TheDailyLinux »
Add Comment »I hadn’t realized this before, but you can shrink a dynamic VirtualBox disk image. This is incredibly helpful if you’ve uninstalled programs or freed up a bunch of space and you want the .vdi image size to reflect that. Otherwise, the dynamic disk image will stay the same size it was before. The process is simple, but can be a bit involved so I’ll just touch on the basics and then refer you to a few guides that were really helpful when I did this for my Ubuntu 9.10 VirtualBox image. These guides can be applied to other guest images as well.
1.) Install “zerofree” on your virtualbox guest machine.
2.) Boot to safe mode (recovery mode) where you can access your root partition (/dev/sda1).
3.) Mount the root partition as read-only (mount -o ro /dev/sda1 /mnt/tmp)
4.) Run “zerofree /dev/sda1″
5.) Shutdown the virtual machine and run “VBoxManage modifyhd –compact /path/to/virtualboximage.vdi”
In-Depth Guides:
http://maketecheasier.com/shrink-your-virtualbox-vm/2009/04/06 — Keep in mind that zerofree does in fact support ext4 (I think this article is a tiny bit dated, but it’s a great one).
http://www.virtualbox.org/manual/UserManual.html — The all important VirtualBox Users Guide.
http://forums.virtualbox.org/viewtopic.php?p=29272#29272 — Another good reference for VirtualBox
Posted by Derek@TheDailyLinux »
30 Comments »Updated: 11/22/2009
This is a step by step tutorial on how to get VirtualBox 3 up and running on Fedora 12. Specifically, this guide was written using the VirtualBox 3.0.8 version and an i386 CPU (32-bit). It can be adapted to upcoming versions and different CPUs (64-bit). The folks at VirtualBox have made it easy to install for Fedora users and I’m going to show you how in a few easy steps. Right, open a terminal window and let’s get to it…
[Read more →]
Posted by Derek@TheDailyLinux »
24 Comments »Note: I have been unable to verify these steps. They should work just fine, but I’m a little concerned about the USB support fix. You may or may not want to try it at this point. I have it here just as a reference for now.
This is a tutorial on how to get VirtualBox up and running on Fedora 11. Also, this tutorial is for the 32-Bit version of VirtualBox, so you’ll have to customize a little more to get the 64-bit version running. Everything in the “code” sections should be copy/pasted/typed into the terminal. Right, let’s get to it:
PreStep.) Open the terminal and get into super user mode:
su -
1.) Get the latest VirtualBox package (as of now, 2.2.4) from the VirtualBox website for Fedora 11 and install it. The following command should download and install the application:
wget http://download.virtualbox.org/virtualbox/2.2.4/VirtualBox-2.2.4_47978_fedora11-1.i586.rpm && rpm -ivh VirtualBox-2.2.4_47978_fedora11-1.i586.rpm
2.) Get the kernel-devel and other needed packages:
yum install make automake autoconf gcc kernel-devel dkms
3.) Run the setup file for VirtualBox:
/etc/init.d/vboxdrv setup
4.) Add yourself to the “vboxusers” group and fix the SELinux Permissions:
usermod -G vboxusers -a username
chcon -t textrel_shlib_t /usr/lib/virtualbox/VirtualBox.so
5.) Run, and enjoy!
VirtualBox
6.) To Get USB Support:
1 – create a new group called “usb”;
2 – locate file usbfs: in my case is /sys/bus/usb/drivers (I suggest to find the file with a usb device inserted;
3 – modify file /etc/fstab inserting a line containing the right path and the number corresponding the “usb” group :
none /sys/bus/usb/drivers usbfs devgid=503,devmode=664 0 0
4 – command mount -a;
5 – start VB and try…;
Source: Fedora Forums
7.) To Properly Backup the VirtualBox Machine (.vdi):
Please refer to my other page here:
How To: Properly Backup a VirtualBox Machine (.VDI)
8.) To Get Sound Working:
Highlight your virtual machine and click on the “Settings” button. Click on the “Sound” category, and then check the “Enable Sound” option. In the drop-down box, select “PulseAudio”. You should now have sound.
That’s it! If you find yourself with problems, feel free to comment below or ask for assistance on the fedora forum thread that I have created located here.
Posted by Derek@TheDailyLinux »
Add Comment »Updated November 25th, 2008
This is a tutorial on how to get VirtualBox up and running on Fedora 10. Also, this tutorial is for the 32-Bit version of VirtualBox, so you’ll have to customize a little more to get the 64-bit version running. Everything in the “code” sections should be copy/pasted/typed into the terminal. Right, let’s get to it:
PreStep.) Open the terminal and get into super user mode:
su -
1.) Get the latest VirtualBox package (as of now, 2.0.6) from the VirtualBox website for Fedora 9 and install it (generally, after a few months, the Fedora 10 link will be available).
wget http://download.virtualbox.org/virtualbox/2.0.6/VirtualBox-2.0.6_39765_fedora9-1.i386.rpm && rpm -ivh VirtualBox-2.0.6_39765_fedora9-1.i386.rpm
2.) Get the kernel-devel package:
yum install make automake autoconf gcc kernel-devel dkms
3.) Run the setup file for VirtualBox:
/etc/init.d/vboxdrv setup
4.) Add yourself to the “vboxusers” group and fix the SELinux Permissions:
usermod -G vboxusers -a username
chcon -t textrel_shlib_t /usr/lib/virtualbox/VirtualBox.so
5.) Run, and enjoy!
VirtualBox
6.) To Get USB Support:
1 – create a new group called “usb”;
2 – locate file usbfs: in my case is /sys/bus/usb/drivers (I suggest to find the file with a usb device inserted;
3 – modify file /etc/fstab inserting a line containing the right path and the number corresponding the “usb” group :
none /sys/bus/usb/drivers usbfs devgid=503,devmode=664 0 0
4 – command mount -a;
5 – start VB and try…;
Source: Fedora Forums
7.) To Properly Backup the VirtualBox Machine (.vdi):
Please refer to my other page here:
How To: Properly Backup a VirtualBox Machine (.VDI)
8.) To Get Sound Working:
Highlight your virtual machine and click on the “Settings” button. Click on the “Sound” category, and then check the “Enable Sound” option. In the drop-down box, select “PulseAudio”. You should now have sound.
That’s it! If you find yourself with problems, feel free to comment below or ask for assistance on the fedora forum thread that I have created located here.
Posted by Derek@TheDailyLinux »
Add Comment »Here’s a screenshot tour of the Fedora 10 Release Candidate (or Preview Release) running within a VirtualBox VM. The countdown begins! 21 Days left as of this entry… Enjoy!
Other useful links:
Release Notes: http://docs.fedoraproject.org/release-notes/f10preview…
Feature List: http://fedoraproject.org/wiki/Releases/10/FeatureList
Mirrors: http://mirrors.fedoraproject.org/publiclist/Fedora/10-Preview/
Artwork: http://fedoraproject.org/wiki/Artwork/F10Themes
Posted by Derek@TheDailyLinux »
Add Comment »
Introduction:
This guide is intended to help users fully install VirtualBox and all of it’s features which don’t work out of the box such as USB support.
[Read more →]
Posted by Derek@TheDailyLinux »
56 Comments »First of all, these are the instructions for a VirtualBox installation on a Linux host. It may or may not be the same directory structure/commands for Windows or Mac OS X hosts.
Most people don’t realize that making a backup of a VirtualBox Machine (.vdi) is more complex than just copy/paste. If you do that, you’ll soon realize (when it’s too late) that it doesn’t work! This is the proper way to backup your VirtualBox Machine:
VBoxManage clonevdi source destination
Example:
VBoxManage clonevdi ~/.VirtualBox/VDI/WindowsXP.vdi ~/WindowsXP_Backup.vdi
NOTE: Although I’m not specifically sure, sometime after Version 2 of this software, the clonedvi command has been replaced with clonehd (see page 108 of the VirtualBox Manual), however, clonedvi will still work as they kept the backwards compatibility.
Then, wait for it to complete. It may take a while depending on the size of your .vdi file (or how much space you allocated towards your virtual machine).
What this actually does is create a new UUID (Universal Unique Identifier) for the cloned VM. This way, you won’t end up with a message similar to this:
A hard disk with UUID {4d749826-6a3f-43ff-90af-42618783bd3a} or with the
same properties (’/home/martin/.VirtualBox/VDI/test.vdi’) is already
registered.
Posted by Derek@TheDailyLinux »
Add Comment »Updated January 9th, 2008
This is a tutorial on how to get VirtualBox up and running on Fedora 8. If you haven’t yet, add yourself as a “sudoer” by visiting the tutorial this page. Also, this tutorial is for the 32-Bit version of VirtualBox, so you’ll have to customize a little more to get the 64-bit version running (as pointed out in the comments). Everything in the “code” sections should be copy/pasted/typed into the terminal. Right, let’s get to it:
1.) Get the VirtualBox 1.5.4 package from the VirtualBox website for Fedora 8 and install it.
wget http://www.virtualbox.org/download/1.5.4/VirtualBox-1.5.4_27034_fedora8-1.i586.rpm && sudo rpm -ivh VirtualBox-1.5.4_27034_fedora8-1.i586.rpm
2.) Get the kernel-devel package:
sudo yum install make automake autoconf gcc kernel-devel
3.) Run the setup file for VirtualBox:
sudo /etc/init.d/vboxdrv setup
4.) Add yourself to the “vboxusers” group (don’t forget the “-” dash!):
su -
usermod -G vboxusers -a username
exit
5.) Run, and enjoy!
VirtualBox
I would recommend disabling compiz if you have it running for VirtualBox. I’ve noticed that it [i]really[/i] slows things down (especially in fullscreen mode).
6.) To Get USB Support:
1 – create a new group called “usb”;
2 – locate file usbfs: in my case is /sys/bus/usb/drivers (I suggest to find the file with a usb device inserted;
3 – modify file /etc/fstab inserting a line containing the right path and the number corresponding the “usb” group :
none /sys/bus/usb/drivers usbfs devgid=503,devmode=664 0 0
4 – command mount -a;
5 – start VB and try…;
Source: Fedora Forums
7.) To Properly Backup the VirtualBox Machine (.vdi):
Please refer to my other page here:
How To: Properly Backup a VirtualBox Machine (.VDI)
8.) To Get Sound Working:
Highlight your virtual machine and click on the “Settings” button. Click on the “Sound” category, and then check the “Enable Sound” option. In the drop-down box, select “PulseAudio”. You should now have sound.
9.) To enlarge an already created VDI or Disk Image:
I plan on making this a little neater, but for right now, I wanted to share the information that I found via the virtualbox forums. A gentleman by the nickname of “gushy” posted these instructions:
- Create a new disk using Virtual Disk Manager (in VirtualBox goto File -> Virtual Disk Manager)
- download System Rescue CD
- set your current VM to have the new disk image as it’s second hard disk and the System Rescue CD iso file as it’s CD
- boot the vm from the CD
- at the command prompt type startx
- when X Windows starts, type gparted in the terminal that is open on screen
- in gparted select the windows partition and choose copy
- select the second hard disk
- right click on the representation of the disk and click paste
- gparted will prompt you for the size of the disk, drag the slider to the max size
- click apply
- wait …….
- when it’s done right click on the disk and choose Manage Flags, and select Boot
- exit gparted and power off the VM
- change the VM settings to only have one disk (the new bigger disk) and deselect the iso as the CD.
- boot the VM into your windows install on it’s new bigger disk!
Original post is located in this thread. And, if your experience was anything like mine, your windows virtual machine will perform a disk check when rebooting for the first time on the larger disk.
