mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2024-12-22 05:35:25 +00:00
803966c76d
As bhyve for a long time didn't have a notion of the explicit SATA
controller and created a controller for each drive, the bhyve driver
in libvirt acted in a similar way and didn't care about the SATA
controllers and assigned PCI addresses to drives directly, as
the generated command will look like this anyway:
2:0,ahci-hd,somedisk.img
This no longer makes sense because:
1. After commit
|
||
---|---|---|
.. | ||
bhyvexml2xmlout-acpiapic.xml | ||
bhyvexml2xmlout-base.xml | ||
bhyvexml2xmlout-bhyveload-bootorder1.xml | ||
bhyvexml2xmlout-bhyveload-bootorder2.xml | ||
bhyvexml2xmlout-bhyveload-bootorder3.xml | ||
bhyvexml2xmlout-bhyveload-bootorder4.xml | ||
bhyvexml2xmlout-bhyveload-bootorder.xml | ||
bhyvexml2xmlout-bhyveload-explicitargs.xml | ||
bhyvexml2xmlout-console.xml | ||
bhyvexml2xmlout-custom-loader.xml | ||
bhyvexml2xmlout-disk-cdrom-grub.xml | ||
bhyvexml2xmlout-disk-cdrom.xml | ||
bhyvexml2xmlout-disk-virtio.xml | ||
bhyvexml2xmlout-grub-bootorder2.xml | ||
bhyvexml2xmlout-grub-bootorder.xml | ||
bhyvexml2xmlout-grub-defaults.xml | ||
bhyvexml2xmlout-localtime.xml | ||
bhyvexml2xmlout-macaddr.xml | ||
bhyvexml2xmlout-metadata.xml | ||
bhyvexml2xmlout-serial-grub-nocons.xml | ||
bhyvexml2xmlout-serial-grub.xml | ||
bhyvexml2xmlout-serial.xml |