This text is removed from another one blog, but that I like much and work and am to install the virtual machine VirtualBox and soon to install Windows for those mythical programs that Ubuntu not yet resists.

VirtualBox is another software of virtualización of code free, available right now for users of Windows and Linux.

Although at the moment already they coexist in my equipment Parallels and VMware Workstation (although it is certain that first of them I use as soon as it), I have not been able to resist to also install VirtualBox, to see how one behaves…

Under Linux, VirtualBox has ready packages to Debian and Ubuntu, but the happy users of Arch Linux also we have two packages to our distribution in AUR, one containing the own program and another one the modules of kernel. After satisfying some previous dependencies, the compilation and later installation of VirtualBox are to sew and to sing, although a little even releases in a powerful machine.

Once installed, you key virtualbox and… Arghh! Illegal instruction and an infamous Segmentation Fault! Then yes that we began well:

Good; the message speaks of which perhaps the servant is not in march. Perhaps the cause is that one. But, where it is explained how to throw to walk the servant? In the manual of user (English, pdf) not it encounter at first sight…

Instead of to continue looking for in the pdf I go away to the AUR Web, where script of promising aspect exists. We will call vbox.sh and its content will be:

#! /bin/sh
CD /opt/virtualbox
export LD_LIBRARY_PATH=$PWD: $LD_LIBRARY_PATH
xpcom_running= `ps aux|grep VBoxSVC|grep - v grep `
if test - z “$xpcom_running”; they then
./VBoxSVC &
fi
./VirtualBox

We give to execution permissions (chmod him x vbox.sh) and now yes, when keying ./vbox.sh, finally it takes the program:

When beating on New the habitual Wizard, or assistant of creation of a virtual machine is taken:

Nothing else to begin the habitual options appear to us:

The machines for TWO, Windows (3,1 to Vista), OS/2 Warp (3, 4 and 4,5), Linux are predefined (2,2, 2,4 and 2,6), several BSD (NetBSD, FreeBSD and OpenBSD), Netware, Solaris and L4.
As it seems that the first delivery has waked up enough interest, I retake the right subject now I left where it: at the time of coming to create some virtual machine.

In my opinion it would not have been nothing bad to prove VirtualBox with Solaris (quite heavy to virtualize in VMware) or with the exotic L4, but the readers command, and in view of the spontaneous interest provoked by Windows for Fundamentals Legacy PCs (that somebody defined this way as a “castrated XP”) we are going to give a touch him to so peculiar device…

Published (19-Ene, 23:20): I finish adding at the end of the article how to increase to the size and resolution of the screen of the virtual Windows.

Following the instructions of the first delivery, we will begin to create a virtual machine of type “Windows XP”. We will accept the propose ram:

We will now create the corresponding image of virtual disk:

Unlike VMware, VirtualBox does not recommend to a priori give to this disc a fixed size, so I incline by one whose size is growing as it is needed:

We give an obvious name to our virtual disk and accepted the size by defect:

In agreement. We accept the proposal:

We select as starting disc the one that we finished creating:

If you are not in agreement with the summary, is your last opportunity to change something:

Bond; your new virtual machine (or rather, its virtual receiver) has these characteristics:

Some things will not convince to you, but it is easy to change them:

For example, to have from where to install is necessary to mount the CD unit or an image ISO:

He would not either be bad to activate the sound:

In the network configuration two things draw attention to me: the absence of an option bridged and the possibility of generating a random MAC for the network adapter:

When everything is to our taste we come to take the machine, to begin the installation of the system. But it is not going to be so easy:

It seems that driver or necessary module still it is not loaded in kernel. And lsmod is enough to verify it. Bond; then we load the module (like root):

# modprobe vboxdrv

But this is not sufficient either:

Now one is a problem of permissions. We solved it thus:

chown usuary: wheel /dev/vboxdrv

where usuary you have to change it by your own name of user.

But, it is necessary to use these two commandos whenever it is wanted to use VirtualBox. That would be latazo, so better to create script (source AUR) that is executed in the starting. In the case of Arch, it is enough to place script in /etc/rc.d and to add his name to the list of units of /etc/rc.conf:

#! /bin/bash

. /etc/rc.conf
. /etc/rc.d/functions

″ marries “$1 in
start)
stat_busy “Starting VirtualBox”
# VirtualBox modulates
/sbin/modprobe vboxdrv || exit 1
# change group of /dev/vboxdrv
chown: wheel /dev/vboxdrv || exit 1
if [$? - gt 0]; they then
stat_fail
else
add_daemon virtualbox
stat_done
fi
; ;
stop)
stat_busy “Stopping VirtualBox”
killall - q VBoxSVC || exit 1
rmmod vboxdrv || exit 1
if [$? - gt 0]; they then
stat_fail
else
stat_done
rm_daemon virtualbox
fi
; ;
restart)
$0 stop
sleep 1
$0 start
; ;
*)
I throw “usage: $0 {start|stop|restart}”
esac

Now yes we managed to start, although there is to pay attention to this message:

One lets know us that the autocaptura of the keyboard is active, that is to say, that the virtual window takes the center, so that what you key will directly go to the virtual machine, and so mouse and keyboard stop working on the machine that does of host (Linux, in our case). One is a functionality similar to the one of Vmware and Parallels, but that behaves here of a a little different way, so that until you clarify yourself you can desesperarte enough. And it is that in VirtualBox it is not worth to press Ctrl and Alt simultaneously to jump to host, but they are others the keys and they have to be beaten consecutively, and not simultaneously. What I did immediately was to change the predefined keys to two that they are common in VMware (mentioned before):

It activates the square of autocaptura and it locates the cursor on the box Host Key. The key or keys beats now that you want to use to change of virtual machine host.

Now yes that everything goes as it soothes:

Eye, that nobody is called here to deceit, that “a castrated” XP is not either a given XP. Sight if not how it asks number of license (and also it will require activation):

The personalisation of the installation yes that is peculiar… We had not been in which Explorer was inseparable of Windows?

Good; no longer there is reverse gear:

Preparation for several resumptions? Luckyly it is only the virtual machine the one that is reinitiated…

The process has been long, but every time we are more close:

This it is the aspect of a Fundamentals Windows virtualized in VirtualBox:

And here the final image goes, with Fundamentals Windows executing itself by means of VirtualBox in a Linux machine:

With Windows or working you can use the menu of VirtualBox (Devices - > Install Guest Additions) to install the tools that will allow to increase the resolution you of screen 1024×768 or the more if your card and monitor allows it to you:

This is everything. Logically all the screens of Windows are property of Microsoft and they are only with didactic aims. Whoever to virtualize Fundamentals Windows will have to acquire a license to Microsoft, but also a process can be followed similar to virtualize any Windows del that is legal proprietor.

Who does not want - or she cannot pay licenses to Microsoft, that virtualizes Linux, so friendly Solaris or BSD and.

Link | Installation of VirtualBox

For Thank you reading this post. You dog now Leave To Comment (0) or Leave To Trackback.