Upstream is no longer willing to backport patches to a branch
this old. If you disagree with the policy, please volunteer
to become the branch maintainer on <email address hidden>
Signed-off-by: Eric Blake <email address hidden>
d3d33c8...
by
Daniel Veillard <email address hidden>
Release of libvirt-0.8.3
* configure.ac docs/news.html.in libvirt.spec.in: updates
* po/*.po*: update and regenerated
bf0bf4e...
by
Jiri Denemark <email address hidden>
qemu: Fix PCI address allocation
Patch version revamped by Eric Blake <email address hidden> of Jiri
Denemark <email address hidden> original patch
When attaching a PCI device which doesn't explicitly set its PCI
address, libvirt allocates the address automatically. The problem is
that when checking which PCI address is unused, we only check for those
with slot number higher than the highest slot number ever used.
Thus attaching/detaching such device several times in a row (31 is the
theoretical limit, less then 30 tries are enough in practise) makes any
further device attachment fail. Furthermore, attaching a device with
predefined PCI address to 0:0:31 immediately forbids attachment of any
PCI device without explicit address.
This patch changes the logic so that we always check all PCI addresses
before we say there is no PCI address available.
Modifications from v1: revert back to remembering the last slot
reserved, but allow wraparound to not be limited by the end.
In this way, slots are still assigned in the same order as
before the patch, rather than filling in the gaps closest to
0 and risking making windows guests mad.
* src/qemu/qemu_conf.c: fix pci reservation code to do a round-robbin
check of all available PCI splot availability before failing.
Another gettext string with no format args sent to printf as a format string.
14954fb...
by
Matthias Bolte <email address hidden>
esx: Set storage pool target path to host.mountInfo.path
Now all storage pool types expose the target path.
5254546...
by
Matthias Bolte <email address hidden>
esx: Make storage pool lookup by name and UUID more robust
Don't rely on summary.url anymore, because its value is different
between an esx:// and vpx:// connection. Use host.mountInfo.path
instead.
Don't fallback to lookup by UUID (actually lookup by absolute path)
in esxVI_LookupDatastoreByName when lookup by name fails. Add a
seperate function for this: esxVI_LookupDatastoreByAbsolutePath
e4938ce...
by
Matthias Bolte <email address hidden>
esx: Restrict vpx:// to handle a single host in a vCenter
Now a vpx:// connection has an explicitly specified host. This
allows to enabled several functions for a vpx:// connection
again, like host UUID, hostname, general node info, max vCPU
count, free memory, migration and defining new domains.
Lookup datacenter, compute resource, resource pool and host
system once and cache them. This simplifies the rest of the
code and reduces overall HTTP(S) traffic a bit.
esx:// and vpx:// can be mixed freely for a migration.
Ensure that migration source and destination refer to the
same vCenter. Also directly encode the resource pool and
host system object IDs into the migration URI in the prepare
function. Then directly build managed object references in
the perform function instead of re-looking up already known
information.
9f85668...
by
Matthias Bolte <email address hidden>
esx: Map some managed object types
Datacenter, ComputeResource and HostSystem will be used for
simplified handling and caching.
