similar to: latest pv_ops dom0 (2.6.29-rc6) crashes / unhandled page fault

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

Xen 3.2.1-rc1 64 bit Dom0: 2.6.16.33 PAE DomU: 2.6.18.8 (from a pull a few weeks ago) If you need the symbols, there from the same Xen I linked to in my post from a few days ago... (XEN) mm.c:3498:d4 ptwr_emulate: could not get_page_from_l1e() (XEN) Unhandled page fault in domain 4 on VCPU 0 (ec=0003) (XEN) Pagetable walk from 00000000c08187f0: (XEN) L4[0x000] = 00000004dfa38027

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 =

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)

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! cc'd to freebsd-security@ as somebody there may correct me, cc'd to secteam@ as maintaner of security/portaudit. On Sun, 28 Aug 2005 10:14:21 +0930 Ian Moore wrote: > I've just updated my acroread port to 7.0.1 & was surprised when portaudit > still listed it as a vulnerability. I think it is portaudit problem. > According to

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

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 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 Jeremy & Keir, sorry to be persistent, but the problem that pvops0 kernel 2.6.32.x still does not boot if x > 18 on my machines (and on many other machines, see this mailing list) is not solved yet. Shouldn''t this be a great focus of debugging and fixing? What is the point of having releases for 4.0.2 or 4.1 if I don''t have a dom0 kernel? The last time I tried

I am working on some other bugs and perf issues - and while working I noticed that both sparse and Coverity have reported some issues with Xen drivers. Please see attached various bug-fixes that I am proposing for 3.6.

(This is a continuation of "[PATCH v9] xen/grant-table: Avoid m2p_override during mapping") The grant mapping API does m2p_override unnecessarily: only gntdev needs it, for blkback and future netback patches it just cause a lock contention, as those pages never go to userspace. Therefore this series does the following: - the bulk of the original function (everything after the mapping

(This is a continuation of "[PATCH v9] xen/grant-table: Avoid m2p_override during mapping") The grant mapping API does m2p_override unnecessarily: only gntdev needs it, for blkback and future netback patches it just cause a lock contention, as those pages never go to userspace. Therefore this series does the following: - the bulk of the original function (everything after the mapping

Hi everyone, I am very excited to see that dom0 pvops is finally coming close to working, so I wanted to give it a try. >From the description it was not clear to me which kernel to chose as base for the patches.hg, so I took the latest (that was ~ 2 weeks ago) kernel on git.kernel.org I could find (post-2.6.28 git tip at that point). I managed to more or less apply all of the patches in the

Hi Ingo, Here''s the chunk of patches to add Xen Dom0 support (it''s probably worth creating a new xen/dom0 topic branch for it). A dom0 Xen domain is basically the same as a normal domU domain, but it has extra privileges to directly access hardware. There are two issues to deal with: - translating to and from the domain''s pseudo-physical addresses and real machine

Hello, First at all, thanks for the great program, I'm enjoying so much. :) I'm adding ogg stream support to my client for Mac OS X. While it works perfectly with shoutcast and mp3 icecast1, I have buffer problems with icecast2/ogg/vorbis. My client, like iTunes (Apple's client - mp3), doesn't pre-bufferize on the first try. If the connection is fast enough, even a 128KB

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

Accelerated msix entry is initialized to zero when msixtbl_pt_register is called. This doesn''t match the value from qemu side, although pirq may already be mapped and binded in qemu side. Kernel will get wrong value when reading msix info. Signed-off-by: Zhenzhong Duan <zhenzhong.duan@oracle.com> Tested-by: Yuval Shaia <yuval.shaia@oracle.com> --- tools/libxc/xc_domain.c

The hypervisor side changes for XSA-46 require the tool stack to now always map the guest pIRQ before granting access permission to the underlying host IRQ (GSI). This in particular requires that pciif.py no longer can skip this step (assuming qemu would do it) for HVM guests. This in turn exposes, however, an inconsistency between xend and qemu: The former wants to always establish 1:1 mappings