Showing posts with label VirtualBox. Show all posts
Showing posts with label VirtualBox. Show all posts

Wednesday, January 13, 2010

VirtualBox-3.1.2 upgrade on Aspire One Linux

I haven't posted for a long time... but just to show some activity, I'm posting regarding the latest VirtualBox upgrade.

On the VirtualBox download site, they haven't posted an RPM for Fedora 8... so I resorted to the 'All distributions' release http://download.virtualbox.org/virtualbox/3.1.2/VirtualBox-3.1.2-56127-Linux_x86.run

The process was smooth and simple
- Remove the old RPM installation

sudo rpm -e VirtualBox-3.0.6_52128_fedora8-1

- Set the execute bit on the downloaded install file

chmod a+x VirtualBox-3.1.2-56127-Linux_x86.run

- Run it

[user@aspireone Downloads]$ sudo ./VirtualBox-3.1.2-56127-Linux_x86.run
Verifying archive integrity... All good.
Uncompressing VirtualBox for Linux installation.........
VirtualBox Version 3.1.2 r56127 (2009-12-17T13:37:07Z) installer
Installing VirtualBox to /opt/VirtualBox
Python found: python, installing bindings...
error: invalid Python installation: unable to open /usr/lib/python2.5/config/Makefile (No such file or directory)
Building the VirtualBox vboxdrv kernel module
Building the VirtualBox netflt kernel module
Building the VirtualBox netadp kernel module

VirtualBox has been installed successfully.

You will find useful information about using VirtualBox in the user manual
  /opt/VirtualBox/UserManual.pdf
and in the user FAQ
  http://www.virtualbox.org/wiki/User_FAQ

We hope that you enjoy using VirtualBox.

I don't thing the python error message is anything to be concerned about.

Wednesday, September 9, 2009

VirtualBox Bridged Mode on Linpus

I wanted to run TurnKey Tomcat in VirtualBox, and use bridged network mode to make the tomcat available on my LAN. Easy I thought...

The basics of setting preparing the host Linux environment I found this post.
However, the Linpus kernel doesn't have
- TUN/TAP support built in the kernel... so I turned to this post.
- Bridge support... so it was time to build my own kernel, for which I turned to this post.

I then discovered that Linpus has a custom build of Grub, that doesn't show a menu on boot... which was something of a problem, as my kernel, built with 'CONFIG_BRIGE=y" did not work properly - the mouse and keyboard didn't seem to work.

I hope to replace the Linpus grub with a more standard variety... but this I'll save for another post. I want to make sure I have a safe procedure for restoring the original version first.

On a side issue, I tried using
- Damn Small Linux (DSL) for recovery - but it hung whilst booting.
- RIPLinux - at first this didn't seem to work either... until I found that by first running it's hardware detection tool, and then running grub, it worked nicely. Strange incompatibility with the Aspire One I suspect.

For my kernel second build, I tried with bridge as a module, CONFIG_BRIGE=y. This worked nicely.

I then hit this error - VERR_SUPDRV_COMPONENT_NOT_FOUND which is easily resolved by modprobing, see this post.

Then, to my horror, I found that Linux bridging doesn't work on WIFI - see this post.

If anyone tries this procedure, and gets it to work, perhaps against a regular Ethernet port, I'd like to hear your experiences.

Monday, July 6, 2009

Snapshots in VirtualBox

Firstly, I want to give credit to this thread - as it steered me onto the right path.

The way snapshots and virtual media (hard disks) work in VirtualBox is clearly not entirely obvious to the newbie, myself included. If you don't understand it, it looks plain buggy... however once you've understood it... there is reason in the madness - and more importantly it works!

In VirtualBox there are 3 types (or modes) of virtual hard disk images, Normal, Immutable and Write-through. These are fairly well explained in the manual - I highly recommend reading at least that section of the manual, as it also helps make sense of snapshots.

I'll discuss only the 'Normal' image type here. This is the default type set, when you create a new machine and hard disk. You start up your guest OS, and everything works nicely. You try powering off the machine, saving the state, everything works as you'd expect.

Then you see the 'Take snapshot' option, and try it. Now, you need to understand how they work - whether you know it or not :)

The snapshot stores the machine state, just like the 'current state' you've used up until now. It also contains a differential image of the hard disk. Ie. from now on, the (normal) hard disk image file (eg. xp.vdi) that was previously being updated, is no longer updated. Instead, when your guest OS writes to disk, it writes into the differential image.

If you create another snapshot, a new differential image is created, so now, the current content of the hard disk is stored across 3 files, the original, and the two snapshots. This of course gives the possibility to go back to an exact, earlier copy of the entire system (including hard disk).

So what's the problem?

Snapshot files, including the differential hard disk image aren't particularly portable. So whilst you can easily move your original hard disk to different machines, moving the updates in your differential files is difficult. Unless you run on basically the same host machine, with the same vbox version you can restore the changes from your differential images.

Or can you?

The solution is to discard your snapshots!

Sounds dangerous? Well, not quite as dangerous as it seems. When you discard a snapshot, it merges the differential image into it's parent image.

So, if you have snapshots like this -
- Snapshot 1
- Snapshot 2
- Current State
And discard 'Snapshot 2', the differential image changes will be merged back into Snapshot 1, leaving -
- Snapshot 1
- Current State
Then discarding 'Snapshot 1', will merge back into your original hard disk image 'xp.vdi'... leaving no snapshots, but also a portable hard disk image.

I recommend experimenting by taking a snapshot, then create some files in the guest OS, and then create another snapshot. Then discard away, and see that the files survive.

Friday, January 2, 2009

VirtualBox on Acer Aspire One

I'd started to install VMware on my Aspire One (Linux), when I came across
macles* post on VirtualBox. In a couple of hours I had it up and running, with Windows XP as the guest OS, nice.

When reading about VirtualBox, the thing that excited me most was the support for USB devices - ie. it can 'pipe' them through to the guest OS, such that devices not supported in the host OS can be used in the guest OS... nice.

So I gave it a try - first was my HP Laserjet M1005 MFP, printer and scanner - no problems. Install the drivers (in XP), plug in the device, tell VirtualBox to enable it, XP detects it and out comes the test page. Similarly for the Scanner. Mounting ISO images of CDs (eg. install CDs) works beautifully too, something XP itself isn't so good at.

Then the Sony Ericsson P1i PC suite. This is a buggy thing to start with... I can no longer get it to install on my Vista work PC, how about XP under VirtualBox? Basically, no problems! I may have to run VirtualBox on my Vista laptop too :)

It's really nice when things work so well.