On 12/13/2011 11:22 AM, Igor Lvovsky wrote:
>> -----Original Message-----
>> From: vdsm-devel-boun...@lists.fedorahosted.org [mailto:vdsm-devel-
>> boun...@lists.fedorahosted.org] On Behalf Of Dor Laor
>> Sent: Tuesday, December 13, 2011 10:02 AM
>> To: engine-de...@ovirt.org; firstname.lastname@example.org
>> Subject: http://www.ovirt.org/wiki/Features/Design/StablePCIAddresses
>> I read the design here and I like to make sure that the future road map
>> will expand beyond the current scope.
>> The current design totally rely on libvirt and does not parse the
>> content of the PCI addressing. That's really really basic. The user
>> should be able to specify pci slot allocation of his devices through the
>> gui. I guess you won't be able to do that w/ the current scheme.
> We know that the current design is not sufficient. This is exactly the
> reason why I am working right now on new one that will give abilities to the
> manager to change PCI addresses per device. But in any case we planning
> that the first addresses allocation will be done by libvirt and vdsm will
> return it to the manager.
> I am not sure whether it will be accessible via GUI. Livnat?
Not sure we'll expose it in the UI/API for editing in the first version,
more likely it will be included in a view-only mode and then extended
for user manipulations.
Anyway we are working on a more explicit API then a Blob, as Igor wrote.
>> Also, what about devices that can't be hot plug (like qxl)? You need to
>> reveal this info to the user. Currently we have ability in the kvm bios
>> (seabios) to automatically disable the host plug of some critical
>> devices like the vga driver (qxl) and others. The user should be allowed
>> to hot plug/unplug only allowed devices.
>> You have to make your design work w/ pci bridges since we'll add it to
>> qemu and once there is such VM (management should enable the bridge)
>> there will be more pci devices available to it.
>> vdsm-devel mailing list
> Engine-devel mailing list
vdsm-devel mailing list