/etc/ppt_aliases needs to be in the boot archive
12680 added PCI pass-through support in bhyve and introduces a new driver aliases file called
This file needs to be added to the boot archive so it is available during early boot.
This was done in OmniOS under https://github.com/omniosorg/illumos-omnios/commit/84bf4029fafd4fe7f1a2afd13999f
Updated by Hans Rosenfeld over 1 year ago
I kinda doubt that /etc/ppt_aliases if of any use outside of SmartOS. It's really just a kludge to work around the problem that changes to /etc/driver_aliases aren't persistent across reboots in SmartOS, hence we introduced this new file which to be loaded as a module by the bootloader.
In any other illumos distribution it's probably much easier and less confusing to just use the normal driver_aliases mechanism, using update_drv(1M) to attach ppt to a device.
Updated by John Levon over 1 year ago
I'm not sure I agree: ppt_aliases is an over-ride mechanism. If you just did a normal update_drv you'd lose the original packaged mapping (not sure what pkg would do with that) and would be unable to undo it easily without recording what it was.
Updated by Andy Fiddaman over 1 year ago
I have been using
ppt_aliases up to now just because of the problem that John highlights - I wanted to keep the original mapping in the
driver_aliases and keep
pkg verify happy:
bloody# update_drv -d -i 'pciex15b3,101f' mlxcx bloody# update_drv -a -i 'pciex15b3,101f' ppt devfsadm: driver failed to attach: ppt Warning: Driver (ppt) successfully added to system but failed to attach bloody# pkg verify mlxcx PACKAGE STATUS pkg://omnios/driver/network/mlxcx ERROR driver: mlxcx ERROR: alias 'pciex15b3,101f' missing from etc/driver_aliases
Updated by Electric Monk over 1 year ago
- Status changed from In Progress to Closed
- % Done changed from 0 to 100
commit b325f34d6fd056178a119182f410f157d35a9ea6 Author: Andy Fiddaman <email@example.com> Date: 2020-05-26T10:02:47.000Z 12781 /etc/ppt_aliases needs to be in the boot archive Reviewed by: Igor Kozhukhov <firstname.lastname@example.org> Reviewed by: Toomas Soome <email@example.com> Reviewed by: Robert Mustacchi <firstname.lastname@example.org> Approved by: Robert Mustacchi <email@example.com>