Review your favorite Linux distribution.
Go Back > Forums > Linux Forums > Linux - Virtualization and Cloud
User Name
Linux - Virtualization and Cloud This forum is for the discussion of all topics relating to Linux Virtualization and Linux Cloud platforms. Xen, KVM, OpenVZ, VirtualBox, VMware, Linux-VServer and all other Linux Virtualization platforms are welcome. OpenStack, CloudStack, ownCloud, Cloud Foundry, Eucalyptus, Nimbus, OpenNebula and all other Linux Cloud platforms are welcome. Note that questions relating solely to non-Linux OS's should be asked in the General forum.


  Search this Thread
Old 06-29-2010, 01:16 PM   #1
LQ Newbie
Registered: Mar 2010
Location: Ireland
Distribution: Ubuntu 9.04
Posts: 6

Rep: Reputation: 0

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 VNs 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

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...

Last edited by Martin_H; 06-29-2010 at 01:18 PM.
Old 06-30-2010, 08:18 AM   #2
Senior Member
Registered: Feb 2003
Location: CT
Distribution: Debian 6-7, WIN 7-10, WIN SRV 03-12r2
Posts: 1,312

Rep: Reputation: 98
Have you tried looking at dmesg or system logs, or even xen logs to see if there is any additional information in them? Also how do these additional IPs work. If for instance you were not planning to run Virtual machines would you just setup additional NICs or are these IPs directed towards your main IP address?

What might work is setting up a dummy interface on the server and bridging to that, then routing traffic through there to your VMs. Although the more I mull it over it might be that the XEN routing script doesn't like pubic IP addresses. I would have to take a look at the script, let me see if I can make some time to do that and get back to you.


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
Xen and KDE 4.4 in CentOS shadowers Linux - Software 2 03-22-2010 07:34 PM
configure Xen on centOS sunils1973 Linux - Virtualization and Cloud 11 01-19-2010 08:00 AM
LXer: Install Fedora 10 PV DomU at Xen 3.3.1 CentOS 5.2 & Xen 3.3.0 Intrepid Server v LXer Syndicated Linux News 0 01-10-2009 11:40 AM
LXer: PV-Grub on CentOS 5.2 PV DomU at Xen 3.3 CentOS 5.2 Dom0 (all 64-bit) LXer Syndicated Linux News 0 10-05-2008 10:12 PM
help me... centos 5.1 on xen bridge yjj3019 Linux - Enterprise 1 03-24-2008 11:59 PM > Forums > Linux Forums > Linux - Virtualization and Cloud

All times are GMT -5. The time now is 03:18 AM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration