Re: [Xen-users] "routed" networking under Xen 3.2.1 / HVM?

["Ray Barnes" <tical.net@xxxxxxxxx>]

Thanks Nick.

To the general population:  I'm bumping into a problem which looks like a bug.  Perhaps it's for lack of knowledge (and _documentation_ of HVM).  If I do the following:

brctl addbr bmette31
ifconfig bmette31 1.2.3.249 netmask 255.255.255.248
xm create bmette31

Where "bmette31" has a config file that has a vif entry like: vif = [ 'type=ioemu, mac=00:16:3e:00:00:07, bridge=bmette31']  this works *just fine*.  I'm able to route through the host to the HVM domain which is set to 1.2.3.250.  However, whenever I use a script which is loosely based on a vif-bridge script that I got from /etc/xen/scripts running Xen 3.2.1 compiled from source, it does not work.  Specifically, I can reach 1.2.3.249 from the outside but not 1.2.3.250.  As far as I can tell, the problem is that whenever 'brctl addbr bmette31' is invoked from outside the script, networking between the host and the HVM guest works fine, but when invoked from within the script, networking between the host and the HVM guest does not work.  Note that while the domain is running (and using the script below), 'brctl show' indicates that I have a bridge called bmette31 and that 'ifconfig bmette31' shows the right IP.  So just to recap - if I comment out 'brctl addbr bmette31' from the script below and run it manually then start the HVM guest, networking is fine, but if I run that from within the script it does not work.  Any ideas before I treat this as a bug and post to xen-devel?

-Ray


#!/bin/bash
#
#vif bridge script for HVMs
#invoke like this:
#
#vif = [ 'type=ioemu, mac=00:16:3e:00:00:07, bridge=bmette31, script=vif-bmette31' ]

/usr/sbin/brctl addbr bmette31

dir=$(dirname "$0")
. "$dir/vif-common.sh"

bridge=${bridge:-}
bridge=$(xenstore_read_default "$XENBUS_PATH/bridge" "$bridge")


RET=0
ip link show $bridge 1>/dev/null 2>&1 || RET=1
if [ "$RET" -eq 1 ]
then
#       do_without_error brctl addbr "$bridge"
    fatal "Could not find bridge device $bridge"
fi

case "$command" in
    online)
        setup_bridge_port "$vif"
        add_to_bridge "$bridge" "$vif"
        sleep 2
        ifconfig "$bridge" 38.106.106.249 netmask 255.255.255.248
        ;;

    offline)
        do_without_error ifconfig "$bridge" down
        do_without_error brctl delbr "$bridge"
        ;;
esac


log debug "Successful vif-bridge $command for $vif, bridge $bridge."
if [ "$command" == "online" ]
then
  success
fi

On Tue, May 13, 2008 at 7:18 AM, Nick Craig-Wood <nick@xxxxxxxxxxxxxx> wrote:

Ray Barnes <tical.net@gmail.com> wrote:
> Understanding that HVM does not support routed networking in the
> sense that we're accustomed to with paravirtualized guests, I'm
> hoping there is some similar use-case scenario I've missed.

I made this work with Xen 3.1 and hvm guests.

Probably the easiest way is to hard code the routing you want in
/etc/xen/qemu-ifup.

The interface is passed in as argument $1 and the bridge name as
argument $2.  Since you aren't bridging you can use the bridge name to
decide how to configure the interface with a shell case statement.

Eg in your /etc/xen/MYDOMAIN file

vif = [ 'type=ioemu, ip=10.1.2.3, bridge=MYDOMAIN' ]

Then in /etc/xen/qemu-ifup something like (untested)

------------------------------------------------------------
#!/bin/sh

if=$1
bridge=$2

case "$bridge" in
   MYDOMAIN)
       ifconfig $if 1.2.3.2 netmask 255.255.255.255 up
       route add -host 1.2.3.3 dev $if
       ;;
   MYDOMAIN2)
       #...
       ;;
esac

echo 1 >/proc/sys/net/ipv4/conf/${if}/proxy_arp
echo 1 >/proc/sys/net/ipv4/conf/${if}/rp_filter
------------------------------------------------------------

You need to make the usual changes for routing rather than bridging in
xen also.

I actually did this in a different very much more complicated way
which allowed the original routing scripts to work.  This way should
work and be a lot simpler though!


--
Nick Craig-Wood <nick@xxxxxxxxxxxxxx> -- http://www.craig-wood.com/nick

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users