Date: Wed, 12 Jan 2022 21:24:12 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254513 --- Comment #36 from Jamie Landeg-Jones <firstname.lastname@example.org> --- (In reply to Dennis Noordsij from comment #35) One of the reasons I chose Vultr is that they provide FreeBSD images. Even though I've always rolled my own, I wanted to show support, and also, if there was some non-OS issue, I wouldn't get tickets closed with "We don't support FreeBSD!" As for installation, Vultr allow you to provide your own ISO to boot from, as well as their "customised OS installs" and also their "ISO library of standard releases" Up until I had this issue with FreeBSD 13, I always used the default Vultr KVM profile rather than the FreeBSD profile - indeed my non-FreeBSD 13 instances are still using it. It was only FreeBSD 13 that got stuck. If Hetzner only provides the older "i440fx" profile, you'd not have noticed the difference. The other issues with FreeBSD (boot on hang) may have been fixed - I've noticed there has been a bit of activity on this bug and the other bug related to this issue, but I haven't been following closely. [Note, you'd need to try a STABLE rather than RELEASE image) I'd never heard of Hetzner until recently, so it will be interesting to compare. (In reply to Kyle Evans from comment #33) If you want, I can help from the Vultr end too. Though I'm assuming they're still running their "free first $100" on signup, so you can actually test it yourself without cost if that's easier. P.S. I've no affiliation with Vultr, I've just been a customer for many years. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.