[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] XEN 4.3 sxp options ip, netmask, gateway no more available ?


  • To: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
  • From: Giovanni Bellac <giovannib1979@xxxxxxxxx>
  • Date: Tue, 28 Jan 2014 11:59:45 +0000 (GMT)
  • Cc: "xen-users@xxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxx>
  • Delivery-date: Tue, 28 Jan 2014 12:00:56 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=ymail.com; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=wuzlXwLHxVfJvmH65//xYNRgLqQvjL1o7B14ydR4jxL2VNybJyHWRxBSrnz5kGfQQLelHB/BByf92NGrzac7O9omN4V3WBHLuQbVtYZ9RE+3kzmKl7vBkPjdM1vUqcfvdqTmnsH5ryZERgfzNX+JLaeyArAexMrAYm4wgYb+dMQ=;
  • List-id: Xen user discussion <xen-users.lists.xen.org>

Hi Ian,

> I know. I was saying that IP should work already, while you seemed to be
> suggesting it didn't work for you.

the "ip" statement in the "vif" line is working. It is setting some iptables (or ebtables) rules.

We have never configured the primary eth0 address inside the domU.

The "ip", "netmask" and "gateway" options in the domU sxp file are forwarding the options to the kernel of the domU when starting:

Output of console when starting the domU with "-c" (console):
...
[    1.667063] IP-Config: Complete:
[    1.667072]      device=eth0, addr=213.160.XX.XX, mask=255.255.255.0, gw=213.160.XX.XX,
[    1.667084]      host=vsrv70428, domain=, nis-domain=XXXXX.tld,
[    1.667094]      bootserver=127.0.255.255, rootserver=127.0.255.255, rootpath=
...


Kind regards
Giovanni



Ian Campbell <Ian.Campbell@xxxxxxxxxx> schrieb am 11:00 Montag, 27.Januar 2014:
On Sun, 2014-01-26 at 09:38 +0000, Giovanni Bellac wrote:
> I am not only talking about the "ip" statement in the "vif" line.

I know. I was saying that IP should work already, while you seemed to be
suggesting it didn't work for you.

> On XEN 3.4 and XEN 4.0 we can push via the "ip", "netmask" and
> "gateway" statements in the domU configuration the networking to the
> domU kernel/domU system, without configuration of the network inside
> the domU.

Do you have a daemon, script or tool within the guest which actually
consumes these settings (probably from xenstore) and implements this?
Because AFAIK there has never been anything on the domU driver side
which would consume these settings automatically.

What OS is the guest running -- perhaps it is a feature of that?

Another possibility is that you were using the vif-nat scripts which has
an option to setup a DHCP server in dom0 and update it as guests come
and go, but nothing about your configuration suggests that you have that
enabled you seem to be using vif-bridge.

We could add support of netmask and gateway to (lib)xl but I'd like to
understand how the whole thing fits together before doing so.

> On XEN 4.0 and earlier the domU is automatically receiving a eth0
> device with the above statements.

Your config file has:
> vif = [ 'mac=00:16:3E:00:88:11,bridge=br0,ip=83.151.XX.XX' ]
> dhcp = "off"
> ip = "83.151.XX.XX"
> netmask = "255.255.255.0"
> gateway = "83.151.XX,XX"

Which seems a bit odd -- firstly ip is given twice (as a top level and
as part of the vif config) and secondly netmask and gateway appear to be
top level settings when really their meaning is only in the context of a
given VIF device. So I'm not clear what the expected meaning should be
if you have two VIF devices.


Ian.



_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.