Re: Networking Support in VirtualBox

Chris, some annotations of your log below that may help. On Wed, Jul 26, 2017 at 09:58:11AM -0400, Chris Rothrock wrote: > NOVA Microhypervisor v7-2006635 (x86_64): Jul 25 2017 11:23:13 [gcc 6.3.0] > [MBI] > > [ 0] TSC:340 kHz BUS:0 kHz DL > [ 0] CORE:0:0:0 6:9e:9:1 [48] Intel(R) Core(TM)

Re: Networking Support in VirtualBox

I have pulled the latest commit and have a new build created (still giving the same condition with no video on either VM window but GUI still works). The serial log output is below. Several items stand out that I can see. Assertion failed from [init -> vbox1] EMT,[init -> vbox2] EMT, and NAT

Re: Networking Support in VirtualBox

The top entry from git log: commit 5e3e8073467628cd2a88fc1025be9a157f976e57 Author: Christian Helmuth Date: Wed May 31 16:05:53 2017 +0200 version: 17.05 This is the version pulled when I started with a fresh environment with the command: git clone

Re: Networking Support in VirtualBox

Chris, On Tue, Jul 25, 2017 at 09:46:52AM -0400, Chris Rothrock wrote: > The run recipe I am using is virtualbox.run. In this recipe there is no > indications that the ACPI has any configurable components. These > capabilities must be set in another file that this recipe is calling - > please

Re: Networking Support in VirtualBox

There was no arbitrary concatenation at all - this was the entirety of the log as it was transmitted across the serial port from the moment the Genode boot started with the NOVA kernel. If any concat was done, it was due to the unmodified code provided with the source. The 32 bit scenario was

Re: Networking Support in VirtualBox

Hello Chris, your log is very hard to read as it seems to arbitrarily concatenate several logs or multiple copies of the same log. I suggest you store one log file per boot of the test machine and attach the resulting file to your email in the future. I'll add some comments about what I read in

Re: Networking Support in VirtualBox

My mistake, the previous output is the working build with no networking enabled. Below is the networking enabled: NOVA Microhypervisor v7-8bcd6fc (x86_32): Jul 21 2017 10:14:19 [gcc 6.3.0] [ 0] TSC:3408373 kHz BUS:0 kHz [ 0] CORE:0:0:0 6:9e:9:1 [48] Intel(R) Core(TM) i5-7500 CPU @ 3.40GHz [ 1]

Re: Networking Support in VirtualBox

I have a desktop purchased for the sole purpose of Genode testing now (finding new hardware with a serial port is almost impossible nowadays). I have the output of the serial port that fails to load the virtualbox VMs. I looked through the log myself but I was unable to see a reason for the

Re: Networking Support in VirtualBox

On 06.07.2017 22:10, Chris Rothrock wrote: > leaves me back at my starting point - I have no means of obtaining serial > log data from a hardware boot. Seriously ? I can't believe. Getting a test machine with the minimal requirement of getting serial log output is fundamental to be productive.

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

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

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

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

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

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:

Re: Networking Support in VirtualBox

Would it work to get logging output over LAN using terminal_log and tcp_terminal? On Fri, Jun 23, 2017 at 3:54 AM, Alexander Boettcher < alexander.boettc...@genode-labs.com> wrote: > Hello, > > On 22.06.2017 20:29, Chris Rothrock wrote: > > Here is what I tried to fix this: > > I have increased

Re: Networking Support in VirtualBox

Hello, On 22.06.2017 20:29, Chris Rothrock wrote: > Here is what I tried to fix this: > I have increased the caps on the nic_bridge to 200 > increased the caps on the vbox1 and vbox2 to 500 > I removed the nic bridge from the config for one vbox in the virtualbox.run > (to see if I can get video

Re: Networking Support in VirtualBox

I am using all of your latest commit changes and I can get everything to work except if the test.vbox file has Adapter 0 enabled="true". if set to false (obviously there is no networking) but the two VM's boot into their respective windows, I can interact with each independently. When I enable

Re: Networking Support in VirtualBox

Hello, On 16.06.2017 20:20, Chris Rothrock wrote: > I'm working with the VirtualBox run recipe where I have set use_net 1, > added the repositories for dde_linux and dde_ipxe for the NIC driver. The > build runs successfully and I can boot to the 2 virtual machines (I have > one as TinyCore and

Networking Support in VirtualBox

I'm working with the VirtualBox run recipe where I have set use_net 1, added the repositories for dde_linux and dde_ipxe for the NIC driver. The build runs successfully and I can boot to the 2 virtual machines (I have one as TinyCore and one as DSL - Damn Small Linux) and interact with the OS's