similar to: HVM PIC/APIC confusion in ACPI firmware?

Hello, I have been retained by a Building Management Company to install a combined Voice/Data solution for a Tennated Office Space. This space will rent offices, with telephone and internet service to inviduals or small groups of individuals. As fate would have it, the service will be provided in a building where we have a major Pop, with a DS-3 worth of ISDN PRI circuits, 345 megs of

Currently running fc3 (2.6.9-1.667) on a test box with a TDM04b and A200D installed with svn trunk. Its working well except one of the cards is sharing interrupts with another device that I'd like to clean up. I'd like to try moving to io-apic interrupt support for more interrupts. The MB bios is config'ed to support apic, but apparently the kernel is not. Is there a kernel level

We also use -runtime-variant _pic which selects the OCaml runtime linked with -fPIC. This will cause a performance regression on i686 although that probably doesn't matter now. A bigger issue is that it will stop supermin from building with older versions of OCaml (<= 4.02.2). We might instead try detecting if it's the old version in ./configure but that gets a bit fragile. ---

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

OCaml has a small runtime which is statically linked into the virt tools (providing things like GC and primitives). Since OCaml 4.03 it has been possible to select variants of this runtime, one of which is compiled with -fPIC, using ‘ocamlopt -runtime-variant _pic’. This has performance implications on i686, but is relatively free on other architectures. Since it (in theory) adds to the

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

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

Attached please see the hvm guest os acpi patch part 3 of 4:piix4acpi_prt.patch The patch added ACPI _PRT table for PCI IRQ routing table in PIC mode and fixed the _PRT table in APIC mode Signed-off-by: Tang Liang <tangliang@lenovo.com> Signed-off-by: Winston Wang <winston.l.wang@intel.com> _______________________________________________ Xen-devel mailing list

The ocaml.opt compiler defaults to building things in the same directory as its input; we need explicit -o options to build in a VPATH $(builddir) when $(srcdir) is read-only (as is the case during 'make distcheck'). We also have to build any side effect files explicitly in cases where we can't directly use -o to control those outputs alongside the final product. Thanks: Richard W.M.

Intercept guest reads of MSR_IA32_MCG_CAP and limit the number of memory banks reported to one. This prevents us from trying to read status of non-existent banks when migrated to a machine with fewer banks. Signed-off-by: Ben Guthro Signed-off-by: David Lively <dlively@virtualiron.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

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, I'm on a Dell VEP 1405 running Debian 9.11 and I'm running a few tests with various interfaces given in PCI passthrough to a qemu/KVM Virtual Machine also running Debian 9.11. I noticed that only one of the four I350 network controllers can be used in PCI passthrough. The available interfaces are: *# dpdk-devbind.py --status Network devices using kernel driver

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>

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