|
|
|
|
|
|
|
|
|
|
xen-users
[Xen-users] Problems with domU networking
Moi!
I upgraded Xen-2.0.1 to Xen-2.0.5 (testing) and everything compiled cleanly.
I'm still able to boot dom0 and start domUs but networking doesn't work
anymore.
xen-br0 appears in dom0, but vif-interfaces now only when ifconfig -a is
used. Interface appears in domU and all seems to be fine, except no any
data doesn't move in any direction. I can't even ping between dom0 and domU.
So it creates an interface, but somehow it doesn't work properly.
What might be wrong? No firewalls enabled atm.
Here are some information.
dolphin:~# ifconfig |grep HWa
eth0 Link encap:Ethernet HWaddr 00:50:DA:B0:D7:77
eth1 Link encap:Ethernet HWaddr 00:0D:88:B5:8E:F4
xen-br0 Link encap:Ethernet HWaddr 00:50:DA:B0:D7:77
dom0 interfaces works fine. Network is up and running. And eth0 is bind to
xen-br0.
dolphin:~# xm create tamagotchi
Using config file "/etc/xen/tamagotchi".
Started domain tamagotchi, console on port 9603
domU creation does fine. Virtual starts up and i can use it from console.
dolphin:~# tail /var/log/xend.log
[2005-04-23 10:22:25 xend] DEBUG (XendDomainInfo:1130) Creating vbd dom=3
uname=file:/swapfiles/tamagotchi.swp
[2005-04-23 10:22:25 xend] DEBUG (blkif:146) Connecting blkif
<BlkifBackendInterface 3 0>
[2005-04-23 10:22:25 xend] DEBUG (XendDomainInfo:1130) Creating vbd dom=3
uname=file:/images2/tamagotchi-home.img
[2005-04-23 10:22:25 xend] DEBUG (blkif:146) Connecting blkif
<BlkifBackendInterface 3 0>
[2005-04-23 10:22:25 xend] DEBUG (XendDomainInfo:1107) Creating vif dom=3
vif=0 mac=FE:FD:0A:00:01:01
[2005-04-23 10:22:25 xend] INFO (XendRoot:91) EVENT> xend.console.create
[11, 3, 9603]
[2005-04-23 10:22:25 xend] WARNING (XendDomainInfo:1038) Unknown config
field restart
[2005-04-23 10:22:25 xend] INFO (XendRoot:91) EVENT> xend.domain.create
['tamagotchi', '3']
[2005-04-23 10:22:25 xend] INFO (XendRoot:91) EVENT> xend.domain.unpause
['tamagotchi', '3']
[2005-04-23 10:22:25 xend] DEBUG (blkif:192) Connecting blkif to event
channel <BlkifBackendInterface 3 0> ports=16:3
Creation logs fine. I noticed a warning, deprecated option maybe?
dolphin:~# xm list
Name Id Mem(MB) CPU State Time(s) Console
Domain-0 0 187 0 r---- 128.1
tamagotchi 3 192 1 -b--- 0.5 9603
domU also shows up in the list.
tamagotchi ~ # ifconfig eth0|grep HWa
eth0 Link encap:Ethernet HWaddr FE:FD:0A:00:01:01
domU network interface is present and MAC address is correct.
All other values are also fine, i just supressed them off.
I'm able to ping the domU address but not dom0.
dom0 cannot ping domU either.
dolphin:~# xm vif-list tamagotchi
(vif (idx 0) (vif 0) (mac fe:fd:0a:00:01:01) (bridge xen-br0) (evtchn 17
4) (index 0))
vif-list looks fine, that was exactly the same it was with previous
xen-version.
dolphin:~# ifconfig vif3.0
vif3.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
BROADCAST MULTICAST MTU:1500 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)
And vif-interface exists, it shows only up with ifconfig vif?.0 or
ifconfig -a,
but it is not displayed if i only type ifconfig. (i displayed earlier)
So here is an issue, i might need some help. Please. :-)
--
Sami Louko <proton@xxxxxxxxx>
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Xen-users] Problems with domU networking,
Sami Louko <=
|
|
|
|
|