Nicolas Richeton

After 5 years, I’ll be leaving Smile at the end of June.

During that time, I’ve been working on web-based applications for numerous companies like Bureau Veritas, Macif or INRA.

Part of my job was also to initiate new integration offers for open source Business Intelligence (BI) and Enterprise Content Management (ECM) solutions with partners such as Nuxeo, Alfresco, Pentaho or SpagoBI.

In the last 2 years, I focused on managing major J2EE projects (1000+ man-days in a few months) and on pushing new tools and methods in order to improve quality and efficiency of development and management (TDD, Continuous Integration and other agile ideas).

It’s now time for me to leave Smile and manage bigger and more challenging projects.

…with a new freebox . This blog was unavailable for several days : NAT stopped working with the previous hardware and I had to wait for the new one. Sorry.

How to set up NAT rules :

If you need to connect to a running virtual machine from the outside, you have two solutions :

– Use the bridged network mode, where the VM gets its own IP address. But you cannot run more than one VM in this mode at the same time (at least with Virtualbox 2.2)

– Use the NAT network mode, and set-up NAT rules to redirect host ports to VM ones. There rules can be set using VBoxManage.

Type the following commands in a terminal (don’t forget to replace place holders : <MachineName> by the VM name and <customname> by anything you want).

VBoxManage setextradata <MachineName> "VBoxInternal/Devices/pcnet/0/LUN#0/Config/<customname>/HostPort" 2222
VBoxManage setextradata <MachineName> "VBoxInternal/Devices/pcnet/0/LUN#0/Config/<customname>/GuestPort" 22
VBoxManage setextradata <MachineName> "VBoxInternal/Devices/pcnet/0/LUN#0/Config/<customname>/Protocol" TCP

Taken from http://mydebian.blogdns.org/?p=111

How to reset interfaces names on Linux :

After moving a Linux virtual machine from one host to another, the ethernet interface name may change from eth0 to eth1 (or something else). This is because the MAC address of this interface changed : Linux keeps reference of all previous MAC to detect new network cards. To restore eth0, simply open this file :

/etc/udev/rules.d/70-persistent-net.rules

.. remove the line with eth0 as NAME and reboot. eth0 will be restored.

Does Virtualbox require CPU with virtualization capabilities ?

NO. Virtualbox can even run on VIA C3 processors (on 486 linux kernel for instance).