@Burer, do you see this error when looking in VBox.log? Should be in the Logs folder of wherever your KolibriOS VM folder is: `00:00:06.095625 NVMe#0Wrk#0: Processing admin command 0xffff…
@Burer, Some good news, I have sent @punk_joker a message but maybe you can answer this as well:
punk_joker,
I think I may be onto something why Virtualbox and VMWare don't work. It's…
Got it, just thought that you want to deal with VMWare later. Just the same result, this message in debug and dead system.
@Burer, my bad! I meant let's avoid testing with calling loaddrv…
Ah, that's not what I meant. Sorry.
I forgot to add the updated image, so check the newest commit and try that one instead. If there's a message saying something like: "Writing to SQ0 doorbell…
@Burer These are interesting results. So it looks like both Virtualbox and VMWare both fail to send a command (at least I think so for VMWare...) except VMWare freezes immediately after that…
Yes, just to be clear. I added NVMe driver (version for 02.04.2024 from forum, I believe) loading to the AUTORUN.DAT, and got just the same results - system froze after a 1–2 seconds after…
NVM, so the QEMU issue was just related to me not having the NVMe device attached to QEMU (I'm an idiot...)
Regardless I've added a new patch to prevent the driver from loading if it fails to…
Well, at least related to the QEMU issue, it looks the data is uninitialized for some reason. I'm working on a fix for this, might help the VMWare situation too.
Calling loaddrv manually on QEMU also produces some weird behavior.
Huh? That's bizarre. I don't think it's a problem with VMWare's NVMe controller because the driver didn't even start PCI device enumeration yet if it didn't print anything. So it's probably a…
I've opened the issue here GSoC/kolibrios-nvme-driver#1
Thank you @Burer and @SweetBread :)
I asked admins, and now GSoC repos should be visibly publicly, but you still can't open issues in them, at least not for me. So will ask for this as well.
Thank you! It's much appreciated.…
Wouldn't mind fixing this issue myself but the source code is not available in the KolibriOS repository for some reason.
Not sure how KFM2 is supposed to look, but Eolite does display the label correctly now.
I should probably close this issue since it's been resolved, however, there's still the Virtualbox…