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

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

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