similar to: dom0 issues with switching from X to console or starting X

Hi, Keir, This patch is a bugfix for saving and restoring MSI/MSI-X across S3. Currently, Dom0''s PCI layer unmaps MSI when S3 and maps them back when resuming. However, this triggers unexpected behaviors. For example, if the drivers still holds that irq at the point of unmapping MSI, Xen will force unbind that pirq. But after resume, we have no mechanism to rebind that pirq. The device

Hello, The email (thread) below from xen-devel mailinglist indicates the changesets that should fix the bug that causes the lenny 2.6.26 xen kernel to crash on newer xen hypervisors. The workaround for this bug has been to use pci=nomsi on the dom0 kernel cmdline, but it would be better to apply the actual fix to the xen kernel in lenny. More information on xen-devel (archives). -- Pasi

Hi, I''m looking at a system hang on a large box: 160 cpus, 2TB. Dom0 is booted with 160 vcpus (don''t ask me why :)), and an HVM guest is started with over 1.5T RAM and 128 vcpus. The system hangs without much activity after couple hours. Xen 4.0.2 and 2.6.32 based 64bit dom0. During hang I discovered: Most of dom0 vcpus are in double_lock_balance spinning on one of the locks:

With the traditional qemu tree fixed to not use PROT_WRITE anymore in the mmap() call for this region, and with the upstream qemu tree not being capable of handling passthrough, yet, there''s no need to treat Dom specially here anymore. This continues to leave unaddressed the case where PV guests map the MSI-X table page(s) before setting up the first MSI-X interrupt (see the original c/s

There are BIOSes that want to map the IO-APIC MMIO region from some ACPI method(s), and there is at least one BIOS flavor that wants to use this mapping to clear an RTE''s mask bit. While we can''t allow the latter, we can permit reads and simply drop write attempts, leveraging the already existing infrastructure introduced for dealing with AMD IOMMUs'' representation as

Note: I''m familiar with gentoo distribution, but not with xen. A time has come, I desided, I need several xen virtual guests on my box (mostly because I want some personal web-applications installed on different environment that my desctop machine and desire to have ''playground'' for web-development attempts) What I have done 1) installed recent gentoo-sources (2.6.39),

Hello, More information and a patch for the bug. -- Pasi ----- Forwarded message from George Dunlap <George.Dunlap at eu.citrix.com> ----- From: George Dunlap <George.Dunlap at eu.citrix.com> To: Jan Beulich <JBeulich at novell.com> Cc: Sander Eikelenboom <linux at eikelenboom.it>, Jeremy Fitzhardinge <jeremy at goop.org>, Yunhong Jiang <yunhong.jiang at

There''re basically two methods to enter a given C-state: legacy (hlt + I/O read), and native(using mwait). MWAIT is always preferred when both underlying CPU and OS support, which is a more efficient way to conduct C-state transition. Xen PM relies on Dom0 to parse ACPI Cx/Px information, which involves one step to notify BIOS about a set of capabilities supported by OSPM. One capability

Hi, Keir, Jan, This patch is a bugfix pointed by Jan. Fix mask_base(actually MSI-X table base, copy name from native) to be a virtual address rather than a physical address. And remove wrong printk in pci_disable_msix. Jan, the error message you saw is wrong output from kernel''s MSI code. Really sorry for my dirty code there. Could you please review the patch and give me feedback?

Signed-off-by: Jan Beulich <jbeulich@novell.com> Index: 2007-06-18/xen/arch/x86/hvm/svm/svm.c =================================================================== --- 2007-06-18.orig/xen/arch/x86/hvm/svm/svm.c 2007-06-15 14:05:46.000000000 +0200 +++ 2007-06-18/xen/arch/x86/hvm/svm/svm.c 2007-06-18 10:23:05.000000000 +0200 @@ -1477,7 +1477,7 @@ static void svm_io_instruction(struct vc

Is there any technical reason for restricting dom0_max_vcpus to be no greater than num_online_cpus()? Since Dom0''s vCPU-s can be pinned later to a subset of physical CPUs anyway, allowing more vCPU-s from the beginning would seem to be only consistent. Thanks, Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

"Jan Beulich" <JBeulich at suse.com> writes: #Okay, this at least clarifies there is a (relatively big) RMRR. There is #a change to the handling of these among the ones that'll become #4.3.3 - mind giving #http://xenbits.xen.org/gitweb/?p=xen.git;a=commitdiff;h=6c63041428cc348bcb2887afabd606bc4bd5523f #a try on top of your 4.3.2 (or trying the tip of the stable-4.3 branch)? #

Hi Jan, I was wondering if we should not let the code fall through and clear all registers to zero but rather clear just the one bit we care about? My concern is that a future Intel revision may expand this function and return other information besides that XSAVEOPT, which would then be wiped out by the fall-through code. I''m thinking something like this. Let me know if I have

Under the assumption that in these cases recurring faults aren''t a security issue and it can be expected that the drivers there are going to try to take care of the problem. Signed-off-by: Jan Beulich <jbeulich@suse.com> --- a/xen/drivers/passthrough/amd/iommu_init.c +++ b/xen/drivers/passthrough/amd/iommu_init.c @@ -625,6 +625,18 @@ static void parse_event_log_entry(struct

On Wed, May 17, 2017 at 4:26 AM, Jerry <jerryubi at gmail.com> wrote: > Howdy, > > I recently went through a frustrating experience trying to get Xen 4 running > on a CentOS 7 system. After a fresh install, fully updating the system, > rebooting, then trying to install Xen4CentOS it would fail to boot into the > 4.9 kernel, sitting there with a blinking cursor

On Tue, May 16, 2017 at 10:26 PM, Jerry <jerryubi at gmail.com> wrote: > Howdy, > > I recently went through a frustrating experience trying to get Xen 4 > running on a CentOS 7 system. After a fresh install, fully updating the > system, rebooting, then trying to install Xen4CentOS it would fail to boot > into the 4.9 kernel, sitting there with a blinking cursor

Jerry, Refer to console=hvc0 from (https://wiki.xen.org/wiki/Xen_FAQ_Console)which is dedicated for domO after Xen kernel loaded, so if it hangs it means somewhere the booting process with xen is not right. Suggest you to close look at the dmsg or log for debugging. Hope that helps and cheers. Xlord On Wed, May 17, 2017 at 11:26 AM, Jerry <jerryubi at gmail.com> wrote: > Howdy, >

>>> On 22.05.14 at 19:19, <mike at estone.ca> wrote: > "Jan Beulich" <JBeulich at suse.com> writes: > #Okay, this at least clarifies there is a (relatively big) RMRR. There is > #a change to the handling of these among the ones that'll become > #4.3.3 - mind giving > #http://xenbits.xen.org/gitweb/?p=xen.git;a=commitdiff;h=6c63041428cc348bcb2 >

Subject: Obtain VESA capabilities and attributes of VESA mode Also, move some more common code to dom0_init_screen_info(). This was tested on 2.6.22.1, and only made apply to 2.6.18 without further testing. Signed-off-by: Jan Beulich <jbeulich@novell.com> Index: head-2007-08-07/arch/i386/kernel/setup-xen.c =================================================================== ---

There is a BUG_ON() at xen/arch/x86/physdev.c:169 which appears to be dependent upon guest behavior (should close event channel before un-mapping pirq), rather than on internal hypervisor state. In 2.6.18, this likely goes unnoticed because pci_device_shutdown() only calls all the driver shutdown routines. In newer kernels, however, it also calls pci_msi_shutdown() and pci_msix_shutdown(), which