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

Re: [Xen-devel] Re: Panic on cpu0


  • To: Keir Fraser <keir@xxxxxxx>
  • From: ZhouPeng <zpengxen@xxxxxxxxx>
  • Date: Thu, 16 Dec 2010 19:24:51 +0800
  • Cc: "Xen-Devel \(E-mail\)" <xen-devel@xxxxxxxxxxxxxxxxxxx>, stephen.spector@xxxxxxxxxx, keir.fraser@xxxxxxxxxxxxx
  • Delivery-date: Thu, 16 Dec 2010 03:25:36 -0800
  • 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=ona+fponTWW5T3pXbe4xvcKHQm0Sn1hoWjFwi1zLSa5cz8BtxqjEq5bkMPAIG+Z80I IggbzzNnF/fXW+4sRKHeHdHwiCSJ56m5bk6GQPRvYVxL/6H/Lakoc8B+whObvMpwLLZ+ eyYTlDzoi8sxNmCP0Xs2wwSVdUnAuks0tk2KE=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Thank you for your reply.

We want to  work in 32-bit system.
And fortunately we don't need IOMMU and passthr at the present.

There is another problem:
xend start failed
err msg is:
xen.lowlevel.xc.Error: (1, "Internal error"), 'Could not obtain handle on privileged command interface (2 =  No such file or directory)'

I find there is nothing in "/proc/xen/" but there is privcmd.o in "bulid-linux-2.6-pvos_x86_32/drivers/xen/xenfs/"

2010/12/16 Keir Fraser <keir@xxxxxxx>
Could you build a 64-bit hypervisor instead? In all honesty, the 32-bit
build gets hardly any testing these days, and not much love.

 -- Keir

On 16/12/2010 09:41, "ZhouPeng" <zpengxen@xxxxxxxxx> wrote:

> The bug exist in iommu(Intel VT-d) support code.
>
> After I disabled the vt-d in bios, system can boot properly.
>
> 2010/12/16 ZhouPeng <zpengxen@xxxxxxxxx>
>> The err msg appears in
>> void *map_domain_page(unsigned long mfn)
>>       BUG_ON(idx >= MAPCACHE_ENTRIES);
>>
>> printk idx is 1024 and BUG_ON is called.
>>
>> I print  Xen call trace msg:
>>
>> [<ffcd3c2>]  map_domain_page+0x1a2/0x230
>> [<ff1cd718>] unmap_domain_page+0x148/0x160
>>                    addr_to_dma_page_maddr+0x1f6/0x250
>>                    __find_next_zero_bit+0x80/0x90
>>                    intel_iommu_map_page+0x14a/0x250
>>                    domain_context_mapping+0x14a/0x250
>>                    rmrr_identity_mapping+0xb7/0x120
>>                    intel_iommu_dom0_init+0x143/0x1eb
>>                    construct_dom0+0x138f/0x16b0
>>                    __start_xen+0x109a/0x1680
>>                    e820nf+0x0/0x4
>>                    __high_start+0x58/0x5a
>>
>> 2010/12/16 Pasi Kärkkäinen <pasik@xxxxxx>
>>
>>> On Thu, Dec 16, 2010 at 03:41:17PM +0800, ZhouPeng wrote:
>>>>    (XEN) Panic on CPU 0:
>>>>    (XEN) Xen BUG at domain_page.c:102
>>>>
>>>>    Any solutions?
>>>>
>>>
>>> You need to post the full boot log, including all output from both Xen and
>>> dom0 Linux.
>>> See: http://wiki.xen.org/xenwiki/XenSerialConsole
>>>
>>> -- Pasi
>>>
>>>>    2010/12/16 ZhouPeng <[1]zpengxen@xxxxxxxxx>
>>>>
>>>>      Hi all,
>>>>
>>>>      I build xen4.1 from the tarbll (with kernel 2.6.32.26 downloaded by
>>>>      default) on fedora8.
>>>>
>>>>      After installing, I get the err msg on startup:
>>>>
>>>>      (XEN) Panic on CPU 0:
>>>>      (XEN) Xen BUG at domain_page.c:102
>>>>
>>>>      5 seconds later, the machine reboot.
>>>>
>>>>      How to deal with this problem.
>>>>
>>>>      Thanks,
>>>>      --
>>>>      Zhou Peng
>>>>      My daily E-Mail: [2]ailvpeng25@xxxxxxxxx
>>>>
>>>>    --
>>>>    Zhou Peng
>>>>    My daily E-Mail: [3]ailvpeng25@xxxxxxxxx
>>>>
>>>> References
>>>>
>>>>    Visible links
>>>>    1. mailto:zpengxen@xxxxxxxxx
>>>>    2. mailto:ailvpeng25@xxxxxxxxx
>>>>    3. mailto:ailvpeng25@xxxxxxxxx
>>>
>>>> _______________________________________________
>>>> Xen-devel mailing list
>>>> Xen-devel@xxxxxxxxxxxxxxxxxxx
>>>> http://lists.xensource.com/xen-devel
>>>
>>
>>





--
Zhou Peng
My daily E-Mail: ailvpeng25@xxxxxxxxx
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

 


Rackspace

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