11.2-BETA3 has introduced a new feature which allows the user to give VM devices an order number. The device order determines which PCI slot is used for a device when bhyve is invoked. Previously the user had no control over this ( see: https://redmine.ixsystems.com/issues/42371 ). Potentially this should allow VM configs via the new WebUI that could only be achieved using iohyve & the CLI in the past. For example, create a VM for FreeNAS master with multiple disks attached. Or make use of UEFI-CSM.
But, there is as yet, no documentation to say how this is supposed to function, nor from brief testing is it clear that there is a simple mapping between a VM device's "order number" and the bhyve pci slot it is attached to. For one thing, the behaviour is dependent on whether you use AHCI or VIRTIO mode for disk devices.
One obvious problem is that users moving from BETA2 to BETA3 are finding their linux VMs have lost network connectivity. For distros that use "predictable network interface names" like enp0s3, instead of eth0, the interface name can change (e.g becomes enp0s4) in BETA3 as the NIC is attached to a different pci slot. The solution is to change the NIC "device order" number in the WebUI.
Currently, there is a bug which prevents additional disk devices from being added to an existing VM via the new webUI. You have to go the old UI to add any additional disk devices, then return to the new webUI.
https://redmine.ixsystems.com/issues/46029
But, there is as yet, no documentation to say how this is supposed to function, nor from brief testing is it clear that there is a simple mapping between a VM device's "order number" and the bhyve pci slot it is attached to. For one thing, the behaviour is dependent on whether you use AHCI or VIRTIO mode for disk devices.
One obvious problem is that users moving from BETA2 to BETA3 are finding their linux VMs have lost network connectivity. For distros that use "predictable network interface names" like enp0s3, instead of eth0, the interface name can change (e.g becomes enp0s4) in BETA3 as the NIC is attached to a different pci slot. The solution is to change the NIC "device order" number in the WebUI.
Currently, there is a bug which prevents additional disk devices from being added to an existing VM via the new webUI. You have to go the old UI to add any additional disk devices, then return to the new webUI.
https://redmine.ixsystems.com/issues/46029
Last edited: