Re: [Embeddedxen-devel] How to get to domU from dom0

[Bornet R. <rom...@he...>]

Hi,

--- Original Message ---
> From: Krishna Pavan [mailto:pos...@gm...] 
> Sent: mardi 20 mars 2012 11:58
> To: Bornet Romain
> Cc: Rossier Daniel; emb...@li...
> Subject: Re: [Embeddedxen-devel] How to get to domU from dom0
> 
> Hi,
> 
> Thank You Bornet Romain,
> 
> It was a mistake completely on my part.
> I should have checked with the Serial Console Output also.
> 
> Here's the pic, where the Kernel+Xen boots up ( and waits for FileSystem I guess)
> I would like to know, 

From your screenshot it seems that you don't have a kernel but only EmbeddedXen.

> How uImage has to be packed with Xen together?

Our build system automatically packages the Xen + linux dom0 + linux domU images together in a single binary uImage. If you follow the build instructions you will get a correct image.

> How that image can be loaded on QEMU-for-ARM, so that it starts booting and show all that initialisation text, as it would do, if run on a actual board?
By building the image as documented and starting Qemu with our scripts you will get domU output and shell in the first Qemu terminal session (ctrl-alt-1) and dom0 output and shell in Qemu terminal session 3 (ctrl-alt-3).

> - you don't provide a disk image for the rootfs (-hda tools/rootfs/rootfs_v6.img)

Yes we provide a rootfs image. Apparently you didn't download and install all the necessary files (3 tar.gz archives in total).
Please refer to the Getting Started page (https://sourceforge.net/apps/mediawiki/embeddedxen/index.php?title=Quick_Start_Guide) for more information regarding environment setup and Qemu startup commands.

> My aim will be to use Kernel alone.

I don't understand your use case " to use Kernel alone" . At some point your kernel will need some user space to jump to... This user space can be minimal (e.g busybox shell only) and completely contained in a RAM disk but is nevertheless required.

> Somehow, If you use a lone kernel image alone, in ELF format / compressed format, it's not working, I mean other images [ embedded-xen works 100% ]. 

I don't understand what you mean with "If you use a lone kernel image alone, in ELF format / compressed format, it's not working," if you try to boot qemu with a dom0 kernel image alone, it won't work since the kernel will lack some initialization and support provided by the hypervisor. You should nevertheless be able to boot a standard vanilla kernel image (not provided by our project).

> But embedded-xen uImage is working.
> Somework has to be done to make it so, I guess,

As said above, all images xen + dom0 kernel + domU kernel are packed together in a single binary which is loaded at startup.

> I am trying and would be interested to know, how could that be made.
> 
> If known,
> 
> Please tell me what needs to be done?
> 
> -- 
> ? Regards :: Krishna Pavan ?

Hope this helps,
    Romain

P.S. Please prefer plain text emails without embedded pictures for mailing lists. It has more chances to show up correctly in every email client and is easier to quote, reply and forward.