If you are using virtio drivers, there’s no longer a need for ‘device virtio_pci’ in your kernel config. It’s autoloaded as a dependency. If you run a custom kernel, remember to take it out. You’ll want to do that now if you’re on 5.1, or later at the next version upgrade if you are on 5.0.
3 Replies to “Kernel config change for virtio”
Comments are closed.
Random question, with the exciting release of Hammer2 and the understable bump in version # from v4 to v5.
What’s the big item that would justify DragonglyBSD to v6?
(I completely realize v6 is probably 3+ years from now. Just curious what the next big ticket item is that people are looking at tackling)
Similar to the comment above …
DragonflyBSD seems to be so great.
But What major things does DragonflyBSD even need worked on?
Seems like there isn’t anything major besides improving Hammer2 that needs to happen. Correct?
The first thought that comes to mind is HAMMER2 being default instead of merely an option.