http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=471
Summary: Passing IP Parameters in 3.0
Product: Xen
Version: 3.0.0
Platform: x86
OS/Version: Linux-2.6
Status: NEW
Severity: critical
Priority: P1
Component: Hypervisor
AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
ReportedBy: malexand@xxxxxxxxxxxxx
After having tried XenOS 4.2, Fedora Core 4, Fedora Core 5T1 as hosts and same
sample plus fc3 and suse as guests it appears that passing the IP parameters
from the domU configs idoes not want to work (dom0 and domU dumps attached). The
only parm getting passed is the mac address, which shows up on the guest nicely.
Any attempt at getting a VM's IP configured through the below wouldn't do:
ip = "10.0.0.2"
netmask = "255.255.192.0"
gateway = "10.0.0.1"
hostname ="vm010000000002"
vif = ['mac=aa:00:00:11:00:11, bridge=xenbr0']
disk = ['file:/mnt/root/xen/centos-full.img,sda1,w']
root = "/dev/sda1 ro"
#console = "10002"
DHCP works. Manually configuring the IP parms in the guest after boot (plus
putting the bridge device into the same subnet) leads to being able to ping both
hosts in any direction, but ssh to the guest along with apparently domain
sockets within the guest failing.
Also, changing cat xend-config.sxp to nat through bridivif-nat and network-nat
seems not work at all - with no xenbr0 being created in this case.
So how do you get 3.0 to pass the ip config to the guests? How do you enable
nat-work around eventual issues there? - A full dump of the xen, ip config on
host and guest ist attached. Any help would be appreciated - thanks in advance.
[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:221 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:23015 (22.4 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
[root@abt-wi-025 network-scripts]# cat ifcfg-eth0
DEVICE=eth0
BOOTPROTO=static
ONBOOT=YES
TYPE=Ethernet
#BOOTPROTO=static
#ONBOOT=yes
#TYPE=Ethernet
#BROADCAST=10.0.0.63
#IPADDR=10.0.0.2
#NETMASK=255.255.192.0
#NETWORK=10.0.0.0
[root@ixi xen]# ifconfig
eth0 Link encap:Ethernet HWaddr 00:02:1E:F4:58:96
inet addr:<valid IP> Bcast:137.208.224.255 Mask:255.255.255.0
inet6 addr: fe80::202:1eff:fef4:5896/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:559551 errors:0 dropped:0 overruns:0 frame:0
TX packets:239898 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:410638449 (391.6 MiB) TX bytes:86102575 (82.1 MiB)
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:124693 errors:0 dropped:0 overruns:0 frame:0
TX packets:124693 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:6244240 (5.9 MiB) TX bytes:6244240 (5.9 MiB)
peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:559979 errors:0 dropped:0 overruns:100 frame:0
TX packets:240079 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:410688242 (391.6 MiB) TX bytes:86129808 (82.1 MiB)
Interrupt:22 Base address:0xdc00
vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:239906 errors:0 dropped:0 overruns:0 frame:0
TX packets:559558 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:86103871 (82.1 MiB) TX bytes:410638919 (391.6 MiB)
vif3.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:104 errors:0 dropped:0 overruns:0 frame:0
TX packets:778 errors:0 dropped:17792 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:9181 (8.9 KiB) TX bytes:66132 ( 64.5 KiB)
xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:228033 errors:0 dropped:0 overruns:0 frame:0
TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:15008970 (14.3 MiB) TX bytes:168 (168.0 b)
[root@ixi xen]#
[root@ixi xen]# brctl show
bridge name bridge id STP enabled interfaces
xenbr0 8000.feffffffffff no peth0
vif0.0
vif3.0
[root@ixi xen]#
[root@ixi xen]# cat centos.full
kernel = "/mnt/root/xen/boot/vmlinuz-2.6.12.6-xen"
ramdisk = "/mnt/root/xen/boot/initrd-2.6.12.6-xen.img"
vcpus = 1
memory = 128
name = "centos-full"
nics = 1
#dhcp ="off"
#dhcp ='DHCP'
ip = "10.0.0.2"
netmask = "255.255.192.0 "
gateway = "10.0.0.1"
hostname ="vm010000000002"
vif = ['mac=aa:00:00:11:00:11, bridge=xenbr0']
disk = ['file:/mnt/root/xen/centos-full.img,sda1,w']
root = "/dev/sda1 ro"
#console = "10002"
[root@ixi xen]# cat xend-config.sxp
# -*- sh -*-
#
# Xend configuration file.
#
# This example configuration is appropriate for an installation that trusts
# only localhost connections, and is otherwise fully functional, with a
# bridged network configuration.
# Commented out entries show the default for that entry, unless otherwise
# specified.
#(logfile /var/log/xend.log)
#(loglevel DEBUG)
#(xend-http-server no)
(xend-http-server yes)
#(xend-unix-server yes)
#(xend-relocation-server no)
(xend-relocation-server yes)
#(xend-unix-path /var/lib/xend/xend-socket)
# Port xend should use for the HTTP interface, if xend-http-server is set.
#(xend-port 8000)
# Port xend should use for the relocation interface, if xend-relocation-server
# is set.
#(xend-relocation-port 8002)
# Address xend should listen on for HTTP connections, if xend-http-server is
# set.
# Specifying 'localhost' prevents remote connections.
# Specifying the empty string '' (the default) allows all connections.
#(xend-address '')
(xend-address localhost)
# Address xend should listen on for relocation-socket connections, if
# xend-relocation-server is set.
# Meaning and default as for xend-address above.
#(xend-relocation-address '')
(xend-relocation-address localhost)
# The limit (in kilobytes) on the size of the console buffer
#(console-limit 1024)
##
# To bridge network traffic, like this:
#
# dom0: fake eth0 -> vif0.0 -+
# |
# bridge -> real eth0 -> the network
# |
# domU: fake eth0 -> vifN.0 -+
#
# use
#
# (network-script network-bridge)
#
# Your eth0 is used as the outgoing interface, by default. To use a different
# one (e.g. eth1) use
#
# (network-script 'network-bridge netdev=eth1')
#
# The bridge is named xenbr0, by default. To rename the bridge, use
#
# (network-script 'network-bridge bridge=<name>')
#
# It is possible to use the network-bridge script in more complicated
# scenarios, such as having two outgoing interfaces, with two bridges, and
# two fake interfaces per guest domain. To do things like this, write
# yourself a wrapper script, and call network-bridge from it, as appropriate.
#
(network-script network-bridge)
# The script used to control virtual interfaces. This can be overridden on a
# per-vif basis when creating a domain or a configuring a new vif. The
# vif-bridge script is designed for use with the network-bridge script, or
# similar configurations.
#
# If you have overridden the bridge name using
# (network-script 'network-bridge bridge=<name>') then you may wish to do the
# same here. The bridge name can also be set when creating a domain or
# configuring a new vif, but a value specified here would act as a default.
#
# If you are using only one bridge, the vif-bridge script will discover that,
# so there is no need to specify it explicitly.
#
(vif-script vif-bridge)
## Use the following if network traffic is routed, as an alternative to the
# settings for bridged networking given above.
#(network-script network-route)
#(vif-script vif-route)
## Use the following if network traffic is routed with NAT, as an alternative
# to the settings for bridged networking given above.
#(network-script network-nat)
#(vif-script vif-nat)
# Dom0 will balloon out when needed to free memory for domU.
# dom0-min-mem is the lowest memory level (in MB) dom0 will get down to.
# If dom0-min-mem=0, dom0 will never balloon out.
(dom0-min-mem 196)
# In SMP system, dom0 will use dom0-cpus # of CPUS
# If dom0-cpus = 0, dom0 will take all cpus available
(dom0-cpus 0)
# Whether to enable core-dumps when domains crash.
#(enable-dump no)
// sde
Reply Forward
Anand Kumria
<wildfire@xxxxxxxxxxx>I have the same issue - the issue for me is that I can not
directly ssh betwe...
Jan 4 (1 day ago)
Anand Kumria
<wildfire@xxxxxxxxxxx>Oh, just a quick follow-up; domU <-> domU connections are
working fine. The i...
Jan 4 (1 day ago)
Mail Delivery Subsystem
<mailer-daemon@xxxxxxxxx>This is an automatically generated Delivery Status
Notification Delivery to t...
Jan 4 (1 day ago)
Anand Kumria
<wildfire@xxxxxxxxxxx>to xen-devel
More options 4:50 am (7 hours ago)
On Wed, 04 Jan 2006 14:46:56 +1100, Anand Kumria wrote:
> On Wed, 04 Jan 2006 13:44:09 +1100, Anand Kumria wrote:
>
>> On Tue, 03 Jan 2006 20:14:34 +0100, sde 9000 wrote:
>>
>>> After having tried XenOS 4.2, Fedora Core 4, Fedora Core 5T1 as hosts and
>>> same sample plus fc3 and suse as guests it appears that passing the IP
>>> parameters from the domU configs idoes not want to work (dom0 and domU dumps
>>> attached). The only parm getting passed is the mac address, which shows up
>>> on the guest nicely.
>>>
>>
>> I have the same issue - the issue for me is that I can not directly ssh
>> between dom0 and a domU instance.
>
> Oh, just a quick follow-up; domU <-> domU connections are working fine.
> The issue is entirely dom0 <-> domU; and all domU's at that too.
>
And one other datapoint, this works perfectly fine under Xen-2.0
Cheers,
--
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
|
Home