Xen users - Jun 2009 - vif-route script not getting domU-IP (vif-IP)

Hi,

I''m using the XEN 3.4.1-pre4 Hypervisor in Routet Mode and I''m
facing
some problems when I start the DomU.
In detail, it means that the DomU IP-Adress will not be implemented in  
the Kernel routing table after starting the domU via "xm create /<path 
+configfle>"
After making a "netstat -nr" it will not show the IPadress bound to  
the VIF<..>-interface.

A small echo in the vif-route script shows that the variable $IP is  
empty. So no value will be available, therefore the script can''t work.

if [ "${ip}" ] ; then
     # If we''ve been given a list of IP addresses, then add routes  
from dom0 to
     # the guest using those addresses.
     for addr in ${ip} ; do
       ${cmdprefix} ip route ${ipcmd} ${addr} dev ${vif} src ${main_ip}
     done
fi

Has sombody faced the same problems ?

Cheers,
Maik

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

I''m using individual vif-route scripts for each domU for customization
reasons.  But in your case, the most likely culprit is that you have no
"ip=" in the vif statement in the domU config file.

-Ray



On Tue, Jun 23, 2009 at 9:51 AM, Maik Brauer
<mailinglist@mbs-technet.com>wrote:
> Hi,
>
> I''m using the XEN 3.4.1-pre4 Hypervisor in Routet Mode and
I''m facing some
> problems when I start the DomU.
> In detail, it means that the DomU IP-Adress will not be implemented in the
> Kernel routing table after starting the domU via "xm create
> /<path+configfle>"
> After making a "netstat -nr" it will not show the IPadress bound
to the
> VIF<..>-interface.
>
> A small echo in the vif-route script shows that the variable $IP is empty.
> So no value will be available, therefore the script can''t work.
>
> if [ "${ip}" ] ; then
>    # If we''ve been given a list of IP addresses, then add routes
from dom0
> to
>    # the guest using those addresses.
>    for addr in ${ip} ; do
>      ${cmdprefix} ip route ${ipcmd} ${addr} dev ${vif} src ${main_ip}
>    done
> fi
>
> Has sombody faced the same problems ?
>
> Cheers,
> Maik
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>

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

Hi Ray,

yes I do (see below):
vif    = [ ''ip=188.40.xxx.xxx'' ]

But it has not been executed in the "vif-route" script.
What else might could be the problem here.


In case of customization, how can I make it variable, so that the IP  
will be forwarded to a unique script.
I do not want to make for each domU a new "vif-route-<domU-name"
script.

Can somebody help me?


Cheers,
Maik



On Jun 24, 2009, at 6:46 AM, Ray Barnes wrote:
> I''m using individual vif-route scripts for each domU for  
> customization reasons.  But in your case, the most likely culprit is  
> that you have no "ip=" in the vif statement in the domU config
file.
>
> -Ray
>
>
>
> On Tue, Jun 23, 2009 at 9:51 AM, Maik Brauer
<mailinglist@mbs-technet.com
> > wrote:
> Hi,
>
> I''m using the XEN 3.4.1-pre4 Hypervisor in Routet Mode and
I''m
> facing some problems when I start the DomU.
> In detail, it means that the DomU IP-Adress will not be implemented  
> in the Kernel routing table after starting the domU via "xm create / 
> <path+configfle>"
> After making a "netstat -nr" it will not show the IPadress bound
to
> the VIF<..>-interface.
>
> A small echo in the vif-route script shows that the variable $IP is  
> empty. So no value will be available, therefore the script can''t
work.
>
> if [ "${ip}" ] ; then
>    # If we''ve been given a list of IP addresses, then add routes  
> from dom0 to
>    # the guest using those addresses.
>    for addr in ${ip} ; do
>      ${cmdprefix} ip route ${ipcmd} ${addr} dev ${vif} src ${main_ip}
>    done
> fi
>
> Has sombody faced the same problems ?
>
> Cheers,
> Maik
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users


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

Hi Ray,

Ups, thanks for that hint.
I''ve checked the whole file.
I found that somewhere in the bottom a line with vif ='''' was
declared.
Sorry for this confusion, after removing this line it is working.

Cheers,
Maik

On Jun 24, 2009, at 10:17 AM, Maik Brauer wrote:
> Hi Ray,
>
> yes I do (see below):
> vif    = [ ''ip=188.40.xxx.xxx'' ]
>
> But it has not been executed in the "vif-route" script.
> What else might could be the problem here.
>
>
> In case of customization, how can I make it variable, so that the IP  
> will be forwarded to a unique script.
> I do not want to make for each domU a new
"vif-route-<domU-name"
> script.
>
> Can somebody help me?
>
>
> Cheers,
> Maik
>
>
>
> On Jun 24, 2009, at 6:46 AM, Ray Barnes wrote:
>
>> I''m using individual vif-route scripts for each domU for  
>> customization reasons.  But in your case, the most likely culprit  
>> is that you have no "ip=" in the vif statement in the domU
config
>> file.
>>
>> -Ray
>>
>>
>>
>> On Tue, Jun 23, 2009 at 9:51 AM, Maik Brauer
<mailinglist@mbs-technet.com
>> > wrote:
>> Hi,
>>
>> I''m using the XEN 3.4.1-pre4 Hypervisor in Routet Mode and
I''m
>> facing some problems when I start the DomU.
>> In detail, it means that the DomU IP-Adress will not be implemented  
>> in the Kernel routing table after starting the domU via "xm create
/
>> <path+configfle>"
>> After making a "netstat -nr" it will not show the IPadress
bound to
>> the VIF<..>-interface.
>>
>> A small echo in the vif-route script shows that the variable $IP is  
>> empty. So no value will be available, therefore the script
can''t
>> work.
>>
>> if [ "${ip}" ] ; then
>>    # If we''ve been given a list of IP addresses, then add
routes
>> from dom0 to
>>    # the guest using those addresses.
>>    for addr in ${ip} ; do
>>      ${cmdprefix} ip route ${ipcmd} ${addr} dev ${vif} src ${main_ip}
>>    done
>> fi
>>
>> Has sombody faced the same problems ?
>>
>> Cheers,
>> Maik
>>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@lists.xensource.com
>> http://lists.xensource.com/xen-users
>>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@lists.xensource.com
>> http://lists.xensource.com/xen-users
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users


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