Hey #freebsd #bhyve users!
-
@mwl have you tried this with NVMe type as disk? s/virtio-blk/nvme/ for the type.
also maybe it runs out of “pci slots” try adding this:
ahci_device_limit="8"
I’ll try this tomorrow and see what comes up
@dch I have not, good idea! maybe virtio as well? Gonna play around some this weekend...
-
-
-
I already freeload sufficiently, thank you!
and I'm not gonna ask for expensive kit just to write one chapter.
@mwl @ParadeGrotesque if we were close I have EMC Fibre Channel disks in shelf that I could loan to you.
-
-
-
-
@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.
-
@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.
@mwl @Tubsta @dch @ctuffli I mean like, I didn’t write an OpenBSD bug report when I found that typo in Absolute OpenBSD. In of course the one chapter you didn’t trust me to have in advance. Nosiree. THEN you tasked me with raising over $150K to date (USD no less, not that Looney stuff) for a conference.
But yeah sure, blame bhyve.
Until of course it comes time to write a book on the subject… ahem!
-
@mwl @Tubsta @dch @ctuffli I mean like, I didn’t write an OpenBSD bug report when I found that typo in Absolute OpenBSD. In of course the one chapter you didn’t trust me to have in advance. Nosiree. THEN you tasked me with raising over $150K to date (USD no less, not that Looney stuff) for a conference.
But yeah sure, blame bhyve.
Until of course it comes time to write a book on the subject… ahem!
Sure, I ask if something's weird and file a bug.
But sometimes, I'm doing something actively daft. If bhyve-vm hangs trying to launch a host with 75 drives, my first instinct is to say "well, this would be because I'm a damn idiot trying to use 75 drives on one VM..."
-
-
-
-
I'm trying to test draid virtually for #openzfsmastery, because nobody's gonna give me a shelf of 60 disks to play with. I set everything up like:
disk35_name="disk35"
disk35_type="ahci-hd"
disk35_dev="sparse-zvol"Seems that if I have 35 ahci-hd entries, disk0 through disk34, bhyve and freebsd works. At disk35, the host panics on boot.
Is this expected with bhyve? Or does FreeBSD need a special tweak with 36 disks?
@mwl
I use 48+ disks zpools on bare-metal hardware, did not see any limit here... -
I'm trying to test draid virtually for #openzfsmastery, because nobody's gonna give me a shelf of 60 disks to play with. I set everything up like:
disk35_name="disk35"
disk35_type="ahci-hd"
disk35_dev="sparse-zvol"Seems that if I have 35 ahci-hd entries, disk0 through disk34, bhyve and freebsd works. At disk35, the host panics on boot.
Is this expected with bhyve? Or does FreeBSD need a special tweak with 36 disks?
Finally getting back to my 72-disk draid bhyve VM for #openzfsmastery.
Turns out that setting ahci_device_limit="8" in the vm-bhyve config let it boot just fine.
Thank you everyone for your suggestions, but especially @dch for this one!
