Never mind. Forgot to configure device in my build setup. Seems to be working. Nice work guys!
On Fri, Mar 3, 2017 at 9:04 PM, Derek Johansen <[email protected]> wrote: > When I run the sudo ./qemu.sh I get the follow in the ELKS window: > > Starting network processes: eth ktcp > > ERROR: failed to open device /dev/eth > failed to open /dev/eth > Starting network services: httpd. > > ELKS 0.2.0 > login: > > My environment is Windows 10 host running Ubuntu linux in virtualbox, > and then qemu running in vbox and elks running in qemu. > > I suspect this error is an issue with so many layers of > virtualization. Is there any hope of making this work or do I need a > more hospitable environment to use elks netwrorking? -- To unsubscribe from this list: send the line "unsubscribe linux-8086" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
