Hi list,
I'm looking for some help in getting my domU network aware. Currently I
can run /etc/xen/scripts/network from dom0 to successfully create xen-br0.
After I do this, dom0 can still access any network resource that it could
before. However, when I start up a domU, it can only ping dom0; it fails to
connect to any other ip. I don't receive any sort of error message,
such as
"Destination host unreachable", ping simply fails to elicit a response.
What follows is more specific information about my setup, as well as the
output from some diagnostic commands I've run:
I'm running xen version 2.0.5 with the /etc/xen/scripts/network from
2.0.6.
Before I upgraded to the newer version of this script, my dom0 would
lose all
network connectivity whenever that script was run.
Here's a list of important ip addresses, just so the information below
makes a
bit more sense:
dom0: 192.168.1.65, domU: 192.168.1.247
gateway: 192.168.1.1, netmask: 255.255.255.0
Both dom0 and domU are using static ips.
Here's the output from running "route -n". Note that this is after
xen-br0 has
been activated.
dom0:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0
xen-br0
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0
xen-br0
domU:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0
xen-br0
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0
xen-br0
In other words they're exactly the same. Also note that I've tried
switching
domU's gateway to 192.168.1.65 (the ip address of dom0) but this doesn't
change
any behavior as far as I can tell.
Here's the results of running ifconfig on dom0 and domU, trimmed
slightly to be
less spammy:
dom0:
eth0 Link encap:Ethernet HWaddr 00:11:43:FD:70:65
inet addr:192.168.1.65 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
vif25.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
xen-br0 Link encap:Ethernet HWaddr 00:11:43:FD:70:65
inet addr:192.168.1.65 Bcast:192.168.1.255 Mask:255.255.255.255
domU:
eth0 Link encap:Ethernet HWaddr AA:00:00:5F:40:EB
inet addr:192.168.1.247 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
The last bit of information that I feel would be appropriate to
share is a few
important lines from the config file I'm using to bring up my domU:
vif = [ 'bridge=xen-br0' ]
#dhcp="dhcp"
ip = "192.168.1.247"
netmask= get_current_ipmask()
gateway= get_current_ipgw()
hostname= "vm%d" % vmid
Anyways, if anyone has an idea of what I'm doing wrong here, I would
love to
hear it. Also, if you have any ideas on what I could to do help further
diagnose what's going wrong with my setup, that would also be very helpful.
Thanks for reading this,
-Zack
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
I'm looking for some help in getting my domU network aware. Currently I
can run /etc/xen/scripts/network from dom0 to successfully create xen-br0.
After I do this, dom0 can still access any network resource that it could
before. However, when I start up a domU, it can only ping dom0; it fails to
connect to any other ip. I don't receive any sort of error message,
such as
"Destination host unreachable", ping simply fails to elicit a response.
What follows is more specific information about my setup, as well as the
output from some diagnostic commands I've run:
I'm running xen version 2.0.5 with the /etc/xen/scripts/network from
2.0.6.
Before I upgraded to the newer version of this script, my dom0 would
lose all
network connectivity whenever that script was run.
Here's a list of important ip addresses, just so the information below
makes a
bit more sense:
dom0: 192.168.1.65, domU: 192.168.1.247
gateway: 192.168.1.1, netmask: 255.255.255.0
Both dom0 and domU are using static ips.
Here's the output from running "route -n". Note that this is after
xen-br0 has
been activated.
dom0:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0
xen-br0
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0
xen-br0
domU:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0
xen-br0
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0
xen-br0
In other words they're exactly the same. Also note that I've tried
switching
domU's gateway to 192.168.1.65 (the ip address of dom0) but this doesn't
change
any behavior as far as I can tell.
Here's the results of running ifconfig on dom0 and domU, trimmed
slightly to be
less spammy:
dom0:
eth0 Link encap:Ethernet HWaddr 00:11:43:FD:70:65
inet addr:192.168.1.65 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
vif25.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
xen-br0 Link encap:Ethernet HWaddr 00:11:43:FD:70:65
inet addr:192.168.1.65 Bcast:192.168.1.255 Mask:255.255.255.255
domU:
eth0 Link encap:Ethernet HWaddr AA:00:00:5F:40:EB
inet addr:192.168.1.247 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
The last bit of information that I feel would be appropriate to
share is a few
important lines from the config file I'm using to bring up my domU:
vif = [ 'bridge=xen-br0' ]
#dhcp="dhcp"
ip = "192.168.1.247"
netmask= get_current_ipmask()
gateway= get_current_ipgw()
hostname= "vm%d" % vmid
Anyways, if anyone has an idea of what I'm doing wrong here, I would
love to
hear it. Also, if you have any ideas on what I could to do help further
diagnose what's going wrong with my setup, that would also be very helpful.
Thanks for reading this,
-Zack
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users