Re: Networking Support in VirtualBox
I am running through a VM (Ubuntu Linux 16.04 in VirtualBox). I was unable to get my laptop with a serial port to work, it looks like it died so to obtain serial logs, I launched my compile through this VM using the QEMU module. The hardware this VM is on is anything but old - it's an 8 core Intel on an Alienware R4 laptop. I have 4 cores, 8 GB memory and 128 MB video RAM allocated to the VM with all virtualization support enabled. I am guessing that running this build through a VM will not work, which leaves me back at my starting point - I have no means of obtaining serial log data from a hardware boot. On Thu, Jul 6, 2017 at 4:00 PM, Alexander Boettcher < alexander.boettc...@genode-labs.com> wrote: > Hi, > > On 06.07.2017 21:40, Chris Rothrock wrote: > > Scratch that, I found the issue with this specific error (I had in the > > virtualbox.run recipe the nic_drv and nic_bridge commented out for > > troubleshooting). I have enabled these again and now have new errors > > listed below. The entire serial output listed below: > > > > NOVA Microhypervisor v7-8bcd6fc (x86_64): Jun 6 2017 12:07:06 [gcc > 6.3.0] > > > > [ 0] TSC:2637247 kHz BUS:1017434 kHz > > [ 0] CORE:0:0:0 6:f:b:0 [0] Intel(R) Core(TM)2 Duo CPU T7700 @ > 2.40GHz > > Hypervisor reports 1x1 CPU > > Warning: CPU has no invariant TSC. > > CPU ID (genode->kernel:package:core:thread) remapping > > remap (0->0:0:0:0) boot cpu > > You either running in a VM (looks bit like Qemu as VMM? [on XEN ?]) or > your CPU is really old, not to say odd. The invariant TSC is suspicious. > Only 1 CPU is more suspicious. According to Intel [0] it has 2 cores and > has hardware virtualization support (Vt-x). > > [0] > http://ark.intel.com/products/29762/Intel-Core2-Duo- > Processor-T7700-4M-Cache-2_40-GHz-800-MHz-FSB > > > [init -> vbox1] Warning: No virtualization hardware acceleration > available > > [init -> vbox2] Warning: No virtualization hardware acceleration > available > > Your CPU has no hardware support for virtualization. You either are not > running on real hardware or the feature is not turned on in your BIOS > (which sometimes is disabled by default by the PC vendors.) > > Cheers, > > -- > Alexander Boettcher > Genode Labs > > http://www.genode-labs.com - http://www.genode.org > > Genode Labs GmbH - Amtsgericht Dresden - HRB 28424 - Sitz Dresden > Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth > -- Thank You, Chris Rothrock Senior System Administrator (315) 308-1637 -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ genode-main mailing list genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
Re: Networking Support in VirtualBox
Hi, On 06.07.2017 21:40, Chris Rothrock wrote: > Scratch that, I found the issue with this specific error (I had in the > virtualbox.run recipe the nic_drv and nic_bridge commented out for > troubleshooting). I have enabled these again and now have new errors > listed below. The entire serial output listed below: > > NOVA Microhypervisor v7-8bcd6fc (x86_64): Jun 6 2017 12:07:06 [gcc 6.3.0] > > [ 0] TSC:2637247 kHz BUS:1017434 kHz > [ 0] CORE:0:0:0 6:f:b:0 [0] Intel(R) Core(TM)2 Duo CPU T7700 @ 2.40GHz > Hypervisor reports 1x1 CPU > Warning: CPU has no invariant TSC. > CPU ID (genode->kernel:package:core:thread) remapping > remap (0->0:0:0:0) boot cpu You either running in a VM (looks bit like Qemu as VMM? [on XEN ?]) or your CPU is really old, not to say odd. The invariant TSC is suspicious. Only 1 CPU is more suspicious. According to Intel [0] it has 2 cores and has hardware virtualization support (Vt-x). [0] http://ark.intel.com/products/29762/Intel-Core2-Duo-Processor-T7700-4M-Cache-2_40-GHz-800-MHz-FSB > [init -> vbox1] Warning: No virtualization hardware acceleration available > [init -> vbox2] Warning: No virtualization hardware acceleration available Your CPU has no hardware support for virtualization. You either are not running on real hardware or the feature is not turned on in your BIOS (which sometimes is disabled by default by the PC vendors.) Cheers, -- Alexander Boettcher Genode Labs http://www.genode-labs.com - http://www.genode.org Genode Labs GmbH - Amtsgericht Dresden - HRB 28424 - Sitz Dresden Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ genode-main mailing list genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
Re: Networking Support in VirtualBox
Yes, I found that I had those commented out for troubleshooting. I resent the new error log with assertion failures. On Thu, Jul 6, 2017 at 3:32 PM, Alexander Boettcher < alexander.boettc...@genode-labs.com> wrote: > Hello, > > On 06.07.2017 20:50, Chris Rothrock wrote: > > I have a serial output available now to help isolate the issue. Below is > > the entire output but it seems that the issue is nic_drv and nic_bridge > (as > > well as log_terminal) are being denied the ROM session necessary. Any > > thoughts as to why? > > In the list of available ROM modules, the nic_bridge, the nic_drv and > the log_terminal is missing: > > > :rom_fs: ROM modules: > > ROM: [7fe07000,7fe1a7e0) acpi_drv > > ROM: [7db6c000,7db6de6a) config > > ROM: [7fb0f000,7fdfccf8) core.o > > ROM: [7f8fb000,7f977cd8) device_pd > > ROM: [7ff9d000,7ffdedd0) fb_drv > > ROM: [00019000,0001a000) hypervisor_info_page > > ROM: [7e89,7e8cc6d0) init > > ROM: [7db6e000,7dc19bf8) ld.lib.so > > ROM: [7d9db000,7db0c050) libc.lib.so > > ROM: [7db4b000,7db53130) libc_pipe.lib.so > > ROM: [7fa01000,7fa0fd70) libc_terminal.lib.so > > ROM: [7fa1,7faf4d40) libiconv.lib.so > > ROM: [7f9d9000,7fa004a0) libm.lib.so > > ROM: [7db54000,7db6b9c8) nit_fb > > ROM: [7db0d000,7db4a2e0) nitpicker > > ROM: [7f99e000,7f9d8790) platform_drv > > ROM: [7f8cd000,7f8e5cf8) ps2_drv > > ROM: [7fdfd000,7fe066f0) pthread.lib.so > > ROM: [7f978000,7f99de18) qemu-usb.lib.so > > ROM: [7e878000,7e88f770) report_rom > > ROM: [7fe1b000,7fe2ba08) rtc_drv > > ROM: [7fe2d000,7ff9cae0) stdcxx.lib.so > > ROM: [7e8cd000,7f8cd000) test.iso > > ROM: [7fe2c000,7fe2cfb1) test.vbox > > ROM: [7f8e6000,7f8fa6a8) timer > > ROM: [7faf5000,7fb0e0a0) vbox_pointer > > ROM: [7dc1a000,7e877678) virtualbox5-nova > > Please check that the files are part of your boot_module list in your > run script and actually really got added. > > Cheers, > > -- > Alexander Boettcher > Genode Labs > > http://www.genode-labs.com - http://www.genode.org > > Genode Labs GmbH - Amtsgericht Dresden - HRB 28424 - Sitz Dresden > Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth > -- Thank You, Chris Rothrock Senior System Administrator (315) 308-1637 -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ genode-main mailing list genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
Re: Networking Support in VirtualBox
Scratch that, I found the issue with this specific error (I had in the virtualbox.run recipe the nic_drv and nic_bridge commented out for troubleshooting). I have enabled these again and now have new errors listed below. The entire serial output listed below: NOVA Microhypervisor v7-8bcd6fc (x86_64): Jun 6 2017 12:07:06 [gcc 6.3.0] [ 0] TSC:2637247 kHz BUS:1017434 kHz [ 0] CORE:0:0:0 6:f:b:0 [0] Intel(R) Core(TM)2 Duo CPU T7700 @ 2.40GHz Hypervisor reports 1x1 CPU Warning: CPU has no invariant TSC. CPU ID (genode->kernel:package:core:thread) remapping remap (0->0:0:0:0) boot cpu Hypervisor info page contains 8 memory descriptors: core image [0010,028a) binaries region [00225000,028a) free for reuse detected physical memory: 0x - size: 0x0009fc00 use physical memory: 0x - size: 0x0009f000 detected physical memory: 0x0010 - size: 0x7fee use physical memory: 0x0010 - size: 0x7fee :virt_alloc: Allocator 0x1e66f0 dump: Block: [2000,3000) size=4K avail=0 max_avail=0 Block: [3000,4000) size=4K avail=0 max_avail=0 Block: [4000,5000) size=4K avail=0 max_avail=0 Block: [5000,6000) size=4K avail=0 max_avail=0 Block: [6000,7000) size=4K avail=0 max_avail=0 Block: [7000,8000) size=4K avail=0 max_avail=0 Block: [8000,9000) size=4K avail=0 max_avail=0 Block: [9000,a000) size=4K avail=0 max_avail=0 Block: [a000,b000) size=4K avail=0 max_avail=0 Block: [b000,c000) size=4K avail=0 max_avail=0 Block: [c000,d000) size=4K avail=0 max_avail=0 Block: [d000,e000) size=4K avail=0 max_avail=0 Block: [e000,f000) size=4K avail=0 max_avail=0 Block: [f000,0001) size=4K avail=0 max_avail=0 Block: [0001,00011000) size=4K avail=0 max_avail=0 Block: [00011000,00012000) size=4K avail=0 max_avail=0 Block: [00012000,00013000) size=4K avail=0 max_avail=0 Block: [00013000,00014000) size=4K avail=0 max_avail=137434760164K Block: [00014000,00015000) size=4K avail=0 max_avail=0 Block: [00015000,00016000) size=4K avail=0 max_avail=0 Block: [00016000,00017000) size=4K avail=0 max_avail=0 Block: [00017000,00018000) size=4K avail=0 max_avail=0 Block: [00018000,00019000) size=4K avail=0 max_avail=0 Block: [00019000,0001a000) size=4K avail=0 max_avail=908K Block: [0001a000,0001b000) size=4K avail=0 max_avail=0 Block: [0001b000,0001c000) size=4K avail=0 max_avail=908K Block: [0001c000,0001d000) size=4K avail=0 max_avail=0 Block: [0001d000,0010) size=908K avail=908K max_avail=908K Block: [00225000,00226000) size=4K avail=0 max_avail=0 Block: [00226000,00227000) size=4K avail=0 max_avail=137434760164K Block: [00227000,00228000) size=4K avail=0 max_avail=0 Block: [00228000,a000) size=2619232K avail=2619232K max_avail=2619232K Block: [b000,bfeff000) size=261116K avail=261116K max_avail=137434760164K Block: [bff04000,7fffbfffd000) size=137434760164K avail=137434760164K max_avail=137434760164K => mem_size=140736144936960 (134216446 MB) / mem_avail=140736144814080 (134216446 MB) :phys_alloc: Allocator 0x1e5620 dump: Block: [1000,2000) size=4K avail=0 max_avail=0 Block: [2000,3000) size=4K avail=0 max_avail=0 Block: [3000,4000) size=4K avail=0 max_avail=0 Block: [4000,5000) size=4K avail=0 max_avail=0 Block: [5000,6000) size=4K avail=0 max_avail=0 Block: [6000,7000) size=4K avail=0 max_avail=0 Block: [7000,8000) size=4K avail=0 max_avail=0 Block: [8000,9000) size=4K avail=0 max_avail=0 Block: [9000,a000) size=4K avail=0 max_avail=0 Block: [a000,b000) size=4K avail=0 max_avail=0 Block: [b000,c000) size=4K avail=0 max_avail=0 Block: [c000,d000) size=4K avail=0 max_avail=2015480K Block: [d000,e000) size=4K avail=0 max_avail=0 Block: [e000,f000) size=4K avail=0 max_avail=0 Block: [f000,0001) size=4K avail=0 max_avail=0 Block: [0001,00011000) size=4K avail=0 max_avail=0 Block: [00011000,00012000) size=4K
Re: Networking Support in VirtualBox
Hello, On 06.07.2017 20:50, Chris Rothrock wrote: > I have a serial output available now to help isolate the issue. Below is > the entire output but it seems that the issue is nic_drv and nic_bridge (as > well as log_terminal) are being denied the ROM session necessary. Any > thoughts as to why? In the list of available ROM modules, the nic_bridge, the nic_drv and the log_terminal is missing: > :rom_fs: ROM modules: > ROM: [7fe07000,7fe1a7e0) acpi_drv > ROM: [7db6c000,7db6de6a) config > ROM: [7fb0f000,7fdfccf8) core.o > ROM: [7f8fb000,7f977cd8) device_pd > ROM: [7ff9d000,7ffdedd0) fb_drv > ROM: [00019000,0001a000) hypervisor_info_page > ROM: [7e89,7e8cc6d0) init > ROM: [7db6e000,7dc19bf8) ld.lib.so > ROM: [7d9db000,7db0c050) libc.lib.so > ROM: [7db4b000,7db53130) libc_pipe.lib.so > ROM: [7fa01000,7fa0fd70) libc_terminal.lib.so > ROM: [7fa1,7faf4d40) libiconv.lib.so > ROM: [7f9d9000,7fa004a0) libm.lib.so > ROM: [7db54000,7db6b9c8) nit_fb > ROM: [7db0d000,7db4a2e0) nitpicker > ROM: [7f99e000,7f9d8790) platform_drv > ROM: [7f8cd000,7f8e5cf8) ps2_drv > ROM: [7fdfd000,7fe066f0) pthread.lib.so > ROM: [7f978000,7f99de18) qemu-usb.lib.so > ROM: [7e878000,7e88f770) report_rom > ROM: [7fe1b000,7fe2ba08) rtc_drv > ROM: [7fe2d000,7ff9cae0) stdcxx.lib.so > ROM: [7e8cd000,7f8cd000) test.iso > ROM: [7fe2c000,7fe2cfb1) test.vbox > ROM: [7f8e6000,7f8fa6a8) timer > ROM: [7faf5000,7fb0e0a0) vbox_pointer > ROM: [7dc1a000,7e877678) virtualbox5-nova Please check that the files are part of your boot_module list in your run script and actually really got added. Cheers, -- Alexander Boettcher Genode Labs http://www.genode-labs.com - http://www.genode.org Genode Labs GmbH - Amtsgericht Dresden - HRB 28424 - Sitz Dresden Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ genode-main mailing list genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
Re: Networking Support in VirtualBox
I have a serial output available now to help isolate the issue. Below is the entire output but it seems that the issue is nic_drv and nic_bridge (as well as log_terminal) are being denied the ROM session necessary. Any thoughts as to why? warning: TCG doesn't support requested feature: CPUID.01H:EDX.vme [bit 1] Bender: Hello World. Need 0275 bytes to relocate modules. Relocating to 7d89: Copying 41066688 bytes... Copying 147640 bytes... NOVA Microhypervisor v7-8bcd6fc (x86_64): Jun 6 2017 12:07:06 [gcc 6.3.0] [ 0] TSC:2643542 kHz BUS:1019894 kHz [ 0] CORE:0:0:0 6:f:b:0 [0] Intel(R) Core(TM)2 Duo CPU T7700 @ 2.40GHz Hypervisor reports 1x1 CPU Warning: CPU has no invariant TSC. CPU ID (genode->kernel:package:core:thread) remapping remap (0->0:0:0:0) boot cpu Hypervisor info page contains 8 memory descriptors: core image [0010,02829000) binaries region [00225000,02829000) free for reuse detected physical memory: 0x - size: 0x0009fc00 use physical memory: 0x - size: 0x0009f000 detected physical memory: 0x0010 - size: 0x7fee use physical memory: 0x0010 - size: 0x7fee :virt_alloc: Allocator 0x1e65f0 dump: Block: [2000,3000) size=4K avail=0 max_avail=0 Block: [3000,4000) size=4K avail=0 max_avail=0 Block: [4000,5000) size=4K avail=0 max_avail=0 Block: [5000,6000) size=4K avail=0 max_avail=0 Block: [6000,7000) size=4K avail=0 max_avail=0 Block: [7000,8000) size=4K avail=0 max_avail=0 Block: [8000,9000) size=4K avail=0 max_avail=0 Block: [9000,a000) size=4K avail=0 max_avail=0 Block: [a000,b000) size=4K avail=0 max_avail=0 Block: [b000,c000) size=4K avail=0 max_avail=0 Block: [c000,d000) size=4K avail=0 max_avail=0 Block: [d000,e000) size=4K avail=0 max_avail=0 Block: [e000,f000) size=4K avail=0 max_avail=0 Block: [f000,0001) size=4K avail=0 max_avail=0 Block: [0001,00011000) size=4K avail=0 max_avail=0 Block: [00011000,00012000) size=4K avail=0 max_avail=0 Block: [00012000,00013000) size=4K avail=0 max_avail=0 Block: [00013000,00014000) size=4K avail=0 max_avail=137434760164K Block: [00014000,00015000) size=4K avail=0 max_avail=0 Block: [00015000,00016000) size=4K avail=0 max_avail=0 Block: [00016000,00017000) size=4K avail=0 max_avail=920K Block: [00017000,00018000) size=4K avail=0 max_avail=0 Block: [00018000,00019000) size=4K avail=0 max_avail=920K Block: [00019000,0001a000) size=4K avail=0 max_avail=0 Block: [0001a000,0010) size=920K avail=920K max_avail=920K Block: [00225000,00226000) size=4K avail=0 max_avail=0 Block: [00226000,00227000) size=4K avail=0 max_avail=137434760164K Block: [00227000,00228000) size=4K avail=0 max_avail=0 Block: [00228000,a000) size=2619232K avail=2619232K max_avail=2619232K Block: [b000,bfeff000) size=261116K avail=261116K max_avail=137434760164K Block: [bff04000,7fffbfffd000) size=137434760164K avail=137434760164K max_avail=137434760164K => mem_size=140736144936960 (134216446 MB) / mem_avail=140736144826368 (134216446 MB) :phys_alloc: Allocator 0x1e5520 dump: Block: [1000,2000) size=4K avail=0 max_avail=0 Block: [2000,3000) size=4K avail=0 max_avail=0 Block: [3000,4000) size=4K avail=0 max_avail=0 Block: [4000,5000) size=4K avail=0 max_avail=0 Block: [5000,6000) size=4K avail=0 max_avail=0 Block: [6000,7000) size=4K avail=0 max_avail=0 Block: [7000,8000) size=4K avail=0 max_avail=0 Block: [8000,9000) size=4K avail=0 max_avail=0 Block: [9000,a000) size=4K avail=0 max_avail=0 Block: [a000,b000) size=4K avail=0 max_avail=0 Block: [b000,c000) size=4K avail=0 max_avail=0 Block: [c000,d000) size=4K avail=0 max_avail=2015956K Block: [d000,e000) size=4K avail=0 max_avail=0 Block: [e000,f000) size=4K avail=0 max_avail=0 Block: [f000,0001) size=4K avail=0 max_avail=0 Block: [0001,00011000) size=4K avail=0 max_avail=0 Block: [00011000,00012000) size=4K avail=0 max_avail=0 Block:
Re: Boot problems using Genode 16.08 with Fiasco.OC r67 on a RPi Model B
Hello, I was finally able to get the RPi to boot completely by adding the following lines from foc r72: https://github.com/skalk/foc/blob/r72/l4/pkg/bootstrap/server/src/platform_common.cc#L47-L49 What still seems odd to me is, that when I'm using genode.img I can use the kernel_addr_r address (0x0100) stored in u-boot to successfully boot the RPi. For the image.elf I have to use a different address - something like 0x8000 - otherwise the RPi just resets itself. Some insight on this would be very helpful! Regards, Alexander On 2017-07-05 18:09, Alexander Weidinger wrote: > Dear Genode community, > > we are currently trying to get a Raspberry Pi 1 Model B running with > Genode 16.08 and Fiasco.OC r67 from https://github.com/skalk/foc/. > > We made changes to both, genode and foc but the basis are the two > mentioned versions. > > Trying to boot the RPi, we are left with the following message, the > board resets itself? and again tries to boot: >> ... >> reading genode.img >> 2060288 bytes read in 331 ms (5.9 MiB/s) >> Kernel image @ 0x100 [ 0x100 - 0x11f7000 ] >> >> Starting k >> L4 Bootstrapper >> Build: #5 Wed Jul 5 17:34:36 CEST 2017, 4.9.2 >> Scanning up to 512 MB RAM, starting at offset 32MB >> >> >> U-Boot 2014.07-rc3-gd4614d4 (Jun 14 2014 - 01:23:23) >> ... > (Trying to boot vanilla genode 16.08 with vanilla foc r67 (from skalk) > leads to the same behavior.) > > We were successful in running our setup (foc r67 and genode 16.08 both > with our changes) on a pandaboard (real hardware) and on pbxa9 (qemu). > Additionally we are able to successfully boot the RPi using vanilla > genode 16.08 with the provided foc version (r56), using our u-boot > configuration. > > Do we need to make additional changes to foc and/or genode to be able to > boot the RPi using r67 of foc? > Any hints or information are very welcomed! > > Regards, > Alexander > > > > -- > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > > > ___ > genode-main mailing list > genode-main@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/genode-main > signature.asc Description: OpenPGP digital signature -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ genode-main mailing list genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
