This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] problem using compiled kernel -- Sisu

To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: Re: [Xen-devel] problem using compiled kernel -- Sisu
From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Date: Wed, 4 Aug 2010 10:24:51 -0400
Cc: Sander Eikelenboom <linux@xxxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>, Sisu Xi <xisisu@xxxxxxxxx>
Delivery-date: Wed, 04 Aug 2010 07:26:06 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4C584B54.1030407@xxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <AANLkTimRQ2+CnfaXiJ=Db0TiGEbj3dqgFNmZTiJ=kJFP@xxxxxxxxxxxxxx> <AANLkTi=LsUjaLAXRE0zh3DExvJg8qwrpezU2aT2Y4b_Q@xxxxxxxxxxxxxx> <4C521E3B.7060400@xxxxxxxx> <AANLkTikdY1bKEOvPAzjXtTGNRVDRmi60zO23OnPzixqP@xxxxxxxxxxxxxx> <AANLkTi=xgw3vWs2Azm1W9Vn5y0QNbjvmkU-3LU0JkEec@xxxxxxxxxxxxxx> <AANLkTikp5MH8=PR4_itCZ4b09mQKqzvwJF1-L1CqeAG6@xxxxxxxxxxxxxx> <4C56F82B.3010208@xxxxxxxx> <AANLkTimGc+b1KuKWi8n6+_j1T0oZ8o83UJPW0sELwzho@xxxxxxxxxxxxxx> <AANLkTi=rGL9=BtSkEESGWLcVTXXbJWJTTCMdigtGyXoY@xxxxxxxxxxxxxx> <4C584B54.1030407@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.20 (2009-12-10)
On Tue, Aug 03, 2010 at 10:01:08AM -0700, Jeremy Fitzhardinge wrote:
>  On 08/02/2010 08:25 PM, Sisu Xi wrote:
> >
> >Fedora release 13 (Goddard)
> >
> >Kernel on an x86_64 (/dev/hvc0)
> >
> >
> >
> >flamenco118.cse.wustl.edu login: (XEN) mm.c:3852:d0 Bad page
> >00000000000b918f: ed=ffff830124ff0000(0), sd=ffff830124ff0000,
> >caf=8000000000000002, taf=7400000000000001
> >(XEN) mm.c:3852:d0 Bad page 00000000000b6850: ed=ffff830124ff0000(0),
> >sd=ffff830124ff0000, caf=8000000000000002, taf=7400000000000001

That is interesting. I see those when I used PVGRUB and launched
a guest that would utilize Xen-SWIOTLB. Thought I wouldn't have the 'd0'
but rather the guest domain id.

I did found out that if I did not use PVGRUB but just used the kernel

kernel = "/mnt/tmp/vmlinuz-2.6.34NEB"
ramdisk = "/mnt/tmp/initramfs-2.6.34NEB.img"
extra ="ro root=/dev/mapper/vg_vs03-lv_root rd_LVM_LV=vg_vs03/lv_root 
rd_LVM_LV=vg_vs03/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 
SYSFONT=latarcyrheb-sun16 KEYTABLE=us console=hvc0 debug init=/bin/bash"

#kernel = "/usr/lib/xen/boot/pv-grub-x86_64.gz"
#kernel = "/home/konrad/ssd/neb/xen/stubdom/mini-os-x86_64-grub/mini-os.gz"
#extra = "(hd0,0)/grub/menu.lst"

these errors would disappear. So I blamed it on MiniOS, but haven't gone
any further than that :-(

FYI, this is what I see on the serial console:
(XEN) mm.c:4147:d1 Bad page 00000000001321bb: ed=ffff830188ce0000(1),
sd=ffff830188ce0000, caf=8000000000000002, taf=7400000000000001
[    0.000000] Kernel panic - not syncing: DMA(-12): Failed to exchange
pages allocated for DMA with Xen! We either don't have the permission or
you do not have enoughfree memory under 4GB!
[    0.000000] 
[    0.000000] Pid: 0, comm: swapper Not tainted 2.6.34NEB #1
[    0.000000] Call Trace:
[    0.000000]  [<ffffffff814536ac>] panic+0x73/0xee
[    0.000000]  [<ffffffff810052c2>] ?
[    0.000000]  [<ffffffff818c6946>] xen_swiotlb_init+0x10a/0x142
[    0.000000]  [<ffffffff8145ceb5>] ? _etext+0x0/0x3

I wonder if he is doing some sort of exchange MFNs and that triggers

Sisu, can you make your Xen command line be as so:
 guest_loglvl=all loglvl=all console=com1,vga com1=115200,8n1 console_to_ring 

The 'console_to_ring' is of interest here.

Xen-devel mailing list