embeddedxen-devel

Re: [Embeddedxen-devel] xen-pxa270-qemu

[sreenaath v. <sre...@gm...>]

 Hi
I tried to run xen-arm on pxa270 emulated on qemu by following this link
http://lists.xensource.com/archives/html/xen-arm/2009-04/msg00001.html

I am not able to get in to dom0 console at all.

This is what I ve done
1. I installed the cross compiler arm-unknown-linux-gnuabi-gcc. The Linux
distro I use is Ubuntu 9.10.

2. I installed the qemu that came default with ubuntu 9.10 linux.

3. The I installed xen-pxa270-qemu from
https://sourceforge.net/projects/embeddedxen.

4. To compile and run it, this is what I did
    a) I untarred the tarball and did a 'make all' inside the
'xen-pxa270-qemu' folder. Before firing the make command, I set the
CROSS_COMPILE env variable to point to the cross compiler
'arm-unknown-linux-gnuabi-gcc'.

    b) Then after successful completion of make command, I followed the
instructions in
http://lists.xensource.com/archives/html/xen-arm/2009-05/msg00000.html

    c) When I run it in non-graphical mode with -nographic option in
qemu-system-arm, the console outputs that xen image is getting loaded and
linux image is getting loaded in dom0. After that nothing happens. I am not
able to enter anything in the command console as it only displays 'Hit Ctrl
'A'  three times to enter in to xen mode'. When I hit Ctrl + 'A' three time
it displays 'Hit Ctrl 'A'  three times to enter in to dom0'

   d) When I ran it, in Graphical mode I saw a black screen popping up and
in the command window I see the message "map addr 0x8297e80". After that
nothing happens. I am not able to see anything in the graphical screen too.


It would be extremely helpful if someone can tell me how to get in to dom0
console.


regards
sreenaath

Re: [Embeddedxen-devel] [XenARM] Re:xen-pxa270-qemu

[sreenaath v. <sre...@gm...>]

Hi
Thanks for the detailed info given in the wiki
http://sourceforge.net/apps/mediawiki/embeddedxen/index.php?title=GettingStarted
.

I am running in to a panic issue (panic at hypervisor.c) when trying to get
the system up and running (as  given in the wiki), which prevents xen from
booting.
This is what I have done.
1. I have a virtual machine having ubuntu-9.10 where I followed and
installed the packages as given in the wiki.

2. In addition to that, I did install the following packages, brctl,
uml-utilities (for 'tunctl') and uboot-mkimage as they were not there in my
ubuntu-9.10 VM.

3. Also I changed the /etc/wemu-ifup script as follows (added two more lines
to what is givien in the wiki for adding the bridge being linking it with
the tap0 interface.)
       /etc/qemu-ifup

       #!/bin/sh
       BRIDGE=br0
      #setup in promiscuous mode qemu's device
      echo ifconfig $1 0.0.0.0 promisc up
      ifconfig $1 0.0.0.0 promisc up
      echo brctl addbr $BRIDGE
      brctl addbr $BRIDGE
      #add it to the bridge
      echo brctl addif $BRIDGE $1
      brctl addif $BRIDGE $1

4. After that I created two dummy flash files 'flash1' and 'flash2' of sixe
32 MB as follows
 $> sudo dd if=/dev/zero of=./flash2 bs=32000000 count=1

5. Then I ran 'qemu' and got the panic at 'hypervisor.c' which I am giving
below. It would be great if you could let me know how to fix it and get it
running.

------------------------------------------------------------------------------------------------------------------------------------------
user@ubuntu:~/embeddedxen# sudo qemu-system-arm -localtime -M mainstone
-kernel ./xen/arch/arm/boot/uImage.mainstone -s -m 256 -pflash ./flash1
-pflash ./flash2 -net nic -net tap,ifname=tap0,script=/etc/qemu-ifup
ifconfig tap0 0.0.0.0 promisc up
brctl addbr br0
device br0 already exists; can't create bridge with the same name
brctl addif br0 tap0
map addr 0x82200a0
root@ubuntu:~/embeddedxen# sudo qemu-system-arm -localtime -M mainstone
-kernel ./xen/arch/arm/boot/uImage.mainstone -s -m 256 -pflash ./flash1
-pflash ./flash2 -net nic -net tap,ifname=tap0,script=/etc/qemu-ifup -serial
stdio
ifconfig tap0 0.0.0.0 promisc up
brctl addbr br0
device br0 already exists; can't create bridge with the same name
brctl addif br0 tap0
map addr 0x82200a0
Uncompressing Xen................................... done, booting the
kernel.
 __  __            _____  _   _____              _ _ _          _
 \ \/ /___ _ __   |___ / / | |___ /     ___ ___ | (_) |__  _ __(_)
  \  // _ \ '_ \    |_ \ | |   |_ \ __ / __/ _ \| | | '_ \| '__| |
  /  \  __/ | | |  ___) || |_ ___) |__| (_| (_) | | | |_) | |  | |
 /_/\_\___|_| |_| |____(_)_(_)____/    \___\___/|_|_|_.__/|_|  |_|

 http://www.cl.cam.ac.uk/netos/xen
 University of Cambridge Computer Laboratory

 Xen version 3.1.3-colibri (root@) (gcc version 4.1.2) Wed Feb 11 11:24:14
CET 2009
 EmbeddedXEN/PENAR Project - Reconfigurable Embedded Digital System (REDS)
Institute from HEIG-VD/Switzerland
 http://reds.heig-vd.ch

 Latest ChangeSet: unavailable

(XEN) Hypervisor area start at: 0xff000000 (virt)
(XEN) Physical RAM map:
(XEN)   00000000a0000000: 0000000004000000
(XEN) End of multi-kernel area (XEN+dom0/U) -> min_page: 0xa0100
(XEN) End of Xen Area: 2561MiB (2622464KiB)
(XEN) End of RAM: 0xa3f00000
(XEN) Boot allocator @ a0100000 - a0115000
(XEN) NUMA turned off
(XEN) Faking a node at 0000000000000000-00000000a3f00000
(XEN) xenheap: 00000000a0115000 - 00000000a0314fff
(XEN) xenheap(virt): ff115000 - ff314fff
(XEN) ### frametable: ff315000
(XEN) ### min_page: a0100
(XEN) ### ps = a0115000 maddr_to_virt(ps)=ff115000
maddr_to_page(ps)=ff3151f8
(XEN) Xen heap: 2MiB (2048kiB)
(XEN) ### first_valid_mfn = a0315
(XEN) ### max_page = a3f00
(XEN) Domain heap initialised: DMA width 32 bits
(XEN) Dom Heap: 15230 pages
(XEN) CPU: XScale-PXA270 [69054117] revision 7 (ARMv5TE)
(XEN) (GCD) xen/arch/arm/hypervisor/mm.c:2070:vector_pt_init():
alloc_xenheap_page
(XEN) Mapping I/O on mainstone...
(XEN) Init IRQ...
(XEN) Initing arch-IRQ...
(XEN) Init scheduler...
(XEN) Using scheduler: Simple EDF Scheduler (sedf)
(XEN) Initializing timer...
(XEN) Platform clock source oscr0 @ 3249600 Hz overflows in 660845 jiffies.
(XEN) Platform periodic timer is osmr0 @ 1000 Hz
(XEN) ### arch_domain create OK
(XEN) Xen BUG at xen/arch/arm/hypervisor/setup.c:464
(XEN) CPU: 0
(XEN) PC is at ff00eea8
(XEN) LR is at ff030ab0
(XEN) pc : [<ff00eea8>]    lr : [<ff030ab0>]
(XEN) sp : ff03ff40  ip : ff03ffb4  fp : ff03ffb0
(XEN) r10: ff052648  r9 : ff052528  r8 : 00000000
(XEN) r7 : ff052454  r6 : 00000000  r5 : ff0364b3  r4 : 000001d0
(XEN) r3 : 00000000  r2 : 00000000  r1 : 0000000a  r0 : ff059073
(XEN) Flags: nZCv  IRQs on  FIQs off  Mode SVC_32
(XEN) Control: 7977  Table: A0004000  DAC: 000000DF
(XEN)
(XEN) ****************************************
(XEN) Panic on CPU 0:
(XEN) Xen BUG at xen/arch/arm/hypervisor/setup.c:464
(XEN) ****************************************
(XEN)
(XEN) Manual reset required ('noreboot' specified)
(XEN) CPU: 0
(XEN) PC is at ff00eea8
(XEN) LR is at ff030a0c
(XEN) pc : [<ff00eea8>]    lr : [<ff030a0c>]
(XEN) sp : ff03ff14  ip : ff03ff88  fp : ff03ff84
(XEN) r10: ff052648  r9 : ff052528  r8 : 00000000
(XEN) r7 : ff052454  r6 : 00000000  r5 : 60000153  r4 : ff030ac0
(XEN) r3 : 00000000  r2 : 00000000  r1 : 0000000a  r0 : ff059071
(XEN) Flags: nZCv  IRQs on  FIQs off  Mode SVC_32
(XEN) Control: 7977  Table: A0004000  DAC: 000000DF
(XEN) [<ff00eeec>] (+0xff00eeec/0xff03a000) from [<ff030a1c>]
(+0xff030a1c/0xff03a000)
(XEN) [<ff030980>] (+0xff030980/0xff03a000) from [<ff030ac0>]
(+0xff030ac0/0xff03a000)
(XEN)  r3 = 00000000  r2 = 000001D0  r1 = FF0364B3  r0 = FF039970
(XEN)  r5 = FF0364B3  r4 = 000001D0
(XEN) [<ff030a84>] (+0xff030a84/0xff03a000) from [<ff008e58>]
(+0xff008e58/0xff00acc8)
(XEN)  r5 = FF05264C  r4 = 00000000
(XEN) [<ff0089b4>] (+0xff0089b4/0xff00acc8) from [<a0008028>] (???)
(XEN) machine_halt called: spinning....
------------------------------------------------------------------------------------------------------------------------------------------

Thanks :)

On Thu, Apr 22, 2010 at 12:56 AM, SAMBUC Lionel <lio...@he...>wrote:

>  Hi,
>
>
>
> Sorry for the delay, I will put online a short step by step procedure to
> compile and
>
> start EmbeddedXen, as well as a FAQ, starting with your questions.
>
> This will be available on the SourceForge web page of the project, I intend
> to have it
>
> online by the end of the day (17h00 GMT, 22nd April 2010).
>
>
>
> The web page is located at http://embeddedxen.sourceforge.net/, this is
> where
>
> you will find the most up to date information.
>
>
>
> Please continue to post any other question on this mailing list.
>
>
>
> Have a nice day,
>
>
>
> Lionel
>
>
>
> *From:* xen...@li... [mailto:
> xen...@li...] *On Behalf Of *sreenaath vasudevan
> *Sent:* mercredi 21 avril 2010 04:50
> *To:* xe...@li...
> *Subject:* [XenARM] Re:xen-pxa270-qemu
>
>
>
>  Hi
>
> I tried to run xen-arm on pxa270 emulated on qemu by following this link
>
> http://lists.xensource.com/archives/html/xen-arm/2009-04/msg00001.html
>
> I am not able to get in to dom0 console at all.
>
>
>
> This is what I ve done
>
> 1. I installed the cross compiler arm-unknown-linux-gnuabi-gcc. The Linux
> distro I use is Ubuntu 9.10.
>
>
>
> 2. I installed the qemu that came default with ubuntu 9.10 linux.
>
>
>
> 3. The I installed xen-pxa270-qemu from
> https://sourceforge.net/projects/embeddedxen.
>
>
>
> 4. To compile and run it, this is what I did
>
>     a) I untarred the tarball and did a 'make all' inside the
> 'xen-pxa270-qemu' folder. Before firing the make command, I set the
> CROSS_COMPILE env variable to point to the cross compiler
> 'arm-unknown-linux-gnuabi-gcc'.
>
>
>
>     b) Then after successful completion of make command, I followed the
> instructions in
> http://lists.xensource.com/archives/html/xen-arm/2009-05/msg00000.html
>
>
>
>     c) When I run it in non-graphical mode with -nographic option in
> qemu-system-arm, the console outputs that xen image is getting loaded and
> linux image is getting loaded in dom0. After that nothing happens. I am not
> able to enter anything in the command console as it only displays 'Hit Ctrl
> 'A'  three times to enter in to xen mode'. When I hit Ctrl + 'A' three time
> it displays 'Hit Ctrl 'A'  three times to enter in to dom0'
>
>
>
>    d) When I ran it, in Graphical mode I saw a black screen popping up and
> in the command window I see the message "map addr 0x8297e80". After that
> nothing happens. I am not able to see anything in the graphical screen too.
>
>
>
>
>
> It would be extremely helpful if someone can tell me how to get in to dom0
> console.
>
>
>
>
> --
> regards
> sreenaath
>



-- 
regards
sreenaath

Re: [Embeddedxen-devel] [XenARM] Re:xen-pxa270-qemu

[sreenaath v. <sre...@gm...>]

The panic is happening in the file hypervisor/setup.c and not in
hypervisor.c as i told in my previous post.
Sorry for the confusion.

On Thu, Apr 22, 2010 at 10:11 PM, sreenaath vasudevan <sre...@gm...
> wrote:

> Hi
> Thanks for the detailed info given in the wiki
> http://sourceforge.net/apps/mediawiki/embeddedxen/index.php?title=GettingStarted
> .
>
> I am running in to a panic issue (panic at hypervisor.c) when trying to get
> the system up and running (as  given in the wiki), which prevents xen from
> booting.
> This is what I have done.
> 1. I have a virtual machine having ubuntu-9.10 where I followed and
> installed the packages as given in the wiki.
>
> 2. In addition to that, I did install the following packages, brctl,
> uml-utilities (for 'tunctl') and uboot-mkimage as they were not there in my
> ubuntu-9.10 VM.
>
> 3. Also I changed the /etc/wemu-ifup script as follows (added two more
> lines to what is givien in the wiki for adding the bridge being linking it
> with the tap0 interface.)
>        /etc/qemu-ifup
>
>        #!/bin/sh
>        BRIDGE=br0
>       #setup in promiscuous mode qemu's device
>       echo ifconfig $1 0.0.0.0 promisc up
>       ifconfig $1 0.0.0.0 promisc up
>       echo brctl addbr $BRIDGE
>       brctl addbr $BRIDGE
>       #add it to the bridge
>       echo brctl addif $BRIDGE $1
>       brctl addif $BRIDGE $1
>
> 4. After that I created two dummy flash files 'flash1' and 'flash2' of sixe
> 32 MB as follows
>  $> sudo dd if=/dev/zero of=./flash2 bs=32000000 count=1
>
> 5. Then I ran 'qemu' and got the panic at 'hypervisor.c' which I am giving
> below. It would be great if you could let me know how to fix it and get it
> running.
>
>
> ------------------------------------------------------------------------------------------------------------------------------------------
> user@ubuntu:~/embeddedxen# sudo qemu-system-arm -localtime -M mainstone
> -kernel ./xen/arch/arm/boot/uImage.mainstone -s -m 256 -pflash ./flash1
> -pflash ./flash2 -net nic -net tap,ifname=tap0,script=/etc/qemu-ifup
> ifconfig tap0 0.0.0.0 promisc up
> brctl addbr br0
> device br0 already exists; can't create bridge with the same name
> brctl addif br0 tap0
> map addr 0x82200a0
> root@ubuntu:~/embeddedxen# sudo qemu-system-arm -localtime -M mainstone
> -kernel ./xen/arch/arm/boot/uImage.mainstone -s -m 256 -pflash ./flash1
> -pflash ./flash2 -net nic -net tap,ifname=tap0,script=/etc/qemu-ifup -serial
> stdio
> ifconfig tap0 0.0.0.0 promisc up
> brctl addbr br0
> device br0 already exists; can't create bridge with the same name
> brctl addif br0 tap0
> map addr 0x82200a0
> Uncompressing Xen................................... done, booting the
> kernel.
>  __  __            _____  _   _____              _ _ _          _
>  \ \/ /___ _ __   |___ / / | |___ /     ___ ___ | (_) |__  _ __(_)
>   \  // _ \ '_ \    |_ \ | |   |_ \ __ / __/ _ \| | | '_ \| '__| |
>   /  \  __/ | | |  ___) || |_ ___) |__| (_| (_) | | | |_) | |  | |
>  /_/\_\___|_| |_| |____(_)_(_)____/    \___\___/|_|_|_.__/|_|  |_|
>
>  http://www.cl.cam.ac.uk/netos/xen
>  University of Cambridge Computer Laboratory
>
>  Xen version 3.1.3-colibri (root@) (gcc version 4.1.2) Wed Feb 11 11:24:14
> CET 2009
>  EmbeddedXEN/PENAR Project - Reconfigurable Embedded Digital System (REDS)
> Institute from HEIG-VD/Switzerland
>  http://reds.heig-vd.ch
>
>  Latest ChangeSet: unavailable
>
> (XEN) Hypervisor area start at: 0xff000000 (virt)
> (XEN) Physical RAM map:
> (XEN)   00000000a0000000: 0000000004000000
> (XEN) End of multi-kernel area (XEN+dom0/U) -> min_page: 0xa0100
> (XEN) End of Xen Area: 2561MiB (2622464KiB)
> (XEN) End of RAM: 0xa3f00000
> (XEN) Boot allocator @ a0100000 - a0115000
> (XEN) NUMA turned off
> (XEN) Faking a node at 0000000000000000-00000000a3f00000
> (XEN) xenheap: 00000000a0115000 - 00000000a0314fff
> (XEN) xenheap(virt): ff115000 - ff314fff
> (XEN) ### frametable: ff315000
> (XEN) ### min_page: a0100
> (XEN) ### ps = a0115000 maddr_to_virt(ps)=ff115000
> maddr_to_page(ps)=ff3151f8
> (XEN) Xen heap: 2MiB (2048kiB)
> (XEN) ### first_valid_mfn = a0315
> (XEN) ### max_page = a3f00
> (XEN) Domain heap initialised: DMA width 32 bits
> (XEN) Dom Heap: 15230 pages
> (XEN) CPU: XScale-PXA270 [69054117] revision 7 (ARMv5TE)
> (XEN) (GCD) xen/arch/arm/hypervisor/mm.c:2070:vector_pt_init():
> alloc_xenheap_page
> (XEN) Mapping I/O on mainstone...
> (XEN) Init IRQ...
> (XEN) Initing arch-IRQ...
> (XEN) Init scheduler...
> (XEN) Using scheduler: Simple EDF Scheduler (sedf)
> (XEN) Initializing timer...
> (XEN) Platform clock source oscr0 @ 3249600 Hz overflows in 660845 jiffies.
> (XEN) Platform periodic timer is osmr0 @ 1000 Hz
> (XEN) ### arch_domain create OK
> (XEN) Xen BUG at xen/arch/arm/hypervisor/setup.c:464
> (XEN) CPU: 0
> (XEN) PC is at ff00eea8
> (XEN) LR is at ff030ab0
> (XEN) pc : [<ff00eea8>]    lr : [<ff030ab0>]
> (XEN) sp : ff03ff40  ip : ff03ffb4  fp : ff03ffb0
> (XEN) r10: ff052648  r9 : ff052528  r8 : 00000000
> (XEN) r7 : ff052454  r6 : 00000000  r5 : ff0364b3  r4 : 000001d0
> (XEN) r3 : 00000000  r2 : 00000000  r1 : 0000000a  r0 : ff059073
> (XEN) Flags: nZCv  IRQs on  FIQs off  Mode SVC_32
> (XEN) Control: 7977  Table: A0004000  DAC: 000000DF
> (XEN)
> (XEN) ****************************************
> (XEN) Panic on CPU 0:
> (XEN) Xen BUG at xen/arch/arm/hypervisor/setup.c:464
> (XEN) ****************************************
> (XEN)
> (XEN) Manual reset required ('noreboot' specified)
> (XEN) CPU: 0
> (XEN) PC is at ff00eea8
> (XEN) LR is at ff030a0c
> (XEN) pc : [<ff00eea8>]    lr : [<ff030a0c>]
> (XEN) sp : ff03ff14  ip : ff03ff88  fp : ff03ff84
> (XEN) r10: ff052648  r9 : ff052528  r8 : 00000000
> (XEN) r7 : ff052454  r6 : 00000000  r5 : 60000153  r4 : ff030ac0
> (XEN) r3 : 00000000  r2 : 00000000  r1 : 0000000a  r0 : ff059071
> (XEN) Flags: nZCv  IRQs on  FIQs off  Mode SVC_32
> (XEN) Control: 7977  Table: A0004000  DAC: 000000DF
> (XEN) [<ff00eeec>] (+0xff00eeec/0xff03a000) from [<ff030a1c>]
> (+0xff030a1c/0xff03a000)
> (XEN) [<ff030980>] (+0xff030980/0xff03a000) from [<ff030ac0>]
> (+0xff030ac0/0xff03a000)
> (XEN)  r3 = 00000000  r2 = 000001D0  r1 = FF0364B3  r0 = FF039970
> (XEN)  r5 = FF0364B3  r4 = 000001D0
> (XEN) [<ff030a84>] (+0xff030a84/0xff03a000) from [<ff008e58>]
> (+0xff008e58/0xff00acc8)
> (XEN)  r5 = FF05264C  r4 = 00000000
> (XEN) [<ff0089b4>] (+0xff0089b4/0xff00acc8) from [<a0008028>] (???)
> (XEN) machine_halt called: spinning....
>
> ------------------------------------------------------------------------------------------------------------------------------------------
>
> Thanks :)
>
>
> On Thu, Apr 22, 2010 at 12:56 AM, SAMBUC Lionel <lio...@he...>wrote:
>
>>  Hi,
>>
>>
>>
>> Sorry for the delay, I will put online a short step by step procedure to
>> compile and
>>
>> start EmbeddedXen, as well as a FAQ, starting with your questions.
>>
>> This will be available on the SourceForge web page of the project, I
>> intend to have it
>>
>> online by the end of the day (17h00 GMT, 22nd April 2010).
>>
>>
>>
>> The web page is located at http://embeddedxen.sourceforge.net/, this is
>> where
>>
>> you will find the most up to date information.
>>
>>
>>
>> Please continue to post any other question on this mailing list.
>>
>>
>>
>> Have a nice day,
>>
>>
>>
>> Lionel
>>
>>
>>
>> *From:* xen...@li... [mailto:
>> xen...@li...] *On Behalf Of *sreenaath vasudevan
>> *Sent:* mercredi 21 avril 2010 04:50
>> *To:* xe...@li...
>> *Subject:* [XenARM] Re:xen-pxa270-qemu
>>
>>
>>
>>  Hi
>>
>> I tried to run xen-arm on pxa270 emulated on qemu by following this link
>>
>> http://lists.xensource.com/archives/html/xen-arm/2009-04/msg00001.html
>>
>> I am not able to get in to dom0 console at all.
>>
>>
>>
>> This is what I ve done
>>
>> 1. I installed the cross compiler arm-unknown-linux-gnuabi-gcc. The Linux
>> distro I use is Ubuntu 9.10.
>>
>>
>>
>> 2. I installed the qemu that came default with ubuntu 9.10 linux.
>>
>>
>>
>> 3. The I installed xen-pxa270-qemu from
>> https://sourceforge.net/projects/embeddedxen.
>>
>>
>>
>> 4. To compile and run it, this is what I did
>>
>>     a) I untarred the tarball and did a 'make all' inside the
>> 'xen-pxa270-qemu' folder. Before firing the make command, I set the
>> CROSS_COMPILE env variable to point to the cross compiler
>> 'arm-unknown-linux-gnuabi-gcc'.
>>
>>
>>
>>     b) Then after successful completion of make command, I followed the
>> instructions in
>> http://lists.xensource.com/archives/html/xen-arm/2009-05/msg00000.html
>>
>>
>>
>>     c) When I run it in non-graphical mode with -nographic option in
>> qemu-system-arm, the console outputs that xen image is getting loaded and
>> linux image is getting loaded in dom0. After that nothing happens. I am not
>> able to enter anything in the command console as it only displays 'Hit Ctrl
>> 'A'  three times to enter in to xen mode'. When I hit Ctrl + 'A' three time
>> it displays 'Hit Ctrl 'A'  three times to enter in to dom0'
>>
>>
>>
>>    d) When I ran it, in Graphical mode I saw a black screen popping up and
>> in the command window I see the message "map addr 0x8297e80". After that
>> nothing happens. I am not able to see anything in the graphical screen too.
>>
>>
>>
>>
>>
>> It would be extremely helpful if someone can tell me how to get in to dom0
>> console.
>>
>>
>>
>>
>> --
>> regards
>> sreenaath
>>
>
>
>
> --
> regards
> sreenaath
>



-- 
regards
sreenaath

Re: [Embeddedxen-devel] [XenARM] Re:xen-pxa270-qemu

[ROSSIER D. <Dan...@he...>]

oups, just realized one thing: please use the last version from the git repository (just follow the instructions from the
GettingStarted wiki page); the .tar.gz which is available from "download" button is outdated; we will update it very soon.

Daniel

From: sreenaath vasudevan [mailto:sre...@gm...]
Sent: vendredi 23 avril 2010 04:14
To: emb...@li...
Subject: Re: [Embeddedxen-devel] [XenARM] Re:xen-pxa270-qemu

The panic is happening in the file hypervisor/setup.c and not in hypervisor.c as i told in my previous post.
Sorry for the confusion.
On Thu, Apr 22, 2010 at 10:11 PM, sreenaath vasudevan <sre...@gm...<mailto:sre...@gm...>> wrote:
Hi
Thanks for the detailed info given in the wiki http://sourceforge.net/apps/mediawiki/embeddedxen/index.php?title=GettingStarted.

I am running in to a panic issue (panic at hypervisor.c) when trying to get the system up and running (as  given in the wiki), which prevents xen from booting.
This is what I have done.
1. I have a virtual machine having ubuntu-9.10 where I followed and installed the packages as given in the wiki.
2. In addition to that, I did install the following packages, brctl, uml-utilities (for 'tunctl') and uboot-mkimage as they were not there in my ubuntu-9.10 VM.
3. Also I changed the /etc/wemu-ifup script as follows (added two more lines to what is givien in the wiki for adding the bridge being linking it with the tap0 interface.)
       /etc/qemu-ifup

       #!/bin/sh
       BRIDGE=br0
      #setup in promiscuous mode qemu's device
      echo ifconfig $1 0.0.0.0 promisc up
      ifconfig $1 0.0.0.0 promisc up
      echo brctl addbr $BRIDGE
      brctl addbr $BRIDGE
      #add it to the bridge
      echo brctl addif $BRIDGE $1
      brctl addif $BRIDGE $1

4. After that I created two dummy flash files 'flash1' and 'flash2' of sixe 32 MB as follows
 $> sudo dd if=/dev/zero of=./flash2 bs=32000000 count=1

5. Then I ran 'qemu' and got the panic at 'hypervisor.c' which I am giving below. It would be great if you could let me know how to fix it and get it running.

------------------------------------------------------------------------------------------------------------------------------------------
user@ubuntu:~/embeddedxen# sudo qemu-system-arm -localtime -M mainstone -kernel ./xen/arch/arm/boot/uImage.mainstone -s -m 256 -pflash ./flash1 -pflash ./flash2 -net nic -net tap,ifname=tap0,script=/etc/qemu-ifup
ifconfig tap0 0.0.0.0 promisc up
brctl addbr br0
device br0 already exists; can't create bridge with the same name
brctl addif br0 tap0
map addr 0x82200a0
root@ubuntu:~/embeddedxen# sudo qemu-system-arm -localtime -M mainstone -kernel ./xen/arch/arm/boot/uImage.mainstone -s -m 256 -pflash ./flash1 -pflash ./flash2 -net nic -net tap,ifname=tap0,script=/etc/qemu-ifup -serial stdio
ifconfig tap0 0.0.0.0 promisc up
brctl addbr br0
device br0 already exists; can't create bridge with the same name
brctl addif br0 tap0
map addr 0x82200a0
Uncompressing Xen................................... done, booting the kernel.
 __  __            _____  _   _____              _ _ _          _
 \ \/ /___ _ __   |___ / / | |___ /     ___ ___ | (_) |__  _ __(_)
  \  // _ \ '_ \    |_ \ | |   |_ \ __ / __/ _ \| | | '_ \| '__| |
  /  \  __/ | | |  ___) || |_ ___) |__| (_| (_) | | | |_) | |  | |
 /_/\_\___|_| |_| |____(_)_(_)____/    \___\___/|_|_|_.__/|_|  |_|

 http://www.cl.cam.ac.uk/netos/xen
 University of Cambridge Computer Laboratory

 Xen version 3.1.3-colibri (root@) (gcc version 4.1.2) Wed Feb 11 11:24:14 CET 2009
 EmbeddedXEN/PENAR Project - Reconfigurable Embedded Digital System (REDS) Institute from HEIG-VD/Switzerland
 http://reds.heig-vd.ch

 Latest ChangeSet: unavailable

(XEN) Hypervisor area start at: 0xff000000 (virt)
(XEN) Physical RAM map:
(XEN)   00000000a0000000: 0000000004000000
(XEN) End of multi-kernel area (XEN+dom0/U) -> min_page: 0xa0100
(XEN) End of Xen Area: 2561MiB (2622464KiB)
(XEN) End of RAM: 0xa3f00000
(XEN) Boot allocator @ a0100000 - a0115000
(XEN) NUMA turned off
(XEN) Faking a node at 0000000000000000-00000000a3f00000
(XEN) xenheap: 00000000a0115000 - 00000000a0314fff
(XEN) xenheap(virt): ff115000 - ff314fff
(XEN) ### frametable: ff315000
(XEN) ### min_page: a0100
(XEN) ### ps = a0115000 maddr_to_virt(ps)=ff115000 maddr_to_page(ps)=ff3151f8
(XEN) Xen heap: 2MiB (2048kiB)
(XEN) ### first_valid_mfn = a0315
(XEN) ### max_page = a3f00
(XEN) Domain heap initialised: DMA width 32 bits
(XEN) Dom Heap: 15230 pages
(XEN) CPU: XScale-PXA270 [69054117] revision 7 (ARMv5TE)
(XEN) (GCD) xen/arch/arm/hypervisor/mm.c:2070:vector_pt_init(): alloc_xenheap_page
(XEN) Mapping I/O on mainstone...
(XEN) Init IRQ...
(XEN) Initing arch-IRQ...
(XEN) Init scheduler...
(XEN) Using scheduler: Simple EDF Scheduler (sedf)
(XEN) Initializing timer...
(XEN) Platform clock source oscr0 @ 3249600 Hz overflows in 660845 jiffies.
(XEN) Platform periodic timer is osmr0 @ 1000 Hz
(XEN) ### arch_domain create OK
(XEN) Xen BUG at xen/arch/arm/hypervisor/setup.c:464
(XEN) CPU: 0
(XEN) PC is at ff00eea8
(XEN) LR is at ff030ab0
(XEN) pc : [<ff00eea8>]    lr : [<ff030ab0>]
(XEN) sp : ff03ff40  ip : ff03ffb4  fp : ff03ffb0
(XEN) r10: ff052648  r9 : ff052528  r8 : 00000000
(XEN) r7 : ff052454  r6 : 00000000  r5 : ff0364b3  r4 : 000001d0
(XEN) r3 : 00000000  r2 : 00000000  r1 : 0000000a  r0 : ff059073
(XEN) Flags: nZCv  IRQs on  FIQs off  Mode SVC_32
(XEN) Control: 7977  Table: A0004000  DAC: 000000DF
(XEN)
(XEN) ****************************************
(XEN) Panic on CPU 0:
(XEN) Xen BUG at xen/arch/arm/hypervisor/setup.c:464
(XEN) ****************************************
(XEN)
(XEN) Manual reset required ('noreboot' specified)
(XEN) CPU: 0
(XEN) PC is at ff00eea8
(XEN) LR is at ff030a0c
(XEN) pc : [<ff00eea8>]    lr : [<ff030a0c>]
(XEN) sp : ff03ff14  ip : ff03ff88  fp : ff03ff84
(XEN) r10: ff052648  r9 : ff052528  r8 : 00000000
(XEN) r7 : ff052454  r6 : 00000000  r5 : 60000153  r4 : ff030ac0
(XEN) r3 : 00000000  r2 : 00000000  r1 : 0000000a  r0 : ff059071
(XEN) Flags: nZCv  IRQs on  FIQs off  Mode SVC_32
(XEN) Control: 7977  Table: A0004000  DAC: 000000DF
(XEN) [<ff00eeec>] (+0xff00eeec/0xff03a000) from [<ff030a1c>] (+0xff030a1c/0xff03a000)
(XEN) [<ff030980>] (+0xff030980/0xff03a000) from [<ff030ac0>] (+0xff030ac0/0xff03a000)
(XEN)  r3 = 00000000  r2 = 000001D0  r1 = FF0364B3  r0 = FF039970
(XEN)  r5 = FF0364B3  r4 = 000001D0
(XEN) [<ff030a84>] (+0xff030a84/0xff03a000) from [<ff008e58>] (+0xff008e58/0xff00acc8)
(XEN)  r5 = FF05264C  r4 = 00000000
(XEN) [<ff0089b4>] (+0xff0089b4/0xff00acc8) from [<a0008028>] (???)
(XEN) machine_halt called: spinning....
------------------------------------------------------------------------------------------------------------------------------------------
Thanks :)

On Thu, Apr 22, 2010 at 12:56 AM, SAMBUC Lionel <lio...@he...<mailto:lio...@he...>> wrote:
Hi,

Sorry for the delay, I will put online a short step by step procedure to compile and
start EmbeddedXen, as well as a FAQ, starting with your questions.
This will be available on the SourceForge web page of the project, I intend to have it
online by the end of the day (17h00 GMT, 22nd April 2010).

The web page is located at http://embeddedxen.sourceforge.net/, this is where
you will find the most up to date information.

Please continue to post any other question on this mailing list.

Have a nice day,

Lionel

From: xen...@li...<mailto:xen...@li...> [mailto:xen...@li...<mailto:xen...@li...>] On Behalf Of sreenaath vasudevan
Sent: mercredi 21 avril 2010 04:50
To: xe...@li...<mailto:xe...@li...>
Subject: [XenARM] Re:xen-pxa270-qemu

 Hi
I tried to run xen-arm on pxa270 emulated on qemu by following this link
http://lists.xensource.com/archives/html/xen-arm/2009-04/msg00001.html
I am not able to get in to dom0 console at all.

This is what I ve done
1. I installed the cross compiler arm-unknown-linux-gnuabi-gcc. The Linux distro I use is Ubuntu 9.10.

2. I installed the qemu that came default with ubuntu 9.10 linux.

3. The I installed xen-pxa270-qemu from https://sourceforge.net/projects/embeddedxen.

4. To compile and run it, this is what I did
    a) I untarred the tarball and did a 'make all' inside the 'xen-pxa270-qemu' folder. Before firing the make command, I set the CROSS_COMPILE env variable to point to the cross compiler 'arm-unknown-linux-gnuabi-gcc'.

    b) Then after successful completion of make command, I followed the instructions in http://lists.xensource.com/archives/html/xen-arm/2009-05/msg00000.html

    c) When I run it in non-graphical mode with -nographic option in qemu-system-arm, the console outputs that xen image is getting loaded and linux image is getting loaded in dom0. After that nothing happens. I am not able to enter anything in the command console as it only displays 'Hit Ctrl 'A'  three times to enter in to xen mode'. When I hit Ctrl + 'A' three time it displays 'Hit Ctrl 'A'  three times to enter in to dom0'

   d) When I ran it, in Graphical mode I saw a black screen popping up and in the command window I see the message "map addr 0x8297e80". After that nothing happens. I am not able to see anything in the graphical screen too.


It would be extremely helpful if someone can tell me how to get in to dom0 console.


--
regards
sreenaath


--
regards
sreenaath



--
regards
sreenaath

Re: [Embeddedxen-devel] [XenARM] Re:xen-pxa270-qemu

[ROSSIER D. <Dan...@he...>]

Apparently, you have no dom0 image in the kernel image. How did you build your image?
Normally, you must use the build-embeddedxen with appropriate option (build-embeddedxen -? for getting all options)

Maybe, could you send us the result of the build-embeddedxen command?

Cheers
Daniel


> -----Original Message-----
> From: sreenaath vasudevan [mailto:sre...@gm...]
> Sent: vendredi 23 avril 2010 04:14
> To: emb...@li...
> Subject: Re: [Embeddedxen-devel] [XenARM] Re:xen-pxa270-qemu
> 
> The panic is happening in the file hypervisor/setup.c and not in hypervisor.c
> as i told in my previous post.
> Sorry for the confusion.
> On Thu, Apr 22, 2010 at 10:11 PM, sreenaath vasudevan
> <sre...@gm...> wrote:
> Hi
> Thanks for the detailed info given in the
> wiki http://sourceforge.net/apps/mediawiki/embeddedxen/index.php?title
> =GettingStarted.
> 
> I am running in to a panic issue (panic at hypervisor.c) when trying to get the
> system up and running (as  given in the wiki), which prevents xen from
> booting.
> This is what I have done.
> 1. I have a virtual machine having ubuntu-9.10 where I followed and installed
> the packages as given in the wiki.
> 2. In addition to that, I did install the following packages, brctl, uml-utilities
> (for 'tunctl') and uboot-mkimage as they were not there in my ubuntu-9.10
> VM.
> 3. Also I changed the /etc/wemu-ifup script as follows (added two more lines
> to what is givien in the wiki for adding the bridge being linking it with the tap0
> interface.)
>        /etc/qemu-ifup
> 
>        #!/bin/sh
>        BRIDGE=br0
>       #setup in promiscuous mode qemu's device
>       echo ifconfig $1 0.0.0.0 promisc up
>       ifconfig $1 0.0.0.0 promisc up
>       echo brctl addbr $BRIDGE
>       brctl addbr $BRIDGE
>       #add it to the bridge
>       echo brctl addif $BRIDGE $1
>       brctl addif $BRIDGE $1
> 
> 4. After that I created two dummy flash files 'flash1' and 'flash2' of sixe 32 MB
> as follows
>  $> sudo dd if=/dev/zero of=./flash2 bs=32000000 count=1
> 
> 5. Then I ran 'qemu' and got the panic at 'hypervisor.c' which I am giving
> below. It would be great if you could let me know how to fix it and get it
> running.
> 
> ----------------------------------------------------------------------------------------------
> --------------------------------------------
> user@ubuntu:~/embeddedxen# sudo qemu-system-arm -localtime -M
> mainstone -kernel ./xen/arch/arm/boot/uImage.mainstone -s -m 256 -pflash
> ./flash1 -pflash ./flash2 -net nic -net tap,ifname=tap0,script=/etc/qemu-ifup
> ifconfig tap0 0.0.0.0 promisc up
> brctl addbr br0
> device br0 already exists; can't create bridge with the same name brctl addif
> br0 tap0 map addr 0x82200a0 root@ubuntu:~/embeddedxen# sudo qemu-
> system-arm -localtime -M mainstone -kernel
> ./xen/arch/arm/boot/uImage.mainstone -s -m 256 -pflash ./flash1 -pflash
> ./flash2 -net nic -net tap,ifname=tap0,script=/etc/qemu-ifup -serial stdio
> ifconfig tap0 0.0.0.0 promisc up brctl addbr br0 device br0 already exists; can't
> create bridge with the same name brctl addif br0 tap0 map addr 0x82200a0
> Uncompressing Xen................................... done, booting the kernel.
>  __  __            _____  _   _____              _ _ _          _
>  \ \/ /___ _ __   |___ / / | |___ /     ___ ___ | (_) |__  _ __(_)
>   \  // _ \ '_ \    |_ \ | |   |_ \ __ / __/ _ \| | | '_ \| '__| |
>   /  \  __/ | | |  ___) || |_ ___) |__| (_| (_) | | | |_) | |  | |
>  /_/\_\___|_| |_| |____(_)_(_)____/    \___\___/|_|_|_.__/|_|  |_|
> 
>  http://www.cl.cam.ac.uk/netos/xen
>  University of Cambridge Computer Laboratory
> 
>  Xen version 3.1.3-colibri (root@) (gcc version 4.1.2) Wed Feb 11 11:24:14 CET
> 2009
>  EmbeddedXEN/PENAR Project - Reconfigurable Embedded Digital System
> (REDS) Institute from HEIG-VD/Switzerland
>  http://reds.heig-vd.ch
> 
>  Latest ChangeSet: unavailable
> 
> (XEN) Hypervisor area start at: 0xff000000 (virt)
> (XEN) Physical RAM map:
> (XEN)   00000000a0000000: 0000000004000000
> (XEN) End of multi-kernel area (XEN+dom0/U) -> min_page: 0xa0100
> (XEN) End of Xen Area: 2561MiB (2622464KiB)
> (XEN) End of RAM: 0xa3f00000
> (XEN) Boot allocator @ a0100000 - a0115000
> (XEN) NUMA turned off
> (XEN) Faking a node at 0000000000000000-00000000a3f00000
> (XEN) xenheap: 00000000a0115000 - 00000000a0314fff
> (XEN) xenheap(virt): ff115000 - ff314fff
> (XEN) ### frametable: ff315000
> (XEN) ### min_page: a0100
> (XEN) ### ps = a0115000 maddr_to_virt(ps)=ff115000
> maddr_to_page(ps)=ff3151f8
> (XEN) Xen heap: 2MiB (2048kiB)
> (XEN) ### first_valid_mfn = a0315
> (XEN) ### max_page = a3f00
> (XEN) Domain heap initialised: DMA width 32 bits
> (XEN) Dom Heap: 15230 pages
> (XEN) CPU: XScale-PXA270 [69054117] revision 7 (ARMv5TE)
> (XEN) (GCD) xen/arch/arm/hypervisor/mm.c:2070:vector_pt_init():
> alloc_xenheap_page
> (XEN) Mapping I/O on mainstone...
> (XEN) Init IRQ...
> (XEN) Initing arch-IRQ...
> (XEN) Init scheduler...
> (XEN) Using scheduler: Simple EDF Scheduler (sedf)
> (XEN) Initializing timer...
> (XEN) Platform clock source oscr0 @ 3249600 Hz overflows in 660845 jiffies.
> (XEN) Platform periodic timer is osmr0 @ 1000 Hz
> (XEN) ### arch_domain create OK
> (XEN) Xen BUG at xen/arch/arm/hypervisor/setup.c:464
> (XEN) CPU: 0
> (XEN) PC is at ff00eea8
> (XEN) LR is at ff030ab0
> (XEN) pc : [<ff00eea8>]    lr : [<ff030ab0>]
> (XEN) sp : ff03ff40  ip : ff03ffb4  fp : ff03ffb0
> (XEN) r10: ff052648  r9 : ff052528  r8 : 00000000
> (XEN) r7 : ff052454  r6 : 00000000  r5 : ff0364b3  r4 : 000001d0
> (XEN) r3 : 00000000  r2 : 00000000  r1 : 0000000a  r0 : ff059073
> (XEN) Flags: nZCv  IRQs on  FIQs off  Mode SVC_32
> (XEN) Control: 7977  Table: A0004000  DAC: 000000DF
> (XEN)
> (XEN) ****************************************
> (XEN) Panic on CPU 0:
> (XEN) Xen BUG at xen/arch/arm/hypervisor/setup.c:464
> (XEN) ****************************************
> (XEN)
> (XEN) Manual reset required ('noreboot' specified)
> (XEN) CPU: 0
> (XEN) PC is at ff00eea8
> (XEN) LR is at ff030a0c
> (XEN) pc : [<ff00eea8>]    lr : [<ff030a0c>]
> (XEN) sp : ff03ff14  ip : ff03ff88  fp : ff03ff84
> (XEN) r10: ff052648  r9 : ff052528  r8 : 00000000
> (XEN) r7 : ff052454  r6 : 00000000  r5 : 60000153  r4 : ff030ac0
> (XEN) r3 : 00000000  r2 : 00000000  r1 : 0000000a  r0 : ff059071
> (XEN) Flags: nZCv  IRQs on  FIQs off  Mode SVC_32
> (XEN) Control: 7977  Table: A0004000  DAC: 000000DF
> (XEN) [<ff00eeec>] (+0xff00eeec/0xff03a000) from [<ff030a1c>]
> (+0xff030a1c/0xff03a000)
> (XEN) [<ff030980>] (+0xff030980/0xff03a000) from [<ff030ac0>]
> (+0xff030ac0/0xff03a000)
> (XEN)  r3 = 00000000  r2 = 000001D0  r1 = FF0364B3  r0 = FF039970
> (XEN)  r5 = FF0364B3  r4 = 000001D0
> (XEN) [<ff030a84>] (+0xff030a84/0xff03a000) from [<ff008e58>]
> (+0xff008e58/0xff00acc8)
> (XEN)  r5 = FF05264C  r4 = 00000000
> (XEN) [<ff0089b4>] (+0xff0089b4/0xff00acc8) from [<a0008028>] (???)
> (XEN) machine_halt called: spinning....
> ----------------------------------------------------------------------------------------------
> --------------------------------------------
> Thanks :)
> 
> On Thu, Apr 22, 2010 at 12:56 AM, SAMBUC Lionel <lionel.sambuc@heig-
> vd.ch> wrote:
> Hi,
> 
> Sorry for the delay, I will put online a short step by step procedure to compile
> and start EmbeddedXen, as well as a FAQ, starting with your questions.
> This will be available on the SourceForge web page of the project, I intend to
> have it online by the end of the day (17h00 GMT, 22nd April 2010).
> 
> The web page is located at http://embeddedxen.sourceforge.net/, this is
> where you will find the most up to date information.
> 
> Please continue to post any other question on this mailing list.
> 
> Have a nice day,
> 
> Lionel
> 
> From: xen...@li... [mailto:xen-arm-
> bo...@li...] On Behalf Of sreenaath vasudevan
> Sent: mercredi 21 avril 2010 04:50
> To: xe...@li...
> Subject: [XenARM] Re:xen-pxa270-qemu
> 
>  Hi
> I tried to run xen-arm on pxa270 emulated on qemu by following this link
> http://lists.xensource.com/archives/html/xen-arm/2009-04/msg00001.html
> 
> I am not able to get in to dom0 console at all.
> 
> This is what I ve done
> 1. I installed the cross compiler arm-unknown-linux-gnuabi-gcc. The Linux
> distro I use is Ubuntu 9.10.
> 
> 2. I installed the qemu that came default with ubuntu 9.10 linux.
> 
> 3. The I installed xen-pxa270-qemu from
> https://sourceforge.net/projects/embeddedxen.
> 
> 4. To compile and run it, this is what I did
>     a) I untarred the tarball and did a 'make all' inside the 'xen-pxa270-qemu'
> folder. Before firing the make command, I set the CROSS_COMPILE env
> variable to point to the cross compiler 'arm-unknown-linux-gnuabi-gcc'.
> 
>     b) Then after successful completion of make command, I followed the
> instructions in http://lists.xensource.com/archives/html/xen-arm/2009-
> 05/msg00000.html
> 
>     c) When I run it in non-graphical mode with -nographic option in qemu-
> system-arm, the console outputs that xen image is getting loaded and linux
> image is getting loaded in dom0. After that nothing happens. I am not able to
> enter anything in the command console as it only displays 'Hit Ctrl 'A'  three
> times to enter in to xen mode'. When I hit Ctrl + 'A' three time it displays 'Hit
> Ctrl 'A'  three times to enter in to dom0'
> 
>    d) When I ran it, in Graphical mode I saw a black screen popping up and in
> the command window I see the message "map addr 0x8297e80". After that
> nothing happens. I am not able to see anything in the graphical screen too.
> 
> 
> It would be extremely helpful if someone can tell me how to get in to dom0
> console.
> 
> 
> --
> regards
> sreenaath
> 
> 
> 
> --
> regards
> sreenaath
> 
> 
> 
> --
> regards
> sreenaath

Re: [Embeddedxen-devel] [XenARM] Re:xen-pxa270-qemu

[SAMBUC L. <lio...@he...>]

Hello,

> -----Original Message-----
> From: sreenaath vasudevan [mailto:sre...@gm...]
> Sent: vendredi 23 avril 2010 04:14
> To: emb...@li...
> Subject: Re: [Embeddedxen-devel] [XenARM] Re:xen-pxa270-qemu
> 
... 
> 
> 	3. Also I changed the /etc/wemu-ifup script as follows (added two
> more lines to what is givien in the wiki for adding the bridge being
> linking it with the tap0 interface.)
> 	       /etc/qemu-ifup
> 
> 	       #!/bin/sh
> 	       BRIDGE=br0
> 	      #setup in promiscuous mode qemu's device
> 	      echo ifconfig $1 0.0.0.0 promisc up
> 	      ifconfig $1 0.0.0.0 promisc up
> 	      echo brctl addbr $BRIDGE
> 	      brctl addbr $BRIDGE
> 	      #add it to the bridge
> 	      echo brctl addif $BRIDGE $1
> 	      brctl addif $BRIDGE $1
> 

While not being a show stopper, your qemu-ifup script seems wrong, please take the one from the GettingStarted guide. Based on your email, I also updated the guide this morning as some steps where incomplete. 

For reference, the complete script:

 #!/bin/sh 
 
 BRIDGE=br0
 
 #setup in promiscuous mode qemu's device
 echo ifconfig $1 0.0.0.0 promisc up
 ifconfig $1 0.0.0.0 promisc up
 #add it to the bridge
 echo brctl addif $BRIDGE $1
 brctl addif $BRIDGE $1

The bridge device is created once (normally in /etc/network/interfaces) and then only modified with regards to the linked interfaces (brctl addif and brctl delif commands). This is also why we can see complaints about trying to create a bridge interface which already exists.

> ---------------------------------------------------------------------
> 	user@ubuntu:~/embeddedxen# sudo qemu-system-arm -localtime -M
> mainstone -kernel ./xen/arch/arm/boot/uImage.mainstone -s -m 256 -pflash
> ./flash1 -pflash ./flash2 -net nic -net tap,ifname=tap0,script=/etc/qemu-ifup
> 	ifconfig tap0 0.0.0.0 promisc up
> 	brctl addbr br0
> 	device br0 already exists; can't create bridge with the same name

This error comes from your "brctl addbr $BRIDGE" command.

> 	brctl addif br0 tap0
> 	map addr 0x82200a0
...
> 
> --
> regards
> sreenaath

Have a nice day,

Lionel

Re: [Embeddedxen-devel] [XenARM] Re:xen-pxa270-qemu

[sreenaath v. <sre...@gm...>]

Hi
I got your point.
I made a mistake by adding the "brctl addbr $BRIDGE" command to the
qemu-ifup script. Initially when I just followed the wiki and had the
original qemu-ifup script given in the wiki, it threw me error as 'br0' was
not added. Hence I added the command in qemu-ifup script, which I should not
have done and rather fired it from command line for the first time alone.
Regarding how I build the image, I ll post my reply in the next post.
Thanks :)

On Fri, Apr 23, 2010 at 9:53 AM, SAMBUC Lionel <lio...@he...>wrote:

> Hello,
>
> > -----Original Message-----
> > From: sreenaath vasudevan [mailto:sre...@gm...]
> > Sent: vendredi 23 avril 2010 04:14
> > To: emb...@li...
> > Subject: Re: [Embeddedxen-devel] [XenARM] Re:xen-pxa270-qemu
> >
> ...
> >
> >       3. Also I changed the /etc/wemu-ifup script as follows (added two
> > more lines to what is givien in the wiki for adding the bridge being
> > linking it with the tap0 interface.)
> >              /etc/qemu-ifup
> >
> >              #!/bin/sh
> >              BRIDGE=br0
> >             #setup in promiscuous mode qemu's device
> >             echo ifconfig $1 0.0.0.0 promisc up
> >             ifconfig $1 0.0.0.0 promisc up
> >             echo brctl addbr $BRIDGE
> >             brctl addbr $BRIDGE
> >             #add it to the bridge
> >             echo brctl addif $BRIDGE $1
> >             brctl addif $BRIDGE $1
> >
>
> While not being a show stopper, your qemu-ifup script seems wrong, please
> take the one from the GettingStarted guide. Based on your email, I also
> updated the guide this morning as some steps where incomplete.
>
> For reference, the complete script:
>
>  #!/bin/sh
>
>  BRIDGE=br0
>
>  #setup in promiscuous mode qemu's device
>  echo ifconfig $1 0.0.0.0 promisc up
>  ifconfig $1 0.0.0.0 promisc up
>  #add it to the bridge
>  echo brctl addif $BRIDGE $1
>  brctl addif $BRIDGE $1
>
> The bridge device is created once (normally in /etc/network/interfaces) and
> then only modified with regards to the linked interfaces (brctl addif and
> brctl delif commands). This is also why we can see complaints about trying
> to create a bridge interface which already exists.
>
> > ---------------------------------------------------------------------
> >       user@ubuntu:~/embeddedxen# sudo qemu-system-arm -localtime -M
> > mainstone -kernel ./xen/arch/arm/boot/uImage.mainstone -s -m 256 -pflash
> > ./flash1 -pflash ./flash2 -net nic -net
> tap,ifname=tap0,script=/etc/qemu-ifup
> >       ifconfig tap0 0.0.0.0 promisc up
> >       brctl addbr br0
> >       device br0 already exists; can't create bridge with the same name
>
> This error comes from your "brctl addbr $BRIDGE" command.
>
> >       brctl addif br0 tap0
> >       map addr 0x82200a0
> ...
> >
> > --
> > regards
> > sreenaath
>
> Have a nice day,
>
> Lionel
>



-- 
regards
sreenaath

[Embeddedxen-devel] RE : [XenARM] Re:xen-pxa270-qemu

[SAMBUC L. <lio...@he...>]

Hello,

from your attched output log, the eu-strip tool is not installed on your system.
It is found in the elfutils package. I will update the wiki and add this package in 
the requirement list, as well as the bridge utils.

Otherwise, both domains are compiled alright. As the final image is made from 
the stripped versions of the images files and as they are not created, they are 
not included. There is no error reported during the creation of the final image 
as this is possible to include only one domain (be it either domU or dom0).

With that last package, you should have an embeddedxen up and running.

Thank you for your feedback, it has helped a lot in the creation of a complete 
step by step guide.

As usual, if any question arise, just let us know!

Regards, 

Lionel
________________________________________
De : sreenaath vasudevan [sre...@gm...]
Date d'envoi : vendredi, 23. avril 2010 21:14
À : ROSSIER Daniel
Cc : emb...@li...
Objet : Re: [Embeddedxen-devel] [XenARM] Re:xen-pxa270-qemu

Hi
Yes I think dom0 is missing. This is how I got the code and how I built it

1. git clone git://embeddedxen.git.sourceforge.net/gitroot/embeddedxen/embeddedxen<http://embeddedxen.git.sourceforge.net/gitroot/embeddedxen/embeddedxen>

2. cd embeddedxen

3. ./build-embeddedxen -u -0 -x

The output in the command line after firing the build-embeddedxen command, the last few line of the output I am giving below. Also I am attaching the full output of the build-embeddedxen command.

4. untarred rootfs like sudo tar -jxf rootfs.tar.bz2
 @ /opt/boards/filesystem/rootfs-
oabi.

After this made changes to config files as told in wiki

Then ran QEMU like this
user@localhost > sudo qemu-system-arm -localtime -M mainstone -kernel xen/arch/arm/boot/uImage.mainstone -pflash ./flash1 -pflash ./flash2 -s -m 256 -net nic -net tap,ifname=tap0,script=/etc/qemu-ifup -serial vc:1000x500

On doing this I got the panic as reported in my previous post. Please do let me know if theres anything wrong wiht the build-embeddexen command or anything is wrong from the output.

--
regards
sreenaath

Re: [Embeddedxen-devel] RE : [XenARM] Re:xen-pxa270-qemu

[SAMBUC L. <lio...@he...>]

Hello,

I have been able to reproduce your issue with QEMU-0.10.5. 
This is a driver / QEMU emulation issue which was introduced between 
QEMU 0.9.1 and QEMU 0.10.5.

I have no fix at the moment, so meanwhile please stick to the 0.9.1
revision.

Regards,

Lionel

> -----Original Message-----
> From: sreenaath vasudevan [mailto:sre...@gm...]
> Sent: samedi 24 avril 2010 21:49
> To: SAMBUC Lionel
> Cc: emb...@li...
> Subject: Re: RE : [Embeddedxen-devel] [XenARM] Re:xen-pxa270-qemu
> 
> Hi Lionel
> Thanks for the quick response.
> I ve installed elfutils and I could see that the WARNING regarding "eu-
> strip missing" while building the image is gone. However I get the
> following two warning.
> WARNING: "HYPERVISOR_shared_info" [drivers/video/backlight/lcd.ko]
> undefined!
> WARNING: "HYPERVISOR_shared_info" [drivers/video/backlight/backlight.ko]
> undefined!
> 
> Not sure If the problem I mentioned below is because of these warnings
> 
> This is the way I built and  ran the image
> building the image -> ./build-embeddedxen -u -0 -x
> 
> running the image -> sudo qemu-system-arm -localtime -M mainstone -kernel
> ./xen/arch/arm/boot/uImage.mainstone -s -m 256 -pflash ./flash1 -pflash
> ./flash2 -net nic -net tap,ifname=tap0,script=/etc/qemu-ifup -serial stdio
> 
> However while running the image, I get "aborted" the following error
> appears(I am pasting only the last few lines. I am attaching the build and
> output log with this post.)
> 
> last few lines of output while running the built image
> ---------------------------------------------------------------------------
> ----------------------------------------------------------
> [DOM0] IP route cache hash table entries: 128 (order: -3, 512 bytes)
> [DOM0] TCP established hash table entries: 512 (order: -1, 2048 bytes)
> [DOM0] TCP bind hash table entries: 256 (order: -2, 1024 bytes)
> [DOM0] <6>TCP: Hash tables configured (established 512 bind 256)
> [DOM0] <6>TCP reno registered
> [DOM0] <4>NetWinder Floating Point Emulator V0.97 (extended precision)
> [DOM0] <6>JFFS2 version 2.2. (NAND) (C) 2001-2006 Red Hat, Inc.
> [DOM0] <6>Initializing Cryptographic API
> [DOM0] <6>io scheduler noop registered
> [DOM0] <6>io scheduler anticipatory registered
> [DOM0] <6>io scheduler deadline registered
> [DOM0] <6>io scheduler cfq registered (default)
> [DOM0] Event-channel device installed.
> [DOM0] Xen virtual console successfully installed as ttyS0
> qemu: fatal: smc91c111_read: Bad reg 0:30e
> 
> R00=c1850300 R01=00000001 R02=00000000 R03=00007ff0
> R04=c0c3a800 R05=c024a19c R06=c1850300 R07=00000000
> R08=c024a194 R09=00000000 R10=c024a674 R11=c0351ebc
> R12=c0351e24 R13=c0351e70 R14=c0130cfc R15=c016ac90
> PSR=a0000010 N-C- A usr32
> Aborted
> 
> ---------------------------------------------------------------------------
> ----------------------------------------------------------
> 
> 
> On Sat, Apr 24, 2010 at 6:28 AM, SAMBUC Lionel <lio...@he...>
> wrote:
> 
> 
> 	Hello,
> 
> 	from your attched output log, the eu-strip tool is not installed on
> your system.
> 	It is found in the elfutils package. I will update the wiki and add
> this package in
> 	the requirement list, as well as the bridge utils.
> 
> 	Otherwise, both domains are compiled alright. As the final image is
> made from
> 	the stripped versions of the images files and as they are not
> created, they are
> 	not included. There is no error reported during the creation of the
> final image
> 	as this is possible to include only one domain (be it either domU or
> dom0).
> 
> 	With that last package, you should have an embeddedxen up and
> running.
> 
> 	Thank you for your feedback, it has helped a lot in the creation of a
> complete
> 	step by step guide.
> 
> 	As usual, if any question arise, just let us know!
> 
> 	Regards,
> 
> 	Lionel
> 	________________________________________
> 	De : sreenaath vasudevan [sre...@gm...]
> 	Date d'envoi : vendredi, 23. avril 2010 21:14
> 	À : ROSSIER Daniel
> 	Cc : emb...@li...
> 	Objet : Re: [Embeddedxen-devel] [XenARM] Re:xen-pxa270-qemu
> 
> 
> 	Hi
> 	Yes I think dom0 is missing. This is how I got the code and how I
> built it
> 
> 
> 	1. git clone
> git://embeddedxen.git.sourceforge.net/gitroot/embeddedxen/embeddedxen<http:
> //embeddedxen.git.sourceforge.net/gitroot/embeddedxen/embeddedxen>
> 
> 
> 	2. cd embeddedxen
> 
> 	3. ./build-embeddedxen -u -0 -x
> 
> 	The output in the command line after firing the build-embeddedxen
> command, the last few line of the output I am giving below. Also I am
> attaching the full output of the build-embeddedxen command.
> 
> 	4. untarred rootfs like sudo tar -jxf rootfs.tar.bz2
> 	 @ /opt/boards/filesystem/rootfs-
> 	oabi.
> 
> 	After this made changes to config files as told in wiki
> 
> 	Then ran QEMU like this
> 	user@localhost > sudo qemu-system-arm -localtime -M mainstone -kernel
> xen/arch/arm/boot/uImage.mainstone -pflash ./flash1 -pflash ./flash2 -s -m
> 256 -net nic -net tap,ifname=tap0,script=/etc/qemu-ifup -serial vc:1000x500
> 
> 	On doing this I got the panic as reported in my previous post. Please
> do let me know if theres anything wrong wiht the build-embeddexen command
> or anything is wrong from the output.
> 
> 
> 	--
> 	regards
> 	sreenaath
> 
> 
> 
> 
> 
> --
> regards
> sreenaath

Re: [Embeddedxen-devel] RE : [XenARM] Re:xen-pxa270-qemu

[sreenaath v. <sre...@gm...>]

Hi Lionel
Thanks for the pointer on qemu version issue.
I am now using qemu-0.9.1 and I am ale to get to dom0 login.  The system is
booting :)
Thanks a lot for helping me out to get to this stage.

I ve some query on getting in to domU.

1. In general, while using xen in a desktop environment, we use xen-tools to
create new guest domains right and then we login in to that particular IP to
login to that guest domain.
In this case, with embeddedxen, we have the image of both dom0 and domU
embedded in to this bootable image. Then how do I get to domU? How do I
navigate between dom0 and domU ?

2. Also I am not able to use standard xen commands in DOM0 ?

Note:
For building the image, I used this command "./build-embeddedxen -u -0 -x"


On Sun, Apr 25, 2010 at 10:28 PM, SAMBUC Lionel <lio...@he...>wrote:

> Hello,
>
> I have been able to reproduce your issue with QEMU-0.10.5.
> This is a driver / QEMU emulation issue which was introduced between
> QEMU 0.9.1 and QEMU 0.10.5.
>
> I have no fix at the moment, so meanwhile please stick to the 0.9.1
> revision.
>
> Regards,
>
> Lionel
>
> > -----Original Message-----
> > From: sreenaath vasudevan [mailto:sre...@gm...]
> > Sent: samedi 24 avril 2010 21:49
> > To: SAMBUC Lionel
> > Cc: emb...@li...
> > Subject: Re: RE : [Embeddedxen-devel] [XenARM] Re:xen-pxa270-qemu
> >
> > Hi Lionel
> > Thanks for the quick response.
> > I ve installed elfutils and I could see that the WARNING regarding "eu-
> > strip missing" while building the image is gone. However I get the
> > following two warning.
> > WARNING: "HYPERVISOR_shared_info" [drivers/video/backlight/lcd.ko]
> > undefined!
> > WARNING: "HYPERVISOR_shared_info" [drivers/video/backlight/backlight.ko]
> > undefined!
> >
> > Not sure If the problem I mentioned below is because of these warnings
> >
> > This is the way I built and  ran the image
> > building the image -> ./build-embeddedxen -u -0 -x
> >
> > running the image -> sudo qemu-system-arm -localtime -M mainstone -kernel
> > ./xen/arch/arm/boot/uImage.mainstone -s -m 256 -pflash ./flash1 -pflash
> > ./flash2 -net nic -net tap,ifname=tap0,script=/etc/qemu-ifup -serial
> stdio
> >
> > However while running the image, I get "aborted" the following error
> > appears(I am pasting only the last few lines. I am attaching the build
> and
> > output log with this post.)
> >
> > last few lines of output while running the built image
> >
> ---------------------------------------------------------------------------
> > ----------------------------------------------------------
> > [DOM0] IP route cache hash table entries: 128 (order: -3, 512 bytes)
> > [DOM0] TCP established hash table entries: 512 (order: -1, 2048 bytes)
> > [DOM0] TCP bind hash table entries: 256 (order: -2, 1024 bytes)
> > [DOM0] <6>TCP: Hash tables configured (established 512 bind 256)
> > [DOM0] <6>TCP reno registered
> > [DOM0] <4>NetWinder Floating Point Emulator V0.97 (extended precision)
> > [DOM0] <6>JFFS2 version 2.2. (NAND) (C) 2001-2006 Red Hat, Inc.
> > [DOM0] <6>Initializing Cryptographic API
> > [DOM0] <6>io scheduler noop registered
> > [DOM0] <6>io scheduler anticipatory registered
> > [DOM0] <6>io scheduler deadline registered
> > [DOM0] <6>io scheduler cfq registered (default)
> > [DOM0] Event-channel device installed.
> > [DOM0] Xen virtual console successfully installed as ttyS0
> > qemu: fatal: smc91c111_read: Bad reg 0:30e
> >
> > R00=c1850300 R01=00000001 R02=00000000 R03=00007ff0
> > R04=c0c3a800 R05=c024a19c R06=c1850300 R07=00000000
> > R08=c024a194 R09=00000000 R10=c024a674 R11=c0351ebc
> > R12=c0351e24 R13=c0351e70 R14=c0130cfc R15=c016ac90
> > PSR=a0000010 N-C- A usr32
> > Aborted
> >
> >
> ---------------------------------------------------------------------------
> > ----------------------------------------------------------
> >
> >
> > On Sat, Apr 24, 2010 at 6:28 AM, SAMBUC Lionel <lio...@he...
> >
> > wrote:
> >
> >
> >       Hello,
> >
> >       from your attched output log, the eu-strip tool is not installed on
> > your system.
> >       It is found in the elfutils package. I will update the wiki and add
> > this package in
> >       the requirement list, as well as the bridge utils.
> >
> >       Otherwise, both domains are compiled alright. As the final image is
> > made from
> >       the stripped versions of the images files and as they are not
> > created, they are
> >       not included. There is no error reported during the creation of the
> > final image
> >       as this is possible to include only one domain (be it either domU
> or
> > dom0).
> >
> >       With that last package, you should have an embeddedxen up and
> > running.
> >
> >       Thank you for your feedback, it has helped a lot in the creation of
> a
> > complete
> >       step by step guide.
> >
> >       As usual, if any question arise, just let us know!
> >
> >       Regards,
> >
> >       Lionel
> >       ________________________________________
> >       De : sreenaath vasudevan [sre...@gm...]
> >       Date d'envoi : vendredi, 23. avril 2010 21:14
> >       À : ROSSIER Daniel
> >       Cc : emb...@li...
> >       Objet : Re: [Embeddedxen-devel] [XenARM] Re:xen-pxa270-qemu
> >
> >
> >       Hi
> >       Yes I think dom0 is missing. This is how I got the code and how I
> > built it
> >
> >
> >       1. git clone
> > git://embeddedxen.git.sourceforge.net/gitroot/embeddedxen/embeddedxen
> <http:
> > //embeddedxen.git.sourceforge.net/gitroot/embeddedxen/embeddedxen>
> >
> >
> >       2. cd embeddedxen
> >
> >       3. ./build-embeddedxen -u -0 -x
> >
> >       The output in the command line after firing the build-embeddedxen
> > command, the last few line of the output I am giving below. Also I am
> > attaching the full output of the build-embeddedxen command.
> >
> >       4. untarred rootfs like sudo tar -jxf rootfs.tar.bz2
> >        @ /opt/boards/filesystem/rootfs-
> >       oabi.
> >
> >       After this made changes to config files as told in wiki
> >
> >       Then ran QEMU like this
> >       user@localhost > sudo qemu-system-arm -localtime -M mainstone
> -kernel
> > xen/arch/arm/boot/uImage.mainstone -pflash ./flash1 -pflash ./flash2 -s
> -m
> > 256 -net nic -net tap,ifname=tap0,script=/etc/qemu-ifup -serial
> vc:1000x500
> >
> >       On doing this I got the panic as reported in my previous post.
> Please
> > do let me know if theres anything wrong wiht the build-embeddexen command
> > or anything is wrong from the output.
> >
> >
> >       --
> >       regards
> >       sreenaath
> >
> >
> >
> >
> >
> > --
> > regards
> > sreenaath
>
>


-- 
regards
sreenaath

Re: [Embeddedxen-devel] RE : [XenARM] Re:xen-pxa270-qemu

[SAMBUC L. <lio...@he...>]

Hello,

The short answer to your questions:

1.a You do not navigate between domains, domU-RT as no input facility such as a 
    console.
1.b You do not create on-the-fly domains, this a is not a foreseen feature.

2. The Xen utilities have not yet been ported, as they need the xenbus 
   infrastructure to run, which is not yet functional (which implies 1.b).

The long answer:

EmbeddedXen is a work-in-progress, We have already come a long way to be able
to run two domains concurrently. Now, the project objectives are as follow:
 * Having two (2) domains on an embedded platform whose roles are:
   o A real-time domain, which is responsible for motor control and the like.
   o A Linux non-RT domain whose job is to run some kind of device interface,
     be it a GUI on a touch screen, a web server, etc...
 * The RT domain registers the drivers it needs to control the peripheral it 
   uses in order to check the system status and modify it. It also communicates
   only with the domain 0 to retrieve any modification in settings and the like.

This means the Dom0 (non-RT) domain is responsible to do all the parameter checking, 
control the rights for any modification of the settings and / or the validity of the 
given settings, while the RT domain only focuses on the system regulation. This allow  
a clear cut between roles and responsibilities, which then simplify the critical code 
(DomU-RT).

The current status of the project is the following:
 o Xen has been partially been ported to the ARM platform, for example we are still 
   missing some feature such as:
    * Memory page granting.
    * The inter-domain channels are completely untested.
    * Live creation of a domain is untested and __is not planned__.
    * Xenbus & XenStore
 o The current Dom0 rootfs does not come with the XEN utilities to manage 
   domains, we are yet to port them and then test them.
 o The DomU system is a bare Xenomai nucleus, with only the needed services from 
   Linux on which it relies to run. This means:
    * No driver are loaded, besides the timer.
    * No network!
    * No Linux scheduler!

Regards, 

Lionel

> -----Original Message-----
> From: sreenaath vasudevan [mailto:sre...@gm...]
> Sent: mardi 27 avril 2010 02:25
> To: SAMBUC Lionel
> Cc: emb...@li...
> Subject: Re: RE : [Embeddedxen-devel] [XenARM] Re:xen-pxa270-qemu
> 
> Hi Lionel
> Thanks for the pointer on qemu version issue.
> I am now using qemu-0.9.1 and I am ale to get to dom0 login.  The system is
> booting :)
> Thanks a lot for helping me out to get to this stage.
> 
> I ve some query on getting in to domU.
> 
> 1. In general, while using xen in a desktop environment, we use xen-tools
> to create new guest domains right and then we login in to that particular
> IP to login to that guest domain.
> In this case, with embeddedxen, we have the image of both dom0 and domU
> embedded in to this bootable image. Then how do I get to domU? How do I
> navigate between dom0 and domU ?
> 
> 2. Also I am not able to use standard xen commands in DOM0 ?
> 
> Note:
> For building the image, I used this command "./build-embeddedxen -u -0 -x"
> 
> 
> On Sun, Apr 25, 2010 at 10:28 PM, SAMBUC Lionel <lio...@he...>
> wrote:
> 
> 
> 	Hello,
> 
> 	I have been able to reproduce your issue with QEMU-0.10.5.
> 	This is a driver / QEMU emulation issue which was introduced between
> 	QEMU 0.9.1 and QEMU 0.10.5.
> 
> 	I have no fix at the moment, so meanwhile please stick to the 0.9.1
> 	revision.
> 
> 	Regards,
> 
> 	Lionel
> 
> 
> 	> -----Original Message-----
> 	> From: sreenaath vasudevan [mailto:sre...@gm...]
> 
> 	> Sent: samedi 24 avril 2010 21:49
> 	> To: SAMBUC Lionel
> 	> Cc: emb...@li...
> 
> 	> Subject: Re: RE : [Embeddedxen-devel] [XenARM] Re:xen-pxa270-qemu
> 	>
> 	> Hi Lionel
> 	> Thanks for the quick response.
> 	> I ve installed elfutils and I could see that the WARNING regarding
> "eu-
> 	> strip missing" while building the image is gone. However I get the
> 	> following two warning.
> 	> WARNING: "HYPERVISOR_shared_info" [drivers/video/backlight/lcd.ko]
> 	> undefined!
> 	> WARNING: "HYPERVISOR_shared_info"
> [drivers/video/backlight/backlight.ko]
> 	> undefined!
> 	>
> 	> Not sure If the problem I mentioned below is because of these
> warnings
> 	>
> 	> This is the way I built and  ran the image
> 	> building the image -> ./build-embeddedxen -u -0 -x
> 	>
> 	> running the image -> sudo qemu-system-arm -localtime -M mainstone -
> kernel
> 	> ./xen/arch/arm/boot/uImage.mainstone -s -m 256 -pflash ./flash1 -
> pflash
> 	> ./flash2 -net nic -net tap,ifname=tap0,script=/etc/qemu-ifup -
> serial stdio
> 	>
> 	> However while running the image, I get "aborted" the following
> error
> 	> appears(I am pasting only the last few lines. I am attaching the
> build and
> 	> output log with this post.)
> 	>
> 	> last few lines of output while running the built image
> 	> -------------------------------------------------------------------
> --------
> 	> ----------------------------------------------------------
> 	> [DOM0] IP route cache hash table entries: 128 (order: -3, 512
> bytes)
> 	> [DOM0] TCP established hash table entries: 512 (order: -1, 2048
> bytes)
> 	> [DOM0] TCP bind hash table entries: 256 (order: -2, 1024 bytes)
> 	> [DOM0] <6>TCP: Hash tables configured (established 512 bind 256)
> 	> [DOM0] <6>TCP reno registered
> 	> [DOM0] <4>NetWinder Floating Point Emulator V0.97 (extended
> precision)
> 	> [DOM0] <6>JFFS2 version 2.2. (NAND) (C) 2001-2006 Red Hat, Inc.
> 	> [DOM0] <6>Initializing Cryptographic API
> 	> [DOM0] <6>io scheduler noop registered
> 	> [DOM0] <6>io scheduler anticipatory registered
> 	> [DOM0] <6>io scheduler deadline registered
> 	> [DOM0] <6>io scheduler cfq registered (default)
> 	> [DOM0] Event-channel device installed.
> 	> [DOM0] Xen virtual console successfully installed as ttyS0
> 	> qemu: fatal: smc91c111_read: Bad reg 0:30e
> 	>
> 	> R00=c1850300 R01=00000001 R02=00000000 R03=00007ff0
> 	> R04=c0c3a800 R05=c024a19c R06=c1850300 R07=00000000
> 	> R08=c024a194 R09=00000000 R10=c024a674 R11=c0351ebc
> 	> R12=c0351e24 R13=c0351e70 R14=c0130cfc R15=c016ac90
> 	> PSR=a0000010 N-C- A usr32
> 	> Aborted
> 	>
> 	> -------------------------------------------------------------------
> --------
> 	> ----------------------------------------------------------
> 	>
> 	>
> 	> On Sat, Apr 24, 2010 at 6:28 AM, SAMBUC Lionel <lionel.sambuc@heig-
> vd.ch>
> 	> wrote:
> 	>
> 	>
> 	>       Hello,
> 	>
> 	>       from your attched output log, the eu-strip tool is not
> installed on
> 	> your system.
> 	>       It is found in the elfutils package. I will update the wiki
> and add
> 	> this package in
> 	>       the requirement list, as well as the bridge utils.
> 	>
> 	>       Otherwise, both domains are compiled alright. As the final
> image is
> 	> made from
> 	>       the stripped versions of the images files and as they are not
> 	> created, they are
> 	>       not included. There is no error reported during the creation
> of the
> 	> final image
> 	>       as this is possible to include only one domain (be it either
> domU or
> 	> dom0).
> 	>
> 	>       With that last package, you should have an embeddedxen up and
> 	> running.
> 	>
> 	>       Thank you for your feedback, it has helped a lot in the
> creation of a
> 	> complete
> 	>       step by step guide.
> 	>
> 	>       As usual, if any question arise, just let us know!
> 	>
> 	>       Regards,
> 	>
> 	>       Lionel
> 	>       ________________________________________
> 	>       De : sreenaath vasudevan [sre...@gm...]
> 	>       Date d'envoi : vendredi, 23. avril 2010 21:14
> 	>       À : ROSSIER Daniel
> 	>       Cc : emb...@li...
> 	>       Objet : Re: [Embeddedxen-devel] [XenARM] Re:xen-pxa270-qemu
> 	>
> 	>
> 	>       Hi
> 	>       Yes I think dom0 is missing. This is how I got the code and
> how I
> 	> built it
> 	>
> 	>
> 	>       1. git clone
> 	>
> git://embeddedxen.git.sourceforge.net/gitroot/embeddedxen/embeddedxen<http:
> 	> //embeddedxen.git.sourceforge.net/gitroot/embeddedxen/embeddedxen>
> 	>
> 	>
> 	>       2. cd embeddedxen
> 	>
> 	>       3. ./build-embeddedxen -u -0 -x
> 	>
> 	>       The output in the command line after firing the build-
> embeddedxen
> 	> command, the last few line of the output I am giving below. Also I
> am
> 	> attaching the full output of the build-embeddedxen command.
> 	>
> 	>       4. untarred rootfs like sudo tar -jxf rootfs.tar.bz2
> 	>        @ /opt/boards/filesystem/rootfs-
> 	>       oabi.
> 	>
> 	>       After this made changes to config files as told in wiki
> 	>
> 	>       Then ran QEMU like this
> 	>       user@localhost > sudo qemu-system-arm -localtime -M mainstone
> -kernel
> 	> xen/arch/arm/boot/uImage.mainstone -pflash ./flash1 -pflash
> ./flash2 -s -m
> 	> 256 -net nic -net tap,ifname=tap0,script=/etc/qemu-ifup -serial
> vc:1000x500
> 	>
> 	>       On doing this I got the panic as reported in my previous
> post. Please
> 	> do let me know if theres anything wrong wiht the build-embeddexen
> command
> 	> or anything is wrong from the output.
> 	>
> 	>
> 	>       --
> 	>       regards
> 	>       sreenaath
> 	>
> 	>
> 	>
> 	>
> 	>
> 	> --
> 	> regards
> 	> sreenaath
> 
> 
> 
> 
> 
> 
> --
> regards
> sreenaath