[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] Problems when creating domU on OMAP5
On Tue, Sep 17, 2013 at 12:54:37PM +0100, Julien Grall wrote: > On 09/16/2013 02:42 PM, Chen Baozi wrote: > >On Mon, Sep 16, 2013 at 09:18:28PM +0800, Chen Baozi wrote: > >>Hi all, > >> > >>I tried to create a domU on OMAP5 today. But it seems there are still some > >>problems to solve before I can successfully creat it. > >> > >>I first cloned Julien's arndale-domU-3.9 branch which mentioned in wiki. > >>Then I modified gic addresses xenvm-4.2.dts to meet OMAP5432 requirement: > >> > >>--- a/arch/arm/boot/dts/xenvm-4.2.dts > >>+++ b/arch/arm/boot/dts/xenvm-4.2.dts > >>@@ -49,13 +49,13 @@ > >> reg = <0 0x80000000 0 0x08000000>; > >> }; > >> > >>- gic: interrupt-controller@2c001000 { > >>+ gic: interrupt-controller@48211000 { > >> compatible = "arm,cortex-a15-gic", "arm,cortex-a9-gic"; > >> #interrupt-cells = <3>; > >> #address-cells = <0>; > >> interrupt-controller; > >>- reg = <0 0x10481000 0 0x1000>, > >>- <0 0x10482000 0 0x100>; > >>+ reg = <0 0x48211000 0 0x1000>, > >>+ <0 0x48212000 0 0x1000>; > >> }; > >> > >> timer { > >> > >>And make the kernel image as wiki said: > >> > >>$ cat arch/arm/boot/zImage arch/arm/boot/xenvm-4.2.dtb > image > >> > >>Write a config file used by xl like: > >> > >>kernel = "/root/domU/image" > >>memory = "128" > >>name = "domU" > >>vcpus = 1 > >>disk = [ 'phy:/dev/loop0,xvda,w' ] > >> > >>Setup loop device: > >> > >>$ losetup /dev/loop0 /root/domU/xen-arm.img > >> > >>which xen-arm.img is the a bootable rootfs. > >> > >>Finally I execute xl to create the domU: > >> > >>$ sudo xl create -f config -d > >>Parsing config from config > >>unable to format domain config as JSON (YAJL:1) > >>[ 80.685264] Failed to unmap pfn:9bce5 rc:-2 > >>[ 80.691741] Failed to unmap pfn:9e7da rc:-2 > >>[ 80.696310] Failed to unmap pfn:9bce5 rc:-2 > >>[ 80.702494] Failed to unmap pfn:9ba57 rc:-2 > >>[ 80.706932] Failed to unmap pfn:9bce3 rc:-2 > >>[ 80.718394] Failed to unmap pfn:9bce2 rc:-2 > >>libxl: error: libxl_device.c:894:device_backend_callback: unable to add > >>device with path /local/domain/0/backend/vbd/1/51712 > >>libxl: error: libxl_create.c:932:domcreate_launch_dm: unable to add disk > >>devices > >>libxl: error: libxl_device.c:894:device_backend_callback: unable to remove > >>device with path /local/domain/0/backend/vbd/1/51712 > >>libxl: error: libxl.c:1451:devices_destroy_cb: libxl__devices_destroy > >>failed for 1 > >>(XEN) mm.c:1092:d0 gnttab_mark_dirty not implemented yet > >> > > > >Besides, after few minutes of executing "xl create" command, there are > >continuous kernel oops message such as: > > I suspect an interrupt problem. I have a patch series that should > fix the different issues with the interrupts, but I didn't take time > to rewrite properly :(. > > Can you give a try to the following branch (and your patches) on the omap5? > > git clone -b interrupts-v1 > git://xenbits.xen.org/people/julieng/xen-unstable.git > > Thanks, Hi Julien, I've ported the top five patches from your interrupts-v1 branch and tested it on OMAP5. It caused stucks while create the domU. And here is the dmesg: http://pastebin.com/QF0jAyCm The commit ID of five patches I ported from interrupts-v1 are: 68d67c0e1e3ba86b99fdc5a19b014c3b642d1edd e638f50cb297a6c243738ddb98ddf69dd27633ee 439a8eea145f1596d955e15ef5ef5672fc876511 34ef513d9710a9ded47263d4c4fc2896b03b051c f906637c38e3f1431a055ccd5adc4b5ea5c9acaf Any ideas? Cheers, Baozi _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |