I read those and just now read: http://ddili.org/ders/d.en/fibers.html.
The main difference, at least from my limited view, is that D fibers have to explicitly yield and as far as I know in project loom they've built this yielding into the JVM when I/O occurs. It looks like libraries have to intercept libc calls in D to achieve the same thing [0].
I also see that D provides a fiber scheduler, but it only schedules on a single thread vs loom's virtualThreadExecutor which will use multiple threads.
I imagine you've already seen [1] and the two other articles it links to.
[0] https://vibed.org/features#fibers
[1] https://tour.dlang.org/tour/en/multithreading/fibers