On Mon, Apr 14, 2025 at 07:38:18PM +0200, Roman Bogorodskiy wrote: > Daniel P. Berrangé wrote: > > > On Mon, Apr 14, 2025 at 02:36:11PM +0200, Roman Bogorodskiy wrote: > > > Hi, > > > > > > I'd like to test the bhyve driver using libvirt-tck, which seems to be > > > very useful both from the continuous integration perspective, > > > and making the bhyve driver closer to other drivers to improve > > > integration with other tooling.
> > > * Missing pty console support > > > > > > Bhyve does not support pty consoles. The bhyve driver currently > > > supports > > > the nmdm console, and bhyve also supports virtio-console and TCP > > > socket > > > connection which are not yet supported by the driver. > > > > Don't have a particular suggestion for this without looking at the code > > in more detail. > > Maybe it will make sense to report supported console configurations via > domain capabilities as well? Yes, it is in scope for the domain capabilities. We've been adding stuff to capabilities as-needed, so there are definitely gaps there which can be filled in. > > When using bhyveload, is there any firmware at all ? Or is it fully > > paravirtualized in some way to avoid any firmware ? When using > > <type>hvm</type> conceptually we would expect a firmware to be > > present. > > In my understanding, it's not paravirtualized, in a way that it doesn't > need special guests preparations and can load any reasonable general > FreeBSD image. It doesn't need any firmware. It's based on the FreeBSD > loader and knows how to load the FreeBSD kernel into memory. Ah, so in that sense it is effectively a replacement for the traditional 'grub2' bootloader or equivalent. With regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
