On 10/24/2017 03:35 PM, Dawid Zamirski wrote:
> Previously, the driver was computing VBOX's devicePort/deviceSlot values
> based on device name and max port/slot values. While this worked, it
> completely ignored values. Additionally, libvirt's built-in
> virDomainDiskDefAssignAddress already do
Previously, the driver was computing VBOX's devicePort/deviceSlot values
based on device name and max port/slot values. While this worked, it
completely ignored values. Additionally, libvirt's built-in
virDomainDiskDefAssignAddress already does a good job setting default
values on virDomainDevice
