similar to: Xen 3.2.1-rc1: ptwr_emulate: could not get_page_from_l1e()

Xen: 3.2.1-rc5 64bit Dom0: 2.6.18.8 (at cs 524) 32-pae DomU: 2.6.26-rc8 32-pae root at newark13:~# xm create -f /linodes/xencaker/xen.conf -c Using config file "/linodes/xencaker/xen.conf". Started domain xencaker root at newark13:~# root at newark13:~# xm dmesg ... (XEN) traps.c:413:d332 Unhandled invalid opcode fault/trap [#6] on VCPU 0 [ec=0000] (XEN)

Hi, Can anybody advise me how to debug this crash? it happens when I try to start a 32 bit kernel on my 64 bit Xen system, the kernel is my own using opensuse 11.1 rc1 2.6.27.7 xen patches, the kernel works as 32 and 64 bit dom0, and as 64 bit domU PV, is there a technique to find out where in the kernel source the crash happens? i.e what line in the source code? (XEN) mm.c:707:d49 Error getting

Hi, We are running a Sun Fire X2100 with 4GB RAM. We followed the how-to which we posted on http://www.debian-administration.org/articles/423, using backports packages for a k7-machine. We have one Sun Fire X2100 running a 2.6.16-16 kernel from backports, which is working fine having used the same how-to. Now we are installing another X2100 using the 2.6.16-18 kernel, which is giving some major

Hi,Chris? I wonder which version of Xen did the para-Linux works with. I applied the patches, compiled them and tried them on both xen-3.0.2 and the latest xen-unstable. Both result in panics when booting Xen and complain as follows: (XEN) Domain 0 kernel supports features = { 00000005 }. (XEN) Domain 0 kernel requires features = { 00000005 }. (XEN) (XEN)

I was giving a try to Debian Xen packages (it looks very promising by the way ; I just happen to love the ? new ? grub which handles xen images, for instance!) ; I have a box which boots correctly with xen-hypervisor-3.0-i386_3.0.2+hg9697-2 and a 2.6.16 dom0 kernel, but crashes when trying to boot linux-image-2.6.17-2-xen-686_2.6.17-7 The result is the same on two boxen (my Pentium M laptop and a

Hello. log of the crashing boot process: http://pasik.reaktio.net/xen/pv_ops-dom0-debug/pv_ops-dom0-bootlog-14-xen331-linux-2.6.29-rc6-crash.txt 2.6.29-rc5 based pv_ops dom0 works on the same computer.. with the same Xen version. I tried with and without pci=nomsi. adding ''noapic'' doesn''t seem to help (I need that with 2.6.29-rc5 to make it work). Any ideas

I got latest (13601) yesterday evening. This doesn''t seem to work to do Restore (at least of the Windows test-image that I''ve been using for testing previously). The VM restores reasonably OK, but it jumps to an invalid address shortly after restoring, giving a D1 blue-screen error (DRIVER_IRQL_LESS_OR_EQUAL), which turns out to be "page-fault in driver" after I

Hi, current paravirt patchqueue dies with ... Checking if this processor honours the WP bit even in supervisor mode... Ok. general protection fault: 0000 [#1] SMP Modules linked in: CPU: 0 EIP: 0061:[<c01021a8>] Not tainted VLI EFLAGS: 00010013 (2.6.20-git8-default-hg770 #7) EIP is at xen_evtchn_do_upcall+0x56/0x94 eax: ffffffff ebx: 00000000 ecx: fbfb9000 edx: ffff8b04

Hi, current paravirt patchqueue dies with ... Checking if this processor honours the WP bit even in supervisor mode... Ok. general protection fault: 0000 [#1] SMP Modules linked in: CPU: 0 EIP: 0061:[<c01021a8>] Not tainted VLI EFLAGS: 00010013 (2.6.20-git8-default-hg770 #7) EIP is at xen_evtchn_do_upcall+0x56/0x94 eax: ffffffff ebx: 00000000 ecx: fbfb9000 edx: ffff8b04

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

I'm running CentOS 5.1 with all updates, and the xen kernel. For some reason the OS is not seeing the full amount of ram. #uname -a Linux CentOS-VM-A 2.6.18-53.1.21.el5xen #1 SMP Tue May 20 10:03:27 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux # free total used free shared buffers cached Mem: 6104064 3445136 2658928 0 1412236

Hi all, a newbie question. I''m trying to install lenny guest image (in an img file) on my lenny Dom0 by following the http://wiki.debian.org/Xen: xm create -c xm-debian.cfg install=true install-mirror=ftp://ftp.XX.debian.org/debian i created the xen-lenny-image.img using dd, format is ext3. disk is defined as (cfg file): disk =

Hello all, please tell me, is it possible (at least theoretically) to circumvent bug 622 [1] by using GRUB instead of /boot/loader to load FreeBSD kernel? Or it is silly idea: even if we bypass /boot/loader we will not be able to run FreeBSD kernel in a HVM-domain on a Intel-based host for some other reason? As far as I know, GRUB can''t load FreeBSD kernel directly, but only can

Hi, I am trying to release domU pages from page_list and xenpage_list after domU shutdown while retaining the rest of the domain information. To achieve this in __domain_finalise_shutdown i call domain_relinquish_resources. This is failing to release pages from page_list for type PGT_l2_page_tables and crashing dom0. To be specific, while testing on mini-os i saw that when

Hi All, I am not very familiar with xen details. Now I am thinking of building two privilged domain(domain 0 not driver domain) at boot time. The other question is that wether it is possible to create another domain 0 by domain-builder running in domain0? Does it make sense when domain 0 is shut down unexpectedly another domain 0 can run at once. Maybe it is absurd. I am looking forwards

Hello, When I install guest OS on xen using "xm create /path/of/file/ubuntu.cfg -c" , I am getting an error message *"Error*: Device 0 (*vif*) could not be connected. Hotplug scripts not working <http://markmail.org/message/24aj3qs6ddrtwdks>" . I also saw that hotplugs and udev are prerequisites to be installed before compiling xen. I could not find hotplugs in Yast.

Hello, When I install guest OS on xen using "xm create /path/of/file/ubuntu.cfg -c" , I am getting an error message *"Error*: Device 0 (*vif*) could not be connected. Hotplug scripts not working <http://markmail.org/message/24aj3qs6ddrtwdks>" . I also saw that hotplugs and udev are prerequisites to be installed before compiling xen. I could not find hotplugs in Yast.

Hey hope this opne is a "make senser". Has anyone tried the "Subject line" combo?, I''ve compiled a dozen src.rpm kernel 3.0 and 3.1 packages with no luck to try native upstream Dom0 kernel support with no success, just a kernel oops and constant reboots. I followed Fedora''s wiki on building a custom kernel, even used F16''s .config which also was a

Hey hope this opne is a "make senser". Has anyone tried the "Subject line" combo?, I''ve compiled a dozen src.rpm kernel 3.0 and 3.1 packages with no luck to try native upstream Dom0 kernel support with no success, just a kernel oops and constant reboots. I followed Fedora''s wiki on building a custom kernel, even used F16''s .config which also was a

2011/7/19 Stefano Stabellini <stefano.stabellini@eu.citrix.com>: > CC''ing Tim and xen-devel > > On Mon, 18 Jul 2011, Jiageng Yu wrote: >> 2011/7/16 Stefano Stabellini <stefano.stabellini@eu.citrix.com>: >> > On Fri, 15 Jul 2011, Jiageng Yu wrote: >> >> 2011/7/15 Jiageng Yu <yujiageng734@gmail.com>: >> >> > 2011/7/15