xen December 2005

xen@lists.fedoraproject.org

9 participants
19 discussions

Re: [Xen-users] Xen-Fedora4 or 5, dead-end...
by Leonardo Pinto 31 Dec '05

31 Dec '05

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 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 ________________________________________________ Mensagem enviada usando OpenLogic WebMail 2.7.2

1 0

Xen-Fedora4 or 5, dead-end...
by Leonardo Pinto 30 Dec '05

30 Dec '05

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

1 0

Re: [Xen-users] They help me please!!!
by Leonardo Pinto 29 Dec '05

29 Dec '05

Hi Eduardo, Evidently I am with them, the RPMs, therefore I installed xen with "yum". Now I am trying really to compile, and we go to see if it functions of truth. They follow: iproute-2.6.11-1, bridge-utils-1.0.4-6, python-twisted-1.3.0-4, gcc-4.0.2-8.fc4, libgcc-4.0.2-8.fc4, binutils-2.15.94.0.2.2-2.1, make-3.80-7, zlib-devel-1.2.2.2-5.fc4, zlib-1.2.2.2-5.fc4, python-2.4.1-2, python-twisted-1.3.0-4. It confers? -- Leonardo Pinto listas#openlogic dot com br > have you installed all the dependencies *before* try to compile Xen? > > Here they are: > > * iproute2 > * bridge-utils > * python twisted >= 1.3 > * gcc >= 3.3 > * binutils > * make > * zlib{,-dev} > * python{,-dev} >= 2.2 > > Your bridge probabilly isn't working because your Fedora is lacking > the iproute and/or bridge-utils package(s). > > Good luck :-) > > Optionally, you can install Latex and Transfig. > -- > Eduardo Costa Lisboa ________________________________________________ Mensagem enviada usando OpenLogic WebMail 2.7.2

1 0

They help me please!!!
by Leonardo Pinto 29 Dec '05

29 Dec '05

Necessary urgent of a version of xen that it functions. The question, my people, is that I am with a stated period for the delivery of a dedicated server, and bet in the Fedora Core 4/5, however I do not obtain to make to function the versions of xen for this. The problem is that when xen does not break, is the net (xen-br0) that it does not function... Somebody would have the RPMs functional that they could send me? He would be very grateful, -- Leonardo Pinto listas#openlogic dot com br ________________________________________________ Mensagem enviada usando OpenLogic WebMail 2.7.2

1 0

Re: [Xen-users] Defective script network-bridge
by Leonardo Pinto 28 Dec '05

28 Dec '05

The problem, great friend, is that it started to function with old scripts. I know that this patch was not the best thing, but I was not obtaining no way to make to function with the news. I need to place the server in production soon. -- Leonardo Pinto listas#openlogic dot com br > On 12/27/05, Leonardo Pinto wrote: > Hi, > > Only to report a bug. It follows my "provisory" solution for one of my > problems. I am using xen of the FC4 2.6.12-1.1454_FC4.i686. > Was having problems to the bridges up. Simply the established > interface disappeared. When I had idea to copy scripts of an old > version of xen (2.0.2), over the news. They are: network-bridge and > vif-bridge. > -- > Leonardo Pinto > > No good for you. Xen 3 is quite another bitch :-) > Better to stick with Xen 3 scripts than changing them > always you install a new version of Xen, yet you can > see that the old scripts may not run with the new Xen. > -- > Fernando Maior ________________________________________________ Mensagem enviada usando OpenLogic WebMail 2.7.2

1 0

Defective script network-bridge
by Leonardo Pinto 27 Dec '05

27 Dec '05

Hi, Only to report a bug. It follows my "provisory" solution for one of my problems. I am using xen of the FC4 2.6.12-1.1454_FC4.i686. Was having problems to the bridges up. Simply the established interface disappeared. When derrepente I had idea to copy scripts of an old version of xen (2.0.2), over the news. They are: network-bridge and vif-bridge. -- Leonardo Pinto listas#openlogic dot com br ________________________________________________ Mensagem enviada usando OpenLogic WebMail 2.7.2

1 0

RE: [Xen-users] RE: [Fedora-xen] Difficulties using the Fedora Core 4
by Ian Pratt 23 Dec '05

23 Dec '05

> > becomes unstable. I am now testing the same HD with kernel > > 2.6.12-1.1454_FC4.i686 in another machine (AMD Duron(tm) > Processor), > > and following the tip of the friend I incapacitated > "acpi=off". Until the moment all good is going... > > yes there have been feedbacks on the xen user list about > acpi=off, noapic and 'swiotlb=force swiotlb=8m' kernel > arguments fixing some bugs raised in recent Xen-3.0 versions. > It's not fully cooked :-) swiotlb=force/8m should *not* be required with xen 3.0.0, only with pre-release versions of the -unstable tree (such as the RH FC4 RPMs). The vast majority of machines seem to work fine with acpi/apic enabled -- I've only seen a handful of people say they've needed to turn them off, and several of these have found that the problem goes away if they updated their BIOS. I would like to get to the bottom of these reports, though. Although Xen doesn't run on all the huge range of PC hardware that Linux does, it does seem to run fine on a very large subset, in particular the vast majority of modern server class hardware. Ian

2 1

RE: [Xen-users] RE: [Fedora-xen] Difficulties using the Fedora Core 4
by Leonardo Pinto 22 Dec '05

22 Dec '05

Already it distrusted that the problem could be distinct between hardwares. - Then the Xen: 2.6.12-1.1454_FC4.i686 is an unstable tree? The problem is: - How we will be able to place in a server in production the Fedora Core 5 that still one meets in Test? - He would not be dangerous to make this? Or I can trust the packages contained in it? -- Leonardo Pinto listas#openlogic dot com br > swiotlb=force/8m should *not* be required with xen 3.0.0, only with > pre-release versions of the -unstable tree (such as the RH FC4 RPMs). > > The vast majority of machines seem to work fine with acpi/apic enabled > -- I've only seen a handful of people say they've needed to turn them > off, and several of these have found that the problem goes away if they > updated their BIOS. I would like to get to the bottom of these reports, > though. ________________________________________________ Mensagem enviada usando OpenLogic WebMail 2.7.2

1 0

RE: [Xen-users] "netdev watchdog" error and non-working sis900network card - solution
by Leonardo Pinto 22 Dec '05

22 Dec '05

Yes, acpi=off seems to have decided my problem of instability. Soon, then I will be returning the HD in the machine in production and I dispatched by post the result. -- Leonardo Pinto listas#openlogic dot com br > The troubles went away when adding kernel options "noapic > acpi=off" to > the modules grub line. > > Both noapic and acpi=off make big difference to the machine > setup - it would probably be a good idea to figure out which > one makes the difference. If it's acpi=off, a new BIOS that > has more suitable things in the ACPI tables is probably the solution. > > If it's the noapic that actually solves the problem, then > that would be useful to know (but I'm not sure what the fix > is, aside from the fact that it may actually be the PCI > enumeration that goes wrong in the system - lspci -vvv may > give some info. > > Yep, there's been a couple of people recently saying that problems have > been fixed with acpi=off and noapic, and this really rather concerns me. > > I'd be very interested to see a diff of the output a native boot vs a > failing xen xen one. > > We need to get this fixed as I certainly wouldn't want to run a system > with 'noapic'. The legacy pic support in xen is really only in their so > that people can run on emulators like vmware or qemu. > > Ian ________________________________________________ Mensagem enviada usando OpenLogic WebMail 2.7.2

1 0

RE: [Xen-users] RE: [Fedora-xen] Difficulties using the Fedora Core 4
by Leonardo Pinto 22 Dec '05

22 Dec '05

Hi, I know that the task of compilation of the Xen is not so difficult. I myself already made it some times. Only that with the advent of the distributions to incorporate it, I really want to leave to make responsible me for this. I cannot make responsible me if I qualify something wrong and kernel becomes unstable. I am now testing the same HD with kernel 2.6.12-1.1454_FC4.i686 in another machine (AMD Duron(tm) Processor), and following the tip of the friend I incapacitated "acpi=off". Until the moment all good is going... I am thankful all, -- Leonardo Pinto listas#openlogic dot com br > Whilst I'm sure that Redhat is working on a publicly available RPM (or > similar) that you can install straight off, I would suggest that you > build your own Xen/Dom0 kernel. It's not TERRIBLY hard - although > there's some quirks and catches. This works for me: > Download some version of Xen from www.xensource.com (snapshot or 3.0.0 > release). > > ... cut ________________________________________________ Mensagem enviada usando OpenLogic WebMail 2.7.2

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xen December 2005