GSoC/kolibrios-nvme-driver
2
0
Fork 0
mirror of https://git.missingno.dev/kolibrios-nvme-driver/ synced 2024-09-19 01:51:03 +02:00
Code Issues 2 Actions Activity

VMWare Fails Initialization #4

New Issue
Closed
opened 2024-08-09 16:03:04 +02:00 by ramenu · 5 comments
ramenu commented 2024-08-09 16:03:04 +02:00
Member
Copy Link

This is a followup of #1 (comment).

Will make this easier to check what's going on by providing more debug logs.

This is a followup of https://git.kolibrios.org/GSoC/kolibrios-nvme-driver/issues/1#issuecomment-472. Will make this easier to check what's going on by providing more debug logs.
ramenu self-assigned this 2024-08-09 16:03:15 +02:00
ramenu commented 2024-08-09 19:56:42 +02:00
Author
Member
Copy Link

@Burer, try pulling the changes from 0f24000b9a and use it to do to your tests. Try VMWare again.

Will make debugging a lot easier for me.

@Burer, try pulling the changes from https://git.kolibrios.org/GSoC/kolibrios-nvme-driver/commit/0f24000b9a02d3d7c55bd1290e20479b0b21637b and use it to do to your tests. Try VMWare again. Will make debugging a lot easier for me.
Burer commented 2024-08-10 10:10:21 +02:00
Copy Link

@ramenu, ups, missed this Issue, so posted results of testing commit 0f24000b9a here:
#2 (comment)

@ramenu, ups, missed this Issue, so posted results of testing commit 0f24000b9a here: https://git.kolibrios.org/GSoC/kolibrios-nvme-driver/issues/2#issuecomment-490
Burer commented 2024-08-10 17:13:17 +02:00
Copy Link

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.
Screenshots from failed and normal autoload from IMG image.
So, I suppose, at least #2 is solved here, not sure about initialization at all.

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. Screenshots from failed and normal autoload from IMG image. So, I suppose, at least #2 is solved here, not sure about initialization at all.
nvme_eec1755d37_vmware_1.png
98 KiB
nvme_eec1755d37_vmware_2.png
130 KiB
nvme_eec1755d37_vmware_1.png nvme_eec1755d37_vmware_2.png
ramenu commented 2024-08-10 17:38:01 +02:00
Author
Member
Copy Link

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.
Screenshots from failed and normal autoload from IMG image.
So, I suppose, at least #2 is solved here, not sure about initialization at all.

Here's my guess. I don't know for sure though. In the logs of the first image, the PCNET32 driver loaded. It possibly shares the same IRQ as the NVMe driver. And because I removed the PCI status bit check (since Virtualbox wasn't setting the bit, and I'm guessing neither VMWare does as well) its possibly that caused some overlapping problems. Again, just an assumption.

The IRQ problem is tricky and I don't know how to get around it at the moment. If you'd like, you can test this theory out by removing the network from VMWare machine and do it again. If it doesn't hang, then I assume that's the problem.

> 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. > Screenshots from failed and normal autoload from IMG image. > So, I suppose, at least #2 is solved here, not sure about initialization at all. Here's my guess. I don't know for sure though. In the logs of the first image, the PCNET32 driver loaded. It possibly shares the same IRQ as the NVMe driver. And because I removed the PCI status bit check (since Virtualbox wasn't setting the bit, and I'm guessing neither VMWare does as well) its possibly that caused some overlapping problems. Again, just an assumption. The IRQ problem is tricky and I don't know how to get around it at the moment. If you'd like, you can test this theory out by removing the network from VMWare machine and do it again. If it doesn't hang, then I assume that's the problem.
👍 1
Burer commented 2024-08-12 09:01:58 +02:00
Copy Link

Update with commit c02d64b35a.
Driver loads okay in VMWare, both using autoload and loading by hand, but system in VMWare can't shut down properly, as described more detailed here:
#5 (comment)

Update with commit c02d64b35a. Driver loads okay in VMWare, both using autoload and loading by hand, but system in VMWare can't shut down properly, as described more detailed here: https://git.kolibrios.org/GSoC/kolibrios-nvme-driver/issues/5#issuecomment-521
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
ramenu
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: GSoC/kolibrios-nvme-driver#4
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?