similar to: APIC not running in Xen

Dear List, I'm trying to perform an automatic server shutdown and restart with NUT 2.6.3, openSUSE 12.2 and an Eaton Eco 1600. The server shutdown works but there is no automatic restart when wall power returns. Unlike successful tests with earlier versions of openSUSE, the UPS unit is never switched off. It goes on beeping for as long as I let it. When I pulled the plug from the wall

Hi, Here is the patch fixing crash when apic=debug is used and APIC is not properly initialized. This issue appears during Xen Dom0 kernel boot (git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git, xen/stable-2.6.32.x head), however I think that patch is rather generic and should be applied to mainline kernel (it applies to Linux Kernel Ver. 2.6.35 and Ver. 2.6.32.19 with small fuzz).

Hi there Managed to get Xen up and running, also to get a 1394 controller to be hidden from dom0 to domU. I run an lvm in raid5 in domU as a fileserver. when I copy data to the raid, I get *hundreds* of these error messages: (XEN) APIC error on CPU0: 02(02) my system is: PC-Chips 848A with AMD Geode NX1750 2 G Ram Raid 1 with md0 that holds Dom0 Raid 1 with md1, that holds lvm for domUs All

since the pv_apic_ops are only present if CONFIG_X86_LOCAL_APIC is compiled in, kvmclock failed to build without this option. This patch fixes this Signed-off-by: Glauber Costa <gcosta at redhat.com> --- arch/x86/kernel/kvmclock.c | 4 ++++ 1 files changed, 4 insertions(+), 0 deletions(-) diff --git a/arch/x86/kernel/kvmclock.c b/arch/x86/kernel/kvmclock.c index ddee040..4bc1be5 100644

Why are these APIC clock init hooks dependent on CONFIG_X86_PAE ? include/asm/paravirt.h: static inline void setup_boot_clock(void) { paravirt_ops.setup_boot_clock(); } static inline void setup_secondary_clock(void) { paravirt_ops.setup_secondary_clock(); } (via the vmi timer patch). - James -- James Morris <jmorris@namei.org>

OK, not strictly in keeping with the subject of the patch set but I needed this to build ;-) Should be merged into 02d-xen-apic-esp0.patch Signed-off-by: Ian Campbell <ian.campbell@xensource.com> diff -r 6fdbec59813e arch/i386/paravirt-xen/enlighten.c --- a/arch/i386/paravirt-xen/enlighten.c Wed Aug 23 15:08:37 2006 +0100 +++ b/arch/i386/paravirt-xen/enlighten.c Wed Aug 23 15:08:37 2006

Similar to the local APIC changes, the IO-APIC access mechanisms should also be restricted to the Xen-specific ones (other than for the local APIC, where the access mechanisms must be entirely suppressed). A nice side effect of this is that the fixmap area shrinks quite a bit, allowing 32-bits to use a little more low memory. Signed-off-by: Jan Beulich <jbeulich@novell.com>

Other than for the legacy APIC, the x2APIC MADT entries have valid ranges possibly extending beyond what our internal arrays can handle, and hence we need to guard ourselves against corrupting memory here. Signed-off-by: Jan Beulich <jbeulich@suse.com> --- a/xen/arch/x86/acpi/boot.c +++ b/xen/arch/x86/acpi/boot.c @@ -97,7 +97,20 @@ acpi_parse_x2apic(struct acpi_subtable_h

Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com> --- This affects Xen 4.2 and 4.1, so I propose it for backport. diff -r 24df082ff3e7 -r 7bc81065d2d5 xen/arch/x86/apic.c --- a/xen/arch/x86/apic.c +++ b/xen/arch/x86/apic.c @@ -970,8 +970,7 @@ void __init x2apic_bsp_setup(void) panic("Interrupt remapping could not be enabled while "

Sadly, we have discovered another line level interrupt race condition in Xen-4.1. The result was that an outstanding un-eoi''d interrupt at the IO-APIC resulted in the mptsas controller offlining the root filesystem. This is now two separate IO-APIC bugs found recently. 1) Cisco C210 M2 server - EOI Broadcast Suppression, io_apci_ack=old 2) Dell R710 - No EOI Broadcast Suppression,

Hello, Is there a known issue using hard drives or images larger than approximately 20 to 100 GB? I''m running xen0-3.0.1-4 package from FC5 I have one HVM machine that uses a 20 GB disk and it works great, but the identical machine except with 100 GB disk gets ext3 kernel errors (didn''t write it down but pretty serious stuff because it basically destroys it''s

Some operating systems access the local APIC TPR very frequently, and we handle that using software-based local APIC virtualization in Xen today. Such virtualization incurs a number of VM exits from the memory-access instructions against the APIC page in the guest. The attached patch enables the TPR shadow feature that provides APIC TPR virtualization in hardware. Our tests indicate it can

This patch moves the IO-APIC include inside #ifdef CONFIG_X86_IO_APIC , which is how Linux 2.6 has it. This is needed for architectures without asm/io_apic.h. I''ve verified that x86 still builds; please apply. Signed-off-by: Hollis Blanchard <hollisb@us.ibm.com> -- Hollis Blanchard IBM Linux Technology Center

These occurrences are largely benign these days and tainting the kernel for them is a bit aggressive. Mostly they relate to failing to setup perf which I think we are all aware is something which needs attention on the Xen/pvops side. Signed-off-by: Ian Campbell <ian.campbell@citrix.com> diff --git a/arch/x86/xen/enlighten.c b/arch/x86/xen/enlighten.c index 974a528..55e3cc7 100644 ---

Hi: Does Trixbox support ACPI and IO-APIC out of the box? My Trixbox server isn't seeing the mainboard's APIC. -Stephen-

While other aspects of the system configuration may still be controlled by the outcome of the table scan, if apic= was given on the command line its effect should not be overridden here. Signed-off-by: Jan Beulich <jbeulich@novell.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hello all, My machine is a dual xeon x5520 server with NUMA support. I have some question about xen dom0 kernel. Since xen hypervisor has provided vcpu schedule, do we need to compile the following feature in dom0 kernel? - Tickless System (Dynamic Ticks) - High Resolution Timer Support - AMD IOMMU support - SMT (Hyperthreading) scheduler support - Multi-core scheduler suppor

Jerry Geis wrote: >/ I have tried in the grub.conf file />/ />/ noapic />/ />/ and />/ />/ apic=off />/ />/ I am still getting the same error message about ACPI />/ in the dmesg output. />/ />/ example: />/ ACPI: PCI interupt .... IRQ 16 />/ eth0: RealTek RTL8139 ... IRQ16 />/ eth0: identified 8139 chip type />/ />/ so ACPI is grabbing IRQ

Local APIC timer may stop at deep C state (C3/C4...) entry/exit. Initial HPET broadcast working in legacy replacing mode, broke RTC intr, so was bypassed. This patch add the logic that use platform timer (PIT) to reenable local APIC timer at C state entry/exit. Currently, only keep PIT enabled with 100Hz freq. The next step is trying to dynamically enable/disable PIT while needed, and give it

The VMCS includes controls that enable the virtualization of interrupts and the Advanced Programmable Interrupt Controller (APIC). When these controls are used, the processor will emulate many accesses to the APIC, track the state of the virtual APIC, and deliver virtual interrupts - all in VMX non-root operation without a VM exit. You can refer to Chapter 29 of the latest SDM. This series of