[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Kernel panic on booting 2.6.32.16 pvops kernel


  • To: Adit Ranadive <adit.262@xxxxxxxxx>
  • From: Sean Shoufu Luo <luoshoufu@xxxxxxxxx>
  • Date: Thu, 22 Jul 2010 14:11:55 +0800
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Wed, 21 Jul 2010 23:13:11 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=OEOetTQ10aIv2KHsv05IiYOZUV5gHLZ8T26DPKc3ciHhSlcBNq0aY0TSvlg/vWUVjX dnLKt9b41Cdp8S8GHIDdhICt8Qe5ySDSuaajw9tgoY2t2en3XIJfFTFyiJ0Qkl3tprmE tsgmP4U2JFuWAXyOdSo+uqT1gB4lKbDbcq4T0=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

It seems out of memory, you can try to add dom0_mem=512M after 'kernel /xen.gz'


On Thu, Jul 22, 2010 at 1:40 PM, Adit Ranadive <adit.262@xxxxxxxxx> wrote:
Im currently running the xen 4.0.1-rc5-pre version with the linux 2.6.32.16 as the pvops kernel.
I get this kernel panic when booting into the dom0 :

[    6.003753] Initializing CPU#0
[    6.011036] DMA: Placing 64MB software IO TLB between ffff880020000000 - ffff880024000000
[    6.011044] DMA: software IO TLB at phys 0x20000000 - 0x24000000
[    6.011047] xen_swiotlb_fixup: buf=ffff880020000000 size=67108864
[    6.018646] 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!
[    6.018647]
[    6.018655] Pid: 0, comm: swapper Not tainted 2.6.32.16 #1
[    6.018659] Call Trace:
[    6.018668]  [<ffffffff8104cf93>] panic+0xa0/0x166
[    6.018676]  [<ffffffff8100d98e>] ? xen_create_contiguous_region+0xea/0xfc
[    6.018683]  [<ffffffff811c8b8f>] ? xen_swiotlb_fixup+0x80/0xa8
[    6.018689]  [<ffffffff817ffc55>] xen_swiotlb_init+0x5c/0x5e
[    6.018695]  [<ffffffff817e3f15>] pci_xen_swiotlb_init+0x17/0x24
[    6.018701]  [<ffffffff817e6cb7>] pci_iommu_alloc+0x70/0x79
[    6.018706]  [<ffffffff817f1878>] mem_init+0x2b/0xf5
[    6.018712]  [<ffffffff817df9fb>] start_kernel+0x1b8/0x3e9
[    6.018717]  [<ffffffff817df2c3>] x86_64_start_reservations+0xae/0xb2
[    6.018723]  [<ffffffff817e265c>] xen_start_kernel+0x451/0x458

Following is the grub config:
title Xen 4.0.1 Testing - Linux 2.6.32.16 pvops
    root (hd0,0)
    kernel /xen.gz noreboot loglvl=all guest_loglvl=all iommu=pv console=tty1 console=com2 com2=57600,8n1
    module /vmlinuz-2.6.32.16 ro root=/dev/vg1/root loglevel=10 swiotlb=force earlyprintk=xen xencons=ttyS1 console=ttyS1
    module /initrd-2.6.32.16.img
    savedefault 0

Im running this on a Dell R610 Poweredge Server with Intel X5550 processors.
Ive tried this with both swiotlb turned on and off. It gives the same kernel panic. Any suggestions or ideas why this is happening?

Thanks,
Adit


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.