similar to: Bug#516610: follow up

I just reproduced the "Early page fault", here is the error message: (XEN) Early fatal page fault at e008:ffff828c801da4a2 (cr2=ffff830fb0dcdff6, ec=0000) I omit the following stack dump, cause I'm typing this manually ;) But I took a photo with my digital camera, if the info is important, I can the provide the stack dump info.. regards, stephan

This message, (XEN) Early fatal page fault at e008:ffff828c801da4a2 seems to be a result of Grub2 not supporting Xen kernels. More info here: http://lists.gnu.org/archive/html/grub-devel/2009-06/msg00219.html And a related thread here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=505517 cheers, iMac

Hi List, I read this list for nearly two years and learnt a lot, but now i have a very strange problem I can''t solve.. I have a firewall machine running Debian, which connects a small office to the internet via a DSL-line (with pppoe) and which is running Shorewall. It allows all outbound traffic and accepts pptp, openvpn and ssh-connections (on a non-standard port) from the internet.

Processing commands for control at bugs.debian.org: > forcemerge 545224 516610 Bug #545224 [src:xen] grub-pc: Makes xen-hypervisor-3.2-1-amd64 hang with "early fatal page fault" on boot Bug #545224 [src:xen] grub-pc: Makes xen-hypervisor-3.2-1-amd64 hang with "early fatal page fault" on boot The source xen and version 3.2.1-2 do not appear to match any binary packages

Hi, I have a problem booting the Xen hypervisor on my brand new Lenovo Thinkpad T400 2765D2G (Core2 Duo P8600 CPU, 2.40GHz. 4GB RAM). I''m running Debian 5.0 (Lenny) and I use the Debian-provided xen-hypervisor-3.2-1-amd64 package. The Dom0 kernel seems to be the Xen patches ported to a 2.6.26 kernel: linux-image-2.6.26-1-xen-amd64 I can boot the hypervisor only very unrealiably: Out of

Processing commands for control at bugs.debian.org: > # reassigning all open bugs reported against versioned xen packages that are no longer in the archive to src:xen > reassign 514918 src:xen 3.3-unstable+hg17961-1 Bug #514918 [xen-utils-unstable] xen-utils-unstable: xend starts with errors Warning: Unknown package 'xen-utils-unstable' Bug reassigned from package

I am having reports of PCI passthrough problems with SR-IOV, in particular it looks like we are hitting the warning at msi:635 and msi:648 in xen; see the following log: (XEN) [VT-D]iommu.c:1785: VT-d page table not sharing with EPT table xenbus dev backend/vbd/1/5696 error 6 opening device (XEN) PCI add Virtual Function 04:1a.0 (XEN) HVM1: HVM Loader (XEN) HVM1: Detected Xen v4.1.0.rc2.pre (XEN)

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 +

This issue I am encountering seems to only happen on multi-socket machines. It also does not help that the only multi-socket box I have is an Romley-EP (so two socket SandyBridge CPUs). The other SandyBridge boxes I''ve (one socket) are not showing this. Granted they are also a different model (42). The problem is that when I run ''perf top'' within an SMP PVHVM guest,

changeset: 8830:fcc833cbaf82 tag: tip user: kaf24@firebug.cl.cam.ac.uk date: Mon Feb 13 10:41:23 2006 +0100 summary: Return real error code from Xen /dev/mem, not EAGAIN. x460: x86_32: Status: - dom0 boots fine - xend loads fine - single HVM domain loads fine - Multiple HVM domains load fine - destruction of any HVM domain causes dom0 to reboot Issues affecting

I started a new thread because this not a pv-ops dom0 anymore. I''m running Andrew Lyon''s 2.6.31-4 patches for a non-pv-ops kernel. Got it again, after issuing "poweroff" from the domU. (XEN) (XEN) NMI - MEMORY ERROR (XEN) ----[ Xen-3.5-unstable x86_64 debug=y Not tainted ]---- (XEN) CPU: 0 (XEN) RIP: e008:[<ffff82c48011f55c>] remove_from_heap+0x8f/0xd0

Hi all, I''m trying to boot XEN. I get the following error though Panic on CPU 0: Early fatal page fault at e008:ff134570 (cr2=fffdf020, ec=0000) Reboot in five seconds... Unknown interrupt (cr2=fffdf020) My system has 2GB of RAM. Has anyone had the same problem and can give an hint? Thanks. In case anyone had done the same I''m doing, I''m actually downloading XEN

I''ve triggered this a few times now, so time to report. Unfortuantely, I don''t have a good recipe for reproducing this one, and this is a reasonably hacked up branch of (domU) XenLinux. So, while I can''t discount bugs in this domU, a domU bug shouldn''t crash Xen like this: (I belive this one was from simply typing halt in domU) (XEN) Assertion ''!

# HG changeset patch # User Ian Campbell <ian.campbell@citrix.com> # Date 1321356497 0 # Node ID 3cfb8f2c4ce898414279d7162206be812584bd5b # Parent 955a6c07dc5e9c55316d1678b2b7cc4313f4fd57 xen: avoid crash enabling turbo mode On a system which has not had P-state information pushed down into the hypervisor running "xenpm enable-turbo-mode" will reliably crash the host. (XEN) PM

The hvm domain which is being debugged sometimes crashes with the following message: (XEN) Failed vm entry (exit reason 0x80000021) caused by invalid guest state (0). (XEN) ************* VMCS Area ************** (XEN) *** Guest State *** (XEN) CR0: actual=0x000000008005003b, shadow=0x000000008005003b, gh_mask=ffffffffffffffff ...[snip]... (XEN) DebugCtl=0000000000000000

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-1 Severity: grave Tags: squeeze sid Justification: causes non-serious data loss Live migration of a guest (running CentOS 5.5, Paravirtualized) crashes the target-host (Hardware: Dell R610, 2x Xeon 5620, 16Gb RAM, Perc/700-Raid) (XEN) ----[ Xen-4.0.1 x86_64 debug=n Not tainted ]---- (XEN) CPU: 9 (XEN) RIP: e008:[<ffff82c4801151f6>]

ioemu-remote: The device model needs to write in the ACPI tables when it wakes up from S3 state. Signed-off-by: Jean Guyader <jean.guyader@eu.citrix.com> -- Jean Guyader _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hey, It looks like one of the patches that went in Xen 4.1 blows up. This used to work over the weekend, so I can only surmise it is one the three patches. This is with a debug=y build (which has been working nicely for the last month or more). It looks like one of the patches that went in Xen 4.1 blows up. This used to work a day ago - that is c/s 23551 worked nicely. ----- Forwarded message

Package: xen-hypervisor-3.2-1-i386-nonpae Version: 3.2.1-2 Severity: important Hello, I just played with my new ALIX board (based on AMD Geode) and found xen is crashing on it. The output of it is attached. Regards, Daniel -- cat /proc/cpuinfo -- processor : 0 vendor_id : AuthenticAMD cpu family : 5 model : 10 model name : Geode(TM) Integrated Processor by AMD

flight 9800 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/9800/ Regressions :-( Tests which did not succeed and are blocking: test-amd64-amd64-xl-sedf 14 guest-localmigrate/x10 fail REGR. vs. 9789 Tests which are failing intermittently (not blocking): test-amd64-i386-xl-win-vcpus1 12 guest-localmigrate/x10 fail pass in 9799 test-amd64-i386-win