[Xen-bugs] [Bug 471] Passing IP Parameters in 3.0

[bugzilla-daemon@xxxxxxxxxxxxxxxxxxx]

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=471





------- Additional Comments From malexand@xxxxxxxxxxxxx  2006-01-05 12:27 
-------
Subject: AW:  Passing IP Parameters in 3.0

Ok /boot/config-2.6.12.6-xen3_7.1_rhel4.1 -> CONFIG_IP_PNP=y$

Now on domU boot that's better:
Built 1 zonelists
Kernel command line:  
ip=10.0.0.2:1.2.3.4:10.0.0.1:255.255.192.0:vm010000000002:eth0:off 
root=/dev/sda1 ro
Initializing CPU#0

But then neither the interface in the dom0 was not configured with the values. 
The stanza eth0:off looks strange. If the format of the ip line should be 
domUIP:netmask:default gw:netmask then the second entry might be wrong. 

[root@localhost ~]# ifconfig
eth0      Link encap:Ethernet  HWaddr AA:00:00:11:00:11
          inet6 addr: fe80::a800:ff:fe11:11/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:277 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:22395 (21.8 KiB)  TX bytes:378 (378.0 b)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:8 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:560 (560.0 b)  TX bytes:560 (560.0 b)

[root@localhost ~]

-----Ursprüngliche Nachricht-----
Von: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx 
[mailto:bugzilla-daemon@xxxxxxxxxxxxxxxxxxx] 
Gesendet: Donnerstag, 05. Jänner 2006 13:01
An: malexand@xxxxxxxxxxxxx
Betreff: [Bug 471] Passing IP Parameters in 3.0

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=471





------- Additional Comments From james@xxxxxxxxxxxxx  2006-01-05 12:00 -------
If you're using a -xen kernel (rather than a -xenU kernel) then you'll probably
find that IP PNP is not configured in (grep for CONFIG_IP_PNP) in the
corresponding config file in the boot directory. This is needed for the ip=
kernel command line to be used. Workarounds include making the ifcfg script
parse /proc/cmdline (e.g. http://software.cfht.hawaii.edu/linuxpc/ifcfg-eth0) or
using a -xenU kernel.

The issue now becomes: do we enable CONFIG_IP_PNP and it's friends for -xen?

BTW - what is "XenOS 4.2"?



-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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