Re: [Xen-users] vif-route problems

[Nick Craig-Wood <nick@xxxxxxxxxxxxxx>]

On Tue, Nov 28, 2006 at 12:54:44PM +0000, Hugo Mills wrote:
>    I've been trying for the last couple of days to get a routed
> network setup functioning, preliminary to modifying the scripts
> (simply) to do ip masquerading. I'm running on a Core 2 Duo laptop,
> with a single (variable) IP address.
> 
>    One problem that I've encountered is that most of the documentation
> I've found (including the networking page on the Xensource wiki) seems
> to be referring to netfront configurations with a vifD.I in the dom0,
> rather than ioemu ones, where (as far as I can tell) you get a tapN
> device. This is somewhat confusing, to say the least. (If I can get
> this working, I will gladly update the wiki with better details). I
> fear that the vif/tap difference may also be a cause of the following
> error:
> 
> hrm@willow:scripts$ sudo xm create rhel4-base
> Using config file "/etc/xen/rhel4-base".
> Error: Device 0 (vif) could not be connected. Backend device not found.

It is a bug AFAICT

  http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=584

>    Configuration for xend is using network-route and vif-route for the
> relevant scripts. The domU configuration is shown below (mostly a copy
> of the hvm example configuration).
> 
>    Can anyone point me in the right direction?

You can use the /etc/xen/qemu-ifup script to configure the networking
which works OK for one hvm domain.

For multiple hvm domains it gets really messy!

Note that the qemu-ifup script is passed the interface name as $1 and
the bridge name as $2, so you can set the bridge name different in
each of your HVM domains, eg

  vif = [ 'type=ioemu, mac=00:16:3e:17:5e:65, bridge=rhel4' ]

Then use $2 in qemu-ifup to configure different stuff according to the
bridge name.

You could make the bridge name be the IP address too I suppose.

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

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