Re: running Virtualbox on Genode
Hi Vincent, > The thing that I don't understand are the macros that you use in scripts > - such as "assert_spec". > Can you point me to where I can find documentation for the various > macros which I understand are based on Expect. in /tool/run/run the specific Expect procedure is defined. For a general understanding what Genode spec values are and used for please read chapter "5.3.4. Platform specifications" of the Genode book [0]. > Noted. I'll try to explore using Intel AMT to support the serial logging. > I've acquired a refurbished Lenovo X201, can you advise how I can try to > emulate what Norman is doing - configuration and run scripts. Read [1] and follow the traces ;-) In the referenced github issue all information are available to setup the scenario. Cheers, Alex. [0] http://genode.org/documentation/genode-foundations-15-05.pdf [1] http://sourceforge.net/p/genode/mailman/message/34165676/ -- 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
Re: running Virtualbox on Genode
Hi, Alex, > I notice the vbox_auto_win8 using the "assert_spec 64bit", does this meant > that this script is for 64-bit Guest OS. No. By invoking the run script you build Genode - not a VM. The VM image is provided by you (vdi/iso) and is just used as is. So it means by invoking the run script the assertion takes care that you build a 64bit Genode "host". >> I understand that the various run scripts are to build Genode with various components including the Guest VM provided in a VDI. >> The thing that I don't understand are the macros that you use in scripts - such as "assert_spec". >> Can you point me to where I can find documentation for the various macros which I understand are based on Expect. But still - whatever you buy/setup - you need a way to get serial output from the machine - otherwise we can't help you really. >> Noted. I'll try to explore using Intel AMT to support the serial logging. >> I've acquired a refurbished Lenovo X201, can you advise how I can try to emulate what Norman is doing - configuration and run scripts. Thanks. On Wed, Sep 23, 2015 at 8:01 PM, Alexander Boettcher < alexander.boettc...@genode-labs.com> wrote: > Hi Vincent, > > On 23.09.2015 04:41, Vincent Digital wrote: > > I understand without serial port hardware, it is near to impossible to > > troubleshoot. > > Yes. > > > Btw, is it necessary to stick to 32-bit versions of the Guest OSs ? > > Yes. We don't support 64bit guests currently. > > > I notice the vbox_auto_win8 using the "assert_spec 64bit", does this > meant > > that this script is for 64-bit Guest OS. > > No. By invoking the run script you build Genode - not a VM. The VM image > is provided by you (vdi/iso) and is just used as is. So it means by > invoking the run script the assertion takes care that you build a 64bit > Genode "host". > > > Anyway, I would to consult you what are the main hardware features that > are > > required to be compatible to the Nova/Genode software ? > > Here at Genode Labs we focus for Genode/Nova on Intel-based hardware > (especially CPU, graphic card, wifi cards) - but not exclusively. In > principal all other vendors do - but you should expect extra efforts to > debug things or to develop/port/enable drivers for your devices. The CPU > must not be too old for the Nova kernel - especially if you want to use > virtualization extensions. Beginning with 1st generation of Intel Core > i3/5/7 CPUs you should be fine. Good experience we have with Lenovo > notebooks which we use regularly/daily to run Genode. > > But still - whatever you buy/setup - you need a way to get serial output > from the machine - otherwise we can't help you really. > > Cheers, > > 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 > -- 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
Re: running Virtualbox on Genode
Hi Vincent, On 23.09.2015 04:41, Vincent Digital wrote: > I understand without serial port hardware, it is near to impossible to > troubleshoot. Yes. > Btw, is it necessary to stick to 32-bit versions of the Guest OSs ? Yes. We don't support 64bit guests currently. > I notice the vbox_auto_win8 using the "assert_spec 64bit", does this meant > that this script is for 64-bit Guest OS. No. By invoking the run script you build Genode - not a VM. The VM image is provided by you (vdi/iso) and is just used as is. So it means by invoking the run script the assertion takes care that you build a 64bit Genode "host". > Anyway, I would to consult you what are the main hardware features that are > required to be compatible to the Nova/Genode software ? Here at Genode Labs we focus for Genode/Nova on Intel-based hardware (especially CPU, graphic card, wifi cards) - but not exclusively. In principal all other vendors do - but you should expect extra efforts to debug things or to develop/port/enable drivers for your devices. The CPU must not be too old for the Nova kernel - especially if you want to use virtualization extensions. Beginning with 1st generation of Intel Core i3/5/7 CPUs you should be fine. Good experience we have with Lenovo notebooks which we use regularly/daily to run Genode. But still - whatever you buy/setup - you need a way to get serial output from the machine - otherwise we can't help you really. Cheers, 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
Re: running Virtualbox on Genode
Hi, Alex,
After a long break, I would like to update you on my recent work.
I've revisited the run script that you created for a USB boot-up.
It worked - previously it was a careless mistake on my part with the dd
command - use a wrong device name.
The USB boot-up could now boot-up partially but mainly on Acer hardware,
but not on Dell or HP hardware - the screen would hang on the Genode bootup.
For the Acer bootup, it was only partial - after the Windows 7 screen came
up, it seemed "hang" for very long. The mouse pointer can still movec
though.
I understand without serial port hardware, it is near to impossible to
troubleshoot. As such, I am thinking of purchasing a refurbished Lenovo
X201 - the same one that Norman is using.
I also tried using VMware Workstation and Virtualbox to boot up the USB
stick. I even swapped the Guest VMs between Ubuntu and Windows 7. All would
hang after Genode boots up.
Btw, is it necessary to stick to 32-bit versions of the Guest OSs ? I
notice the vbox_auto_win8 using the "assert_spec 64bit", does this meant
that this script is for 64-bit Guest OS.
Anyway, I would to consult you what are the main hardware features that are
required to be compatible to the Nova/Genode software ?
I would like to move on to a hard-disk based configuration in the long run.
I hope to be able to run two operating systems, Windows and a Linux on top
of Genode/Nova, both supporting Java applications. Can you recommend any
scripts or configuration steps that I can use to do such a setup. I am
trying using the vbox_auto_win7 and vbox_auto_win8 scripts.
Thanks.
On Thu, Sep 10, 2015 at 8:06 PM, Vincent Digital
wrote:
> Okay, noted. Thanks.
> I'll try again maybe with a new USB stick.
>
> Regards.
>
> On Thu, Sep 10, 2015 at 3:48 PM, Alexander Boettcher <
> alexander.boettc...@genode-labs.com> wrote:
>
>> Some additional note:
>>
>> make sure that you remove/uncomment all RUN_OPT in your etc/build.conf
>> and really replace it by this line:
>>
>> # Set RUN_OPT in your build.conf to: RUN_OPT = --include image/disk
>>
>> Otherwise the resulting image is not in the expected state.
>>
>> Alex.
>>
>> On 10.09.2015 05:38, Vincent Digital wrote:
>> > Hi, Alex,
>> >
>> > I've used your USB_RUN script to create an image file.
>> > I followed your instructions to prepare the USB stick. However, the USB
>> > stick cannot boot up.
>> > Unfortunately, I do not have access to a laptop with serial port so I am
>> > unable to get any logs.
>> > Can I check with you on your instructions (the mini-howto below)
>> instead.
>> > Thanks.
>> >
>> > # Short mini howto for nova_x86_64:
>> > # - assumption - /dev/sdc is your USB stick
>> > # - assumption - you are in the genode source root directory
>> > # - assumption - you have prepared all external ports
>> > # - assumption - you have build the rump tools -> tool/tool_chain_rump
>> > #
>> > # create a nova_x86_64 build directory
>> > # - tool/create_builddir nova_x86_64
>> > #
>> > # Put/symlink your Windows 7 vdi to build/nova_x86_64/win7.vdi
>> > #
>> > # Set RUN_OPT in your build.conf to: RUN_OPT = --include image/disk
>> > #
>> > # Build everything:
>> > # - make -C build/nova_x86_64 run/vbox_usb
>> > #
>> > # Make sure that the USB is not used - all partitions are un-mounted.
>> >>> How should I prepare this USB stick, should it be formatted under a
>> > particular filesystem (ext2, or FAT32)
>> >>> I have tried various ways - delete everything including partitions,
>> etc.
>> > and then create a new partition
>> >>> Can I clarify the steps below are in sequential order
>> >>> 1. dd operation
>> >>> 2. fdisk operation - delete all partitions, then create a new
>> partition
>> > and then write to disk.
>> >>> 3. Resizefs operation
>> >>> 4. Mount partiton (I tried this but could not get a successful mount
>> > until I create a filesystem using mke2fs. Is this step necessary ?)
>> >
>> > # Copy disk image to your USB stick:
>> > # - sudo dd if=build/nova_x86_64/var/run/vbox_usb.img of=/dev/sdc
>> > #
>> > # Make sure that the USB partition of the stick is un-mounted.
>> > #
>> > # Resize USB stick partition to maximum:
>> > # - sudo fdisk /dev/sdc
>> > # -- delete partition ('d')
>> > # -- create partition - ('p')
>> > # -- write table to disk and exit ('w')
>> > #
>> > # - sudo resize2fs -p /dev/sdc1
>> > #
>> > # Mount Genode partition on USB stick and copy your Windows image to
>> the USB
>> > # stick:
>> > #
>> > # - sudo mount /dev/sdc1 /media/genode
>> > # - cp build/nova_x86_64/win7.vdi /media/genode/.
>> > # - mkdir /media/genode/ram
>> > # - cp build/nova_x86_64/bin/overlay_win7.vdi /media/genode/ram/.
>> > # - umount /media/genode
>> > #
>> > # Boot your USB stick. For debugging get the serial output of the test
>> > machine.
>> > #
>> >
>> >
>> >
>> >
>> >
>> >
>> > On Tue, Sep 1, 2015 at 3:03 AM, Alexander Boettcher <
>> > alexander.boettc...@genode-labs.com> wrote:
>> >
>> >> On 28.08.2015 13:44, Alexander Boettcher wrote:
>> The part that I am
Re: running Virtualbox on Genode
Okay, noted. Thanks.
I'll try again maybe with a new USB stick.
Regards.
On Thu, Sep 10, 2015 at 3:48 PM, Alexander Boettcher <
alexander.boettc...@genode-labs.com> wrote:
> Some additional note:
>
> make sure that you remove/uncomment all RUN_OPT in your etc/build.conf
> and really replace it by this line:
>
> # Set RUN_OPT in your build.conf to: RUN_OPT = --include image/disk
>
> Otherwise the resulting image is not in the expected state.
>
> Alex.
>
> On 10.09.2015 05:38, Vincent Digital wrote:
> > Hi, Alex,
> >
> > I've used your USB_RUN script to create an image file.
> > I followed your instructions to prepare the USB stick. However, the USB
> > stick cannot boot up.
> > Unfortunately, I do not have access to a laptop with serial port so I am
> > unable to get any logs.
> > Can I check with you on your instructions (the mini-howto below) instead.
> > Thanks.
> >
> > # Short mini howto for nova_x86_64:
> > # - assumption - /dev/sdc is your USB stick
> > # - assumption - you are in the genode source root directory
> > # - assumption - you have prepared all external ports
> > # - assumption - you have build the rump tools -> tool/tool_chain_rump
> > #
> > # create a nova_x86_64 build directory
> > # - tool/create_builddir nova_x86_64
> > #
> > # Put/symlink your Windows 7 vdi to build/nova_x86_64/win7.vdi
> > #
> > # Set RUN_OPT in your build.conf to: RUN_OPT = --include image/disk
> > #
> > # Build everything:
> > # - make -C build/nova_x86_64 run/vbox_usb
> > #
> > # Make sure that the USB is not used - all partitions are un-mounted.
> >>> How should I prepare this USB stick, should it be formatted under a
> > particular filesystem (ext2, or FAT32)
> >>> I have tried various ways - delete everything including partitions,
> etc.
> > and then create a new partition
> >>> Can I clarify the steps below are in sequential order
> >>> 1. dd operation
> >>> 2. fdisk operation - delete all partitions, then create a new
> partition
> > and then write to disk.
> >>> 3. Resizefs operation
> >>> 4. Mount partiton (I tried this but could not get a successful mount
> > until I create a filesystem using mke2fs. Is this step necessary ?)
> >
> > # Copy disk image to your USB stick:
> > # - sudo dd if=build/nova_x86_64/var/run/vbox_usb.img of=/dev/sdc
> > #
> > # Make sure that the USB partition of the stick is un-mounted.
> > #
> > # Resize USB stick partition to maximum:
> > # - sudo fdisk /dev/sdc
> > # -- delete partition ('d')
> > # -- create partition - ('p')
> > # -- write table to disk and exit ('w')
> > #
> > # - sudo resize2fs -p /dev/sdc1
> > #
> > # Mount Genode partition on USB stick and copy your Windows image to the
> USB
> > # stick:
> > #
> > # - sudo mount /dev/sdc1 /media/genode
> > # - cp build/nova_x86_64/win7.vdi /media/genode/.
> > # - mkdir /media/genode/ram
> > # - cp build/nova_x86_64/bin/overlay_win7.vdi /media/genode/ram/.
> > # - umount /media/genode
> > #
> > # Boot your USB stick. For debugging get the serial output of the test
> > machine.
> > #
> >
> >
> >
> >
> >
> >
> > On Tue, Sep 1, 2015 at 3:03 AM, Alexander Boettcher <
> > alexander.boettc...@genode-labs.com> wrote:
> >
> >> On 28.08.2015 13:44, Alexander Boettcher wrote:
> The part that I am not sure are the "win7.vdi" and "overlay_win7.vdi"
> files. How are they linked to the vbox_auto_win7.iso file ?
> I have copied them onto the thumbdrive but is this correct ?
> >>
> >> You may try the following branch
> >> https://github.com/alex-ab/genode/commits/vbox_usb_run. There exists
> now
> >> a run script called repos/ports/run/vbox_usb.run which helps you in
> >> setting up a Virtualbox on Genode/NOVA running from USB stick and
> >> fetching the Virtualbox image from the vary same USB stick. Please
> >> follow the instruction as described in the run script.
> >>
> >> Still, there a lot of manual steps to go - but it may help a bit.
> >>
> >> Please keep in mind, depending on the read and write performance of your
> >> USB controller and stick the overall experience may be not as good as
> >> when used with a real hard disk.
> >>
> >> Alex.
> >>
> >>
> >>
> --
> >> ___
> >> genode-main mailing list
> >> genode-main@lists.sourceforge.net
> >> https://lists.sourceforge.net/lists/listinfo/genode-main
> >>
> >
> >
> >
> >
> --
> > 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
> >
>
>
>
> ---
Re: running Virtualbox on Genode
Some additional note:
make sure that you remove/uncomment all RUN_OPT in your etc/build.conf
and really replace it by this line:
# Set RUN_OPT in your build.conf to: RUN_OPT = --include image/disk
Otherwise the resulting image is not in the expected state.
Alex.
On 10.09.2015 05:38, Vincent Digital wrote:
> Hi, Alex,
>
> I've used your USB_RUN script to create an image file.
> I followed your instructions to prepare the USB stick. However, the USB
> stick cannot boot up.
> Unfortunately, I do not have access to a laptop with serial port so I am
> unable to get any logs.
> Can I check with you on your instructions (the mini-howto below) instead.
> Thanks.
>
> # Short mini howto for nova_x86_64:
> # - assumption - /dev/sdc is your USB stick
> # - assumption - you are in the genode source root directory
> # - assumption - you have prepared all external ports
> # - assumption - you have build the rump tools -> tool/tool_chain_rump
> #
> # create a nova_x86_64 build directory
> # - tool/create_builddir nova_x86_64
> #
> # Put/symlink your Windows 7 vdi to build/nova_x86_64/win7.vdi
> #
> # Set RUN_OPT in your build.conf to: RUN_OPT = --include image/disk
> #
> # Build everything:
> # - make -C build/nova_x86_64 run/vbox_usb
> #
> # Make sure that the USB is not used - all partitions are un-mounted.
>>> How should I prepare this USB stick, should it be formatted under a
> particular filesystem (ext2, or FAT32)
>>> I have tried various ways - delete everything including partitions, etc.
> and then create a new partition
>>> Can I clarify the steps below are in sequential order
>>> 1. dd operation
>>> 2. fdisk operation - delete all partitions, then create a new partition
> and then write to disk.
>>> 3. Resizefs operation
>>> 4. Mount partiton (I tried this but could not get a successful mount
> until I create a filesystem using mke2fs. Is this step necessary ?)
>
> # Copy disk image to your USB stick:
> # - sudo dd if=build/nova_x86_64/var/run/vbox_usb.img of=/dev/sdc
> #
> # Make sure that the USB partition of the stick is un-mounted.
> #
> # Resize USB stick partition to maximum:
> # - sudo fdisk /dev/sdc
> # -- delete partition ('d')
> # -- create partition - ('p')
> # -- write table to disk and exit ('w')
> #
> # - sudo resize2fs -p /dev/sdc1
> #
> # Mount Genode partition on USB stick and copy your Windows image to the USB
> # stick:
> #
> # - sudo mount /dev/sdc1 /media/genode
> # - cp build/nova_x86_64/win7.vdi /media/genode/.
> # - mkdir /media/genode/ram
> # - cp build/nova_x86_64/bin/overlay_win7.vdi /media/genode/ram/.
> # - umount /media/genode
> #
> # Boot your USB stick. For debugging get the serial output of the test
> machine.
> #
>
>
>
>
>
>
> On Tue, Sep 1, 2015 at 3:03 AM, Alexander Boettcher <
> alexander.boettc...@genode-labs.com> wrote:
>
>> On 28.08.2015 13:44, Alexander Boettcher wrote:
The part that I am not sure are the "win7.vdi" and "overlay_win7.vdi"
files. How are they linked to the vbox_auto_win7.iso file ?
I have copied them onto the thumbdrive but is this correct ?
>>
>> You may try the following branch
>> https://github.com/alex-ab/genode/commits/vbox_usb_run. There exists now
>> a run script called repos/ports/run/vbox_usb.run which helps you in
>> setting up a Virtualbox on Genode/NOVA running from USB stick and
>> fetching the Virtualbox image from the vary same USB stick. Please
>> follow the instruction as described in the run script.
>>
>> Still, there a lot of manual steps to go - but it may help a bit.
>>
>> Please keep in mind, depending on the read and write performance of your
>> USB controller and stick the overall experience may be not as good as
>> when used with a real hard disk.
>>
>> Alex.
>>
>>
>> --
>> ___
>> genode-main mailing list
>> genode-main@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/genode-main
>>
>
>
>
> --
> 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
>
--
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-
Re: running Virtualbox on Genode
Hello Vincent, On 10.09.2015 05:38, Vincent Digital wrote: > Hi, Alex, > > I've used your USB_RUN script to create an image file. > I followed your instructions to prepare the USB stick. However, the USB > stick cannot boot up. > Unfortunately, I do not have access to a laptop with serial port so I am > unable to get any logs. > Can I check with you on your instructions (the mini-howto below) instead. > Thanks. > # > # Make sure that the USB is not used - all partitions are un-mounted. >>> How should I prepare this USB stick, should it be formatted under a > particular filesystem (ext2, or FAT32) No preparation. The image you copy with dd already contains a valid mbr + ext2 partition. So after the dd command, you should be able already to mount the ext2 partition. If this does not work - something is already odd - so make sure that mounting it already succeeds ! (Let's call it step 0). >>> Can I clarify the steps below are in sequential order >>> 1. dd operation Yes >>> 2. fdisk operation - delete all partitions, then create a new partition > and then write to disk. There should be exactly one partition to delete. >>> 3. Resizefs operation Yes >>> 4. Mount partiton (I tried this but could not get a successful mount > until I create a filesystem using mke2fs. Is this step necessary ?) The first 3 steps are ok. If the 4. step does not succeed something failed during re-partition and ext2 resize of the ext2 partition. Effectively you should see on the ext2 partition the very same content as after Step 0 (dd). The main goal of step 2-3 is to expand the ext2 partition over the whole USB stick - otherwise there is not enough place for the VM image. Cheers, 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
Re: running Virtualbox on Genode
Hi, Alex,
I've used your USB_RUN script to create an image file.
I followed your instructions to prepare the USB stick. However, the USB
stick cannot boot up.
Unfortunately, I do not have access to a laptop with serial port so I am
unable to get any logs.
Can I check with you on your instructions (the mini-howto below) instead.
Thanks.
# Short mini howto for nova_x86_64:
# - assumption - /dev/sdc is your USB stick
# - assumption - you are in the genode source root directory
# - assumption - you have prepared all external ports
# - assumption - you have build the rump tools -> tool/tool_chain_rump
#
# create a nova_x86_64 build directory
# - tool/create_builddir nova_x86_64
#
# Put/symlink your Windows 7 vdi to build/nova_x86_64/win7.vdi
#
# Set RUN_OPT in your build.conf to: RUN_OPT = --include image/disk
#
# Build everything:
# - make -C build/nova_x86_64 run/vbox_usb
#
# Make sure that the USB is not used - all partitions are un-mounted.
>> How should I prepare this USB stick, should it be formatted under a
particular filesystem (ext2, or FAT32)
>> I have tried various ways - delete everything including partitions, etc.
and then create a new partition
>> Can I clarify the steps below are in sequential order
>> 1. dd operation
>> 2. fdisk operation - delete all partitions, then create a new partition
and then write to disk.
>> 3. Resizefs operation
>> 4. Mount partiton (I tried this but could not get a successful mount
until I create a filesystem using mke2fs. Is this step necessary ?)
# Copy disk image to your USB stick:
# - sudo dd if=build/nova_x86_64/var/run/vbox_usb.img of=/dev/sdc
#
# Make sure that the USB partition of the stick is un-mounted.
#
# Resize USB stick partition to maximum:
# - sudo fdisk /dev/sdc
# -- delete partition ('d')
# -- create partition - ('p')
# -- write table to disk and exit ('w')
#
# - sudo resize2fs -p /dev/sdc1
#
# Mount Genode partition on USB stick and copy your Windows image to the USB
# stick:
#
# - sudo mount /dev/sdc1 /media/genode
# - cp build/nova_x86_64/win7.vdi /media/genode/.
# - mkdir /media/genode/ram
# - cp build/nova_x86_64/bin/overlay_win7.vdi /media/genode/ram/.
# - umount /media/genode
#
# Boot your USB stick. For debugging get the serial output of the test
machine.
#
On Tue, Sep 1, 2015 at 3:03 AM, Alexander Boettcher <
alexander.boettc...@genode-labs.com> wrote:
> On 28.08.2015 13:44, Alexander Boettcher wrote:
> >> The part that I am not sure are the "win7.vdi" and "overlay_win7.vdi"
> >> files. How are they linked to the vbox_auto_win7.iso file ?
> >> I have copied them onto the thumbdrive but is this correct ?
>
> You may try the following branch
> https://github.com/alex-ab/genode/commits/vbox_usb_run. There exists now
> a run script called repos/ports/run/vbox_usb.run which helps you in
> setting up a Virtualbox on Genode/NOVA running from USB stick and
> fetching the Virtualbox image from the vary same USB stick. Please
> follow the instruction as described in the run script.
>
> Still, there a lot of manual steps to go - but it may help a bit.
>
> Please keep in mind, depending on the read and write performance of your
> USB controller and stick the overall experience may be not as good as
> when used with a real hard disk.
>
> Alex.
>
>
> --
> ___
> genode-main mailing list
> genode-main@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/genode-main
>
--
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
Re: running Virtualbox on Genode
On 28.08.2015 13:44, Alexander Boettcher wrote: >> The part that I am not sure are the "win7.vdi" and "overlay_win7.vdi" >> files. How are they linked to the vbox_auto_win7.iso file ? >> I have copied them onto the thumbdrive but is this correct ? You may try the following branch https://github.com/alex-ab/genode/commits/vbox_usb_run. There exists now a run script called repos/ports/run/vbox_usb.run which helps you in setting up a Virtualbox on Genode/NOVA running from USB stick and fetching the Virtualbox image from the vary same USB stick. Please follow the instruction as described in the run script. Still, there a lot of manual steps to go - but it may help a bit. Please keep in mind, depending on the read and write performance of your USB controller and stick the overall experience may be not as good as when used with a real hard disk. Alex. -- ___ genode-main mailing list genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
running Virtualbox on Genode
Hi, On 28.08.2015 11:48, Vincent Digital wrote: > I could now proceed to my next stage - basically to build a Genode system > with NOVA micro-kernel, running Virtualbox with a Windows 7 VM. > I have managed to make the "vbox_auto_win7.run" script - everything is made > successfully and the output is a "vbox_auto_win7.iso" file. > However, when I tried to use the "vbox_auto_win7.iso" file and put it onto > a USB thumdrive to run. The result is that after boot-up, it just hang. You should get the serial output of that machine in order to efficiently debug and set up things. > > The part that I am not sure are the "win7.vdi" and "overlay_win7.vdi" > files. How are they linked to the vbox_auto_win7.iso file ? > I have copied them onto the thumbdrive but is this correct ? This particular run-script makes some assumption about the hardware environment and is solely executed automatically by our test infrastructure. The run script assumes that the test machine has a disk at a AHCI controller and there the fourth partition contains a ext2 filesystem with two files - namely the win7.vdi and overlay_win7.vdi. Please read the beginning of vbox_auto_win7_share.run, which describes roughly the expected state of the test machine, if you want to use the vbox_auto* scripts. (The other way is to write your own run script matching your desired hardware setup.) > I have tried to understand the email exchange on > http://sourceforge.net/p/genode/mailman/message/33496592/ discussion > between Christian and Adrian. > Does anyone have a blueprint on how I can create a "win7.vdi" using an > existing Windows 7 DVD onto a "ext2" partition. For creating a vdi just use a Virtualbox installation of your favourite OS. Install and setup your VM using the normal Virtualbox tools. The resulting vdi image you than copy at the right place in the ext2 partition of your test machine. The overlay vdi can be created as described in vbox_auto_win7_share.run. If all this is in place correctly, you may copy the resulting vbox_auto_win7_share.run to your usb stick and boot it. The Genode scenario on the USB stick than will read the vdi image from your AHCI hard disk. In this setup changes to the VM are written to the overlay vdi image - so that your original win7.vdi doesn't get changed/messed up accidentally. Hope it helps, Alexander Boettcher. -- ___ genode-main mailing list genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
Re: running VirtualBox on Genode
Hello, On 29.07.2015 08:44, Daren Sin wrote: > I seem to have found the problem. Now, I would like to run some other Can you give some short note what was the issue and how you fixed it? We can use this knowledge to improve things on our side (error messages, checks, correlate it to other issues we already identified but not rated high priority enough to be fixed soon ...). Thanks. > (larger) OS on Virtualbox, instead of the Tiny Core Linux, which was > previously suggested that I run. However, how should I go about doing this, > because if I simply swap the test.iso file to a bigger file, I would get an > error The run script is not suited well for big(ger) images, since everything first gets loaded by the bootloader into RAM and stays there. So, effectively you have less memory actually during runtime (if you ever manage to load everything). > >>> "Want to load module to 0xbe9000 len 0x3e40 but only have 0x27ffe000 > RAM" That is a message of Grub complaining about having insufficient RAM space to load everything. For bigger images, we put it typically in one partition on the harddisk using ext2. We use than our ahci driver + part_blk + rump_fs (for ext2) to load the images (.vdi) directly from the disk. This is done by our vbox test run scripts executed every night automatically to test win7/win8 - look for repos/ports/run/vbox_auto_*.run. This is all bit advanced (but doable) and needs to be setup for your machine accordingly. The vbox_auto_*.run can serve you as blue-print. The other option is to read the images from a usb stick with usb driver + part_blk + rump_fs, but this needs some manually tweaking/work by you - [0] could be maybe of use here. [0] http://genode.org/documentation/release-notes/14.08#Booting_from_a_GRUB2_disk_image_with_an_ext2_partition Cheers, Alex. > > I inspected the virtualbox.run file, and experimented with changing some of > the quantum values, but to no avail. What should I do here? > > Daren > > On Wed, Jul 22, 2015 at 8:46 PM, Alexander Boettcher < > alexander.boettc...@genode-labs.com> wrote: > >> Hello, >> >> On 20.07.2015 10:43, Daren Sin wrote: >>> I waited for there seemed to be no further progress. I tried other >>> solutions suggested by searches online, such as using UNetBootin on >> Ubuntu, >>> but was directed to a grub interface, saying that the kernel image was >>> corrupt. I also tried burning it on a DVD instead. >> >> the output looks actually good in that regard that the kernel came up - >> so you did all right with copying the image to the stick. Still, >> something is wrong and we need the serial output of the machine to see >> what is ongoing, as Nobody III suggested already. If you adventures >> enough, you may also apply the last commit of the following experimental >> branch [0] to your branch and rebuild - with that you should get some >> limited output on the VGA console screen. >> >> Cheers, >> >> Alex. >> >> [0] https://github.com/alex-ab/genode/commits/experimental_vga_console >> >>> >>> Am I doing something by mistake, like using the wrong commands? >>> >>> Daren >>> >>> On Mon, Jul 13, 2015 at 5:13 PM, Alexander Boettcher < >>> alexander.boettc...@genode-labs.com> wrote: >>> Hello, On 13.07.2015 11:04, Daren Sin wrote: > In order to run from my USB, where should I obtain the .iso file from? The iso image of the VM (test.iso for virtualbox.run) is part of the generated Genode iso image in your build directory (/var/run/virtualbox.iso). Just copy the Genode iso to your usb stick by using dd. Cheers, Alex. > > Cheers > Daren > > On Fri, Jul 10, 2015 at 5:15 PM, Alexander Boettcher < > alexander.boettc...@genode-labs.com> wrote: > >> On 10.07.2015 10:36, Daren Sin wrote: >>> Hi Alex and Christian, >>> >>> Really really thankful for the advice; apologies for the spoonfeeding as >>> well. Making changes to virtualbox.run, I've managed to boot up TinyLinux >>> on QEMU, but while QEMU says "booting kernel", the terminal reflects: >>> >>> ... >>> [init -> virtualbox] attempted to write to non-existing port 0xa79+1 >> . >> (02) >>> [init -> virtualbox] attempted to write to non-existing port 0xa79+1 >> . >> (05) >>> [init -> virtualbox] attempted to write to non-existing port 0xa79+1 >> . >> (02) >>> [init -> virtualbox] attempted to write to non-existing port 0xa79+1 >> . >> (00) >>> [init -> virtualbox] VMM: invalid gueststate >>> [init -> virtualbox] VMM: invalid gueststate >>> [init -> virtualbox] VMM: invalid gueststate >>> [init -> virtualbox] VMM: invalid gueststate >> >> I have another workaround to get a bit further, but finally Qemu for >> me >> (version 2.1.2 and 2.3.0) dies with an internal failure - so it will >> of >> no help to you. Please do as Christian suggested. >> >> Alex. >> >>> ... >>> >>
Re: running VirtualBox on Genode
Hi thanks! I seem to have found the problem. Now, I would like to run some other (larger) OS on Virtualbox, instead of the Tiny Core Linux, which was previously suggested that I run. However, how should I go about doing this, because if I simply swap the test.iso file to a bigger file, I would get an error >> "Want to load module to 0xbe9000 len 0x3e40 but only have 0x27ffe000 RAM" I inspected the virtualbox.run file, and experimented with changing some of the quantum values, but to no avail. What should I do here? Daren On Wed, Jul 22, 2015 at 8:46 PM, Alexander Boettcher < alexander.boettc...@genode-labs.com> wrote: > Hello, > > On 20.07.2015 10:43, Daren Sin wrote: > > I waited for there seemed to be no further progress. I tried other > > solutions suggested by searches online, such as using UNetBootin on > Ubuntu, > > but was directed to a grub interface, saying that the kernel image was > > corrupt. I also tried burning it on a DVD instead. > > the output looks actually good in that regard that the kernel came up - > so you did all right with copying the image to the stick. Still, > something is wrong and we need the serial output of the machine to see > what is ongoing, as Nobody III suggested already. If you adventures > enough, you may also apply the last commit of the following experimental > branch [0] to your branch and rebuild - with that you should get some > limited output on the VGA console screen. > > Cheers, > > Alex. > > [0] https://github.com/alex-ab/genode/commits/experimental_vga_console > > > > > Am I doing something by mistake, like using the wrong commands? > > > > Daren > > > > On Mon, Jul 13, 2015 at 5:13 PM, Alexander Boettcher < > > alexander.boettc...@genode-labs.com> wrote: > > > >> Hello, > >> > >> On 13.07.2015 11:04, Daren Sin wrote: > >>> In order to run from my USB, where should I obtain the .iso file from? > >> > >> The iso image of the VM (test.iso for virtualbox.run) is part of the > >> generated Genode iso image in your build directory > >> (/var/run/virtualbox.iso). Just copy the Genode iso to your > >> usb stick by using dd. > >> > >> Cheers, > >> > >> Alex. > >> > >>> > >>> Cheers > >>> Daren > >>> > >>> On Fri, Jul 10, 2015 at 5:15 PM, Alexander Boettcher < > >>> alexander.boettc...@genode-labs.com> wrote: > >>> > On 10.07.2015 10:36, Daren Sin wrote: > > Hi Alex and Christian, > > > > Really really thankful for the advice; apologies for the spoonfeeding > >> as > > well. Making changes to virtualbox.run, I've managed to boot up > >> TinyLinux > > on QEMU, but while QEMU says "booting kernel", the terminal reflects: > > > > ... > > [init -> virtualbox] attempted to write to non-existing port 0xa79+1 > . > (02) > > [init -> virtualbox] attempted to write to non-existing port 0xa79+1 > . > (05) > > [init -> virtualbox] attempted to write to non-existing port 0xa79+1 > . > (02) > > [init -> virtualbox] attempted to write to non-existing port 0xa79+1 > . > (00) > > [init -> virtualbox] VMM: invalid gueststate > > [init -> virtualbox] VMM: invalid gueststate > > [init -> virtualbox] VMM: invalid gueststate > > [init -> virtualbox] VMM: invalid gueststate > > I have another workaround to get a bit further, but finally Qemu for > me > (version 2.1.2 and 2.3.0) dies with an internal failure - so it will > of > no help to you. Please do as Christian suggested. > > Alex. > > > ... > > > > On Fri, Jul 10, 2015 at 3:23 PM, Alexander Boettcher < > > alexander.boettc...@genode-labs.com> wrote: > > > >> Hello, > >> > >> On 10.07.2015 08:13, Daren Sin wrote: > >>> [init -> acpi] Could not open ROM session for module "config" > >>> [init -> acpi] void* abort(): abort called > >> > >> That it the actual reason, the acpi driver did not find a > >> configuration > >> xml node. The issue got fixed already on current Genode master > branch, > >> but for now you may apply the following fix [0]. Nevertheless, > please > >> consider the suggestions of Christian Helmuth. > >> > >> Cheers, > >> > >> Alex. > >> > >> [0] > >> > >> > > >> > https://github.com/alex-ab/genode/commit/738ad842f546afef16f3eb642ca3ff5c7c36e0cd > >>> > >>> What might be the problem? > >>> > >>> Thanks! > >>> > >>> On Wed, Jul 8, 2015 at 1:23 AM, Martin Stein < > >> martin.st...@genode-labs.com> > >>> wrote: > >>> > Hi Daren, > > On 08.07.2015 04:51, Daren Sin wrote: > > Hi, > > > > I've found this > > page > > >> > > >> > http://genode.org/documentation/release-notes/14.02#VirtualBox_on_top_of_the_NOVA_microhypervisor > > and managed to run the /make prepare/ command, but got stuck at > the > >> next > > one. > > The 'make prepare' mechanism is o
Re: running VirtualBox on Genode
Hello, On 20.07.2015 10:43, Daren Sin wrote: > I waited for there seemed to be no further progress. I tried other > solutions suggested by searches online, such as using UNetBootin on Ubuntu, > but was directed to a grub interface, saying that the kernel image was > corrupt. I also tried burning it on a DVD instead. the output looks actually good in that regard that the kernel came up - so you did all right with copying the image to the stick. Still, something is wrong and we need the serial output of the machine to see what is ongoing, as Nobody III suggested already. If you adventures enough, you may also apply the last commit of the following experimental branch [0] to your branch and rebuild - with that you should get some limited output on the VGA console screen. Cheers, Alex. [0] https://github.com/alex-ab/genode/commits/experimental_vga_console > > Am I doing something by mistake, like using the wrong commands? > > Daren > > On Mon, Jul 13, 2015 at 5:13 PM, Alexander Boettcher < > alexander.boettc...@genode-labs.com> wrote: > >> Hello, >> >> On 13.07.2015 11:04, Daren Sin wrote: >>> In order to run from my USB, where should I obtain the .iso file from? >> >> The iso image of the VM (test.iso for virtualbox.run) is part of the >> generated Genode iso image in your build directory >> (/var/run/virtualbox.iso). Just copy the Genode iso to your >> usb stick by using dd. >> >> Cheers, >> >> Alex. >> >>> >>> Cheers >>> Daren >>> >>> On Fri, Jul 10, 2015 at 5:15 PM, Alexander Boettcher < >>> alexander.boettc...@genode-labs.com> wrote: >>> On 10.07.2015 10:36, Daren Sin wrote: > Hi Alex and Christian, > > Really really thankful for the advice; apologies for the spoonfeeding >> as > well. Making changes to virtualbox.run, I've managed to boot up >> TinyLinux > on QEMU, but while QEMU says "booting kernel", the terminal reflects: > > ... > [init -> virtualbox] attempted to write to non-existing port 0xa79+1 . (02) > [init -> virtualbox] attempted to write to non-existing port 0xa79+1 . (05) > [init -> virtualbox] attempted to write to non-existing port 0xa79+1 . (02) > [init -> virtualbox] attempted to write to non-existing port 0xa79+1 . (00) > [init -> virtualbox] VMM: invalid gueststate > [init -> virtualbox] VMM: invalid gueststate > [init -> virtualbox] VMM: invalid gueststate > [init -> virtualbox] VMM: invalid gueststate I have another workaround to get a bit further, but finally Qemu for me (version 2.1.2 and 2.3.0) dies with an internal failure - so it will of no help to you. Please do as Christian suggested. Alex. > ... > > On Fri, Jul 10, 2015 at 3:23 PM, Alexander Boettcher < > alexander.boettc...@genode-labs.com> wrote: > >> Hello, >> >> On 10.07.2015 08:13, Daren Sin wrote: >>> [init -> acpi] Could not open ROM session for module "config" >>> [init -> acpi] void* abort(): abort called >> >> That it the actual reason, the acpi driver did not find a >> configuration >> xml node. The issue got fixed already on current Genode master branch, >> but for now you may apply the following fix [0]. Nevertheless, please >> consider the suggestions of Christian Helmuth. >> >> Cheers, >> >> Alex. >> >> [0] >> >> >> https://github.com/alex-ab/genode/commit/738ad842f546afef16f3eb642ca3ff5c7c36e0cd >>> >>> What might be the problem? >>> >>> Thanks! >>> >>> On Wed, Jul 8, 2015 at 1:23 AM, Martin Stein < >> martin.st...@genode-labs.com> >>> wrote: >>> Hi Daren, On 08.07.2015 04:51, Daren Sin wrote: > Hi, > > I've found this > page >> >> http://genode.org/documentation/release-notes/14.02#VirtualBox_on_top_of_the_NOVA_microhypervisor > and managed to run the /make prepare/ command, but got stuck at the >> next > one. The 'make prepare' mechanism is outdated. It has been replaced by >> the prepare_port command in tool/ports. Call the tool without arguments for a short manpage. > I tried doing that, but got a /Error: libc is not > prepared or outdated/ error. The error indicates that the third-party package "libc", which is needed for your scenario, is missing or too old. You can update it by doing './prepare_port libc' in tool/ports. There may be further >> third-party packages (ports) that need such treatment. Cheers, Martin >> >> -- Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support >> that you need to offload your IT needs
Re: running VirtualBox on Genode
Are you looking at the serial output, or just the screen? Because the screen doesn't give all the output. On Jul 21, 2015 11:33 PM, "Daren Sin" wrote: > Hi Alexander, > > Thanks for your suggestion! > > I tried using dd to boot Genode on USB, by using virtualbox.iso in the > build-nova folder as per your suggestion: > > sudo dd if=virtualbox.iso of=/dev/sdb > > There was some progress, but it stopped at a startup screen: > > NOVA Microhypervisor v7-9916e62 (x86_64): Jul 10 2015 [gcc 4.9.2] > > [0] CORE :0 :0 :0 6:1a :5 :1 [11] Intel(R) Core(TM) i7 CPU960 @3.20 GHz > [2] CORE :0 :2 :0 6:1a :5 :1 [11] Intel(R) Core(TM) i7 CPU960 @3.20 GHz > [5] CORE :0 :1 :1 6:1a :5 :1 [11] Intel(R) Core(TM) i7 CPU960 @3.20 GHz > [4] CORE :0 :0 :1 6:1a :5 :1 [11] Intel(R) Core(TM) i7 CPU960 @3.20 GHz > [1] CORE :0 :1 :0 6:1a :5 :1 [11] Intel(R) Core(TM) i7 CPU960 @3.20 GHz > [7] CORE :0 :3 :1 6:1a :5 :1 [11] Intel(R) Core(TM) i7 CPU960 @3.20 GHz > [3] CORE :0 :3 :0 6:1a :5 :1 [11] Intel(R) Core(TM) i7 CPU960 @3.20 GHz > [6] CORE :0 :2 :1 6:1a :5 :1 [11] Intel(R) Core(TM) i7 CPU960 @3.20 GHz > > I waited for there seemed to be no further progress. I tried other > solutions suggested by searches online, such as using UNetBootin on Ubuntu, > but was directed to a grub interface, saying that the kernel image was > corrupt. I also tried burning it on a DVD instead. > > Am I doing something by mistake, like using the wrong commands? > > Daren > > On Mon, Jul 13, 2015 at 5:13 PM, Alexander Boettcher < > alexander.boettc...@genode-labs.com> wrote: > >> Hello, >> >> On 13.07.2015 11:04, Daren Sin wrote: >> > In order to run from my USB, where should I obtain the .iso file from? >> >> The iso image of the VM (test.iso for virtualbox.run) is part of the >> generated Genode iso image in your build directory >> (/var/run/virtualbox.iso). Just copy the Genode iso to your >> usb stick by using dd. >> >> Cheers, >> >> Alex. >> >> > >> > Cheers >> > Daren >> > >> > On Fri, Jul 10, 2015 at 5:15 PM, Alexander Boettcher < >> > alexander.boettc...@genode-labs.com> wrote: >> > >> >> On 10.07.2015 10:36, Daren Sin wrote: >> >>> Hi Alex and Christian, >> >>> >> >>> Really really thankful for the advice; apologies for the spoonfeeding >> as >> >>> well. Making changes to virtualbox.run, I've managed to boot up >> TinyLinux >> >>> on QEMU, but while QEMU says "booting kernel", the terminal reflects: >> >>> >> >>> ... >> >>> [init -> virtualbox] attempted to write to non-existing port 0xa79+1 . >> >> (02) >> >>> [init -> virtualbox] attempted to write to non-existing port 0xa79+1 . >> >> (05) >> >>> [init -> virtualbox] attempted to write to non-existing port 0xa79+1 . >> >> (02) >> >>> [init -> virtualbox] attempted to write to non-existing port 0xa79+1 . >> >> (00) >> >>> [init -> virtualbox] VMM: invalid gueststate >> >>> [init -> virtualbox] VMM: invalid gueststate >> >>> [init -> virtualbox] VMM: invalid gueststate >> >>> [init -> virtualbox] VMM: invalid gueststate >> >> >> >> I have another workaround to get a bit further, but finally Qemu for me >> >> (version 2.1.2 and 2.3.0) dies with an internal failure - so it will of >> >> no help to you. Please do as Christian suggested. >> >> >> >> Alex. >> >> >> >>> ... >> >>> >> >>> On Fri, Jul 10, 2015 at 3:23 PM, Alexander Boettcher < >> >>> alexander.boettc...@genode-labs.com> wrote: >> >>> >> Hello, >> >> On 10.07.2015 08:13, Daren Sin wrote: >> > [init -> acpi] Could not open ROM session for module "config" >> > [init -> acpi] void* abort(): abort called >> >> That it the actual reason, the acpi driver did not find a >> configuration >> xml node. The issue got fixed already on current Genode master >> branch, >> but for now you may apply the following fix [0]. Nevertheless, please >> consider the suggestions of Christian Helmuth. >> >> Cheers, >> >> Alex. >> >> [0] >> >> >> >> >> https://github.com/alex-ab/genode/commit/738ad842f546afef16f3eb642ca3ff5c7c36e0cd >> > >> > What might be the problem? >> > >> > Thanks! >> > >> > On Wed, Jul 8, 2015 at 1:23 AM, Martin Stein < >> martin.st...@genode-labs.com> >> > wrote: >> > >> >> Hi Daren, >> >> >> >> On 08.07.2015 04:51, Daren Sin wrote: >> >>> Hi, >> >>> >> >>> I've found this >> >>> page >> >> >> >> >> >> http://genode.org/documentation/release-notes/14.02#VirtualBox_on_top_of_the_NOVA_microhypervisor >> >>> and managed to run the /make prepare/ command, but got stuck at >> the >> next >> >>> one. >> >> >> >> The 'make prepare' mechanism is outdated. It has been replaced by >> the >> >> prepare_port command in tool/ports. Call the tool without arguments >> >> for >> >> a short manpage. >> >> >> >>> I tried doing that, but got a /Error: libc is not >> >>> prepared or outdated/ error. >> >> >> >> The error in
Re: running VirtualBox on Genode
Hi Alexander, Thanks for your suggestion! I tried using dd to boot Genode on USB, by using virtualbox.iso in the build-nova folder as per your suggestion: sudo dd if=virtualbox.iso of=/dev/sdb There was some progress, but it stopped at a startup screen: NOVA Microhypervisor v7-9916e62 (x86_64): Jul 10 2015 [gcc 4.9.2] [0] CORE :0 :0 :0 6:1a :5 :1 [11] Intel(R) Core(TM) i7 CPU960 @3.20 GHz [2] CORE :0 :2 :0 6:1a :5 :1 [11] Intel(R) Core(TM) i7 CPU960 @3.20 GHz [5] CORE :0 :1 :1 6:1a :5 :1 [11] Intel(R) Core(TM) i7 CPU960 @3.20 GHz [4] CORE :0 :0 :1 6:1a :5 :1 [11] Intel(R) Core(TM) i7 CPU960 @3.20 GHz [1] CORE :0 :1 :0 6:1a :5 :1 [11] Intel(R) Core(TM) i7 CPU960 @3.20 GHz [7] CORE :0 :3 :1 6:1a :5 :1 [11] Intel(R) Core(TM) i7 CPU960 @3.20 GHz [3] CORE :0 :3 :0 6:1a :5 :1 [11] Intel(R) Core(TM) i7 CPU960 @3.20 GHz [6] CORE :0 :2 :1 6:1a :5 :1 [11] Intel(R) Core(TM) i7 CPU960 @3.20 GHz I waited for there seemed to be no further progress. I tried other solutions suggested by searches online, such as using UNetBootin on Ubuntu, but was directed to a grub interface, saying that the kernel image was corrupt. I also tried burning it on a DVD instead. Am I doing something by mistake, like using the wrong commands? Daren On Mon, Jul 13, 2015 at 5:13 PM, Alexander Boettcher < alexander.boettc...@genode-labs.com> wrote: > Hello, > > On 13.07.2015 11:04, Daren Sin wrote: > > In order to run from my USB, where should I obtain the .iso file from? > > The iso image of the VM (test.iso for virtualbox.run) is part of the > generated Genode iso image in your build directory > (/var/run/virtualbox.iso). Just copy the Genode iso to your > usb stick by using dd. > > Cheers, > > Alex. > > > > > Cheers > > Daren > > > > On Fri, Jul 10, 2015 at 5:15 PM, Alexander Boettcher < > > alexander.boettc...@genode-labs.com> wrote: > > > >> On 10.07.2015 10:36, Daren Sin wrote: > >>> Hi Alex and Christian, > >>> > >>> Really really thankful for the advice; apologies for the spoonfeeding > as > >>> well. Making changes to virtualbox.run, I've managed to boot up > TinyLinux > >>> on QEMU, but while QEMU says "booting kernel", the terminal reflects: > >>> > >>> ... > >>> [init -> virtualbox] attempted to write to non-existing port 0xa79+1 . > >> (02) > >>> [init -> virtualbox] attempted to write to non-existing port 0xa79+1 . > >> (05) > >>> [init -> virtualbox] attempted to write to non-existing port 0xa79+1 . > >> (02) > >>> [init -> virtualbox] attempted to write to non-existing port 0xa79+1 . > >> (00) > >>> [init -> virtualbox] VMM: invalid gueststate > >>> [init -> virtualbox] VMM: invalid gueststate > >>> [init -> virtualbox] VMM: invalid gueststate > >>> [init -> virtualbox] VMM: invalid gueststate > >> > >> I have another workaround to get a bit further, but finally Qemu for me > >> (version 2.1.2 and 2.3.0) dies with an internal failure - so it will of > >> no help to you. Please do as Christian suggested. > >> > >> Alex. > >> > >>> ... > >>> > >>> On Fri, Jul 10, 2015 at 3:23 PM, Alexander Boettcher < > >>> alexander.boettc...@genode-labs.com> wrote: > >>> > Hello, > > On 10.07.2015 08:13, Daren Sin wrote: > > [init -> acpi] Could not open ROM session for module "config" > > [init -> acpi] void* abort(): abort called > > That it the actual reason, the acpi driver did not find a > configuration > xml node. The issue got fixed already on current Genode master branch, > but for now you may apply the following fix [0]. Nevertheless, please > consider the suggestions of Christian Helmuth. > > Cheers, > > Alex. > > [0] > > > >> > https://github.com/alex-ab/genode/commit/738ad842f546afef16f3eb642ca3ff5c7c36e0cd > > > > What might be the problem? > > > > Thanks! > > > > On Wed, Jul 8, 2015 at 1:23 AM, Martin Stein < > martin.st...@genode-labs.com> > > wrote: > > > >> Hi Daren, > >> > >> On 08.07.2015 04:51, Daren Sin wrote: > >>> Hi, > >>> > >>> I've found this > >>> page > >> > > >> > http://genode.org/documentation/release-notes/14.02#VirtualBox_on_top_of_the_NOVA_microhypervisor > >>> and managed to run the /make prepare/ command, but got stuck at the > next > >>> one. > >> > >> The 'make prepare' mechanism is outdated. It has been replaced by > the > >> prepare_port command in tool/ports. Call the tool without arguments > >> for > >> a short manpage. > >> > >>> I tried doing that, but got a /Error: libc is not > >>> prepared or outdated/ error. > >> > >> The error indicates that the third-party package "libc", which is > >> needed > >> for your scenario, is missing or too old. You can update it by doing > >> './prepare_port libc' in tool/ports. There may be further > third-party > >> packages (ports) that need such treatment. > >> > >> Cheers, > >> Martin > >
Re: running VirtualBox on Genode
Hello, On 13.07.2015 11:04, Daren Sin wrote: > In order to run from my USB, where should I obtain the .iso file from? The iso image of the VM (test.iso for virtualbox.run) is part of the generated Genode iso image in your build directory (/var/run/virtualbox.iso). Just copy the Genode iso to your usb stick by using dd. Cheers, Alex. > > Cheers > Daren > > On Fri, Jul 10, 2015 at 5:15 PM, Alexander Boettcher < > alexander.boettc...@genode-labs.com> wrote: > >> On 10.07.2015 10:36, Daren Sin wrote: >>> Hi Alex and Christian, >>> >>> Really really thankful for the advice; apologies for the spoonfeeding as >>> well. Making changes to virtualbox.run, I've managed to boot up TinyLinux >>> on QEMU, but while QEMU says "booting kernel", the terminal reflects: >>> >>> ... >>> [init -> virtualbox] attempted to write to non-existing port 0xa79+1 . >> (02) >>> [init -> virtualbox] attempted to write to non-existing port 0xa79+1 . >> (05) >>> [init -> virtualbox] attempted to write to non-existing port 0xa79+1 . >> (02) >>> [init -> virtualbox] attempted to write to non-existing port 0xa79+1 . >> (00) >>> [init -> virtualbox] VMM: invalid gueststate >>> [init -> virtualbox] VMM: invalid gueststate >>> [init -> virtualbox] VMM: invalid gueststate >>> [init -> virtualbox] VMM: invalid gueststate >> >> I have another workaround to get a bit further, but finally Qemu for me >> (version 2.1.2 and 2.3.0) dies with an internal failure - so it will of >> no help to you. Please do as Christian suggested. >> >> Alex. >> >>> ... >>> >>> On Fri, Jul 10, 2015 at 3:23 PM, Alexander Boettcher < >>> alexander.boettc...@genode-labs.com> wrote: >>> Hello, On 10.07.2015 08:13, Daren Sin wrote: > [init -> acpi] Could not open ROM session for module "config" > [init -> acpi] void* abort(): abort called That it the actual reason, the acpi driver did not find a configuration xml node. The issue got fixed already on current Genode master branch, but for now you may apply the following fix [0]. Nevertheless, please consider the suggestions of Christian Helmuth. Cheers, Alex. [0] >> https://github.com/alex-ab/genode/commit/738ad842f546afef16f3eb642ca3ff5c7c36e0cd > > What might be the problem? > > Thanks! > > On Wed, Jul 8, 2015 at 1:23 AM, Martin Stein < martin.st...@genode-labs.com> > wrote: > >> Hi Daren, >> >> On 08.07.2015 04:51, Daren Sin wrote: >>> Hi, >>> >>> I've found this >>> page >> >> http://genode.org/documentation/release-notes/14.02#VirtualBox_on_top_of_the_NOVA_microhypervisor >>> and managed to run the /make prepare/ command, but got stuck at the next >>> one. >> >> The 'make prepare' mechanism is outdated. It has been replaced by the >> prepare_port command in tool/ports. Call the tool without arguments >> for >> a short manpage. >> >>> I tried doing that, but got a /Error: libc is not >>> prepared or outdated/ error. >> >> The error indicates that the third-party package "libc", which is >> needed >> for your scenario, is missing or too old. You can update it by doing >> './prepare_port libc' in tool/ports. There may be further third-party >> packages (ports) that need such treatment. >> >> Cheers, >> Martin >> >> >> >> -- >> Don't Limit Your Business. Reach for the Cloud. >> GigeNET's Cloud Solutions provide you with the tools and support that >> you need to offload your IT needs and focus on growing your business. >> Configured For All Businesses. Start Your Cloud Today. >> https://www.gigenetcloud.com/ >> ___ >> genode-main mailing list >> genode-main@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/genode-main >> > > > > > > >> -- > Don't Limit Your Business. Reach for the Cloud. > GigeNET's Cloud Solutions provide you with the tools and support that > you need to offload your IT needs and focus on growing your business. > Configured For All Businesses. Start Your Cloud Today. > https://www.gigenetcloud.com/ > > > > ___ > genode-main mailing list > genode-main@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/genode-main > >> -- Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Clou
Re: running VirtualBox on Genode
Hi, In order to run from my USB, where should I obtain the .iso file from? Cheers Daren On Fri, Jul 10, 2015 at 5:15 PM, Alexander Boettcher < alexander.boettc...@genode-labs.com> wrote: > On 10.07.2015 10:36, Daren Sin wrote: > > Hi Alex and Christian, > > > > Really really thankful for the advice; apologies for the spoonfeeding as > > well. Making changes to virtualbox.run, I've managed to boot up TinyLinux > > on QEMU, but while QEMU says "booting kernel", the terminal reflects: > > > > ... > > [init -> virtualbox] attempted to write to non-existing port 0xa79+1 . > (02) > > [init -> virtualbox] attempted to write to non-existing port 0xa79+1 . > (05) > > [init -> virtualbox] attempted to write to non-existing port 0xa79+1 . > (02) > > [init -> virtualbox] attempted to write to non-existing port 0xa79+1 . > (00) > > [init -> virtualbox] VMM: invalid gueststate > > [init -> virtualbox] VMM: invalid gueststate > > [init -> virtualbox] VMM: invalid gueststate > > [init -> virtualbox] VMM: invalid gueststate > > I have another workaround to get a bit further, but finally Qemu for me > (version 2.1.2 and 2.3.0) dies with an internal failure - so it will of > no help to you. Please do as Christian suggested. > > Alex. > > > ... > > > > On Fri, Jul 10, 2015 at 3:23 PM, Alexander Boettcher < > > alexander.boettc...@genode-labs.com> wrote: > > > >> Hello, > >> > >> On 10.07.2015 08:13, Daren Sin wrote: > >>> [init -> acpi] Could not open ROM session for module "config" > >>> [init -> acpi] void* abort(): abort called > >> > >> That it the actual reason, the acpi driver did not find a configuration > >> xml node. The issue got fixed already on current Genode master branch, > >> but for now you may apply the following fix [0]. Nevertheless, please > >> consider the suggestions of Christian Helmuth. > >> > >> Cheers, > >> > >> Alex. > >> > >> [0] > >> > >> > https://github.com/alex-ab/genode/commit/738ad842f546afef16f3eb642ca3ff5c7c36e0cd > >>> > >>> What might be the problem? > >>> > >>> Thanks! > >>> > >>> On Wed, Jul 8, 2015 at 1:23 AM, Martin Stein < > >> martin.st...@genode-labs.com> > >>> wrote: > >>> > Hi Daren, > > On 08.07.2015 04:51, Daren Sin wrote: > > Hi, > > > > I've found this > > page > > >> > http://genode.org/documentation/release-notes/14.02#VirtualBox_on_top_of_the_NOVA_microhypervisor > > and managed to run the /make prepare/ command, but got stuck at the > >> next > > one. > > The 'make prepare' mechanism is outdated. It has been replaced by the > prepare_port command in tool/ports. Call the tool without arguments > for > a short manpage. > > > I tried doing that, but got a /Error: libc is not > > prepared or outdated/ error. > > The error indicates that the third-party package "libc", which is > needed > for your scenario, is missing or too old. You can update it by doing > './prepare_port libc' in tool/ports. There may be further third-party > packages (ports) that need such treatment. > > Cheers, > Martin > > > > >> > -- > Don't Limit Your Business. Reach for the Cloud. > GigeNET's Cloud Solutions provide you with the tools and support that > you need to offload your IT needs and focus on growing your business. > Configured For All Businesses. Start Your Cloud Today. > https://www.gigenetcloud.com/ > ___ > genode-main mailing list > genode-main@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/genode-main > > >>> > >>> > >>> > >>> > >>> > >>> > >> > -- > >>> Don't Limit Your Business. Reach for the Cloud. > >>> GigeNET's Cloud Solutions provide you with the tools and support that > >>> you need to offload your IT needs and focus on growing your business. > >>> Configured For All Businesses. Start Your Cloud Today. > >>> https://www.gigenetcloud.com/ > >>> > >>> > >>> > >>> ___ > >>> genode-main mailing list > >>> genode-main@lists.sourceforge.net > >>> https://lists.sourceforge.net/lists/listinfo/genode-main > >>> > >> > >> > >> > >> > -- > >> Don't Limit Your Business. Reach for the Cloud. > >> GigeNET's Cloud Solutions provide you with the tools and support that > >> you need to offload your IT needs and focus on growing your business. > >> Configured For All Businesses. Start Your Cloud Today. > >> https://www.gigenetcloud.com/ > >> ___ > >> genode-main mailing list > >> genode-main@lists.sourceforge.net > >> https://lists.sourceforge.net/lists/listinfo/genode-main > >> > > > > > > > > > > > > > --
Re: running VirtualBox on Genode
On 10.07.2015 10:36, Daren Sin wrote: > Hi Alex and Christian, > > Really really thankful for the advice; apologies for the spoonfeeding as > well. Making changes to virtualbox.run, I've managed to boot up TinyLinux > on QEMU, but while QEMU says "booting kernel", the terminal reflects: > > ... > [init -> virtualbox] attempted to write to non-existing port 0xa79+1 . (02) > [init -> virtualbox] attempted to write to non-existing port 0xa79+1 . (05) > [init -> virtualbox] attempted to write to non-existing port 0xa79+1 . (02) > [init -> virtualbox] attempted to write to non-existing port 0xa79+1 . (00) > [init -> virtualbox] VMM: invalid gueststate > [init -> virtualbox] VMM: invalid gueststate > [init -> virtualbox] VMM: invalid gueststate > [init -> virtualbox] VMM: invalid gueststate I have another workaround to get a bit further, but finally Qemu for me (version 2.1.2 and 2.3.0) dies with an internal failure - so it will of no help to you. Please do as Christian suggested. Alex. > ... > > On Fri, Jul 10, 2015 at 3:23 PM, Alexander Boettcher < > alexander.boettc...@genode-labs.com> wrote: > >> Hello, >> >> On 10.07.2015 08:13, Daren Sin wrote: >>> [init -> acpi] Could not open ROM session for module "config" >>> [init -> acpi] void* abort(): abort called >> >> That it the actual reason, the acpi driver did not find a configuration >> xml node. The issue got fixed already on current Genode master branch, >> but for now you may apply the following fix [0]. Nevertheless, please >> consider the suggestions of Christian Helmuth. >> >> Cheers, >> >> Alex. >> >> [0] >> >> https://github.com/alex-ab/genode/commit/738ad842f546afef16f3eb642ca3ff5c7c36e0cd >>> >>> What might be the problem? >>> >>> Thanks! >>> >>> On Wed, Jul 8, 2015 at 1:23 AM, Martin Stein < >> martin.st...@genode-labs.com> >>> wrote: >>> Hi Daren, On 08.07.2015 04:51, Daren Sin wrote: > Hi, > > I've found this > page >> http://genode.org/documentation/release-notes/14.02#VirtualBox_on_top_of_the_NOVA_microhypervisor > and managed to run the /make prepare/ command, but got stuck at the >> next > one. The 'make prepare' mechanism is outdated. It has been replaced by the prepare_port command in tool/ports. Call the tool without arguments for a short manpage. > I tried doing that, but got a /Error: libc is not > prepared or outdated/ error. The error indicates that the third-party package "libc", which is needed for your scenario, is missing or too old. You can update it by doing './prepare_port libc' in tool/ports. There may be further third-party packages (ports) that need such treatment. Cheers, Martin >> -- Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ ___ genode-main mailing list genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main >>> >>> >>> >>> >>> >>> >> -- >>> Don't Limit Your Business. Reach for the Cloud. >>> GigeNET's Cloud Solutions provide you with the tools and support that >>> you need to offload your IT needs and focus on growing your business. >>> Configured For All Businesses. Start Your Cloud Today. >>> https://www.gigenetcloud.com/ >>> >>> >>> >>> ___ >>> genode-main mailing list >>> genode-main@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/genode-main >>> >> >> >> >> -- >> Don't Limit Your Business. Reach for the Cloud. >> GigeNET's Cloud Solutions provide you with the tools and support that >> you need to offload your IT needs and focus on growing your business. >> Configured For All Businesses. Start Your Cloud Today. >> https://www.gigenetcloud.com/ >> ___ >> genode-main mailing list >> genode-main@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/genode-main >> > > > > > > -- > Don't Limit Your Business. Reach for the Cloud. > GigeNET's Cloud Solutions provide you with the tools and support that > you need to offload your IT needs and focus on growing your business. > Configured For All Businesses. Start Your Cloud Today. > https://www.gigenetcloud.com/ > > > > ___ > genode-main mailing list > genode-main@lists.sourceforge.net > https://lists.sourceforge.n
Re: running VirtualBox on Genode
Hi Alex and Christian, Really really thankful for the advice; apologies for the spoonfeeding as well. Making changes to virtualbox.run, I've managed to boot up TinyLinux on QEMU, but while QEMU says "booting kernel", the terminal reflects: ... [init -> virtualbox] attempted to write to non-existing port 0xa79+1 . (02) [init -> virtualbox] attempted to write to non-existing port 0xa79+1 . (05) [init -> virtualbox] attempted to write to non-existing port 0xa79+1 . (02) [init -> virtualbox] attempted to write to non-existing port 0xa79+1 . (00) [init -> virtualbox] VMM: invalid gueststate [init -> virtualbox] VMM: invalid gueststate [init -> virtualbox] VMM: invalid gueststate [init -> virtualbox] VMM: invalid gueststate ... On Fri, Jul 10, 2015 at 3:23 PM, Alexander Boettcher < alexander.boettc...@genode-labs.com> wrote: > Hello, > > On 10.07.2015 08:13, Daren Sin wrote: > > [init -> acpi] Could not open ROM session for module "config" > > [init -> acpi] void* abort(): abort called > > That it the actual reason, the acpi driver did not find a configuration > xml node. The issue got fixed already on current Genode master branch, > but for now you may apply the following fix [0]. Nevertheless, please > consider the suggestions of Christian Helmuth. > > Cheers, > > Alex. > > [0] > > https://github.com/alex-ab/genode/commit/738ad842f546afef16f3eb642ca3ff5c7c36e0cd > > > > What might be the problem? > > > > Thanks! > > > > On Wed, Jul 8, 2015 at 1:23 AM, Martin Stein < > martin.st...@genode-labs.com> > > wrote: > > > >> Hi Daren, > >> > >> On 08.07.2015 04:51, Daren Sin wrote: > >>> Hi, > >>> > >>> I've found this > >>> page > >> > http://genode.org/documentation/release-notes/14.02#VirtualBox_on_top_of_the_NOVA_microhypervisor > >>> and managed to run the /make prepare/ command, but got stuck at the > next > >>> one. > >> > >> The 'make prepare' mechanism is outdated. It has been replaced by the > >> prepare_port command in tool/ports. Call the tool without arguments for > >> a short manpage. > >> > >>> I tried doing that, but got a /Error: libc is not > >>> prepared or outdated/ error. > >> > >> The error indicates that the third-party package "libc", which is needed > >> for your scenario, is missing or too old. You can update it by doing > >> './prepare_port libc' in tool/ports. There may be further third-party > >> packages (ports) that need such treatment. > >> > >> Cheers, > >> Martin > >> > >> > >> > -- > >> Don't Limit Your Business. Reach for the Cloud. > >> GigeNET's Cloud Solutions provide you with the tools and support that > >> you need to offload your IT needs and focus on growing your business. > >> Configured For All Businesses. Start Your Cloud Today. > >> https://www.gigenetcloud.com/ > >> ___ > >> genode-main mailing list > >> genode-main@lists.sourceforge.net > >> https://lists.sourceforge.net/lists/listinfo/genode-main > >> > > > > > > > > > > > > > -- > > Don't Limit Your Business. Reach for the Cloud. > > GigeNET's Cloud Solutions provide you with the tools and support that > > you need to offload your IT needs and focus on growing your business. > > Configured For All Businesses. Start Your Cloud Today. > > https://www.gigenetcloud.com/ > > > > > > > > ___ > > genode-main mailing list > > genode-main@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/genode-main > > > > > > -- > Don't Limit Your Business. Reach for the Cloud. > GigeNET's Cloud Solutions provide you with the tools and support that > you need to offload your IT needs and focus on growing your business. > Configured For All Businesses. Start Your Cloud Today. > https://www.gigenetcloud.com/ > ___ > genode-main mailing list > genode-main@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/genode-main > -- Thank you! Regards, Daren -- Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/___ genode-main mailing list genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
Re: running VirtualBox on Genode
Hello, On 10.07.2015 08:13, Daren Sin wrote: > [init -> acpi] Could not open ROM session for module "config" > [init -> acpi] void* abort(): abort called That it the actual reason, the acpi driver did not find a configuration xml node. The issue got fixed already on current Genode master branch, but for now you may apply the following fix [0]. Nevertheless, please consider the suggestions of Christian Helmuth. Cheers, Alex. [0] https://github.com/alex-ab/genode/commit/738ad842f546afef16f3eb642ca3ff5c7c36e0cd > > What might be the problem? > > Thanks! > > On Wed, Jul 8, 2015 at 1:23 AM, Martin Stein > wrote: > >> Hi Daren, >> >> On 08.07.2015 04:51, Daren Sin wrote: >>> Hi, >>> >>> I've found this >>> page >> http://genode.org/documentation/release-notes/14.02#VirtualBox_on_top_of_the_NOVA_microhypervisor >>> and managed to run the /make prepare/ command, but got stuck at the next >>> one. >> >> The 'make prepare' mechanism is outdated. It has been replaced by the >> prepare_port command in tool/ports. Call the tool without arguments for >> a short manpage. >> >>> I tried doing that, but got a /Error: libc is not >>> prepared or outdated/ error. >> >> The error indicates that the third-party package "libc", which is needed >> for your scenario, is missing or too old. You can update it by doing >> './prepare_port libc' in tool/ports. There may be further third-party >> packages (ports) that need such treatment. >> >> Cheers, >> Martin >> >> >> -- >> Don't Limit Your Business. Reach for the Cloud. >> GigeNET's Cloud Solutions provide you with the tools and support that >> you need to offload your IT needs and focus on growing your business. >> Configured For All Businesses. Start Your Cloud Today. >> https://www.gigenetcloud.com/ >> ___ >> genode-main mailing list >> genode-main@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/genode-main >> > > > > > > -- > Don't Limit Your Business. Reach for the Cloud. > GigeNET's Cloud Solutions provide you with the tools and support that > you need to offload your IT needs and focus on growing your business. > Configured For All Businesses. Start Your Cloud Today. > https://www.gigenetcloud.com/ > > > > ___ > genode-main mailing list > genode-main@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/genode-main > -- Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ ___ genode-main mailing list genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
Re: running VirtualBox on Genode
Hello Daren, how long did you wait for the scenario to boot in Qemu? IMHO your provided log is truncated maybe you just have to be more patient to see some progress. On the other hand, it does not make much sense to run VirtualBox (a VMM) in Qemu (an emulator) and we do not test this use case. So, please don't expect it to work flawlessly. I suggest you find a Intel-VT-capable box, e.g. a Core i5, and boot from USB storage. Regards -- Christian Helmuth Genode Labs http://www.genode-labs.com/ · http://genode.org/ https://twitter.com/GenodeLabs · /ˈdʒiː.nəʊd/ Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth -- Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ ___ genode-main mailing list genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
Re: running VirtualBox on Genode
Hi thanks! That really helped a lot. Now, running make run/virtualbox has some progress, and QEMU is started. But I don't get anything on QEMU (except the description of NOVA), and I got the following in the terminal: Genode 15.05 int main(): --- create local services --- int main(): --- start init --- int main(): transferred 444 MB to init Quota exceeded! amount=24576, size=4096, consumed=24576 [init] upgrading quota donation for Env::CPU (8192 bytes) Quota exceeded! amount=32768, size=4096, consumed=32768 [init] upgrading quota donation for Env::CPU (8192 bytes) [init -> acpi] available memory for ACPI 2048 kiB, for PCI_DRV 5468 kiB [init -> acpi] void Acpi_table::_parse_tables(T*, Genode::uint32_t) [with T = unsigned int; Genode::uint32_t = unsigned int]: Found MADT [init -> acpi] MADT IRQ 0 -> GSI 2 flags: 0 [init -> acpi] MADT IRQ 5 -> GSI 5 flags: d [init -> acpi] MADT IRQ 9 -> GSI 9 flags: d [init -> acpi] MADT IRQ 10 -> GSI 10 flags: d [init -> acpi] MADT IRQ 11 -> GSI 11 flags: d [init -> acpi] Could not open ROM session for module "config" [init -> acpi] void* abort(): abort called [init -> virtualbox] void init_libc_lock_pipe(): init_libc_lock_pipe() [init -> virtualbox] using the pipe libc plugin [init -> virtualbox] getenv called for non-existent variable "XML_MEM_BREAKPOINT" [init -> virtualbox] getenv called for non-existent variable "XML_MEM_TRACE" [init -> virtualbox] getenv called for non-existent variable "LC_ALL" [init -> virtualbox] getenv called for non-existent variable "LC_CTYPE" [init -> virtualbox] getenv called for non-existent variable "LANG" [init -> virtualbox] getenv called for non-existent variable "PATH_LOCALE" [init -> virtualbox] getenv called for non-existent variable "VBOX_DISABLE_HOST_DISK_CACHE" [init -> virtualbox] getenv called for non-existent variable "CHARSETALIASDIR" [init -> virtualbox] getenv called for non-existent variable "TZ" [init -> virtualbox] int access(const char*, int): access not implemented [init -> virtualbox] getenv called for non-existent variable "TZ" [init -> virtualbox] fcntl(): command 2 not supported [init -> virtualbox] Log created: 2015-07-10T06:05:00.62100Z [init -> virtualbox] main Executable: /virtualbox [init -> virtualbox] Could not open ROM session for module "usb_devices" [init -> virtualbox] Could not retrieve the "usb_devices" ROM file.USB device pass-through unavailable. [init -> virtualbox] SystemProperties : Cannot determine default Guest Additions ISO location. Most likely they are not available int main(): --- init created, waiting for exit condition --- What might be the problem? Thanks! On Wed, Jul 8, 2015 at 1:23 AM, Martin Stein wrote: > Hi Daren, > > On 08.07.2015 04:51, Daren Sin wrote: > > Hi, > > > > I've found this > > page > http://genode.org/documentation/release-notes/14.02#VirtualBox_on_top_of_the_NOVA_microhypervisor > > and managed to run the /make prepare/ command, but got stuck at the next > > one. > > The 'make prepare' mechanism is outdated. It has been replaced by the > prepare_port command in tool/ports. Call the tool without arguments for > a short manpage. > > > I tried doing that, but got a /Error: libc is not > > prepared or outdated/ error. > > The error indicates that the third-party package "libc", which is needed > for your scenario, is missing or too old. You can update it by doing > './prepare_port libc' in tool/ports. There may be further third-party > packages (ports) that need such treatment. > > Cheers, > Martin > > > -- > Don't Limit Your Business. Reach for the Cloud. > GigeNET's Cloud Solutions provide you with the tools and support that > you need to offload your IT needs and focus on growing your business. > Configured For All Businesses. Start Your Cloud Today. > https://www.gigenetcloud.com/ > ___ > genode-main mailing list > genode-main@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/genode-main > -- Thank you! Regards, Daren -- Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/___ genode-main mailing list genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
Re: running VirtualBox on Genode
Hi Daren, On 08.07.2015 04:51, Daren Sin wrote: > Hi, > > I've found this > page > http://genode.org/documentation/release-notes/14.02#VirtualBox_on_top_of_the_NOVA_microhypervisor > and managed to run the /make prepare/ command, but got stuck at the next > one. The 'make prepare' mechanism is outdated. It has been replaced by the prepare_port command in tool/ports. Call the tool without arguments for a short manpage. > I tried doing that, but got a /Error: libc is not > prepared or outdated/ error. The error indicates that the third-party package "libc", which is needed for your scenario, is missing or too old. You can update it by doing './prepare_port libc' in tool/ports. There may be further third-party packages (ports) that need such treatment. Cheers, Martin -- Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ ___ genode-main mailing list genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
Re: running VirtualBox on Genode
Hi, I've found this page http://genode.org/documentation/release-notes/14.02#VirtualBox_on_top_of_the_NOVA_microhypervisor and managed to run the *make prepare* command, but got stuck at the next one. Where am I supposed to add the part? And after this *config* portion, am I supposed to run *make run/virtualbox* in the build directory? I tried doing that, but got a *Error: libc is not prepared or outdated* error. Thanks! On Tue, Jul 7, 2015 at 5:06 PM, Christian Helmuth < christian.helm...@genode-labs.com> wrote: > Hello again, > > On Tue, Jul 07, 2015 at 11:05:03AM +0800, Daren Sin wrote: > > I've seen the Genode website, and I noticed that it is possible to run > > VirtualBox on Genode. I'm currently running Genode on a NOVA hypervisor. > > > > What should I do to get VirtualBox running on Genode? > > For a first impression, you give 'run/virtualbox' in the ports > repository a spin. This run script uses a bootable CDROM image from > the file 'bin/test.iso' as test case. I suggest you download a small > Linux live CD, e.g., http://tinycorelinux.net/, and save it as > 'bin/test.iso'. > > Regards > -- > Christian Helmuth > Genode Labs > > http://www.genode-labs.com/ · http://genode.org/ > https://twitter.com/GenodeLabs · /ˈdʒiː.nəʊd/ > > Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden > Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth > > > -- > Don't Limit Your Business. Reach for the Cloud. > GigeNET's Cloud Solutions provide you with the tools and support that > you need to offload your IT needs and focus on growing your business. > Configured For All Businesses. Start Your Cloud Today. > https://www.gigenetcloud.com/ > ___ > genode-main mailing list > genode-main@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/genode-main > -- Thank you! Regards, Daren -- Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/___ genode-main mailing list genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
Re: running VirtualBox on Genode
Hello again, On Tue, Jul 07, 2015 at 11:05:03AM +0800, Daren Sin wrote: > I've seen the Genode website, and I noticed that it is possible to run > VirtualBox on Genode. I'm currently running Genode on a NOVA hypervisor. > > What should I do to get VirtualBox running on Genode? For a first impression, you give 'run/virtualbox' in the ports repository a spin. This run script uses a bootable CDROM image from the file 'bin/test.iso' as test case. I suggest you download a small Linux live CD, e.g., http://tinycorelinux.net/, and save it as 'bin/test.iso'. Regards -- Christian Helmuth Genode Labs http://www.genode-labs.com/ · http://genode.org/ https://twitter.com/GenodeLabs · /ˈdʒiː.nəʊd/ Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth -- Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ ___ genode-main mailing list genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
running VirtualBox on Genode
Hi all, I've seen the Genode website, and I noticed that it is possible to run VirtualBox on Genode. I'm currently running Genode on a NOVA hypervisor. What should I do to get VirtualBox running on Genode? Thank you! -- Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/___ genode-main mailing list genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
