I thought so too. The funny thing is, I can automate it using ifconfig as a command from the interfaces file.

Here is my last post from the ubuntu forums:

So, I have finally got everything working as it should. Here is a brief HOWTO:

Create a bridge using your primary address and assign an alias to one of your secondary addresses. This is my resulting /etc/network/interfaces file:

Code:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

auto br0
iface br0 inet static
    address 174.142.61.18
    network 174.142.61.0
    netmask 255.255.255.224
    broadcast 174.142.61.31
    gateway 174.142.61.1
    bridge_ports eth0
    bridge_stp off
    bridge_maxwait 5
    post-up ifconfig br0 up promisc
    post-up ifconfig br0:0 174.142.62.118 netmask 255.255.255.248 broadcast 174.142.62.119
If you notice, this is a strange way of editing the interfaces file. If I defined the alias br0:0 as a separate entry, networking would simply not work.

Setup libvirt / KVM and build your server using vmbuilder.

See the Server Guide for instructions:
https://help.ubuntu.com/9.04/serverg...alization.html

In my case, I passed the following networking flags to vmbuilder:

Code:
--ip=174.142.62.113 --gw=174.142.62.113 --mask=255.255.255.248
I set the default gateway to the virtual machine's eth0 IP address, as it wouldn't be able to see the gateway provided by the datacenter otherwise.

Then, edit your virtual machine using virsh edit MachineName

Look for the line
Code:
 <graphics type='vnc' port='-1' autoport='yes' listen='127.0.0.1'/>
and replace 127.0.0.1 with your primary IP.

Use xvncviewer to connect to the virtual machine:
Code:
xvncviewer 174.142.61.18
Then I added the following line to the VM's /etc/network/interfaces file:

Code:
post-up route add default gw 174.142.61.1
And voila! All my troubles have gone away.

Install SSHd, edit the XML file back to 127.0.0.1 (why have an unencrypted VNC session when SSH is faster and safer?) and carry on with your work.

It may not be a pretty solution, but it's the only one that worked for me and this problem drove me up the wall for a long time.