|
|
|
|
|
|
|
|
|
|
xen-users
[Xen-users] Xen 3.0.2.2 - Losing network after starting xend. [SOLVED]
Hi list.
Found this reference on the net:
http://mark.foster.cc/wiki/index.php/Xen_3.0.x_on_Debian_Sarge
"If you are upgrading on top of a Xen 2.0.x
installation, move or rename the /etc/xen/scripts
folder, lest your networking not work after the
upgrade."
and upgrading was exactly what I had done and this did the trick for me!
Rebooted in a default 2.4 Debian kernel, did a "rm -rf /etc/xen" and
then went to /root/xen-xen-3.0.2-2/ and did a "sh ./install.sh" and
rebooted in Xen3. "/etc/init.d/xend start" now starts up correctly.
Cheers
-- Jan
_______________________________________________________
Hi list.
I am trying to upgrade a well-running server from Xen 2.0.6 to 3.0.2.2.
After building and installing 3.0.2.2 from source the machine boots OK
in 3.0.2.2 and dom0 comes up and I ssh into it. But after starting xend
I loose the network. Going to the physical console I did an 'ifconfig'
and had the response below.
What's wrong here ? Is Xen trying to change my network card to run IPV6,
or has it just renamed eth1 (which is the physical network connection)
to veth1 and use IPV6 internally for the bridging ? How can I get
network connectivity back ?
Cheers
-- Jan Holst Jensen, Novo Nordisk A/S, Denmark
eth1 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:67054 errors:0 dropped:0 overruns:1 frame:0
TX packets:190 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:44173742 (42.1 MiB) TX bytes:17478 (17.0 KiB)
Interrupt:18 Base address:0xcc00
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)
veth0 Link encap:Ethernet HWaddr 00:01:03:2B:38:76
inet addr:10.9.18.135 Bcast:10.9.19.255 Mask:255.255.255.255
inet6 addr: fe80::201:3ff:fe2b:3876/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:65811 errors:0 dropped:0 overruns:0 frame:0
TX packets:228 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:43368120 (41.3 MiB) TX bytes:16454 (16.0 KiB)
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:227 errors:0 dropped:0 overruns:0 frame:0
TX packets:65811 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:16364 (15.9 KiB) TX bytes:43368120 (41.3 MiB)
xen-br0 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:61912 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:41053352 (39.1 MiB) TX bytes:468 (468.0 b)
Before running xend, the output of ifconfig is
eth1 Link encap:Ethernet HWaddr 00:01:03:2B:38:76
inet addr:10.9.18.135 Bcast:10.9.19.255 Mask:255.255.254.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:6376 errors:0 dropped:0 overruns:1 frame:0
TX packets:126 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4316185 (4.1 MiB) TX bytes:15152 (14.7 KiB)
Interrupt:52 Base address:0xdc80
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
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)
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
<Prev in Thread] |
Current Thread |
[Next in Thread> |
- [Xen-users] Xen 3.0.2.2 - Losing network after starting xend. [SOLVED],
JHJE (Jan Holst Jensen) <=
|
|
|
|
|