|
xen-devel
Re: [Xen-devel] Re: Panic on cpu0
On Thu, Dec 16, 2010 at 11:25:49PM +0800, ZhouPeng wrote:
> Hi Pasi,
>
> How to build and load 32bit dom0 in 64bit Xen hypervisor?
>
> How to build 64 bit Xen hypervisor on my Linux 32 bits fc8 pls?
>
Usually you build them separately, maybe on different servers,
or on different VMs, or on different chroot..
ie. have a 64bit environment for building the hypervisor,
and 32bit environment to build the dom0 kernel and xen tools/userland.
-- Pasi
> 2010/12/16 Pasi Kärkkäinen <[1]pasik@xxxxxx>
>
> On Thu, Dec 16, 2010 at 07:24:51PM +0800, ZhouPeng wrote:
> > Thank you for your reply.
> >
> > We want to work in 32-bit system.
> >
>
> You know you can have a 32bit dom0 kernel running on 64bit Xen
> hypervisor?
>
> -- Pasi
> > 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 <[1][2]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" <[2][3]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 <[3][4]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 <[4][5]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: [5][6]http://wiki.xen.org/xenwiki/XenSerialConsole
> > >>>
> > >>> -- Pasi
> > >>>
> > >>>> 2010/12/16 ZhouPeng <[1][6][7]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][7][8]ailvpeng25@xxxxxxxxx
> > >>>>
> > >>>> --
> > >>>> Zhou Peng
> > >>>> My daily E-Mail: [3][8][9]ailvpeng25@xxxxxxxxx
> > >>>>
> > >>>> References
> > >>>>
> > >>>> Visible links
> > >>>> 1. mailto:[9][10]zpengxen@xxxxxxxxx
> > >>>> 2. mailto:[10][11]ailvpeng25@xxxxxxxxx
> > >>>> 3. mailto:[11][12]ailvpeng25@xxxxxxxxx
> > >>>
> > >>>> _______________________________________________
> > >>>> Xen-devel mailing list
> > >>>> [12][13]Xen-devel@xxxxxxxxxxxxxxxxxxx
> > >>>> [13][14]http://lists.xensource.com/xen-devel
> > >>>
> > >>
> > >>
> >
> > --
> > Zhou Peng
> > My daily E-Mail: [14][15]ailvpeng25@xxxxxxxxx
> >
> > References
> >
> > Visible links
> > 1. mailto:[16]keir@xxxxxxx
> > 2. mailto:[17]zpengxen@xxxxxxxxx
> > 3. mailto:[18]zpengxen@xxxxxxxxx
> > 4. mailto:[19]pasik@xxxxxx
> > 5. [20]http://wiki.xen.org/xenwiki/XenSerialConsole
> > 6. mailto:[21]zpengxen@xxxxxxxxx
> > 7. mailto:[22]ailvpeng25@xxxxxxxxx
> > 8. mailto:[23]ailvpeng25@xxxxxxxxx
> > 9. mailto:[24]zpengxen@xxxxxxxxx
> > 10. mailto:[25]ailvpeng25@xxxxxxxxx
> > 11. mailto:[26]ailvpeng25@xxxxxxxxx
> > 12. mailto:[27]Xen-devel@xxxxxxxxxxxxxxxxxxx
> > 13. [28]http://lists.xensource.com/xen-devel
> > 14. mailto:[29]ailvpeng25@xxxxxxxxx
>
> --
> Zhou Peng
> My daily E-Mail: [30]ailvpeng25@xxxxxxxxx
>
> References
>
> Visible links
> 1. mailto:pasik@xxxxxx
> 2. mailto:keir@xxxxxxx
> 3. mailto:zpengxen@xxxxxxxxx
> 4. mailto:zpengxen@xxxxxxxxx
> 5. mailto:pasik@xxxxxx
> 6. http://wiki.xen.org/xenwiki/XenSerialConsole
> 7. mailto:zpengxen@xxxxxxxxx
> 8. mailto:ailvpeng25@xxxxxxxxx
> 9. mailto:ailvpeng25@xxxxxxxxx
> 10. mailto:zpengxen@xxxxxxxxx
> 11. mailto:ailvpeng25@xxxxxxxxx
> 12. mailto:ailvpeng25@xxxxxxxxx
> 13. mailto:Xen-devel@xxxxxxxxxxxxxxxxxxx
> 14. http://lists.xensource.com/xen-devel
> 15. mailto:ailvpeng25@xxxxxxxxx
> 16. mailto:keir@xxxxxxx
> 17. mailto:zpengxen@xxxxxxxxx
> 18. mailto:zpengxen@xxxxxxxxx
> 19. mailto:pasik@xxxxxx
> 20. http://wiki.xen.org/xenwiki/XenSerialConsole
> 21. mailto:zpengxen@xxxxxxxxx
> 22. mailto:ailvpeng25@xxxxxxxxx
> 23. mailto:ailvpeng25@xxxxxxxxx
> 24. mailto:zpengxen@xxxxxxxxx
> 25. mailto:ailvpeng25@xxxxxxxxx
> 26. mailto:ailvpeng25@xxxxxxxxx
> 27. mailto:Xen-devel@xxxxxxxxxxxxxxxxxxx
> 28. http://lists.xensource.com/xen-devel
> 29. mailto:ailvpeng25@xxxxxxxxx
> 30. mailto:ailvpeng25@xxxxxxxxx
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
Home