xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@linaro.org>
To: Chen Baozi <baozich@gmail.com>
Cc: Xen Developer List <xen-devel@lists.xen.org>
Subject: Re: Problems when creating domU on OMAP5
Date: Wed, 18 Sep 2013 15:48:51 +0100	[thread overview]
Message-ID: <5239BD53.4050002@linaro.org> (raw)
In-Reply-To: <20130918020644.GA10532@cbz-workstation>

On 09/18/2013 03:06 AM, Chen Baozi wrote:
> On Tue, Sep 17, 2013 at 12:47:35PM +0100, Julien Grall wrote:
>> On 09/16/2013 02:18 PM, 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
>> Can you to copy the output in pastebin of the following command?
>> xl -vvv create -f config -d
> 
> See: http://pastebin.com/kGjQUM86

What is your dom0 linux configuration file?
Did you enable at least the following config:
/* For dom0 */
CONFIG_XEN_BLKDEV_BACKEND=y
CONFIG_XEN_NETDEV_BACKEND=y

/* For the guest */
CONFIG_XEN_BLKDEV_FRONTEND=y
CONFIG_XEN_NETDEV_FRONTEND=y

-- 
Julien Grall

  reply	other threads:[~2013-09-18 14:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-16 13:18 Problems when creating domU on OMAP5 Chen Baozi
2013-09-16 13:42 ` 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 [this message]
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=5239BD53.4050002@linaro.org \
    --to=julien.grall@linaro.org \
    --cc=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).