Re: [Engine-devel] Stable PCI Addresses design wiki
my notes:
why adding new parameter to create verb and not using the createInfo? (or this is the
intention?)
if we expect xml to be large, perhaps it would be better to get it from db only before
sending it to vdsm,
to keep the vm object from getting too big, meaning never get it as part of vm dynamic.
----- 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.
Thanks
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
>
> http://www.ovirt.org/wiki/Features/Design/StablePCIAddresses
> _______________________________________________
> Engine-devel mailing list
> Engine-devel(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/engine-devel
>
_______________________________________________
Engine-devel mailing list
Engine-devel(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel