Thread: [Embeddedxen-devel] How to get to domU from dom0
Brought to you by:
rossierd
From: Krishna P. <pos...@gm...> - 2012-03-19 14:10:29
|
Hi, tools/qemu-1.0-reds/arm-softmmu/qemu-system-arm -s -localtime -M versatilepb -cpu arm1136 -kernel uImage.embeddedxen.versatilev6 -pflash tools/resources/flash1 -pflash tools/resources/flash2 -m 256 -hda tools/rootfs/rootfs_v6.img from stv6h But, How to move from domU from dom0 ? I have searched docs, but Is it that I have missed any docs in the packages? Please Suggest! -- ✉ Regards :: Krishna Pavan ✍ |
From: Rossier D. <Dan...@he...> - 2012-03-19 14:36:18
|
> -----Original Message----- > From: Krishna Pavan [mailto:pos...@gm...] > Sent: lundi 19 mars 2012 15:10 > To: emb...@li... > Subject: [Embeddedxen-devel] How to get to domU from dom0 > > Hi, > > tools/qemu-1.0-reds/arm-softmmu/qemu-system-arm -s -localtime -M > versatilepb -cpu arm1136 -kernel uImage.embeddedxen.versatilev6 -pflash > tools/resources/flash1 -pflash tools/resources/flash2 -m 256 -hda > tools/rootfs/rootfs_v6.img > > from stv6h The image "uImage.embeddedxen.versatilev6" actually contains all the necessary binary including hypervisor, dom0 and domU. > But, How to move from domU from dom0 ? Easy, on the emulated framebuffer (qemu: ctrl+alt+1), you get what is happening on domU. On the serial console, (ctrl+alt+3) you have all the dom0 activities. This is how it works today on qemu; on HTC, a simple touch on the "magnifier" virtual key performs the switch between the two domains. Cheers Daniel > > I have searched docs, but > > Is it that I have missed any docs in the packages? > > > Please Suggest! > -- > ✉ Regards :: Krishna Pavan ✍ |
From: Rossier D. <Dan...@he...> - 2012-03-19 14:51:45
|
> -----Original Message----- > From: Rossier Daniel [mailto:Dan...@he...] > Sent: lundi 19 mars 2012 15:36 > To: Krishna Pavan; emb...@li... > Subject: Re: [Embeddedxen-devel] How to get to domU from dom0 > > > -----Original Message----- > > From: Krishna Pavan [mailto:pos...@gm...] > > Sent: lundi 19 mars 2012 15:10 > > To: emb...@li... > > Subject: [Embeddedxen-devel] How to get to domU from dom0 > > > > Hi, > > > > tools/qemu-1.0-reds/arm-softmmu/qemu-system-arm -s -localtime -M > > versatilepb -cpu arm1136 -kernel uImage.embeddedxen.versatilev6 > > -pflash > > tools/resources/flash1 -pflash tools/resources/flash2 -m 256 -hda > > tools/rootfs/rootfs_v6.img > > > > from stv6h > > The image "uImage.embeddedxen.versatilev6" actually contains all the > necessary binary including hypervisor, dom0 and domU. > > > But, How to move from domU from dom0 ? > > Easy, on the emulated framebuffer (qemu: ctrl+alt+1), you get what is > happening on domU. On the serial console, (ctrl+alt+3) you have all the dom0 > activities. This is how it works today on qemu; on HTC, a simple touch on the > "magnifier" virtual key performs the switch between the two domains. Just to make things clear: switch between the two domains mean switching the screen/focus. The two domains are obviously scheduled continuously and therefore run (nearly) simultaneously. > > Cheers > Daniel > > > > > I have searched docs, but > > > > Is it that I have missed any docs in the packages? > > > > > > Please Suggest! > > -- > > ✉ Regards :: Krishna Pavan ✍ > > ------------------------------------------------------------------------------ > This SF email is sponsosred by: > Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d- > msazure _______________________________________________ > Embeddedxen-devel mailing list > Emb...@li... > https://lists.sourceforge.net/lists/listinfo/embeddedxen-devel |
From: Bornet R. <rom...@he...> - 2012-03-20 10:19:42
|
Hi Krishna and list, --- Original Message --- > From: Krishna Pavan [mailto:pos...@gm...] > Sent: mardi 20 mars 2012 10:14 > To: Rossier Daniel > Cc: emb...@li... > Subject: Re: [Embeddedxen-devel] How to get to domU from dom0 > > Thank You Embedded-Xen-Devel & Rossier, > > I would like to know > -pflash file --> use 'file' as a parallel flash image flash1 & flash2 are used. > 1. Are they some kind of BIOS? related to that of linux & colibri? The Qemu -pflash option can be used to boot an emulated system from an emulated flash (NAND/NOR) device. Qemu needs to be patched for supporting this option and our current version in EmbeddedXen tree is not already patched for this support. We currently boot from an emulated harddisk interface (-had Qemu option). To be short, you can ignore these options and remove them from the Qemu command-line. It is a remaining of older project in our scripts and we will remove them from the distributed scripts to not confuse the user. > 2. If need to run either kernel alone on QEMU-for-ARM, If it's Embedded Xen or other, Will it be possible by supplying a zImage/uImage/vmlinux[ELF]? > I have been experiencing and trying to run the uImage.embeddedxen.versatilev6 alone like this, I get a blankscreen and nothing else.... > > Screenshot is here > > Please Suggest ! Please use the provided startup scripts at the root of the EmbeddedXen tree (stv6h script in your case). You will thus have all necessary Qemu options configured correctly. In your example, there are some errors / missing options compared to what we use in our scripts - memory size is set to 128MB in your command line (-m 128) where we use 256MB - you don't provide a disk image for the rootfs (-hda tools/rootfs/rootfs_v6.img) Hope this helps Romain |
From: Bornet R. <rom...@he...> - 2012-03-20 13:02:57
|
Keep list in the loop... From: Krishna Pavan [mailto:pos...@gm...] Sent: mardi 20 mars 2012 13:53 To: Bornet Romain Subject: Re: [Embeddedxen-devel] How to get to domU from dom0 Hi Thank You, From your screenshot it seems that you don't have a kernel but only EmbeddedXen. Oh ...... I thought I got Kernel also, but it's OK, My main objective is to break and make. I thought I will get it easily by that approach. Since, bootloader on QEMU for certain machine will already be present, I wanted to test Kernel, Kernel + Xen etc etc. Xen + linux dom0 + linux domU images together in a single binary uImage. If you follow the build instructions you will get a correct image. I have successfully loaded embedded-xen on qemu, I just wanted to start to understand how it's made. For that reason, I have started to pick from roots to make a string. Qemu terminal session (ctrl-alt-1) and dom0 output and shell in Qemu terminal session 3 (ctrl-alt-3). Yeah! I got it from Rossier Daniel, and I have successfully got a demo. > - you don't provide a disk image for the rootfs (-hda tools/rootfs/rootfs_v6.img) Hey, you in the sense, If I/You/We provide kernel only and do not provide rootfs, ..... that was the case. BTW, I have got all the packages downloaded. > My aim will be to use Kernel alone. I don't understand your use case " to use Kernel alone" . The same break and make, I just wanted to try. 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. Oh, that was really very useful information. 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). Yeah, that vanilla kernel, is somehow responsible for all the other thoughts, I have had. lone kernel image of vanilla works, I don't know, If some tweaking has already been done. I just tried a downloaded one. As said above, all images xen + dom0 kernel + domU kernel are packed together in a single binary which is loaded at startup. Probably, I need to look into the makefile, to know, how it has been done. P.S. Please prefer plain text emails without embedded pictures for mailing lists. yeah! sure, I will, just attached pics for easy understanding, I will maximum try to avoid those. -- ✉ Thanks & Regards :: Krishna Pavan ✍ |
From: Krishna P. <pos...@gm...> - 2012-03-20 13:13:19
|
Hi Thank You, > From your screenshot it seems that you don't have a kernel but only > EmbeddedXen. > > Oh ...... I thought I got Kernel also, but it's OK, My main objective is to break and make. I thought I will get it easily by that approach. Since, bootloader on QEMU for certain machine will already be present, I wanted to test Kernel, Kernel + Xen etc etc. Xen + linux dom0 + linux domU images together in a single binary uImage. If > you follow the build instructions you will get a correct image. > > I have successfully loaded embedded-xen on qemu, I just wanted to start to understand how it's made. For that reason, I have started to pick from roots to make a string. > > Qemu terminal session (ctrl-alt-1) and dom0 output and shell in Qemu > terminal session 3 (ctrl-alt-3). > > Yeah! I got it from Rossier Daniel, and I have successfully got a demo. > > - you don't provide a disk image for the rootfs (-hda > tools/rootfs/rootfs_v6.img) > Hey, you in the sense, If I/You/We provide kernel only and do not provide rootfs, ..... that was the case. BTW, I have got all the packages downloaded. > My aim will be to use Kernel alone. I don't understand your use case " to use Kernel alone" . The same break and make, I just wanted to try. > 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. > > Oh, that was really very useful information. 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). > > Yeah, that vanilla kernel, is somehow responsible for all the other thoughts, I have had. lone kernel image of vanilla works, I don't know, If some tweaking has already been done. I just tried a downloaded one. As said above, all images xen + dom0 kernel + domU kernel are packed > together in a single binary which is loaded at startup. > Probably, I need to look into the makefile, to know, how it has been done. > P.S. Please prefer plain text emails without embedded pictures for mailing > lists. > yeah! sure, I will, just attached pics for easy understanding, I will maximum try to avoid those. -- ✉ Thanks & Regards :: Krishna Pavan ✍ |