For this example we can assume a few things:

1. You have already set up a headless VirtualBox server
2. You have already created a Virtual Machine instance. For this sample, we will call the Virtual Machine “MyVM”.

Believe it or not, setting up bridged networking to allow your VM to access your network is pretty simple and completed by issuing the following VBoxManage command in a terminal window.

Command: VBoxManage modifyvm “MyVM” –nic1 bridged –nictype1 82540OEM –bridgeadapter eth0

Break it down

To understand a bit more about what’s happening here, let’s break down the command string from the beginning.

VBoxManage - This is the command line utility used to access, control, configure and manage your VirtualBox Virtual Machines.

modifyvm - This command allows you to make changes to the properties of a Virtual Machine, including the amount of memory assigned, nic interfaces, Virtual device boot sequence, number of CPUs, etc. It can be compared to the Settings dialog of the VirtualBox Graphical user Interface. The command line version, however, offers additional advanced options not found in the GUI.

Note: the VM must be registered within VirtualBox, but must not be running

“MyVM” – This is simply the name of the VM you want to modify.

–nic1 bridged - The –nic1 parameter is used to set the type of networking your VM should use for each of the it’s virtual network cards. You can have more than one network card in use for a VM so the paramater is written as –nicX where X is the network card being targeted. Here, “–nic1″ is the first network interface, –nic2 would be the second and so on. This portion of the command string is setting the type of networking on the first interface to “bridged”.

–nictype1 82540OEM – The –nictype1 parameter allows you to specify which networking hardware VirtualBox should emulate for the VM’s virtual network cards. Here we set the networking hardware to emulate an Intel PRO/1000 MT Desktop card or 82540EM.

–nictypeX follows the same sequence numbering and –nicX for multiple interfaces where –nictype1 is the first virtual card, –nictype2 is the second and so on.

Note:  The following is a list of the available nic hardware types and the associated ID recognized in VirtualBox.

• AMD PCNet PCI II = Am79C970A
• AMD PCNet FAST III = Am79C973 (the default)
• Intel PRO/1000 MT Desktop = 82540EM
• Intel PRO/1000 T Server = 82543GC
• Intel PRO/1000 MT Server = 82545EM
• Paravirtualized network adapter = virtio-net

–bridgeadapter1 eth0 – Finally we have the –bridgeadapter paramater. This is the only part of the command string that references a part of the VirtualBox host and tells your VM which physical host adapter to pass it’s traffic through.

Again, this uses the same sequence numbering as nicX and nictypeX for multiple interfaces. Here, we are setting the bridgeadapter for our first virtual network card to use the eth0  interface on the host. Note that is eth zero, as in the number and not the letter O.

And that’s it. Restart your VM and you should now have a working bridged network interface for you VM with full network and internet access.

It’s no secret that I am a fan of Ubuntu Linux. BUT.. one of the annoying things about using Ubuntu is trying to set up a network printer on a desktop or workstation. Regarding nearly all administrative tasks under most Linux systems that would require root permissions, Ubuntu has done a nice job of making it possible to operate a system as a “normal” user without elevated privileges, and then easily gain the elevated (root) privileges temporarily assigned to complete some specific administrative task. Ubuntu detects when a user is trying to do something requiring the elevated (root) privileges and pops up a small window asking for the current user’s password to gain the required permission. All the magic happens behind the scene and the user never has to issue a text command. It wasn’t long ago that users would have had to open a command terminal and issue all the instructions by hand. Well.. we’ve come a long way.. With the exception of installing a network printer. For some reason, when installing a printer in Ubuntu, the user is not prompted with the normal su password pop-up that presents itself for all other administrative tasks. Instead, the CUPS system prompts the user for the root password – and under Ubuntu, there is no root password by default meaning that root can not complete any direct action requiring a password. In fact, root can not log directly into the system at all. Fortunately, the solution is fairly easy.

The Solution

Do not try to install a printer from System > Administration > Printing menu. It won’t work. Sure, it will allow you to go through the wizard and give you the false impression that you’re actually accomplishing something – until you reach the point where a driver needs to be installed and you’re prompted for the root password. Instead, go to the Applications > Accessories menu and select Terminal.

Once the terminal window opens, issue the following command

sudo system-config-printer

The next line in the terminal window will ask for your password. Type in your user password and hit enter. If all is correct, the printer setup and configuration window will open with elevated privileges enabled and you can finish installing and setting up your new printer from comfort of an easy to use GUI.

Sample Setup

Lets take a few minutes and walk through the process. In this example, I will be setting up a Dell 1700 Laser Printer in my Home Office. Before you get started, you will need to know a few things about the printer first.

IP address: What IP address did you assign to your network printer?

RAW Port: Typically, the default RAW Port is 9100. If you assigned something different you’ll need to remember what it is.

Open a Terminal Window: System > Administration > Terminal

Terminal Window

Issue the command “sudo system-config-printer” (no quotes)

sudo command

Provide your password when prompted.

sudo password

The Printer Configuration window should have opened

Printer Configuration

Press the “New” button to add a new printer.

The “New Printer” window will open after a brief search displaying the “select Device” panel

Under the “Devices” list, expand the “Network Printer” selection by clicking the small black arrow.

Next, Select “AppSocket/HP JetDirect”

At the right, new options will be displayed (Host and Port Number)

In the host field, type the IP address of the network printer you’re installing.

In the Port Number field, type the RAW port number for the network printer. If you did not change this directly in the Printer’s Settings, or you are not sure, then leave the default value 9100.

Select Device

Press the “Forward” button: The next panel is the “Choose Driver” panel

Choose the “Select Printer from Database” option

Highlight the “Generic” option under the “Makes” list

Chose Driver Panel 1

Press the “Forward” button: The next panel is the “Choose Driver” panel #2

On this Panel, under the “Model” list, select “PCL 6/PCL XL Driver”

Under the “Drivers” Select the “PCL 6/PCL XL Driver – CUPS + Gutenprint v5.2.3 [en] (recommended)”

Choose Driver Panel 2

Press the “Forward” button: The next panel is “Describe the Printer”

Printer Name: in this field, type a name for your printer as it will appear in you installed printers list. I’ll call mine “Dell1700″ Note that spaces are not permitted here.

Description (optional): In this field, type a short description of your printer to help identfy it in you installed printers list. I described mine as “Dell Printer Home Office”. You can leave this blank if you want.

Location (optional): In this field, put a location descriptor that will help to identify the location of the printer in the installed printers list. For this field, I used “Home Office”. You can leave this blank if you want.

Describe the Printer

When you finish, click the “Apply” button. You’ll be prompted and asked if you want to print a test page, which might be a good idea at this point to make sure you got everything set up correctly.

Test Printing

If everything went well, you will now see a new printer added to your installed printers list under “Printer Configuration“.

New Printer Installed

Note: This walkthrough was completed using a Dell 1700 Laserprinter and does work with these instructions. This printer does not have linux drivers available. If your printer has supported/avalible drivers provided by your manufacturer, your setup process may be different. This information is provided as a general guide.

I hope you find this information helpful. Leave a comment to let me know what you think. Is there a better / easier way to do this? Did I miss anything? Leave a comment.

Change of Plans – As I was writing the above, Something occurred to me.

Some points of interest

• Google uses a custom version of Ubuntu for internal operations.
• Google has generated a lot of Buzz recently about entering the office application market opposite Microsoft.
• Canonical/Ubuntu has made impressive progress bringing an alternative desktop operating system to market and is regarded by some as an acceptable replacement to Microsoft.
• Following the Quote from Mark Shuttleworth himself, it does sound like Canonical and Google have been at least talking about ways to “finalize Jaunty plans”.

  "We will be gathering forces in Mountain View on 8th - 12th December to
  survey the upstream landscape and finalize Jaunty plans, enjoying the
  excellent hospitality of Google and Silicon Valley's abundance of talent
  and innovation." - Mark Shuttleworth

Warning – Pure Speculation Follows:

Is it possible that Canonical’s intention to cater to web apps means teaming up or forming some sort of partnership with Google to use or push Google’s suite of web applications (Google Apps) while providing a competitive operating system to rival Microsoft?

References:
http://bits.blogs.nytimes.com
https://lists.ubuntu.com/archives/ubuntu-devel-announce/2008-September/000481.html