search for: xen_idle

...3/99] do_softirq+0x3f/0x63 Dec 8 12:19:27 server kernel: [do_IRQ+31/37] do_IRQ+0x1f/0x25 Dec 8 12:19:27 server kernel: [evtchn_do_upcall+132/192] evtchn_do_upcall+0x84/0xc0 Dec 8 12:19:27 server kernel: [hypervisor_callback+44/52] hypervisor_callback+0x2c/0x34 Dec 8 12:19:27 server kernel: [xen_idle+97/127] xen_idle+0x61/0x7f Dec 8 12:19:27 server kernel: [cpu_idle+76/97] cpu_idle+0x4c/0x61 Dec 8 12:19:27 server kernel: [start_kernel+370/372] start_kernel+0x172/0x174 Dec 8 12:19:27 server kernel: Mem-info: Dec 8 12:19:27 server kernel: DMA per-cpu: Dec 8 12:19:27 server kernel: cpu 0 ho...

...rnel: [<ffffffff802063aa>] hypercall_page+0x3aa/0x1000 Apr 18 01:10:00 xenmaster kernel: [<ffffffff802063aa>] hypercall_page+0x3aa/0x1000 Apr 18 01:10:00 xenmaster kernel: [<ffffffff8026e4e5>] raw_safe_halt+0x84/0xa8 Apr 18 01:10:00 xenmaster kernel: [<ffffffff8026ba22>] xen_idle+0x38/0x4a Apr 18 01:10:00 xenmaster kernel: [<ffffffff8024a803>] cpu_idle+0x97/0xba Apr 18 01:10:00 xenmaster kernel: [<ffffffff80634b09>] start_kernel+0x21f/0x224 Apr 18 01:10:00 xenmaster kernel: [<ffffffff806341e5>] _sinittext+0x1e5/0x1eb Apr 18 01:10:00 xenmaster kernel: Ap...

Just gave 3.0 a spin. Had been running 2.0.7 for the past 3 months or so without problems (aside from intermittent failure during live migration). Anyway, 3.0 seems to have an issue with my machine. It starts up the 4 domains that I''ve got defined (was running 6 user domains with 2.0.7, but two of those were running 2.4 kernels which I can''t seem to build with Xen 3.0 yet, and

Stamp softlockup thread earlier before do_timer, because the latter is the one to actually trigger lock warning for long-time offline. Or else, I obserevd softlockup warning easily at manual vcpu hot-remove/plug, or when suspend cancel into old context. One point here is to cover both stolen and blocked time to compare with offline threshold. vcpu hotplug falls into ''stolen''

Hi, I just want to know if somebody use 2.6.31.4 xenified kernel (aka OpenSUSE) in production? We have been testing it on new Nehalem Xeon server for few weeks w/o any problem. But as soon we tried it on production machine - after several production domUs started - hard OS failure. We had to switch back to 2.6.18.8 - xen stock kernel. Peter _______________________________________________

...123974b2 ############################################### Centos 4.1 dom0, Tyan 2462 SMP, 8k kernel stack ############################################### Still seeing (vcpu#1) crashed on cpu#0 when tryin to bring up smp domU''s, I am able to three going, the 4th will crash. c01070e0 <xen_idle>: c01070e0: 55 push %ebp c01070e1: b9 00 e0 ff ff mov $0xffffe000,%ecx c01070e6: 21 e1 and %esp,%ecx c01070e8: 89 e5 mov %esp,%ebp c01070ea: 83 ec 0c sub $0xc,%esp c01070e...

...100 > Dec 18 10:47:57 hive kernel: [hypervisor_callback+61/72] > hypervisor_callback+0x3d/0x48 > Dec 18 10:47:57 hive kernel: [safe_halt+32/80] safe_halt+0x20/0x50 > Dec 18 10:47:57 hive kernel: [start_hz_timer+18/32] start_hz_timer > +0x12/0x20 > Dec 18 10:47:57 hive kernel: [xen_idle+44/96] xen_idle+0x2c/0x60 > Dec 18 10:47:57 hive kernel: [cpu_idle+139/224] cpu_idle+0x8b/0xe0 > Dec 18 10:47:57 hive kernel: [start_kernel+427/496] start_kernel > +0x1ab/0x1f0 > Dec 18 10:47:57 hive kernel: [unknown_bootoption+0/480] > unknown_bootoption+0x0/0x1e0 > "&quo...

...hive kernel: [hypervisor_callback+61/72] > > hypervisor_callback+0x3d/0x48 > > Dec 18 10:47:57 hive kernel: [safe_halt+32/80] safe_halt+0x20/0x50 > > Dec 18 10:47:57 hive kernel: [start_hz_timer+18/32] start_hz_timer > > +0x12/0x20 > > Dec 18 10:47:57 hive kernel: [xen_idle+44/96] xen_idle+0x2c/0x60 > > Dec 18 10:47:57 hive kernel: [cpu_idle+139/224] cpu_idle+0x8b/0xe0 > > Dec 18 10:47:57 hive kernel: [start_kernel+427/496] start_kernel > > +0x1ab/0x1f0 > > Dec 18 10:47:57 hive kernel: [unknown_bootoption+0/480] > > unknown_bootoption+...

...hive kernel: [hypervisor_callback+61/72] > > hypervisor_callback+0x3d/0x48 > > Dec 18 10:47:57 hive kernel: [safe_halt+32/80] safe_halt+0x20/0x50 > > Dec 18 10:47:57 hive kernel: [start_hz_timer+18/32] start_hz_timer > > +0x12/0x20 > > Dec 18 10:47:57 hive kernel: [xen_idle+44/96] xen_idle+0x2c/0x60 > > Dec 18 10:47:57 hive kernel: [cpu_idle+139/224] cpu_idle+0x8b/0xe0 > > Dec 18 10:47:57 hive kernel: [start_kernel+427/496] start_kernel > > +0x1ab/0x1f0 > > Dec 18 10:47:57 hive kernel: [unknown_bootoption+0/480] > > unknown_bootoption+...

...;{do_IRQ+63} <ffffffff802f6b82>{evtchn_do_upcall+192} <ffffffff8010b5f6>{do_hypervisor_callback+30} <EOI> <ffffffff801073aa>{hypercall_page+938} <ffffffff801073aa>{hypercall_page+938} <ffffffff8010f702>{safe_halt+132} <ffffffff80108d77>{xen_idle+106} <ffffffff80108e36>{cpu_idle+171} <ffffffff804cd77a>{start_kernel+488} <ffffffff804cd223>{_sinittext+547} Code: 48 8b 85 e8 00 00 00 66 83 78 06 00 74 25 0f b7 40 04 41 8d RIP <ffffffff88009a1e>{:bnx2:bnx2_poll+231} RSP <ffffffff80503de8> CR2: 000000...

...0093aa>] ? hypercall_page+0x3aa/0x1001 [ 106.816456] [<ffffffff810093aa>] ? hypercall_page+0x3aa/0x1001 [ 106.816467] [<ffffffff8100ec12>] ? xen_vcpuop_set_next_event+0x0/0x60 [ 106.816477] [<ffffffff8100e6b3>] ? xen_safe_halt+0xc/0x15 [ 106.816486] [<ffffffff8100bfc7>] ? xen_idle+0x37/0x40 [ 106.816495] [<ffffffff81010e97>] ? cpu_idle+0xa2/0xda [ 106.816505] [<ffffffff81531cdd>] ? start_kernel+0x3dc/0x3e8 [ 106.816516] [<ffffffff81533c93>] ? xen_start_kernel+0x586/0x58a [ 106.816525] ---[ end trace 672dc18af7fa0bc2 ]--- [ 106.816686] e1000: eth2: e1000_cle...

...? hypercall_page+0x3aa/0x1001 [488054.896330] [<ffffffff810093aa>] ? hypercall_page+0x3aa/0x1001 [488054.896343] [<ffffffff8100e160>] ? xen_vcpuop_set_next_event+0x0/0x60 [488054.896354] [<ffffffff8100dcb3>] ? xen_safe_halt+0xc/0x15 [488054.896366] [<ffffffff8100be63>] ? xen_idle+0x37/0x40 [488054.896377] [<ffffffff8100feb1>] ? cpu_idle+0xa2/0xda [488054.896388] [<ffffffff814f5cdd>] ? start_kernel+0x3dc/0x3e8 [488054.896397] Mem-Info: [488054.896404] Node 0 DMA per-cpu: [488054.896413] CPU 0: hi: 0, btch: 1 usd: 0 [488054.896422] CPU 1: hi: 0,...

Hello everybody, I''ve finished with pci export from DomU to Dom0 (Debian Etch) but now i have a new problem, and a big one. My ethernet card is dropping packets but after some time (i can''t tell how) It can work for a day (not in production so not hard tested) and then all packets are dropped. Look at the ifconfig output : eth0      Link encap:Ethernet  HWaddr

...8>] evtchn_do_upcall+0x86/0xe0 [<ffffffff8025cc1a>] do_hypervisor_callback+0x1e/0x2c <EOI> [<ffffffff802063aa>] hypercall_page+0x3aa/0x1000 [<ffffffff802063aa>] hypercall_page+0x3aa/0x1000 [<ffffffff8026afe2>] raw_safe_halt+0x84/0xa8 [<ffffffff802684f8>] xen_idle+0x38/0x4a [<ffffffff80247bcd>] cpu_idle+0x97/0xba BUG: soft lockup detected on CPU#7! Etc., etc etc, It does not crash the Xen zones directly, but clogs up the Xen web1 console etc. We did not see this when running the 2.6.18-8.1.8 Xen kernel, instead the Xen zones crashed less frequent wi...

...8>] evtchn_do_upcall+0x86/0xe0 [<ffffffff8025cc1a>] do_hypervisor_callback+0x1e/0x2c <EOI> [<ffffffff802063aa>] hypercall_page+0x3aa/0x1000 [<ffffffff802063aa>] hypercall_page+0x3aa/0x1000 [<ffffffff8026afe2>] raw_safe_halt+0x84/0xa8 [<ffffffff802684f8>] xen_idle+0x38/0x4a [<ffffffff80247bcd>] cpu_idle+0x97/0xba BUG: soft lockup detected on CPU#7! Etc., etc etc, It does not crash the Xen zones directly, but clogs up the Xen web1 console etc. We did not see this when running the 2.6.18-8.1.8 Xen kernel, instead the Xen zones crashed less frequent wi...

...vtchn_do_upcall+0x13c/0x1fc [ 364.024802] [<ffffffff8020bbde>] do_hypervisor_callback+0x1e/0x30 [ 364.024802] <EOI> [<ffffffff8037c992>] force_evtchn_callback+0xa/0xb [ 364.024802] [<ffffffff8020e795>] xen_safe_halt+0x90/0xa6 [ 364.024802] [<ffffffff8020a0c8>] xen_idle+0x2e/0x66 [ 364.024802] [<ffffffff80209cd6>] cpu_idle+0x97/0xb9 [ 364.024802] [ 364.024802] handlers: [ 364.024802] [<ffffffffa00b42ad>] (megasas_isr+0x0/0x45 [megaraid_sas]) [ 364.024802] Disabling IRQ #19 My take on this: Xen (or rather the dom0 kernel?) disables the shared IRQ...

...tirq+75} <ffffffff8010d28e>{do_IRQ+67} <ffffffff8020472d>{evtchn_do_upcall+132} <ffffffff8010b4c2>{do_hypervisor_callback+30} <EOI> <ffffffff801073aa>{hypercall_page+938} <ffffffff801073aa> {hypercall_page+938} <ffffffff801093bf>{xen_idle+134} <ffffffff8010943b>{cpu_idle+80} <ffffffff803676ab>{start_kernel+478} <ffffffff803670cc>{_sinittext+204} Code: 40 8a 7d 53 8b 45 08 41 23 46 0c 3b 45 00 40 0f b6 cf 89 c8 RIP <ffffffff8801c732>{:ip_tables:ipt_do_table+197} RSP <ffffffff803154c8> CR2: ffffc2...

...2608d6>] do_hypervisor_callback+0x1e/0x2c <EOI> [<ffffffff802063aa>] hypercall_page+0x3aa/0x1000 [<ffffffff802063aa>] hypercall_page+0x3aa/0x1000 [<ffffffff802999eb>] rcu_pending+0x26/0x50 [<ffffffff8026f4d5>] raw_safe_halt+0x84/0xa8 [<ffffffff8026ca50>] xen_idle+0x38/0x4a [<ffffffff8024afa1>] cpu_idle+0x97/0xba _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

...ftirq+0x101/0x15c [<c042613e>] __do_softirq+0x5e/0xc3 [<c0406edf>] do_softirq+0x56/0xaf [<c0406e80>] do_IRQ+0xa5/0xae [<c0549913>] evtchn_do_upcall+0x64/0x9b [<c04055d9>] hypervisor_callback+0x3d/0x48 [<c0408632>] raw_safe_halt+0x8c/0xaf [<c040321a>] xen_idle+0x22/0x2e [<c0403339>] cpu_idle+0x91/0xab [<c06eb9f5>] start_kernel+0x37a/0x381 ======================= Code: c0 74 07 8b 08 8b 58 04 eb 05 83 c9 ff 31 db 89 da 89 c8 f7 d2 f7 d0 21 fa 21 f0 89 d1 09 c1 74 13 68 bd 1a 62 c0 e8 de 7b 01 00 <0f> 0b 91 01 9e 1a 62 c0 5d f0 83 04 2...

...vtchn_do_upcall+0x13c/0x1fc [ 364.024802] [<ffffffff8020bbde>] do_hypervisor_callback+0x1e/0x30 [ 364.024802] <EOI> [<ffffffff8037c992>] force_evtchn_callback+0xa/0xb [ 364.024802] [<ffffffff8020e795>] xen_safe_halt+0x90/0xa6 [ 364.024802] [<ffffffff8020a0c8>] xen_idle+0x2e/0x66 [ 364.024802] [<ffffffff80209cd6>] cpu_idle+0x97/0xb9 [ 364.024802] [ 364.024802] handlers: [ 364.024802] [<ffffffffa00b42ad>] (megasas_isr+0x0/0x45 [megaraid_sas]) [ 364.024802] Disabling IRQ #19 My take on this: Xen (or rather the dom0 kernel?) disables the shared IRQ...