This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-users] XEN\Centos\Networking

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] XEN\Centos\Networking
From: MHarran <martinharran@xxxxxxxxx>
Date: Tue, 29 Jun 2010 13:47:08 -0700 (PDT)
Delivery-date: Tue, 29 Jun 2010 13:49:56 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
I’ve got a Hetzner EQ4 server running Centos in which I want to run a Linux VM (distro doesn’t matter but probably Ubuntu) and a Windows 2008 VM (possibly 2 of latter).

I have installed XEN and can get a test Centos VM and a W2008 VM running okay in bridged mode but I’m seriously struggling to get routed networking up and running which I need so that I can access the machines directly using the extra IP’s that Hetzner have supplied.

The error I’m getting is "Error: Device 0 (vif) could not be connected. /etc/xen/scripts/vif-route failed; error detected." and my gut feeling is that this has something to do with the way the IPs are set up; although a seasoned Windows user, I’m still little more than a newbie to Linux so I may be making some fundamental errors here

First question is do the additional IP’s need to be set up before I do anything with the VMs? I’ve been following the tutorials here and here and they don’t mention that but I’m guessing that the server needs to know about the IPs before they can be used. I have tried setting them up using ifcfg-eth0:1, ifcfg-eth0:2, ifcfg-eth0:3 but they do not respond to ping.

When I change to routing, however, using the instructions here, I cannot get the VMs to start, they return "Error: Device 0 (vif) could not be connected. /etc/xen/scripts/vif-route failed; error detected."

I’m also confused about the settings to use for these IP’s. Hetzner have a funny way of issuing the additional IP’s, you have to request them individually which means you do not necessarily end up with contiguous addresses, here is what they gave me:

Main IP:
SCOPE="peer 78.xx.x.33"

(Note: for some reason, I have written in my original notes that the Netmask should be but is what is showing after a reinstall. Could that be an error?)

The first additional IP is 78.xx.xx.45; I did not receive any instructions for that but I presume the netmask, and broadcast are the same.

My other two additional IPs are 178.nn.nn.157 and 178.nn.nn.157, i.e a completely different group.

The other details supplied for those two IPs are Gateway: 178.nn.nn.145 Mask:

As far as I can make out, in Xen networking, all the additional IPs should point to the main IP as their gateway so should I just ignore the gateway settings that Hetzner provided by email and set all the gateways to the main IP 78.xx.xx.55? Also, how to I treat the different netmaks in the two pairs of IP?

Final question - sorry for so many :) - is what is the significance of "SCOPE" in the main IP rather than GATEWAY?

*Those instructions are actually for Debian but I've made the appropriate changes for Centos; I'm not that bothered about what distribution Dom0 runs on so I tried it with Debian, same problem with Error: Device 0 (vif) could not be connected...

View this message in context: XEN\Centos\Networking
Sent from the Xen - User mailing list archive at Nabble.com.
Xen-users mailing list
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] XEN\Centos\Networking, MHarran <=