|
|
|
|
|
|
|
|
|
|
xen-users
RE: [Xen-users] Network issue when booting into Xen
>> On all but one system I have acquired for Xen testing I seem to have to have
>> network troubles with.
>>
>What does ifconfig show on a) the host, b) the client?
Xen Machine:
eth0 Link encap:Ethernet HWaddr 00:0C:29:4A:69:63
inet addr:192.168.5.30 Bcast:192.168.5.255 Mask:255.255.255.0
inet6 addr: fe80::20c:29ff:fe4a:6963/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:25 errors:0 dropped:0 overruns:0 frame:0
TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1763 (1.7 KiB) TX bytes:594 (594.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:3 errors:0 dropped:0 overruns:0 frame:0
TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:336 (336.0 b) TX bytes:336 (336.0 b)
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 MTU:1500 Metric:1
RX packets:28 errors:0 dropped:0 overruns:0 frame:0
TX packets:21 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1943 (1.8 KiB) TX bytes:1314 (1.2 KiB)
Interrupt:17 Base address:0x1400
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 NOARP MTU:1500 Metric:1
RX packets:9 errors:0 dropped:0 overruns:0 frame:0
TX packets:25 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:594 (594.0 b) TX bytes:1763 (1.7 KiB)
virbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0
inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
UP BROADCAST RUNNING 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:0
RX bytes:0 (0.0 b) TX bytes:468 (468.0 b)
xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:34 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:1881 (1.8 KiB) TX bytes:0 (0.0 b)
The other machines are bsd routers and windows boxes, all communicate fine
before I boot into xen, but not after. The problem clearly lies on the xen box.
>> After booting into a clean install of CentOS 5.1, everything works well. I
>> install xen-3.0.3-41.el5 through yum and after I reboot I cannot access
>> network resources for some reason.
>>
>Do you mean that you cannot access network resources from the host or
>from the client?
Once I boot into xen I cannot access anything to or from my xen machine. It
cant ping anything, and nothing can ping it for example.
>> Is there something I am doing wrong? This is the 3rd of 4 systems that
>> exhibit this behavior. Unfortunately the only working system cannot be used
>> for Xen J
>>
>What is your kernel?
>
>Cheers,
>
>Cliff
When booted into CentOS (with everything fine) its 2.6.18-53.1.4.el5.
When booted into Xen, its 2.6.18-53.1.4.el5xen.
It seems I can reproduce this in Fedora Core 8 as well. I get the same behavior!
Thanks,
jlc
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
|
|