Update with commit eec1755d37. The system hanged up on first autoload, but loaded okay on second with driver fully working. Loading driver by hands on ISO image also worked fine. …
@Burer, I've lowered this number to 64 in the newer commits, please test now. Thank you.
@Burer, Oh.. well so the problem is the driver uses 256 queue entries. But VMWare only has 255. I'll add in a fix for lowering the queue requirement later.
This is not a bug in the driver, just…
@Burer, try pulling the changes from 0f24000b9a and use it to do to your tests. Try VMWare again.
Will…
UPD. Loading driver manually works fine now, at least for me in VirtualBox. But if loading driver multiple times, it loads connected devices multiple times, duplicating them and messing up…
@Burer, Thank you for providing these extensive tests! It's much appreciated, as always. :) I've opened a separate issue for these topics, I'm going to close this issue since it's been resolved now.
I think this is related to GSoC/kolibrios-nvme-driver#1 (comment) but I'm not sure.
I'll add a new commit providing very verbose logs later, it will…
@Burer , I've added the commit which removes the interrupt status bit check. This is not ideal but until I can think of a better solution I'll leave it like this for now.
So please test the…
@Burer, so I got the NVMe driver working on Virtualbox, however I haven't given this an extensive test yet. That specific freeze was caused by the interrupt status bit in the PCI status register…
Aha, so the controller is finally receiving commands properly, that's good news! It's just stuck calling the interrupt handler repeatedly, presumably because a command isn't being acknowledged as…
@Burer Following up on this,
Unfortunately, I haven't been able to fix this issue. However, I was able to find one useful hint as…