similar to: Page Fault in PV?

Package: xen-hypervisor-4.0-i386 Version: 4.0.1-4 This is the same machine referenced in http://bugs.debian.org/665413. It is an HP d530 SFF workstation (model DG784A) with 4GiB of RAM. It has run for years on the lenny xen + linux stack. If my notes are correct, it also ran smoothly for about a year with the lenny hypervisor + kernel and the squeeze userland. Rebooting into squeeze xen +

minios: support COW for a zero page Permits to support sparse data. Signed-off-by: Samuel Thibault <samuel.thibault@eu.citrix.com> diff -r 27ad7ed41be2 extras/mini-os/arch/x86/mm.c --- a/extras/mini-os/arch/x86/mm.c Fri Jan 18 15:55:13 2008 +0000 +++ b/extras/mini-os/arch/x86/mm.c Fri Jan 18 16:02:32 2008 +0000 @@ -50,6 +50,7 @@ #endif unsigned long *phys_to_machine_mapping; +unsigned

Hi, List, In checking the page fault problem when using pv-grub to start domU in opensuse12.3[1], found that the problem is caused by ''-fstack-protector'' flag which is introduced in rpm build: export EXTRA_CFLAGS_XEN_TOOLS="$RPM_OPT_FLAGS" export EXTRA_CFLAGS_QEMU_TRADITIONAL="$RPM_OPT_FLAGS" export EXTRA_CFLAGS_QEMU_XEN="$RPM_OPT_FLAGS" with

I would like to know approximately the overall execution flow when the guest O/S page fault - how is the page fault transfer to a page fault in the host O/S? Thanks. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

One could even debate whether reserved bit faults are always fatal (and should never be propagated to the guest)... Signed-off-by: Jan Beulich <jbeulich@novell.com> Index: 2008-01-28/xen/arch/x86/traps.c =================================================================== --- 2008-01-28.orig/xen/arch/x86/traps.c 2008-01-28 11:31:44.000000000 +0100 +++ 2008-01-28/xen/arch/x86/traps.c

I''m porting a light weight kernel to run under the Xen hypervisor and have run into a problem while trying to switch to my page tables on x86-64. After a minor problem with switching to the new PML4 table that was cleared up when Mark Williamson suggested mapping everything read-only in the current map before switching, as well as switching the memory management code to use the

Hi, I''ve got a strange problem with XEN: I''m testing a 64-bit HVM-domain (a little OS written by me) with XEN 3.0.4 changeset 13138 on x86_64 (Dom0 and XEN taken from SLES 10 SP1). Always at the same point I get a page fault (which is okay) in PL=3 with strange interrupt data on the stack: the EIP is okay, but the CS saved is the TSS instead of my 64-bit user CS selector. I

From: David Hildenbrand <david at redhat.com> commit 63341ab03706e11a31e3dd8ccc0fbc9beaf723f0 upstream. In case we have to migrate a ballon page to a newpage of another zone, the managed page count of both zones is wrong. Paired with memory offlining (which will adjust the managed page count), we can trigger kernel crashes and all kinds of different symptoms. One way to reproduce: 1.

From: David Hildenbrand <david at redhat.com> commit 63341ab03706e11a31e3dd8ccc0fbc9beaf723f0 upstream. In case we have to migrate a ballon page to a newpage of another zone, the managed page count of both zones is wrong. Paired with memory offlining (which will adjust the managed page count), we can trigger kernel crashes and all kinds of different symptoms. One way to reproduce: 1.

From: David Hildenbrand <david at redhat.com> commit 63341ab03706e11a31e3dd8ccc0fbc9beaf723f0 upstream. In case we have to migrate a ballon page to a newpage of another zone, the managed page count of both zones is wrong. Paired with memory offlining (which will adjust the managed page count), we can trigger kernel crashes and all kinds of different symptoms. One way to reproduce: 1.

From: David Hildenbrand <david at redhat.com> commit 63341ab03706e11a31e3dd8ccc0fbc9beaf723f0 upstream. In case we have to migrate a ballon page to a newpage of another zone, the managed page count of both zones is wrong. Paired with memory offlining (which will adjust the managed page count), we can trigger kernel crashes and all kinds of different symptoms. One way to reproduce: 1.

From: David Hildenbrand <david at redhat.com> commit 63341ab03706e11a31e3dd8ccc0fbc9beaf723f0 upstream. In case we have to migrate a ballon page to a newpage of another zone, the managed page count of both zones is wrong. Paired with memory offlining (which will adjust the managed page count), we can trigger kernel crashes and all kinds of different symptoms. One way to reproduce: 1.

From: David Hildenbrand <david at redhat.com> commit 63341ab03706e11a31e3dd8ccc0fbc9beaf723f0 upstream. In case we have to migrate a ballon page to a newpage of another zone, the managed page count of both zones is wrong. Paired with memory offlining (which will adjust the managed page count), we can trigger kernel crashes and all kinds of different symptoms. One way to reproduce: 1.

3.16.83-rc1 review patch. If anyone has any objections, please let me know. ------------------ From: David Hildenbrand <david at redhat.com> commit 63341ab03706e11a31e3dd8ccc0fbc9beaf723f0 upstream. In case we have to migrate a ballon page to a newpage of another zone, the managed page count of both zones is wrong. Paired with memory offlining (which will adjust the managed page count),

Hello, We''re curious about page fault handling in Xen-devel. In particular, during kernel boot-up, the kernel tests if the CPU "honours the WP bit". This causes a page fault with error code 3 (expected behavior). Does Xen still make a copy of the execution stack frame on the guest OS stack, as specified in the original "Xen and the Art of Virtualization" paper?

This is a note to let you know that I've just added the patch titled virtio-balloon: fix managed page counts when migrating pages between zones to the 4.4-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary The filename of the patch is: virtio-balloon-fix-managed-page-counts-when-migrating-pages-between-zones.patch

This is a note to let you know that I've just added the patch titled virtio-balloon: fix managed page counts when migrating pages between zones to the 4.9-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary The filename of the patch is: virtio-balloon-fix-managed-page-counts-when-migrating-pages-between-zones.patch

This is a note to let you know that I've just added the patch titled virtio-balloon: fix managed page counts when migrating pages between zones to the 4.14-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary The filename of the patch is: virtio-balloon-fix-managed-page-counts-when-migrating-pages-between-zones.patch

This is a note to let you know that I've just added the patch titled virtio-balloon: fix managed page counts when migrating pages between zones to the 4.19-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary The filename of the patch is: virtio-balloon-fix-managed-page-counts-when-migrating-pages-between-zones.patch

This is a note to let you know that I've just added the patch titled virtio-balloon: fix managed page counts when migrating pages between zones to the 5.3-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary The filename of the patch is: virtio-balloon-fix-managed-page-counts-when-migrating-pages-between-zones.patch