Re: Virtual machines from .vdi images

this particular machine has only USB 2.0 ports, no USB 3 ports. On Thu, Nov 2, 2017 at 6:14 PM, Nobody III wrote: > Do they work in all of your ports though? For me, some of my ports (USB > 3.0) worked and others (USB 2.0) did not. I'm asking about ports, not >

Re: Virtual machines from .vdi images

Do they work in all of your ports though? For me, some of my ports (USB 3.0) worked and others (USB 2.0) did not. I'm asking about ports, not devices. On Thu, Nov 2, 2017 at 1:12 PM, Chris Rothrock wrote: > I use both a USB keyboard and mouse. Both of these properly work

Re: Virtual machines from .vdi images

I use both a USB keyboard and mouse. Both of these properly work in the framebuffer window as well as in the TinyCore VM window without any issues. I have not tried other USB devices at this time, however. On Thu, Nov 2, 2017 at 2:45 PM, Nobody III wrote: > I'd also

Re: Virtual machines from .vdi images

I'd also verify that the platform driver works. I found that the Linux USB driver didn't detect devices plugged into USB 2.0 ports when running on Genode. The USB 3.0 ports worked just fine, and all the USB ports work when running Linux. I'd recommend checking whether you get similar results. On

Re: Restoring child with checkpointed state

Hi David On 11/02/2017 10:35 AM, David Werner wrote: > Hi, > > let me rephrase my question. Is "Thread::myself()->native_thread().kcap" > returning the kcap of another capability than > "Thread::myself->cap().data()->kcap()" ? As far as i understand yes. The > former returns the kcap of the gate

Re: Restoring child with checkpointed state

Hi, let me rephrase my question. Is "Thread::myself()->native_thread().kcap" returning the kcap of another capability than "Thread::myself->cap().data()->kcap()" ? As far as i understand yes. The former returns the kcap of the gate capability while the latter returns the capability of the

Re: binary naming

Thanks, that's exactly what I needed. Am 01.11.2017 um 15:40 schrieb Christian Helmuth: > Hello Johannes, > > I don't know exactly the compilation dependencies of your init binary > and how it should be built. But, you may have a look into > >