Solo es un enlace: http://www.linuxformat.co.uk/forums/viewtopic.php?t=6438

Para evitar perder la información, como ya nos ha ocurrido bastante, repetimos el contenido aquí:

1. Start Virtual box and log into Ubuntu.

2. Hit the right ctrl key so you can get your mouse pointer outside the virtual machine.

3.Go to top of virtual window, click on devices then select “Install Guest Additions”
You will see a window pop up inside Ubuntu showing you that there are some new files mounted in a virtual CDROM drive. One of those files should be VBoxLinuxAdditions.run

You must run the file with some admin permissions so do that this way…

4. Click inside the Ubuntu screen again then go to Applications – Accessories then Terminal. The terminal window is where you will run the file from, but first we must navigate to the correct directory.

5. type this… cd /media/cdrom0 (then hit enter, there is a space after cd!)

6. next type… dir (You should see amongst the files displayed VBoxLinuxAdditions.run)

7. now type… sudo sh ./VBoxLinuxAdditions.run (yes, that is a full stop before the slash!)

after you hit enter and it has done its stuff, the files are now accessable from Ubuntu.

8. You now need to reboot the virtual machine or press Ctrl+Alt+backspace.

9. Log onto the Ubuntu desktop and this time go to System – Preferences then Screen Resolution. You should now have more options than the three low res options you had at the beginning of the day!

Debería dar buenos resultados de frente (probado con Ubuntu 8.04 en VirtualBox bajo Ubuntu 9.10)

Uno de los momentos mas frustrantes en mi experiencia con Linux es que una vez acabada la instalación quedo de brazos cruzados sin saber realmente qué hacer.

Para evitar caer nuevamente en esa situación, estableceré algunos proyectos a realizar y documentaré el avance en el Blog. Está demás decir que los aportes son extremadamente bienvenidos.

De acuerdo visto en un post anterior trabajo con Windows Vista como sistema operativo Host y con VirtualBox 3.x como aplicación de virtualización donde tengo una máquina con Ubuntu 9.10

La intención es levantar un WebServer en Ubuntu que pueda ser consultado desde el Browser del Host.

Como CMS instala Joomla y levantar Sugar CRM.

Las task de este proyecto son

• Aclarar las opciones de Networking de VirtualBox para establecer servicios en una máquina virtual
• Instalar una versión Liviana de Linux (Sin Interface gráfica)
• Instalar los servicios (LAMP)
• Optimizar y Securitizar
• Establecer en Producción

¿Se me olvida algo?

LV

Purtroppo per usare Nokia Pc Suite su linux non si può usare WINE. Bisogna semplicemente emularlo su una macchina virtuale come VirtualBox

Per fare questo bisogna scaricare i seguenti file:

-VirtualBox

-Una versione di Windows (è consigliata una versione di Windows XP)

-Nokia Pc Suite7.1.40.1

Dopo aver installato Windows in VirtualBox, bisogna abilitare i dispositivi USB in configurazione di VirtualBox per la guest di Windows XP, per poi installare Nokia Pc Suite. Windows sarà così in grado di rilevare il telefono cellulare Nokia in allegato

Per configurare l’ USB in VirtualBox da terminale:

sudo gedit /etc/fstab

eseguire in coda
## USB VirtualBox:
none /proc/bus/usb usbfs devgid=SZ0,devmode=664 0 0

sostituire SZ0 con il risultato del primo comando

Questo sitema potrebbe dare problemi solo con le periferiche di archiviazione
di massa.

Para instalar sistemas operativos cliente, vamos virtualizar computadores, através da VirtualBox. Comecem por instalar este software e criar a máquina virtual.
Em seguida vamos instalar os sistemas operativos através de uma imagem.

Bom Trabalho,
Prof. Rui Barreiro

Tutto cio che serve per installare Chrome OS è un sistema operativo (Linux, OS X e Windows) con installato sopra un software che permette l’ installazione e l’ emulazione di un sistema operativo in pochi minuti come VirtualBox o VMware.

La seguente guida vi aiuterà a installare ed eseguire Google Chrome OS in VirtualBox in Windows 7.

1. Scaricare l’ ultima versionedi VirtualBox per Windows 7
2. Scaricare il file .Vmdk per Chrome OS
3. Avviare VirtualBox e cliccare su nuovo e avviare una procedura guidata per l’ installazione di una VM in VirtualBox
4. Nominare “Chrome OS” e selezionare “Linux” dal menu di sistema operativo, e selezionare “Other Linux”
5. Assegnare un po’ di memoria RAM in Mb. Si consigliano 512 Mb di RAM
6. Selezionate “usa hard disk esistente” e selezionate il file .Vmdk di chrome
7. Fai clic su “Next” e completate la procedura

Ora sara possibile utilizzare il sistema operativo Chrome OS.
Per utilizzare il sistema bisogna possedere un ID di Google.

With the open sourcing of Google Chrome OS as Chromium OS project, people have started building the OS on their own and a couple of them can be found here and here. I have tried out the build that is available as a torrent mentioned in the TechCrunch article, but could not login to the OS (Network not connected and offline login failed) in neither VMWare nor VirtualBox on a Leopard. However, it logged in fine in VirtualBox on Ubuntu 9.10. The performance though was terribly bad. There is also a USB bootable image available here, which I have not tried out yet.

I have downloaded the Chromium source code and have built the OS image and ran it successfully on both VMWare and VirtualBox. The code is downloaded as a tarball for this build process. If you wish to make changes to the code and contribute, the source should be downloaded using git, in which case, the Chromium depot tools need to be installed as a prerequisite.

What is Chrome OS?

Chrome OS is a lightweight OS designed to be used by netbooks, focused only on the web. It is built on top of the Linux kernel and aims to be faster, simpler and secure.

• Built on top of Linux kernel
• Faster boot times
• Entirely web-based
• Minimal user interface
• Encrypted storage of all user data in the cloud
• Self verification of integrity of OS at every boot

What it is not?

Chrome OS is NOT a replacement for desktop operating systems. You can’t just go and replace your current OS with Chrome OS!

Build Process:

I have done the entire build on my 32 bit Ubuntu 9.10. The image works fine in VirtualBox in the same machine and also on VMWare in a Leopard. The steps in brief are:

1. Making the local repository
2. Creating the build environment
3. Including Chrome browser
4. Building the platform packages
5. Building the kernel
6. Building the final OS image
7. Converting the image to a VMWare image
8. Converting the image into a bootable USB disk (optional)

Creating the local repository took about an hour to complete. Other steps are relatively faster; the building of the platform packages and the kernel took 10 minutes each and the final OS image itself took 5 minutes. Conversion into a VMWare image requires qemu. Do a sudo apt-get install qemu-kvm before starting the conversion.

How does it work?

The OS is nothing but a browser, well almost! The OS boots and you have a nice blue screen (no, not the BSOD ) asking for the username and password. A Gmail account is required to login to the OS. The build number below the login screen is unique for each build of the Chromium OS image.

On login, the user is directly taken to the Chrome browser and everything the OS has to offer is available right there. It’s all about the web!

Clicking on the Chrome logo on the top left corner gives you a list of web apps (even Yahoo! Mail and Hotmail). Orkut is missing, but Facebook isn’t Almost all the websites that I use regularly worked fine. Flash too works great without any noticeable problems.

On the downside, command line access sucks (Do Ctrl + Alt + T to access the terminal). Typing ‘exit’ at the command line does not take you back to the browser right away. It never did for me, at least! I always ended up typing ‘exit’ about 4-5 times and suddenly the browser will appear. Also the OS becomes unresponsive in both VMWare and VirtualBox if left unused for a few minutes.

The minimalistic UI seems to be a cautious approach. There are two themes available right now – GTK+ and Classic. The look feel at the moment is not at all good. But we can expect Google (and the Open Source community!) to improve on this in the coming months.

The OS is targeted at those who use computers almost solely for accessing the Internet. It is simple and nicely done. But the performance of the Chrome OS is not satisfactory on a virtual machine. The user interface also needs to improve quite a bit.

Keeping all the data in the cloud could be a double-edged sword with potential paranoid users trying to avoid Chrome OS just for that reason. Google is betting on the fact that the market for net-books will increase in the future and that users who want to connect to the Internet fast would prefer an OS which lets them do that without much difficulties.

All you fans of OSen that Apple doesn’t provide iTunes for — GNU/Linux, *BSD, etc. — may find it annoying that there’s no real way to restore or jailbreak your shiny new iPhone or iPod Touch besides dual-booting or finding a compatible machine, huh?

Firstly, this is kinda what you have to expect after buying an Apple device   If it doesn’t fit into the Apple World™, you’d better believe that a whole host of problems will rise up.  If you’re a nice local IT guy like me though, you may wish to help liberate the souls of hapless iFollowers partially, and assist them in the jailbreaking of their devices.

As it turns out, virtualization software can help.  Alas, VMware Workstation does not work, and I haven’t tried QEMU.  The problem with VMware seems to be that iTunes doesn’t see the iPod at one critical step, and eventually gives up looking, handing you an error (usually 1611).  VirtualBox works great, though it requires a bit of manual work.  You will, sadly, need Sun’s Personal Use and Evalutation License (PUEL) version of VirtualBox, which is not Free Software — the Open Source Edition (OSE) does not support USB last I checked.  To clarify, VirtualBox PUEL is free in price, but not open-source free as in freedom.

This tutorial should work for all OSen capable of USB 2.0 and USB-enabled VirtualBox, and the jailbreaking section should work for the iPod Touch 1G/2G, and the iPhone 1G/2G/3G/3GS.  I don’t think the restore process will let you downgrade firmware, though, so you should have firmware 3.0.1 or lower.  We will be using redsn0w 0.8  to jailbreak.  This app works better in Windoze anyways; it often fails on GNU/Linux even though that OS is also supported.

BY USING THIS GUIDE YOU AGREE THAT I AM NOT TO BE HELD RESPONSIBLE FOR DAMANGES, LOSS OF FUNCTION, etc. etc etc…..  Basically, don’t be a douche.  I don’t think it’s even possible to screw up your iPod/iPhone with this; Apple actually did a good job at least in ensuring there’s pretty much always a way to restore if things go awry.  Losing your data will definitely happen if you restore, though — that’s part of what the restore does — so back up.  The jailbreaking shouldn’t cost you your data, but being safe can’t hurt.

Now that all that crap is over with, go ahead and grab VirtualBox PUEL, and make your virtual machine.  The OS I used is Windows XP Pro SP3, others may or may not work.  I wouldn’t advise a 64-bit Windows copy (the LibUsb-Win32 drivers are 32-bit, and this complicates matters), and XP is probably overall your best bet.  Make sure to enable USB in the settings, and install the OS.  You may also need to have the guest OS able to get to the Internet.

Once you have the VM up and running (I installed the guest additions, you may not need them), get the LibUsb-Win32 drivers and install them.  I’m not sure why exactly they are necessary, but they seem to in general make this whole process much smoother and more fail-proof.  Here they are, make sure to get the latest .exe file.  Reboot after installation.

Next, you need iTunes.  I’m not sure if later versions don’t work, but I would really recommend version 8.2.0, as I’ve had the most success with it.  You can find a downloadable copy here.

And last, you need the actual firmware you’re going to install.  I won’t link it, as the legality is somewhat questionable (as is everything with Apple), but you should be able to use Google to find a firmware that works with your model iPod/iPhone.  Remember, the .ipsw file you need is different for every model of iPod — one for the 2G iPhone, one for the 2G iPod, one for the 1G iPod, etc. etc.  I recommend firmware 3.0 for iPods, and 3.0.1 for iPhones (fixes an SMS exploit).  3.1 and later have nice features, but protect against the jailbreak hack we will use later.  If you’re too comfortable bending over for Steve Jobs, then you can go right for the latest firmware (3.1.2 at the time of writing)   There ARE exploits for 3.1+, blackra1n seems to be the one everyone goes to, but they have some shortcomings.  Google for more info, I won’t get into it here.  If you do use 3.1+, you may need a later version of iTunes; I’m not sure.

Once all this is acquired, and you’ve rebooted your VM again, don’t let iTunes start.  The first thing to do is open up a command prompt and cd to “C:\Program Files\LibUsb-Win32\bin”, or wherever else you installed that package.  Once there, run “install-filter.exe -i”.  There should be no output from the command.

Next, we get the iPod/iPhone ready.  Plug it in and turn it completely off — it’s okay if iTunes starts up in a fuss once it sees the connection.  We are now going to enter DFU mode, which is an even lower-level version of the Recovery mode, and works better sometimes.  Follow these instructions carefully.  There are lots of differing instructions online, but I find these steps to work the best — if they don’t, Google for DFU mode and try other methods.  If, after many retries, you can’t get in DFU mode, then you can try in Recovery mode, which may work.  I believe you get in Recovery mode by plugging in the device to the PC and holding down the Home button for a while until you see an image depicting a connection to iTunes.  Here are the DFU instructions, though:

0.) Ensure your iPod/iPhone is connected to the computer via your USB cable, and completely powered off.

1.) Press in and hold down the power switch for about three seconds, until a tiny bit after you see the silver Apple logo.  Once you see that, also start holding in the Home button, or whatever that button’s name is on the front of the device.  After a little while, the device should completely power off again.  If you see the image depicting connecting an iPod to iTunes, all is not lost, although this usually works better if you start holding the Home button earlier so that you never see that screen before the device shuts down.

2.) Now that the device is off again, keep holding the power switch and the Home button for about a full second, and then switch to holding just the Home button.  If you see the Apple logo again, you held down the power button too long, and you’ll have to start over.  If the screen stays  completely off, that’s good — keep holding down that Home button for a good 15-20 seconds, and then you can release; you should be in DFU mode.  You can verify this by running the ‘lsusb’ program in your chosen bare-metal OS, or whatever equivalent function it offers to show all USB devices plugged in, or by looking in the Devices -> USB Devices section of VirtualBox’s menu (that does not refresh automatically, you have to keep opening the menu every few seconds to refresh).  Then, you may stop holding down the Home button.

If anything goes wrong during this sequence, start all over.  If you want out of DFU mode, hold down the power and Home buttons for a bit and the device should be off (no real detectable difference), so then you can power it on again — don’t worry, you can’t get stuck in DFU mode!

Now you can give the virtual machine the iPod/iPhone — use Devices -> USB Devices to check your device.  The VM may immediately drop it again, just go back in and check it again.

iTunes will detect the device now.  Remember throughout this guide, usually when iTunes shows a slim progress bar that keeps going through, it’s looking for the device or waiting for it to be unchecked/rechecked in Devices -> USB Devices.  It may do this now, in which case you should check the iPod/iPhone in USB Devices if it isn’t checked, and if it is, uncheck and then recheck.

iTunes should now complain that the device is in recovery mode, and needs to be restored.  That’s what we want.  Hold down the left Shift key and click the Restore button in iTunes.  Now, choose the .ipsw firmware file you downloaded before.  This is why I specified downloading the firmware manually — if you just click the Restore button, iTunes will download and install the very latest firmware, which is likely not what you want if you’re going to jailbreak.  Even if you aren’t, I recommend the manual method.

Go ahead and feed it the .ipsw.  After extracting it, iTunes will do some preparation, and then show another floating progress bar most likely.  Uncheck the iPod in the VM menu, wait a second, and it should reappear in the menu (in Recovery mode this time, not DFU).  Check it again, and iTunes will proceed.  At this point, you should start to get feedback on the iPod/iPhone.

After some more work, iTunes will again stall at “Preparing iPod for restore…”, and the iPod should disconnect from the VM.  Go ahead and reconnect it.  It will be listed as not in Recovery mode anymore.  The floating bar will persist for a while — DON’T disconnect and reconnect the device from the VM, as I suggested before, in this case!  From here on, remember: when the iPod/iPhone has a slowly filling progress bar on its display, don’t tamper with the VM connection.  The progress bar should switch back to a normal bar shortly.

Sit back and relax, there won’t be any need for user interaction for a while.  Sooner or later, iTunes will again show a floating progress bar while it verifies the iPod software.  Still, don’t disconnect — there’s still a progress bar on the device, right?  Right.

If you got an error around the 1600s during this process, you likely failed to reconnect/disconnect/whateverconnect the device when iTunes wanted you to.  Try again.  If you get a low error number like 9 or 2, you likely disconnected or such when iTunes was busy working on the iPhone/iPod — don’t worry, just try again.

The iPod will disconnect for quite a while.  When it becomes ready again, you should have a newly restored iPod/iPhone!  Congratulations   If you want to truly make this device yours, and jailbreak it, keep reading.

Okay, jailbreak time.  Google around for a tool called redsn0w, and download it.  This guide was written for version 0.8 — if later versions come out, they may or may not work.

We need to again enter DFU mode.  This time, it’s mandatory.  Follow the above instructions to get in DFU mode, and connect the device to the virtual machine using its menu.  Close iTunes, and start redsn0w.  Feed it the same .ipsw firmware you have on your iPod/iPhone.  Click next, and it will patch the firmware.  You will be asked what to install for a package manager on the jailbroken device (I recommend Cydia only; Icy is faster and slicker but now unmaintained and is also more bug-prone in my experience).

You will be given instructions now by redsn0w on entering DFU mode.  Since we already did that, just click through them without doing anything to your device, waiting when it forces you to wait.  Make sure your iPod/iPhone is connected to the VM in the VM menu, and is in DFU mode!  Once redsn0w sees your device, it will skip through the rest of the instructions and begin.

Throughout the jailbreak process, redsn0w will every now and again stall on “Waiting for reboot…”.  This is your cue to reconnect the iPod/iPhone in VirtualBox’s menu if it got disconnected, or if it is still connected there, disconnect and reconnect.

Congratulations on your squeaky-clean jailbroken iPhone or iPod   Now go, and use it to show off the power of a world full of enterprising hackers!  The less Winblows is necessary, the better

Feel free to comment with questions, troubles, — or hey, even thank yous if I helped you out; they are much appreciated

Iseng-iseng aja nyoba Chrome OS.. Meski konsepnya udah dari lama banget udah keliatan jelas, tapi baru kemaren-kemaren ini rilis resminya….

I decided to take a look at Google Chrome OS
www.chromium.org has instructions for Getting and Building a Chromium-Based OS
But – having seen a link on engagdet.com to a VMware download I decided to ”takle the easy route” and  use the .vmdk file

Creating a VM to run Chrome OS

Based on various posts on the web, it looked the “best chance” of getting this work ing was to create a VM in VirtualBox.
So, I installed VirtualBox and setup a VM.

Web comments I read indicate that selecting Linux 2.6  as the version yields best results

I opted for a minimal amount of Ram.

I used the .vmdk file (chrome-os-0.4.22.8-gdgt.vmdk) from http://gdgt.com/google/chrome-os/download/
and setup VirtualBox to point to this file

Summary Info

Booting up and Logging on

The VM boots up and presents a logon screen
Based on web comments I decided to try an account called “chronos” <no password>

Result – I’m in
Time to setup a gmail account (sigh!)

Usefull Links

Google Chrome OS
Getting and Building a Chromium-Based OS
What is Google Chrome
Google prepares for Chrome OS update with Web Event

VirtualBox, Sun Microsystem’s Virtualization platform, is a fairly solid contender as far as Virtualization softwares go.  For those of you who already know about VirtualBox, you are undoubtedly aware that there is a standalone install that has a console with a GUI, allowing you to simply click in a console window and access your virtual machines.  Why would you want to run this without a monitor?  Well, primarily so that you can access the guests via remote desktop.

Assumptions:

1. you have pre-built a server of some kind
2. you installed a linux-based environment on the pre-built server (I chose Debian linux)
3. you want to run several guests on the server and access them via remote desktop

if any of the above assumptions fail to describe the situation perhaps this isn’t quite the solution you’re looking for.  I’ll continue on with my own assumption:  that this is the solution you’re looking for.

You need to install VirtualBox as the root user, so execute an “su root” at your earliest convenience.  I also like to discourage interaction as the root user unless absolutely necessary, so lets create a new user called vboxadmin:

groupadd vboxadmin && useradd -d /home/vboxadmin -m -g vboxadmin && passwd vboxadmin

You will be prompted to enter a password for vboxadmin.  Pick a good one, for example:  8iJ23Cf&7de.  You will also need to make sure that the VirtualBox repositories are added to your stock Debian repositories, accomplished like so:

cat “deb http://download.virtualbox.org/virtualbox/debian lenny non-free” >> /etc/apt/sources.list.d/virtualbox.list

If you were to try and update the repos and download VirtualBox you’d get an error telling you to go get the public key from Sun Microsystems, but you can pre-empt this by first snagging this key using the wget command:

wget -q http://download.virtualbox.org/virtualbox/debian/sun_vbox.asc -O- | apt-key add -

Now you need to update repositories (aptitude update) and update our server (aptitude upgrade) and now we rock and roll with our installation:

aptitude install linux-headers-$(uname -r) build-essential virtualbox-2.*

The above command will install the linux headers required by VirtualBox as well we installing VirtualBox 2-point-something.  The installer will tell you it is creating a new group called vboxusers, when prompted enter “Ok,” and there will no doubt be some manner of kernel error because you’re using a stock Debian linux kernel – don’t worry, though, because you’ll be prompted to compile a customer VirtualBox-friendly kernel and this you should absolutely agree to do.  Afterwards you need to add your vboxadmin to the vboxusers group:

adduser vboxadmin vboxusers

At this point you can download a virtual machine or create a new one from the command line interface.  You can read about my VirtualBox CLI tips over here.  To start a guest in headless mode execute:

VBoxHeadless -startvm “My Awesome Virtual Machine”

Now just connect via RDP (Remote Desktop Protocol) or VNC (Virtual Network Connection) and you’re good to go.

Nuova versione per VirtualBox (versione PUEL) che giunge alla release 3.0.10. Con questo software potete virtualizzare sistemi operativi a vostro piacimento (Licenza: VirtualBox PUEL , OS: Karmic Koala 32/64bits Formato: Deb).

Fonte/Download: VirtualBox

I decided to take a look at Ubuntu.

Download location

I downloaded Ubuntu from http://www.ubuntu.com/getubuntu/download
The download is in the form of a .iso (ubuntu-9.10-desktop-i386.iso)

System Requirements

Requires at least 256Mb Ram (the standard installation CD requires 384MB of RAM).
Install requires at least 3 GB of disk space.
(Source: Ubuntu System Requirements)

Version

I used Ubuntu Desktop 9.10 (32 bit)

Creating the VM

I decided to install Ubuntu in Virtual Box.
The install is very straightforward and some handy tips are also available on the Ubuntu site

Enter a Name for the VM
Set the Operating System to “Linux“
Set Version to “Ubuntu“

Installation

Attach the CD to the downloaded .ISO file (ubuntu-9.10-desktop-i386.iso) and Turn on the VM.
Select “Install Ubuntu” (doh !)

Choose the Language

Select TimeZone

Followed by Keyboard Layout

Set partition details (go with the defaults)

Set username (this is also used to form the suggested computername)

Ready to Rock ‘n’ Roll…

It’s happening … my first Ubuntu install is underway!

It’s installed!

Booting up and logging on

After detaching the .ISO, it’s time to “give it a go” !

Booting up…

Login prompt

It’s booted – no errors (well no visible errors anyway !)
Job done.

Useful Links

What is Ubuntu
System Requirements
Ubuntu Download
Installing Guest Additions for Ubuntu in VirtualBox

Salve a tutti… Questa è la mia prima guida che vi spiega come installare una virtual box in Sabayon Linux, tramite equo.
La guida è stata testata da me su una sabayon 5.0 con GNOME e un notebook Asus PRO5AVseries, anche conosciuto come N50VN.

Se è la prima volta che installate un programma da equo dovete prima di tutto rendere operativo equo sincronizzando le repository. Per farlo seguite la guida a questo indirizzo

Una volta reso operativo equo apriamo un terminale diamo il comando

su

per accedere al superutente e inseriamo la password

nel terminale ora digitiamo il seguente comando

equo install virtualbox-bin

per installare virtualbox e installiamo i moduli del kernel necessari dando

equo install virtualbox-modules

una volta installati i moduli necessari dobbiamo caricarli per fare questo basta digitare nel terminale il seguente comando

/etc/init.d/vboxdrv setup

se per caso questo comando dovesse darvi errore c’è sempre questo:

modprobe vboxdrv

e ora la nostra macchina virtuale è funzionante… anche se c’è ancora qualche altre
passo da fare a meno che non vogliate caricare ad ogni avvio i moduli vi basta
dare un altro comandino da terminale
Sempre come SU date il seguente comando

nano /etc/conf.d/modules

potete sostituire a nano (editor di testi da terminale) gedit (editor di testi grafico,se siete su gnome) o kwrite (editor di testi grafico, se siete su KDE)

e inserite a fine file queste tre righe [quella col cancelletto potete evitarla ma migliora la legibilità del file ]:

# Modulo kernel di VirtualBox:
modules_2_6=”vboxdrv”
module_vboxdrv_args=”"

ora è davvero tutto…

A breve stilerò una guida anche su come usare la VirtualBox anche se mi sembra facile ed intuitivo

Alla prossima puntata

After installing VirtualBox here are some quick screenshots showing what “Settings” are exposed for Virtual Machine properties.
These are all fairly typical, but I’ve posted here as a handy reference. 

General 

System 

    

Hard Disks

CD/DVD-Rom

Floppy

Audio

Network

Serial Ports  

USB

Shared Folders           

I decided to take a look at VirtualBox.
I’ve included screenshots below showing what the installation process looks like.

Download Location

VirtualBox can be downloaded from http://www.virtualbox.org/wiki/Downloads

I used VirtualBox 3.0.12 for Windows hosts x86/amd64

Installation

Installation is very straightforward and consists of clicking on the downloaded executeable (VirtualBox-3.0.12-54655-Win.exe) and following a small number of prompts as shown:
(I experienced about 5 prompts to confirm installation of unsigned drivers. I’ve only inclued one example of each below to avoid duplication)