@dch I have not, good idea! maybe virtio as well? Gonna play around some this weekend...
@mwl @dch I did as part of my testing. I use NVMe devices for everything, no matter the underlying storage (thanks @ctuffli ). FWIW ahci-hd should only used for compatibility requirements (usually to get virtio drivers onboard for Windows guests) as it dog slow.
@Tubsta @dch @mwl hopefully goes without saying, but yell at me if a virtual shelf of N NVMe disks in bhyve doesn’t work
@ctuffli @dch @mwl You might know the current state, what is the pci device limit currently in bhyve? I think it is 32 but might be wrong
@Tubsta @dch @mwl bhyve "slot" specification in the max is bus:pcislot:function where bus is 0-255, pcislot is 0-31, and function is 0-7. If the maths don't fail me, that is around 64k-ish devices

@ctuffli @Tubsta @dch @mwl So, we talking bhyve or vm-bhyve?

I would not be surprised if vm-bhyve doesn’t assume that, “no one would ever want more than 8 devices”, or at least devices of one type.

Have you tried raw bhyve?

@dexter @ctuffli @Tubsta @dch vm-bhyve, because I'm lazy
@mwl @dexter @ctuffli @dch No, not lazy. You just want consistency because fat fingers on a massive native command line just gives you headaches you don’t need (well that is my excuse) #repeatable #bhyve

@Tubsta @dch @dexter @ctuffli

bhyve seems to work well, but yeah, those command lines are 

@mwl @Tubsta @dch @ctuffli I am speaking purely from a diagnostics perspective. I believe, to their credit, their log shows the command that was executed. Which is kinda important, given the many “bhyve” bugs along the lines of “it’s treating my boot drive as if it is a CD-ROM drive …” #TrueStory!

So yeah. Share the underlying actual stuff please because very few vm-bhyve bugs are bhyve bugs.

@dexter @mwl @dch @ctuffli That is how I found the issue yesterday. The logs are excellent in vm-bhyve.