Table of Contents
Advertisement
information may be read from the device naming in Domain0. All virtual devices follow
the rule vif<domain number>.<interface_number>.
For example, if you want to know the device name for the third interface (eth2) of the
VM Guest with id 5, the device in Domain0 would be vif5.2. To obtain a list of all
available interfaces, run the command ip a.
The device naming does not contain any information to which bridge this interface is
connected. However, this information is available in Domain0. To get an overview
about which interface is connected to which bridge, run the command brctl show.
The output may look like the following:
# brctl show
bridge name
br0
br1
br2
In this example, there are three configured bridges: br0, br1 and br2. Currently, br0 and
br1 each have a real Ethernet device added: eth0 and eth1, respectively. There is one
VM Guest running with the id 2 that has two Ethernet devices available. eth0 on the
VM Guest is bridged with eth1 on the VM Host Server and eth1 on the VM Guest is
connected to eth0 on the VM Host Server. At this time, the third bridge with name br2
is not connected to any VM Guest nor real Ethernet device.
6.3 Host Based Routing in Xen
Xen can be set up to use host based routing in the controlling Domain0. Unfortunately,
this is not yet well supported from YaST and requires quite an amount of manual editing
of configuration files. Thus, this is a task, that requires an advanced administrator.
The following configuration will only work when using fixed IP addresses. Using DHCP
is not realizable with this procedure, because the IP address must be known to both,
the VM Guest and the VM Host Server system.
The easiest way to create a routed guest is to change the networking from a bridged to
a routed network. As a requirement to the following procedures, a VM Guest with a
bridged network setup must be installed. For example, the VM Host Server is named
48
Virtualization with Xen
bridge id
8000.001cc0309083
8000.000476f060cc
8000.000000000000
STP enabled
interfaces
no
eth0
vif2.1
no
eth1
vif2.0
no
Advertisement
Table of Contents
