Dear Genode Community, In the Genode site there is a sreenshot showing VBox and Seoul VMMs on top of Genode / Nova. Seoul executes TinyCore and VBox Win7 as Guest-OSes. However, I could not find the corresponding run script. I am trying to recreate a similar environment. Actually I would like to evaluate a similar scenario where I could deploy and run multiple VMs running TC as Guest-Os. I would like also to be able to control and see the VMs (enter the Guest-OS, start/stop the VM) from the Genode window as the screenshot shows. ------ Having said that, I´ve struggling to understand how to create a run script capable to build such Software System capable to boot from a USB. I´ve ran successfully some scripts with QEMU: seoul-fancy.run, seoul-genode. VirtualBox facing many problems, either on QEMU or USB stick. So at first I would like to stick with Seoul. In this case, being able to run multiple VMs (Seoul+TinyCore) from Genode/Nova. Which way shall I follow to create a run script that fullfils what I expect? Is there already any run script? Thanks for your attention and wonderful initiative with Genode. Best regards, Roger
Hello,
On 01.09.2015 16:48, Roger Ferreira wrote:
Dear Genode Community, I would like also to be able to control and see the VMs (enter the Guest-OS, start/stop the VM) from the Genode window as the screenshot shows.
So at first I would like to stick with Seoul. In this case, being able to run multiple VMs (Seoul+TinyCore) from Genode/Nova. Which way shall I follow to create a run script that fullfils what I expect? Is there already any run script?
you may try the branch [0] , which contains a new run script in repos/gems/run/seoul-wm-cli.run. The script creates a GUI scenario (nitpicker + window manager) containing the cli_monitor applications with which you can start/kill via a command-line-based launcher several Seoul instances using the Tinycore VM. I added several drivers - like usb, ps/2 and the nic driver and nic bridge, so that you should be able to use the Browser in the VM - if your hardware is supported.
Just invoke the run script and copy the result via dd to your USB stick. (Running in Qemu should also work but it is not sooo quick).
In the cli monitor application you just have to type
start seoul
Cheers,
Alex.
Hi Alex, Thanks, that is what I was looking for. I tested with QEMU. However, after booting from USB stick, my USB keyboard / mouse doesn´t work. I am not able to capture any log. I am using a normal x86 desktop computer. ---- Regarding the seoul multiboot scheme, I saw it does not allow a ISO, correct? It seems to expect a bootloader (munich), them the bzImage, an some aditional gz. Actually I have prepared a custom remasterized version of TinyCore with some specific libs / apps. It works alone. But when I tried to port to seoul, sitill using munich, I don´t have a bzImage. I have a vmlinuz, core.gz and my own stuff as TCZ extensions. The vmlinuz I customize some files. I really don´t know to set up this to work with seoul. Sorry if it is a naive question, I am not kernel specialist, I am more of a application developer.
Regards, Roger
Subject: Re: Genode/NOVA+Multiple VMMs Seoul / VBox To: genode-main@lists.sourceforge.net From: alexander.boettcher@...1... Date: Thu, 3 Sep 2015 11:40:52 +0200
Hello,
On 01.09.2015 16:48, Roger Ferreira wrote:
Dear Genode Community, I would like also to be able to control and see the VMs (enter the Guest-OS, start/stop the VM) from the Genode window as the screenshot shows.
So at first I would like to stick with Seoul. In this case, being able to run multiple VMs (Seoul+TinyCore) from Genode/Nova. Which way shall I follow to create a run script that fullfils what I expect? Is there already any run script?
you may try the branch [0] , which contains a new run script in repos/gems/run/seoul-wm-cli.run. The script creates a GUI scenario (nitpicker + window manager) containing the cli_monitor applications with which you can start/kill via a command-line-based launcher several Seoul instances using the Tinycore VM. I added several drivers - like usb, ps/2 and the nic driver and nic bridge, so that you should be able to use the Browser in the VM - if your hardware is supported.
Just invoke the run script and copy the result via dd to your USB stick. (Running in Qemu should also work but it is not sooo quick).
In the cli monitor application you just have to type
start seoul
Cheers,
Alex.
[0] https://github.com/alex-ab/genode/tree/seoul_wm_cli
Monitor Your Dynamic Infrastructure at Any Scale With Datadog! Get real-time metrics from all of your servers, apps and tools in one place. SourceForge users - Click here to start your Free Trial of Datadog now! http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140 _______________________________________________ genode-main mailing list genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
Hello,
On 04.09.2015 15:51, Roger Ferreira wrote:
I am not able to capture any log.
I fear without any log it will become hard to impossible to get it running.
I am using a normal x86 desktop computer.
You should, for example, obtain a PCI serial card and attach it - if your machine hasn't already a serial connector on-board or something like Intel AMT SOL (SerialOverLAN).
Regarding the seoul multiboot scheme, I saw it does not allow a ISO, correct?
Yes.
It seems to expect a bootloader (munich), them the bzImage, an some aditional g Actually I have prepared a custom remasterized version of TinyCore with some specific libs / apps. It works alone. But when I tried to port to seoul, sitill using munich, I don´t have a bzImage. I have a vmlinuz, core.gz and my own stuff as TCZ extensions. The vmlinuz I customize some files.
For Seoul you have two ways to boot things - either boot a multiboot compliant kernel, which Linux is not, or boot a VM from a raw disk image.
Munich (as a multiboot kernel) is a small helper to bootstrap a Linux kernel. Munich expects as first multiboot image the Linux kernel and the second multiboot image has to be the initial ram disk. (see http://os.inf.tu-dresden.de/~kauer/oslo/README for pointers to munich)
For the Seoul/Tinycore demo we had to manually squash the core.gz and all the Firefox browser related files into a initial ram disk (tc-browser.gz). I fear we didn't documented it well. As far as I remember it was no fun. Could be - because we don't create for Seoul VMs regularly. So, we have no ready to use work-flow we could share. Setting up a VM with Virtualbox is - in that regard - much more user-friendly.
The other option of course is to install your intended VM setup on a disk - or in a VM on a virtual disk, e.g. use Virtualbox on your Linux/Windows. Finally use the raw disk image for Seoul - there are ways to convert a vdi/vmdk image into a raw disk image. A hybrid iso/usb bootable image should also work in principal as raw disk image - however never tried.
Just a note - you may need several iterations of Linux kernel configuration tweaking and rebuilds until you may get it running in Seoul. Seoul was/is more or less a research VMM and does not support everything out-of-a-box what a standard Linux distribution kernel enables/expects from the hardware.
Regards,
Alex.
Hi Alex, I understand the 2 options. But I still have more doubt / questions. In the multiboot scheme, I tried to replace the bzImage with the newer TinyCore 6.3 vmlinuz together with the initrd core.gz. But that didn´t work. In thesis, I just replaced the kernel, the bzImage by the vmlinuz. I even tried to compare bzImage and vmlinuz files using xxd and od -xc. vmlinuz begins with MZ. I get the following error message I found on munich source code: ERROR(-11, ~mbi->flags & MBI_FLAG_MODS, "module flag missing"); I don´t have any idea how to debug this to find out what is wrong. I got the munich source code thinking to place some PRINTF stuff, but I don´t know how to make it. I am using Ubuntu 12.04. ---------- Then I tried the 2nd option. I create a raw disk using qemu-img, than I use dd to format it from a iso. But now I don´t know how to configure that in the run script. I tried in the <multiboot> section without success. I believe it should be in another place. Any hint? How to find documentation regarding that? Thanks for your help and patiente. Regards, Roger
Subject: Re: Genode/NOVA+Multiple VMMs Seoul / VBox To: genode-main@lists.sourceforge.net From: alexander.boettcher@...1... Date: Sat, 5 Sep 2015 22:25:44 +0200
Hello,
On 04.09.2015 15:51, Roger Ferreira wrote:
I am not able to capture any log.
I fear without any log it will become hard to impossible to get it running.
I am using a normal x86 desktop computer.
You should, for example, obtain a PCI serial card and attach it - if your machine hasn't already a serial connector on-board or something like Intel AMT SOL (SerialOverLAN).
Regarding the seoul multiboot scheme, I saw it does not allow a ISO, correct?
Yes.
It seems to expect a bootloader (munich), them the bzImage, an some aditional g Actually I have prepared a custom remasterized version of TinyCore with some specific libs / apps. It works alone. But when I tried to port to seoul, sitill using munich, I don´t have a bzImage. I have a vmlinuz, core.gz and my own stuff as TCZ extensions. The vmlinuz I customize some files.
For Seoul you have two ways to boot things - either boot a multiboot compliant kernel, which Linux is not, or boot a VM from a raw disk image.
Munich (as a multiboot kernel) is a small helper to bootstrap a Linux kernel. Munich expects as first multiboot image the Linux kernel and the second multiboot image has to be the initial ram disk. (see http://os.inf.tu-dresden.de/~kauer/oslo/README for pointers to munich)
For the Seoul/Tinycore demo we had to manually squash the core.gz and all the Firefox browser related files into a initial ram disk (tc-browser.gz). I fear we didn't documented it well. As far as I remember it was no fun. Could be - because we don't create for Seoul VMs regularly. So, we have no ready to use work-flow we could share. Setting up a VM with Virtualbox is - in that regard - much more user-friendly.
The other option of course is to install your intended VM setup on a disk - or in a VM on a virtual disk, e.g. use Virtualbox on your Linux/Windows. Finally use the raw disk image for Seoul - there are ways to convert a vdi/vmdk image into a raw disk image. A hybrid iso/usb bootable image should also work in principal as raw disk image - however never tried.
Just a note - you may need several iterations of Linux kernel configuration tweaking and rebuilds until you may get it running in Seoul. Seoul was/is more or less a research VMM and does not support everything out-of-a-box what a standard Linux distribution kernel enables/expects from the hardware.
Regards,
Alex.
genode-main mailing list genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
Hello Roger,
On 06.09.2015 20:21, Roger Ferreira wrote:
In the multiboot scheme, I tried to replace the bzImage with the newer TinyCore 6.3 vmlinuz together with the initrd core.gz. But that didn´t work.
On Qemu it doesn't work for me either. Natively (Intel Core i5, Lenovo X201) it does - at least Tinycore 6.3. boots up into a shell from where I can access the network. So, I just downloaded http://tinycorelinux.net/6.x/x86/release/Core-6.3.iso and copied out the vmlinuz and core.gz and used it together with 'munich'.
I create a raw disk using qemu-img, than I use dd to format it from a iso. But now I don´t know how to configure that in the run script. I tried in the <multiboot> section without success.
I extended my branch and added to the setup a Seoul VM configuration, which boots from a raw disc image. I had no success with Tinycore, however some Genode scenarios booted natively (not in Qemu!). E.g. I build Genode/Fiasco run/printf and used this hybrid iso/usb image unmodified as raw disc with the Seoul VMM.
In the Genode cli_monitor shell you now may also use "start seoul-img" beside "start seoul".
Any hint? How to find documentation regarding that?
Not I'm aware of. For configuration of the Seoul VMM you may have a look into the files located in contrib/seoul-<hash>/src/app/seoul/model/*. At the end of all the models there is a short description how to configure the models - parameters etc. For the Genode port of Seoul we translate it in repos/ports/src/app/seoul/device_model_registry.cc to xml syntax, which you finally can add to the <config> node of the Genode Seoul process. This is done, e.g., in seoul.inc which generates the Genode configuration for Seoul and stores it as vm_seoul.cfg in your build directory.
For repos/gems/run/seoul-wm-cli.run the Seoul VM configurations are fixed and created in rom_fs inlined - to make it hopefully easier to read/grasp by a user.
Hope it clarifies a bit,
Alex.
Thanks for your help and patiente. Regards, Roger
Subject: Re: Genode/NOVA+Multiple VMMs Seoul / VBox To: genode-main@lists.sourceforge.net From: alexander.boettcher@...1... Date: Sat, 5 Sep 2015 22:25:44 +0200
Hello,
On 04.09.2015 15:51, Roger Ferreira wrote:
I am not able to capture any log.
I fear without any log it will become hard to impossible to get it running.
I am using a normal x86 desktop computer.
You should, for example, obtain a PCI serial card and attach it - if your machine hasn't already a serial connector on-board or something like Intel AMT SOL (SerialOverLAN).
Regarding the seoul multiboot scheme, I saw it does not allow a ISO, correct?
Yes.
It seems to expect a bootloader (munich), them the bzImage, an some aditional g Actually I have prepared a custom remasterized version of TinyCore with some specific libs / apps. It works alone. But when I tried to port to seoul, sitill using munich, I don´t have a bzImage. I have a vmlinuz, core.gz and my own stuff as TCZ extensions. The vmlinuz I customize some files.
For Seoul you have two ways to boot things - either boot a multiboot compliant kernel, which Linux is not, or boot a VM from a raw disk image.
Munich (as a multiboot kernel) is a small helper to bootstrap a Linux kernel. Munich expects as first multiboot image the Linux kernel and the second multiboot image has to be the initial ram disk. (see http://os.inf.tu-dresden.de/~kauer/oslo/README for pointers to munich)
For the Seoul/Tinycore demo we had to manually squash the core.gz and all the Firefox browser related files into a initial ram disk (tc-browser.gz). I fear we didn't documented it well. As far as I remember it was no fun. Could be - because we don't create for Seoul VMs regularly. So, we have no ready to use work-flow we could share. Setting up a VM with Virtualbox is - in that regard - much more user-friendly.
The other option of course is to install your intended VM setup on a disk - or in a VM on a virtual disk, e.g. use Virtualbox on your Linux/Windows. Finally use the raw disk image for Seoul - there are ways to convert a vdi/vmdk image into a raw disk image. A hybrid iso/usb bootable image should also work in principal as raw disk image - however never tried.
Just a note - you may need several iterations of Linux kernel configuration tweaking and rebuilds until you may get it running in Seoul. Seoul was/is more or less a research VMM and does not support everything out-of-a-box what a standard Linux distribution kernel enables/expects from the hardware.
Regards,
Alex.
genode-main mailing list genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
genode-main mailing list genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
Hi Alex,
First of all thanks for your time and patience.
I struggled with inumerous attempts.
First I checked how you built the tc-browser.gz.
Instead of cpio / gunzip, you did a disk image which I could reproduce with dd and mkfs.ext2.
But I kept using cpio / gunzip and advdef in the end to build the final gz.
Finally I managed to produce a "working version" with qemu-TC only, and then with qemu-Genode/Seoul-TC.
What I noticed it that there must be a SIZE limit for the INITRD file.
Initially it was as big as 256 M, which then I reduced close to 100 M.
But only when I got close to 46 M, like tc-browser.tc, it worked.
I don´t if this limit depends on qemu, could not find further info.
Unfortunatelly, I don´t know yet why, but TC does not do the login. It ends with login prompt.
I tried different boot codes, checked the INITRD files, folders, permissions, etc.
With your version of bzImage / tc-browser.gz works nicely!
------
I understood how seoul-wm-cli.run is configured, with the inlined representing the vm_seoul.cfg .
I will try to see later the new setup you created.
------
What I realized so far, is that this setup with Seoul-Customized TC is more complicated than I expected.
I will try to go back with the VirtualBox examples and see if I can do with the CLI monitor the same, replacing Seoul with VBox.
I still need to have some GUI to Manage (view / control) the VMs.
For me it is much easier to have a ISO as VM.
Regards,
Roger
Subject: Re: Genode/NOVA+Multiple VMMs Seoul / VBox To: genode-main@lists.sourceforge.net From: alexander.boettcher@...1... Date: Mon, 7 Sep 2015 12:56:48 +0200
Hello Roger,
On 06.09.2015 20:21, Roger Ferreira wrote:
In the multiboot scheme, I tried to replace the bzImage with the newer TinyCore 6.3 vmlinuz together with the initrd core.gz. But that didn´t work.
On Qemu it doesn't work for me either. Natively (Intel Core i5, Lenovo X201) it does - at least Tinycore 6.3. boots up into a shell from where I can access the network. So, I just downloaded http://tinycorelinux.net/6.x/x86/release/Core-6.3.iso and copied out the vmlinuz and core.gz and used it together with 'munich'.
I create a raw disk using qemu-img, than I use dd to format it from a iso. But now I don´t know how to configure that in the run script. I tried in the <multiboot> section without success.
I extended my branch and added to the setup a Seoul VM configuration, which boots from a raw disc image. I had no success with Tinycore, however some Genode scenarios booted natively (not in Qemu!). E.g. I build Genode/Fiasco run/printf and used this hybrid iso/usb image unmodified as raw disc with the Seoul VMM.
In the Genode cli_monitor shell you now may also use "start seoul-img" beside "start seoul".
Any hint? How to find documentation regarding that?
Not I'm aware of. For configuration of the Seoul VMM you may have a look into the files located in contrib/seoul-<hash>/src/app/seoul/model/*. At the end of all the models there is a short description how to configure the models - parameters etc. For the Genode port of Seoul we translate it in repos/ports/src/app/seoul/device_model_registry.cc to xml syntax, which you finally can add to the <config> node of the Genode Seoul process. This is done, e.g., in seoul.inc which generates the Genode configuration for Seoul and stores it as vm_seoul.cfg in your build directory.
For repos/gems/run/seoul-wm-cli.run the Seoul VM configurations are fixed and created in rom_fs inlined - to make it hopefully easier to read/grasp by a user.
Hope it clarifies a bit,
Alex.
Thanks for your help and patiente. Regards, Roger
Subject: Re: Genode/NOVA+Multiple VMMs Seoul / VBox To: genode-main@lists.sourceforge.net From: alexander.boettcher@...1... Date: Sat, 5 Sep 2015 22:25:44 +0200
Hello,
On 04.09.2015 15:51, Roger Ferreira wrote:
I am not able to capture any log.
I fear without any log it will become hard to impossible to get it running.
I am using a normal x86 desktop computer.
You should, for example, obtain a PCI serial card and attach it - if your machine hasn't already a serial connector on-board or something like Intel AMT SOL (SerialOverLAN).
Regarding the seoul multiboot scheme, I saw it does not allow a ISO, correct?
Yes.
It seems to expect a bootloader (munich), them the bzImage, an some aditional g Actually I have prepared a custom remasterized version of TinyCore with some specific libs / apps. It works alone. But when I tried to port to seoul, sitill using munich, I don´t have a bzImage. I have a vmlinuz, core.gz and my own stuff as TCZ extensions. The vmlinuz I customize some files.
For Seoul you have two ways to boot things - either boot a multiboot compliant kernel, which Linux is not, or boot a VM from a raw disk image.
Munich (as a multiboot kernel) is a small helper to bootstrap a Linux kernel. Munich expects as first multiboot image the Linux kernel and the second multiboot image has to be the initial ram disk. (see http://os.inf.tu-dresden.de/~kauer/oslo/README for pointers to munich)
For the Seoul/Tinycore demo we had to manually squash the core.gz and all the Firefox browser related files into a initial ram disk (tc-browser.gz). I fear we didn't documented it well. As far as I remember it was no fun. Could be - because we don't create for Seoul VMs regularly. So, we have no ready to use work-flow we could share. Setting up a VM with Virtualbox is - in that regard - much more user-friendly.
The other option of course is to install your intended VM setup on a disk - or in a VM on a virtual disk, e.g. use Virtualbox on your Linux/Windows. Finally use the raw disk image for Seoul - there are ways to convert a vdi/vmdk image into a raw disk image. A hybrid iso/usb bootable image should also work in principal as raw disk image - however never tried.
Just a note - you may need several iterations of Linux kernel configuration tweaking and rebuilds until you may get it running in Seoul. Seoul was/is more or less a research VMM and does not support everything out-of-a-box what a standard Linux distribution kernel enables/expects from the hardware.
Regards,
Alex.
genode-main mailing list genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
genode-main mailing list genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
genode-main mailing list genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
Hi,
On 10.09.2015 21:55, Roger Ferreira wrote:
Initially it was as big as 256 M, which then I reduced close to 100 M.
But only when I got close to 46 M, like tc-browser.tc, it worked.
Did you try to set ramdisk_size on the linux command line ? The default size according to "scripts/extract-ikconfig bzImage-3.1" is:
CONFIG_BLK_DEV_RAM=y CONFIG_BLK_DEV_RAM_COUNT=1 CONFIG_BLK_DEV_RAM_SIZE=131072
Maybe the 128M are to small for your setup ?
Alex.
Hi, Actually 2 times that, 256 MB. But in this case I would need to COMPILE / BUILD TinyCore from source. At least the kernel. I found this file with the following set:http://tinycorelinux.net/6.x/x86/release/src/kernel/config-3.16.6-tinycoreCO... CONFIG_BLK_DEV_RAM_COUNT=8 CONFIG_BLK_DEV_RAM_SIZE=8192yielding a limit of 64 M.You are suggesting to get the patched kernel and build it?http://tinycorelinux.net/6.x/x86/release/src/kernel/linux-3.16.6-patched.txz
Subject: Re: Genode/NOVA+Multiple VMMs Seoul / VBox To: genode-main@lists.sourceforge.net From: alexander.boettcher@...1... Date: Thu, 10 Sep 2015 23:17:19 +0200
Hi,
On 10.09.2015 21:55, Roger Ferreira wrote:
Initially it was as big as 256 M, which then I reduced close to 100 M.
But only when I got close to 46 M, like tc-browser.tc, it worked.
Did you try to set ramdisk_size on the linux command line ? The default size according to "scripts/extract-ikconfig bzImage-3.1" is:
CONFIG_BLK_DEV_RAM=y CONFIG_BLK_DEV_RAM_COUNT=1 CONFIG_BLK_DEV_RAM_SIZE=131072
Maybe the 128M are to small for your setup ?
Alex.
Monitor Your Dynamic Infrastructure at Any Scale With Datadog! Get real-time metrics from all of your servers, apps and tools in one place. SourceForge users - Click here to start your Free Trial of Datadog now! http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140 _______________________________________________ genode-main mailing list genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
Hi,
On 13.09.2015 00:30, Roger Ferreira wrote:
CONFIG_BLK_DEV_RAM_SIZE=8192yielding a limit of 64 M.You are suggesting to get the patched kernel and build it?http://tinycorelinux.net/6.x/x86/release/src/kernel/linux-3.16.6-patched.txz
just tried myself to increase the ramdisk and changed nothing else and it succeeded to boot (and the root fs is now 256M big compared to 128M before) - so just ignore my comment - seems to have no effect actually.
What I noticed it that there must be a SIZE limit for the INITRD file. Initially it was as big as 256 M, which then I reduced close to 100 M. But only when I got close to 46 M, like tc-browser.tc, it worked.
How exactly does the error case looks like (the linux kernel complains, or the seoul VMM complains, or some Genode components ?)
Alex.
Hi, I built a 89M image and I am using Tinycore 6.3 vmlinuz. I get the following error on QEMU window:> sudo qemu-system-i386 -kernel vmlinuz -append "quiet" -initrd tc-dds.gzFailed to execute /init (error -28)Kernel panic - not syncing: No working init found. On Genode with QEMU, using the seoul-wm-cli.run script adapted to the new kernel / initrd images everything works fine:genode/build/nova_x86_32$ make run/seoul-wm-cli_tc until I launch the VM:> start seoul
The same error saw on QEMU alone appears in the cli_monitor->seoul VM window. I will try to build the kernel. Thanks.
Subject: Re: Genode/NOVA+Multiple VMMs Seoul / VBox To: genode-main@lists.sourceforge.net From: alexander.boettcher@...1... Date: Sun, 13 Sep 2015 13:21:12 +0200
Hi,
On 13.09.2015 00:30, Roger Ferreira wrote:
CONFIG_BLK_DEV_RAM_SIZE=8192yielding a limit of 64 M.You are suggesting to get the patched kernel and build it?http://tinycorelinux.net/6.x/x86/release/src/kernel/linux-3.16.6-patched.txz
just tried myself to increase the ramdisk and changed nothing else and it succeeded to boot (and the root fs is now 256M big compared to 128M before) - so just ignore my comment - seems to have no effect actually.
What I noticed it that there must be a SIZE limit for the INITRD file. Initially it was as big as 256 M, which then I reduced close to 100 M. But only when I got close to 46 M, like tc-browser.tc, it worked.
How exactly does the error case looks like (the linux kernel complains, or the seoul VMM complains, or some Genode components ?)
Alex.
genode-main mailing list genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
Initrd images are usually (if not always) cpio archives without gzip compression. On Sep 13, 2015 6:43 AM, "Roger Ferreira" <rogerdff@...16...> wrote:
Hi,
I built a 89M image and I am using Tinycore 6.3 vmlinuz.
I get the following error on QEMU window:
sudo qemu-system-i386 -kernel vmlinuz -append "quiet" -initrd tc-dds.gz
Failed to execute /init (error -28) Kernel panic - not syncing: No working init found.
On Genode with QEMU, using the seoul-wm-cli.run script adapted to the new kernel / initrd images everything works fine: genode/build/nova_x86_32$ make run/seoul-wm-cli_tc
until I launch the VM:
start seoul
The same error saw on QEMU alone appears in the cli_monitor->seoul VM window.
I will try to build the kernel.
Thanks.
Subject: Re: Genode/NOVA+Multiple VMMs Seoul / VBox To: genode-main@lists.sourceforge.net From: alexander.boettcher@...1... Date: Sun, 13 Sep 2015 13:21:12 +0200
Hi,
On 13.09.2015 00:30, Roger Ferreira wrote:
CONFIG_BLK_DEV_RAM_SIZE=8192yielding a limit of 64 M.You are
suggesting to get the patched kernel and build it? http://tinycorelinux.net/6.x/x86/release/src/kernel/linux-3.16.6-patched.txz
just tried myself to increase the ramdisk and changed nothing else and it succeeded to boot (and the root fs is now 256M big compared to 128M before) - so just ignore my comment - seems to have no effect actually.
What I noticed it that there must be a SIZE limit for the INITRD file. Initially it was as big as 256 M, which then I reduced close to 100 M. But only when I got close to 46 M, like tc-browser.tc, it worked.
How exactly does the error case looks like (the linux kernel complains, or the seoul VMM complains, or some Genode components ?)
Alex.
genode-main mailing list genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
genode-main mailing list genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
Hi, By reading Documentation/init.txt I realized I was missing the root=/dev/ram0. That solved the problem. In the original run script example, it is there in the cmdline. I am quite sure I had tested before with that boot option. The only difference is that I managed to reduce the image now down to 89M. Nevertheless, I appreciate the help and apologize for any inconvenience.
Regards, Roger Date: Sun, 13 Sep 2015 15:06:47 +0000 Subject: RE: Genode/NOVA+Multiple VMMs Seoul / VBox From: hungryninja101@...9... To: genode-main@lists.sourceforge.net
Initrd images are usually (if not always) cpio archives without gzip compression. On Sep 13, 2015 6:43 AM, "Roger Ferreira" <rogerdff@...16...> wrote:
Hi, I built a 89M image and I am using Tinycore 6.3 vmlinuz. I get the following error on QEMU window:> sudo qemu-system-i386 -kernel vmlinuz -append "quiet" -initrd tc-dds.gzFailed to execute /init (error -28)Kernel panic - not syncing: No working init found. On Genode with QEMU, using the seoul-wm-cli.run script adapted to the new kernel / initrd images everything works fine:genode/build/nova_x86_32$ make run/seoul-wm-cli_tc until I launch the VM:> start seoul
The same error saw on QEMU alone appears in the cli_monitor->seoul VM window. I will try to build the kernel. Thanks.
Subject: Re: Genode/NOVA+Multiple VMMs Seoul / VBox To: genode-main@lists.sourceforge.net From: alexander.boettcher@...1... Date: Sun, 13 Sep 2015 13:21:12 +0200
Hi,
On 13.09.2015 00:30, Roger Ferreira wrote:
CONFIG_BLK_DEV_RAM_SIZE=8192yielding a limit of 64 M.You are suggesting to get the patched kernel and build it?http://tinycorelinux.net/6.x/x86/release/src/kernel/linux-3.16.6-patched.txz
just tried myself to increase the ramdisk and changed nothing else and it succeeded to boot (and the root fs is now 256M big compared to 128M before) - so just ignore my comment - seems to have no effect actually.
What I noticed it that there must be a SIZE limit for the INITRD file. Initially it was as big as 256 M, which then I reduced close to 100 M. But only when I got close to 46 M, like tc-browser.tc, it worked.
How exactly does the error case looks like (the linux kernel complains, or the seoul VMM complains, or some Genode components ?)
Alex.
genode-main mailing list genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
------------------------------------------------------------------------------
_______________________________________________
genode-main mailing list
genode-main@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/genode-main
------------------------------------------------------------------------------ _______________________________________________ genode-main mailing list genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
Hello,
On 13.09.2015 21:10, Roger Ferreira wrote:
The only difference is that I managed to reduce the image now down to 89M. Nevertheless, I appreciate the help and apologize for any inconvenience.
I get the following error on QEMU window: sudo qemu-system-i386 -kernel vmlinuz -append "quiet" -initrd tc-dds.gzFailed to execute /init (error -28)Kernel panic - not syncing: No working init found.
Make sure to use some "-m" option with Qemu, otherwise your VM only sees 128M RAM by default - which is far to less. Something like "-m 256" should do in your case.
I played a bit around and found now a workflow to build a customized Tinycore based VM image which boots up nicely in Seoul on native hardware as Qemu(if you patient enough).
I updated my branch with necessary fixes [0] and attached the howto to this mail.
Cheers,
Alex
Hi Alex,
You are right, later on I had to use the -m option with QEMU.
I will take a look and try the new fix.
Thanks a lot for your help and availability.
Subject: Re: Genode/NOVA+Multiple VMMs Seoul / VBox To: genode-main@lists.sourceforge.net From: alexander.boettcher@...1... Date: Mon, 14 Sep 2015 14:02:07 +0200
Hello,
On 13.09.2015 21:10, Roger Ferreira wrote:
The only difference is that I managed to reduce the image now down to 89M. Nevertheless, I appreciate the help and apologize for any inconvenience.
I get the following error on QEMU window: sudo qemu-system-i386 -kernel vmlinuz -append "quiet" -initrd tc-dds.gzFailed to execute /init (error -28)Kernel panic - not syncing: No working init found.
Make sure to use some "-m" option with Qemu, otherwise your VM only sees 128M RAM by default - which is far to less. Something like "-m 256" should do in your case.
I played a bit around and found now a workflow to build a customized Tinycore based VM image which boots up nicely in Seoul on native hardware as Qemu(if you patient enough).
I updated my branch with necessary fixes [0] and attached the howto to this mail.
Cheers,
Alex
[0] https://github.com/alex-ab/genode/tree/seoul_wm_cli
------------------------------------------------------------------------------ _______________________________________________ genode-main mailing list genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
Hi Alex, I did follow and tested the image case. I am using nova_x86_32. I works on QEMU alone. Unfortunately, with Genode-Seoul-QEMU, seoul-wm-cli.run script, it boots but after a while Loading Extensions..., a memory problem appears:[cli_monitor -> seoul-img -> seoul] Uncaught exception of type 'N6Genode9Allocator130Out_of_memoryE´ (use ´c++filt -t´ to demangle)[cli_monitor -> seoul-img -> seoul] abort called - thread: ´vCPU dispatcher´ Subject: Re: Genode/NOVA+Multiple VMMs Seoul / VBox To: genode-main@lists.sourceforge.net From: alexander.boettcher@...1... Date: Mon, 14 Sep 2015 14:02:07 +0200
Hello,
On 13.09.2015 21:10, Roger Ferreira wrote:
The only difference is that I managed to reduce the image now down to 89M. Nevertheless, I appreciate the help and apologize for any inconvenience.
I get the following error on QEMU window: sudo qemu-system-i386 -kernel vmlinuz -append "quiet" -initrd tc-dds.gzFailed to execute /init (error -28)Kernel panic - not syncing: No working init found.
Make sure to use some "-m" option with Qemu, otherwise your VM only sees 128M RAM by default - which is far to less. Something like "-m 256" should do in your case.
I played a bit around and found now a workflow to build a customized Tinycore based VM image which boots up nicely in Seoul on native hardware as Qemu(if you patient enough).
I updated my branch with necessary fixes [0] and attached the howto to this mail.
Cheers,
Alex
[0] https://github.com/alex-ab/genode/tree/seoul_wm_cli
------------------------------------------------------------------------------ _______________________________________________ genode-main mailing list genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
Hi Ferreira,
On 19.09.2015 03:27, Roger Ferreira wrote:
Hi Alex, I did follow and tested the image case. I am using nova_x86_32. I works on QEMU alone. Unfortunately, with Genode-Seoul-QEMU, seoul-wm-cli.run script, it boots but after a while Loading Extensions..., a memory problem appears:[cli_monitor -> seoul-img -> seoul] Uncaught exception of type 'N6Genode9Allocator130Out_of_memoryE´ (use ´c++filt -t´ to demangle)[cli_monitor -> seoul-img -> seoul] abort called - thread: ´vCPU dispatcher´ Subject: Re: Genode/NOVA+Multiple VMMs Seoul / VBox
sound familiar - I added to the seoul_wm_cli branch a fixup commit.
Alex.
To: genode-main@lists.sourceforge.net From: alexander.boettcher@...1... Date: Mon, 14 Sep 2015 14:02:07 +0200
Hello,
On 13.09.2015 21:10, Roger Ferreira wrote:
The only difference is that I managed to reduce the image now down to 89M. Nevertheless, I appreciate the help and apologize for any inconvenience.
I get the following error on QEMU window: sudo qemu-system-i386 -kernel vmlinuz -append "quiet" -initrd tc-dds.gzFailed to execute /init (error -28)Kernel panic - not syncing: No working init found.
Make sure to use some "-m" option with Qemu, otherwise your VM only sees 128M RAM by default - which is far to less. Something like "-m 256" should do in your case.
I played a bit around and found now a workflow to build a customized Tinycore based VM image which boots up nicely in Seoul on native hardware as Qemu(if you patient enough).
I updated my branch with necessary fixes [0] and attached the howto to this mail.
Cheers,
Alex
[0] https://github.com/alex-ab/genode/tree/seoul_wm_cli
genode-main mailing list genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
genode-main mailing list genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
Hi Alex, Thanks, it worked. I tested the iso with QEMU and VMware Player. Will try booting from a USB later. The VGA configuration you describe has to be followed strictly. I tried Xorg without success. ----- Taking advantage, now that I have this setup working, I would like to improve it a bit. In the wm-cli, if possible, how could I:- setup a minimal file system to share files among VMs- shutdown / reboot the base system Regards, Roger
Subject: Re: Genode/NOVA+Multiple VMMs Seoul / VBox To: genode-main@lists.sourceforge.net From: alexander.boettcher@...1... Date: Mon, 21 Sep 2015 09:28:47 +0200
Hi Ferreira,
On 19.09.2015 03:27, Roger Ferreira wrote:
Hi Alex, I did follow and tested the image case. I am using nova_x86_32. I works on QEMU alone. Unfortunately, with Genode-Seoul-QEMU, seoul-wm-cli.run script, it boots but after a while Loading Extensions..., a memory problem appears:[cli_monitor -> seoul-img -> seoul] Uncaught exception of type 'N6Genode9Allocator130Out_of_memoryE´ (use ´c++filt -t´ to demangle)[cli_monitor -> seoul-img -> seoul] abort called - thread: ´vCPU dispatcher´ Subject: Re: Genode/NOVA+Multiple VMMs Seoul / VBox
sound familiar - I added to the seoul_wm_cli branch a fixup commit.
Alex.
To: genode-main@lists.sourceforge.net From: alexander.boettcher@...1... Date: Mon, 14 Sep 2015 14:02:07 +0200
Hello,
On 13.09.2015 21:10, Roger Ferreira wrote:
The only difference is that I managed to reduce the image now down to 89M. Nevertheless, I appreciate the help and apologize for any inconvenience.
I get the following error on QEMU window: sudo qemu-system-i386 -kernel vmlinuz -append "quiet" -initrd tc-dds.gzFailed to execute /init (error -28)Kernel panic - not syncing: No working init found.
Make sure to use some "-m" option with Qemu, otherwise your VM only sees 128M RAM by default - which is far to less. Something like "-m 256" should do in your case.
I played a bit around and found now a workflow to build a customized Tinycore based VM image which boots up nicely in Seoul on native hardware as Qemu(if you patient enough).
I updated my branch with necessary fixes [0] and attached the howto to this mail.
Cheers,
Alex
[0] https://github.com/alex-ab/genode/tree/seoul_wm_cli
genode-main mailing list genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
genode-main mailing list genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
genode-main mailing list genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
Hi Ferreira,
On 22.09.2015 02:13, Roger Ferreira wrote:
Thanks, it worked.
nice !
The VGA configuration you describe has to be followed strictly. I tried Xorg without success.
Yes. You need to have Xfbdev.
Taking advantage, now that I have this setup working, I would like to improve it a bit. In the wm-cli, if possible, how could I:
- setup a minimal file system to share files among VMs
There is no support by the Seoul VMM to setup a shared filesystem between VM and host (Genode). (In contrast: Virtualbox has support by using the guest additions within the VM. This is supported already by our VBox port.) You would need for Seoul to setup some network file system between Seoul VM and Genode host - but that is not my familiar topic.
Emery, Josef, others : do you think some 9p based setup is imaginable respectively working already ? Better ideas ?
- shutdown / reboot the base system
Their is no support in Genode right now.
Cheers,
Alex.
Hey,
On Tue, Sep 22, 2015 at 01:27:32PM +0200, Alexander Boettcher wrote:
Emery, Josef, others : do you think some 9p based setup is imaginable respectively working already ? Better ideas ?
It would be great if we had virtio-9p http://www.linux-kvm.org/page/9p_virtio in Seoul but after a look into Qemu sources the implementation seems fairly extensive.
Regards
On Tue, Sep 22, 2015 at 04:47:03PM +0200, Christian Helmuth wrote:
Hey,
On Tue, Sep 22, 2015 at 01:27:32PM +0200, Alexander Boettcher wrote:
Emery, Josef, others : do you think some 9p based setup is imaginable respectively working already ? Better ideas ?
It would be great if we had virtio-9p http://www.linux-kvm.org/page/9p_virtio in Seoul but after a look into Qemu sources the implementation seems fairly extensive.
I'm compiling a kernel for seoul right now, if that goes well, I may take a stab at it. I was thinking I would start with TCP rather than virtio, but if virtio looks like a socket shouldn't be too hard to do both.
Emery
Hi, I read about the 9pvirtio. That would do the job. Actually, my main objective is to use DDS (Data Distribution Service), from OMG, as a communication middleware for my apps, which beneath relies on TCP/UDP. Among different implementations, I will be using OpenDDS, since I need the sources. I was first trying to port OpenDDS to Genode, expecting to use Genode as the Guest-OS, but it was taking a lot of time to port the libraries. I stopped in the fifth, there are almost 20. I then decided to use TinyCore and could easily build the OpenDDS lib in it. But besides that, it would be nice to have a way to share some files. Or at least some sort of Shared Memory between the VMs. ------In the mean time, I will also be trying VBox. Regards, Roger Date: Tue, 22 Sep 2015 19:32:25 +0200 From: emery@...261... To: genode-main@lists.sourceforge.net Subject: Re: Genode/NOVA+Multiple VMMs Seoul / VBox
On Tue, Sep 22, 2015 at 04:47:03PM +0200, Christian Helmuth wrote:
Hey,
On Tue, Sep 22, 2015 at 01:27:32PM +0200, Alexander Boettcher wrote:
Emery, Josef, others : do you think some 9p based setup is imaginable respectively working already ? Better ideas ?
It would be great if we had virtio-9p http://www.linux-kvm.org/page/9p_virtio in Seoul but after a look into Qemu sources the implementation seems fairly extensive.
I'm compiling a kernel for seoul right now, if that goes well, I may take a stab at it. I was thinking I would start with TCP rather than virtio, but if virtio looks like a socket shouldn't be too hard to do both.
Emery
------------------------------------------------------------------------------ _______________________________________________ genode-main mailing list genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
-
unknown＠example.com -
Alexander Boettcher -
Christian Helmuth -
Nobody III -
Roger Ferreira