|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-users] cannot ping vms created on ubuntu oneiric (11.10) dom0+ natty vm
Thanks for your help. I got the vm to work.
I did the following:
in xend-config.sxp , created a bridge via the following line:
...
(network-script 'network-bridge bridge=mybr0')
...
I did not define netdev but let xend find it on its own.
This yielded a ping-able vm and the following ifconfig on dom0:
[sudo] password for walter:
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:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
mybr0 Link encap:Ethernet HWaddr 00:15:17:80:3f:c6
inet addr:163.1.87.47 Bcast:0.0.0.0 Mask:255.255.254.0
inet6 addr: fe80::215:17ff:fe80:3fc6/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:233 errors:0 dropped:0 overruns:0 frame:0
TX packets:97 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:23644 (23.6 KB) TX bytes:12687 (12.6 KB)
peth0 Link encap:Ethernet HWaddr 00:15:17:80:3f:c6
inet6 addr: fe80::215:17ff:fe80:3fc6/64 Scope:Link
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:246 errors:0 dropped:2 overruns:0 frame:0
TX packets:103 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:29330 (29.3 KB) TX bytes:13569 (13.5 KB)
Interrupt:16 Memory:fc3e0000-fc400000
vif1.0 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:86 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:32
RX bytes:0 (0.0 B) TX bytes:10996 (10.9 KB)
vif2.0 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:70 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:32
RX bytes:0 (0.0 B) TX bytes:9190 (9.1 KB)
I did notice that only natty vms created properly. oneiric and lucid failed per
below:
error on oneiric:
Aborting.
Running command 'xt-install-image --hostname=lucidxentest3
--location=/tmp/8dYxfQmutJ --dist=oneiric --install-method=debootstrap
--mirror=http://gb.archive.ubuntu.com/ubuntu/ --cache=yes
--cachedir=/var/cache/apt/archives/ 2>&1' failed with exit code 256.
Aborting
umount: /tmp/8dYxfQmutJ/proc: not found
Running command 'umount /tmp/8dYxfQmutJ/proc 2>&1' failed with exit code 256.
lucid:
/sbin/init: error while loading shared libraries: libnih.so.1: cannot open
shared object file: No such file or directory
[ 0.566371] Kernel panic - not syncing: Attempted to kill init!
________________________________________
From: Benjamin Weaver
Sent: 26 January 2012 15:19
To: Todd H. Foster; xen-users@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-users] cannot ping vms created on ubuntu oneiric (11.10)
dom0+ natty vm
with dom0 network interface set to eth0, ifconfig is:
brctl show is:
bridge name bridge id STP enabled interfaces
eth0 8000.001517803fc6 no peth0
vif1.0
(in unix shell peth0 and vif1.0 line up under interfaces)
But notice the ifconfig, which is as follows. ifconfig -a shows eth0, but not up
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:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
peth0 Link encap:Ethernet HWaddr 00:15:17:80:3f:c6
inet6 addr: fe80::215:17ff:fe80:3fc6/64 Scope:Link
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:627 errors:0 dropped:7 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:85555 (85.5 KB) TX bytes:492 (492.0 B)
Interrupt:16 Memory:fc3e0000-fc400000
vif1.0 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:32
RX bytes:0 (0.0 B) TX bytes:468 (468.0 B)
________________________________________
From: Todd H. Foster [toddf@xxxxxxxxxxxxxxxxx]
Sent: 25 January 2012 18:25
To: Benjamin Weaver; xen-users@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-users] cannot ping vms created on ubuntu oneiric (11.10)
dom0+ natty vm
On the dom0 do brctl show and past the results.
________________________________
From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx on behalf of Benjamin Weaver
Sent: Wed 1/25/2012 10:22 AM
To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] cannot ping vms created on ubuntu oneiric (11.10) dom0+
natty vm
When I create a vm using a default dom0 network interface as eth0, I cannot
ping the vm.
I notice that a virbr0 bridge is created. I had never seen this virbr0 when
running Debian dom0s. I removed virbr0 by erasing the nodes in the default.xml
file specifying this bridge.
I still could not ping my vm.
Do I need explicitly to create a bridge called eth0? I never needed to to this
when running dom0 on Debian.
In a proper setup, would I have a network interface called eth0, and a bridge
called eth0, both expicitly defined in /etc/network/interfaces?
If so, do I give the bridge the same address information as the primary network
device, eth0?
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |