Hi All, I really find me without exit. They repair the following scene: Using the Xen-2.6.12-1.1454_FC4 everything functions, however at some moment a breaking in the system happens and everything summarizes the instability. After a long traffic in the net interface, happens one overload and nothing more it is transmitted. Using the Xen-2.6.14-1.21_FC5 everything seems steady very, however it does not have skill to make domU to "see" the net interface. They repair my configurations: (dom0) [root@fedora ~]# cat /proc/interrupts : ... 12: 81 Phys-irq eth0, peth1 ... I established in /o/etc/xen/xend-config.sxp: (network-script ''network-bridge netdev=eth1'') being thus: eth0 Link encap:Ethernet Endereço de HW 00:08:54:28:9E:04 inet end.: 192.168.254.1 Bcast:192.168.254.255 Masc:255.255.255.0 endereço inet6: fe80::208:54ff:fe28:9e04/64 Escopo:Link ... eth1 Link encap:Ethernet Endereço de HW 00:03:88:00:DD:8E inet end.: 192.168.0.1 Bcast:192.168.0.255 Masc:255.255.255.0 endereço inet6: fe80::203:88ff:fe00:dd8e/64 Escopo:Link ... vif0.0 Link encap:Ethernet Endereço de HW FE:FF:FF:FF:FF:FF endereço inet6: fe80::fcff:ffff:feff:ffff/64 Escopo:Link UP BROADCASTRUNNING MULTICAST MTU:1500 Métrica:1 ... xenbr0 Link encap:Ethernet Endereço de HW FE:FF:FF:FF:FF:FF endereço inet6: fe80::200:ff:fe00:0/64 Escopo:Link UP BROADCASTRUNNING MULTICAST MTU:1500 Métrica:1 ... (domU) [root@conectiva10 ~]# cat /proc/interrupts CPU0 256: 23280 Dynamic-irq timer0 257: 0 Dynamic-irq resched0 258: 0 Dynamic-irq callfunc0 259: 170 Dynamic-irq xenbus 260: 492 Dynamic-irq xencons 261: 1 Dynamic-irq blkif 262: 25782 Dynamic-irq blkif 263: 11455 Dynamic-irq blkif NMI: 0 ERR: 0 /var/log/boot.log: Dec 31 05:22:44 conectiva10 ifup: Delaying the initiation eth0. Dec 31 05:22:44 conectiva10 network: Bringing up interface eth0: failed Please, some good soul could give a light to me?! Happy New Year for all, -- Leonardo Pinto listas#openlogic dot com br ________________________________________________ Mensagem enviada usando OpenLogic WebMail 2.7.2
Leonardo Pinto
2005-Dec-31 13:59 UTC
[Fedora-xen] Re: [Xen-users] Xen-Fedora4 or 5, dead-end...
Hi big friend "Steven Anderson", "Try changing the MTU size to 1492 or 1460 on the interfaces except" Its suggestion for the problem of the FC4 functioned yes Sir. Now I am calmer and with this already I can place the server in production with bigger tranquillity. However I notice some other instability in xen of the FC4, therefore it wanted to exactly see xen of the FC5 to function, therefore if something to give wrong already would have the solution... Much thankful by the attention. Greetings, -- Leonardo Pinto listas#openlogic dot com br> Hi All, > > I really find me without exit. They repair the following scene: > > Using the Xen-2.6.12-1.1454_FC4 everything functions, however at somemoment> a breaking in the system happens and everything summarizes theinstability.> After a long traffic in the net interface, happens one overload andnothing> more it is transmitted. > > Using the Xen-2.6.14-1.21_FC5 everything seems steady very, however itdoes> not have skill to make domU to "see" the net interface. They repair my > configurations: > > (dom0) > [root@fedora ~]# cat /proc/interrupts : > .... > 12: 81 Phys-irq eth0, peth1 > .... > > I established in /o/etc/xen/xend-config.sxp: > (network-script ''network-bridge netdev=eth1'') > > being thus: > > eth0 Link encap:Ethernet Endereço de HW 00:08:54:28:9E:04 > inet end.: 192.168.254.1 Bcast:192.168.254.255 Masc:255.255.255.0 > endereço inet6: fe80::208:54ff:fe28:9e04/64 Escopo:Link > .... > eth1 Link encap:Ethernet Endereço de HW 00:03:88:00:DD:8E > inet end.: 192.168.0.1 Bcast:192.168.0.255 Masc:255.255.255.0 > endereço inet6: fe80::203:88ff:fe00:dd8e/64 Escopo:Link > .... > vif0.0 Link encap:Ethernet Endereço de HW FE:FF:FF:FF:FF:FF > endereço inet6: fe80::fcff:ffff:feff:ffff/64 Escopo:Link > UP BROADCASTRUNNING MULTICAST MTU:1500 Métrica:1 > .... > xenbr0 Link encap:Ethernet Endereço de HW FE:FF:FF:FF:FF:FF > endereço inet6: fe80::200:ff:fe00:0/64 Escopo:Link > UP BROADCASTRUNNING MULTICAST MTU:1500 Métrica:1 > .... > > (domU) > [root@conectiva10 ~]# cat /proc/interrupts > CPU0 > 256: 23280 Dynamic-irq timer0 > 257: 0 Dynamic-irq resched0 > 258: 0 Dynamic-irq callfunc0 > 259: 170 Dynamic-irq xenbus > 260: 492 Dynamic-irq xencons > 261: 1 Dynamic-irq blkif > 262: 25782 Dynamic-irq blkif > 263: 11455 Dynamic-irq blkif > NMI: 0 > ERR: 0 > > /var/log/boot.log: > Dec 31 05:22:44 conectiva10 ifup: Delaying the initiation eth0. > Dec 31 05:22:44 conectiva10 network: Bringing up interface eth0: failed > > Please, some good soul could give a light to me?! > > Happy New Year for all, > > -- > Leonardo Pinto________________________________________________ Mensagem enviada usando OpenLogic WebMail 2.7.2
Leonardo Pinto
2006-Jan-02 10:42 UTC
[Fedora-xen] Re: [Xen-users] Xen-Fedora4 or 5, dead-end...
> Did changing the MTU size help?Yes, its help was of much value. However it is as I said before: The Xen of the Fedora Core 5 is much more steady, however the virtual machine does not obtain to see the interface eth0, being without network...> Also is there a package for fedora core 5 already? I didnt even know > fedora core 5 was released? Thanks in advance!Yes! It reads this: http://fedoranews.org/wiki/Fedora_Weekly_News_Issue_27 Greetings, -- Leonardo Pinto listas#openlogic dot com br ________________________________________________ Mensagem enviada usando OpenLogic WebMail 2.7.2