From: Chen Baozi <baozich@gmail.com>
To: Xen Developer List <xen-devel@lists.xen.org>
Subject: Problems when creating domU on OMAP5
Date: Mon, 16 Sep 2013 21:18:28 +0800 [thread overview]
Message-ID: <20130916131828.GA15286@cbz-workstation> (raw)
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
Any ideas?
Baozi
next reply other threads:[~2013-09-16 13:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-16 13:18 Chen Baozi [this message]
2013-09-16 13:42 ` Problems when creating domU on OMAP5 Chen Baozi
2013-09-17 11:54 ` Julien Grall
2013-09-18 2:08 ` Chen Baozi
2013-09-30 8:30 ` Chen Baozi
2013-10-07 12:36 ` Julien Grall
2013-11-07 6:14 ` Chen Baozi
2013-11-07 8:23 ` Ian Campbell
2013-09-17 11:47 ` Julien Grall
2013-09-18 2:06 ` Chen Baozi
2013-09-18 14:48 ` Julien Grall
2013-09-18 16:12 ` Andrii Anisov
2013-09-19 13:39 ` Chen Baozi
2013-09-24 0:39 ` Vaibhav Bedia
2013-09-25 9:12 ` Chen Baozi
2013-09-25 13:39 ` Vaibhav Bedia
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130916131828.GA15286@cbz-workstation \
--to=baozich@gmail.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).