mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2024-12-28 00:25:23 +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
|
||
---|---|---|
.. | ||
bhyve_capabilities.c | ||
bhyve_capabilities.h | ||
bhyve_command.c | ||
bhyve_command.h | ||
bhyve_device.c | ||
bhyve_device.h | ||
bhyve_domain.c | ||
bhyve_domain.h | ||
bhyve_driver.c | ||
bhyve_driver.h | ||
bhyve_monitor.c | ||
bhyve_monitor.h | ||
bhyve_parse_command.c | ||
bhyve_parse_command.h | ||
bhyve_process.c | ||
bhyve_process.h | ||
bhyve_utils.h |