On 12/01/2011 04:09 PM, Miki Kenneth wrote:
I know that we are talking about only stable addresses, but I would
like to broaden the scope a bit
(don't kick me guys)...
Shouldn't we keep a run-time configuration vs "saved/commit"
By run time I mean: the current memory/cpu/disks/address per VM and by "stable"
I mean the "one in the DB".
That way, I'm going to be able to change properties in the stable config, which will
not affect the running one
(and vice versa).
Maybe this is totally different feature - but I decide to throw it on the table.
shouldn't that be part of the snapshot improvements design?
----- Original Message -----
> From: "Eli Mesika"<emesika(a)redhat.com>
> To: engine-devel(a)ovirt.org
> Sent: Wednesday, November 30, 2011 5:17:42 PM
> Subject: Re: [Engine-devel] Stable PCI Addresses design wiki
> Hi again
> The following is a design draft for a new feature of oVirt-engine
> planned for 3.1
> The feature allow devices in guest virtual machines to retain the
> same PCI address allocations as other devices are added or removed
> from the guest configuration. This is particularly important for
> Windows guests in order to prevent warnings or reactivation when
> device addresses change.
> This feature is supported by libvirt and should be implemented by
> RHEVM and VDSM.
> When creating a VM, QEMU allocates PCI addresses to the guest
> devices, these addresses are being reported by libvirt to VDSM and
> VDSM should report it back to RHEVM. RHEVM should persist the PCI
> addresses and report it as part of the VM configuration on the next
> run. If a change to the VM devices occurred RHEVM should detect the
> change and persist the new PCI addresses.
> Please review.
> Eli Mesika
> Redhat ISRAEL
> ----- Original Message -----
>> From: "Eli Mesika"<emesika(a)redhat.com>
>> To: engine-devel(a)ovirt.org
>> Sent: Wednesday, November 30, 2011 5:06:37 PM
>> Subject: [Engine-devel] Stable PCI Addresses design wiki
>> Engine-devel mailing list
> Engine-devel mailing list
Engine-devel mailing list