Differences between revisions 4 and 5
Revision 4 as of 2008-10-02 03:23:31
Size: 7621
Editor: ?JosephRawson
Comment: trying to finish adding all the snippets of code that's required
Revision 5 as of 2008-10-02 06:11:22
Size: 7638
Editor: FranklinPiat
Comment: formating
Deletions are marked like this. Additions are marked like this.
Line 16: Line 16:
The method outlined below will help get user mode linux machines and virtualbox The method outlined below will help get DebPkg:user-mode-linux machines and VirtualBox
Line 55: Line 55:




virtualbox-ose (you may need to build the modules with module-assistant)

You will need to add your user to these groups: uml-net and vboxusers
 * DebPkg:bridge-utils
 * DebPkg:uml-utilities
 * DebPkg:
 * DebPkg:virtualbox-ose (you may need to build the modules with [:ModuleAssistant:module-assistant], from virtualbox-ose-source)

You will need to add your user to these groups: {{{uml-net}}} and {{{vboxusers}}}
Line 85: Line 81:
Edit /etc/default/uml-utilites and set UML_SWITCH_OPTIONS="-tap tap0" .   Edit /etc/default/uml-utilites and set {{{UML_SWITCH_OPTIONS="-tap tap0"}}}.
Line 88: Line 84:

{{{sudo /etc/init.d/uml-utilities stop}}}
sudo /etc/init.d/uml-utilities stop
Line 92: Line 89:

{{{sudo ifup tap0}}}
sudo ifup tap0
Line 96: Line 94:

{{{sudo /etc/init.d/uml-utilities start}}}
sudo /etc/init.d/uml-utilities start
Line 237: Line 236:
=== See also ===
Line 239: Line 239:
##See also:
## If this page belongs to an existing Category, add it below.
## CategorySomething | CategoryAnother
 * VirtualBox

[:DebianWiki/EditorGuide#translation:Translation(s)]: none

(!) [:/Discussion:Discussion]

There is not much info here yet. This page is devoted to describing how to configure debian to be able to use a virtual network on your system that lets different virtualization applications to work together and be able to talk to each other on the virtual network.


Virtual Networking

Getting User Mode Linux networked with VirtualBox


The method outlined below will help get user-mode-linux machines and VirtualBox machines working on the same "virtual network". In this routine, we will be creating a primary tap interface and bridging it. This is not the same as bridging the local ethernet interface, and the virtual machines will only be accessible from the host system.

In this guide, I will be using some abbreviations. The term "uml" will be used to refer to a user-mode-linux virtual machine. The term "vbox" will be used to refer to a virtualbox machine. The term "VM" (or "vm") will be used for an unspecified virtual machine (either uml or vbox). Also there will be some assumptions being made that you may want to change. It will be assumed that your local network interface will be called eth0. It will also be assumed that the virtual network that you'll be creating is on, with the host being and the main uml machine on .

This guide will also make use of a persistent uml machine to run the dhcp server and the nameserver for the virtual network. This is not really necessary, as you can choose to run those programs on the host system. It is useful, however, if you wish to keep the configuration on the host system at a minimum, and also to minimize the requirement for root access on the host system.

These instructions can be modified to use vde2. Doing this will allow you to also use qemu and kvm machines on the same network. Using vde2 would probably be the optimal setup for this guide, but since I'm not using it at the moment, these instructions will have to suffice.

One final note. These instructions will assume that you are either familiar with the programs and/or procedures detailed here, or are willing to read up on them. These instructions aren't meant to be howto's for using rootstrap, setting up a bridged network, configuring dhcp3-server, etc. I will try to provide links to places where you can learn how to do these things, but this guide isn't meant to be a replacement for those instructions.

Prepare Host System

Install Requirements

Required packages on host system:

You will need to add your user to these groups: uml-net and vboxusers

You will need to log out entirely and possibly kill every process being run by that user in order to finalize the addition to the groups (slay is a good command for this). The rest of the guide will assume that this has already been done.

Prepare TAP Interface

Edit /etc/network/interfaces and add these lines:

        auto tap0
        iface tap0 inet static
                tunctl_user uml-net

The ip address can be changed according to your needs, but the rest of the guide will assume that it's set to .

Edit /etc/default/uml-utilites and set UML_SWITCH_OPTIONS="-tap tap0".

Now you can stop uml-utilities:

sudo /etc/init.d/uml-utilities stop

Bring up the new tap interface:

sudo ifup tap0

Now start uml-utilities again:

sudo /etc/init.d/uml-utilities start

This should start the uml_switch on tap0.

At this point, you will probably want to enable masquerading to get the tap network access to the local network or internet. You will only have to do this once here, since later, we will write scripts to help manage this.

sudo su
 iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
echo '1' > /proc/sys/net/ipv4/ip_forward

Don't bother reading below here

Prepare Rootstrap

my rootstrap.conf:

## I have about 100M or so free using a 1G 
## filesystem.  I'm not running much more than
## the standard, plus dhcp3-server, bind9 and 
## some extra stuff like xemacs, rsync, slay, etc.
modules=network mkfs mount debian uml umount
## we will set the memory back down to 32M once
## the rootstrap is over, but having it high is
## helpful for installing the system
## you don't really need this one, but it can be 
## informative, and will help when you run into problems

## the rest of the guide will assume that this
## hostname is being used, but you can change
## this, just be aware that this hostname will 
## be used in the guide.

## most of this was just uncommented from
## the example rootstrap.conf file and the
## ip's were modified.
## get the nameserver from /etc/resolv.conf
## and replace this option

exclude=pcmcia-cs setserial



Prepare TAP Bridge

add this to network interfaces no auto here, bring this interface up when you login to the desktop

iface br0 inet static
        bridge_ports tap0
        bridge_stp off
        bridge_fd 2.5
        post-up /etc/network/br0-interface up
        post-down /etc/network/br0-interface down

save this in /etc/network/br0-interface replace username with the your user name

set -e

case "$1" in 
    iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
    echo '1' > /proc/sys/net/ipv4/ip_forward
    su -l -c "env TERM=console linux ubd0=$ubd0 eth0=daemon con=pts mem=32m umid=nethead" username &
    su -l -c "uml_mconsole nethead halt" username
    iptables -t nat -D POSTROUTING -o eth0 -j MASQUERADE
    echo '0' > /proc/sys/net/ipv4/ip_forward

Make VirtualBox Machine

set -e
case "$2" in
        # ensure that the TAP device is down
        sudo VBoxTunctl -d $IF >/dev/null 2>&1
        # Create a TAP network device
        sudo VBoxTunctl -u $LOGNAME -t $IF >/dev/null 2>&1
        # Bring it up (without IP address)
        sudo ifconfig $IF up
        # Add it to the bridge
        sudo brctl addif $BRIDGE $IF
        # Tell VirtualBox the name of the interface
        echo $IF
        sudo VBoxTunctl -d $IF >/dev/null 2>&1

See also