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 on even one)
your serial log output would tell you what goes wrong and you could fix it (with high probably) in less then 5 minutes.
If you have some Intel vPro machine, there you me use the Intel AMT SOL (SerialOverLine) feature to capture the log (if you managed to configure it correctly).
In principle, without serial output (PCI serial card, Mini PCI card/PCMCIA for notebooks, builtin UART/serial device ...) this kind of try and error play is useless.
Nothing I changed made any difference. As long as enabled="true" was set, neither VM loaded at all. This is booting from physical hardware, not in a virtualized environment. Thoughts?
Is the network device in your native machine supported by our network driver? lwip.run can be used for a simple test first.
I attached my serial log output of virtualbox.run with network and 2 VMs from a oldish Lenovo X201 Thinkpad (using amtterm to get Intel AMT SOL output.)
Regards,
[0] https://github.com/alex-ab/genode/commits/staging_vbox_run