We are getting close to the end of the month, so we may need to freeze
next Monday or Tuesday. Are we ready for 1.3.0 now :-) ? I see that
configure.ac targets 1.2.18, so a priori no, but would rather have a
clear answer :-)
Thanks,
Daniel
--
Daniel Veillard | Open Source and
On Wed, 2015-07-22 at 15:58 +0100, Daniel P. Berrange wrote:
Any suggestions on how to proceed?
We've hit this many times before and always just shorten the file
names in GIT to avoid it.
Really we could do with adding a check for filename length to
make check to avoid this again.
On 07/22/2015 11:50 AM, Daniel Veillard wrote:
We are getting close to the end of the month, so we may need to freeze
next Monday or Tuesday. Are we ready for 1.3.0 now :-) ? I see that
configure.ac targets 1.2.18, so a priori no, but would rather have a
clear answer :-)
I had posted
Daniel P. Berrange wrote:
On Sun, Jul 19, 2015 at 11:20:35AM +0300, Roman Bogorodskiy wrote:
Bhyve as of r279225 (FreeBSD -CURRENT) or r284894 (FreeBSD 10-STABLE)
supports using UTC time offset via the '-u' argument to bhyve(8). By
default it's still using localtime.
Make the bhyve
On Wed, Jul 22, 2015 at 04:44:56PM +0200, Andrea Bolognani wrote:
Hi everyone,
commit cc3d52e[1] has apparently broken 'make dist' for at least some
platforms: Fedora 20 is fine[2], but both Fedora 21 and rawhide[3][4]
are currently failing. My laptop is running Fedora 22 and can make
dist
If a pci address had a function number out of range, the error message
would be:
Insufficient specification for PCI address
This was due to an unnecessary call to virDevicePCIAddressIsValid()
during parse of the pci address - we will anyway check for validity of
the PCI address later on.
With
On 07/22/2015 08:44 AM, Andrea Bolognani wrote:
1. rename the test case, making it shorter;
Works if we can do it, but I agree we should add a syntax check to
enforce it.
2. bump tar format from ustar, which has limitations on the length
of file names, to posix/pax, which has no
Commit ac3ed20 breaks build on FreeBSD with:
CC util/libvirt_util_la-virnetdev.lo
util/virnetdev.c:2967:1: error: unused function 'virNetDevRDMAFeature'
[-Werror,-Wunused-function]
virNetDevRDMAFeature(const char *ifname,
^
So hide virNetDevRDMAFeature function under the #ifdef
On Wed, Jul 22, 2015 at 04:59:35PM +0100, Daniel P. Berrange wrote:
On Wed, Jul 22, 2015 at 05:49:20PM +0200, Andrea Bolognani wrote:
On Wed, 2015-07-22 at 15:58 +0100, Daniel P. Berrange wrote:
Any suggestions on how to proceed?
We've hit this many times before and always just
On Wed, Jul 22, 2015 at 05:49:20PM +0200, Andrea Bolognani wrote:
On Wed, 2015-07-22 at 15:58 +0100, Daniel P. Berrange wrote:
Any suggestions on how to proceed?
We've hit this many times before and always just shorten the file
names in GIT to avoid it.
Really we could do with
While searching the hostdevs the drive type can be either *_TYPE_DRIVE
or *_TYPE_NONE. If the type is _TYPE_NONE on the first scsi_host, then
there is an erroneous match that the address already exists.
Although this works by chance currently because hostdev's are added one
at a time and
Changes from v6 to v7:
* rebased on top of master now that the series this one
builds on have been merged
Again, I'm only sending patch 1/5 to the list because the
rest of the series hasn't changed from v5. Here are
pointers for your convenience:
2/5
On Wed, Jul 22, 2015 at 05:49:20PM +0200, Andrea Bolognani wrote:
On Wed, 2015-07-22 at 15:58 +0100, Daniel P. Berrange wrote:
Any suggestions on how to proceed?
We've hit this many times before and always just shorten the file
names in GIT to avoid it.
Really we could do with
From: Shivaprasad G Bhat sb...@linux.vnet.ibm.com
The nodeinfo is reporting incorrect number of cpus and incorrect host
topology on PPC64 KVM hosts. The KVM hypervisor on PPC64 needs only
the primary thread in a core to be online, and the secondaries offlined.
While scheduling a guest in, the kvm
Daniel P. Berrange wrote:
On Sun, Jul 19, 2015 at 11:20:36AM +0300, Roman Bogorodskiy wrote:
---
docs/drvbhyve.html.in | 28
1 file changed, 28 insertions(+)
ACK
Pushed, thanks!
Regards,
Daniel
--
|: http://berrange.com -o-
On 07/17/2015 02:43 PM, Laine Stump wrote:
This makes the range and static host array management in
virNetworkDHCPDefParseXML() more similar to what is done in
virNetworkDefUpdateIPDHCPRange() and virNetworkDefUpdateIPDHCPHost() -
they use VIR_APPEND_ELEMENT rather than a combination of
On 07/17/2015 02:43 PM, Laine Stump wrote:
This makes the range and static host array management in
virNetworkDHCPDefParseXML() more similar to what is done in
virNetworkDefUpdateIPDHCPRange() and virNetworkDefUpdateIPDHCPHost() -
they use VIR_APPEND_ELEMENT rather than a combination of
On 07/17/2015 02:43 PM, Laine Stump wrote:
There are some non-0 default values in virDomainControllerDef (and
will soon be more) that are easier to not forget if the remembering is
done by a single initializer function (rather than inline code after
allocating the obejct with generic
On 07/22/2015 03:54 PM, John Ferlan wrote:
On 07/17/2015 02:43 PM, Laine Stump wrote:
This patch provides qemu support for the contents of model in
controller for the two existing PCI controller types that need it
(i.e. the two controller types that are backed by a device that must
be
On 07/22/2015 04:18 PM, Laine Stump wrote:
On 07/22/2015 03:54 PM, John Ferlan wrote:
...
+if (deviceName
+VIR_STRDUP(options-type, deviceName) 0)
+goto cleanup;
+
As has been told to me before - virStrdup/VIR_STRDUP is tolerant of
I am running Openstack Tempest on an arm64 platform and am seeing some
test failures related to attaching volumes to an instance. This is an
example of the disk XML generated by one of the tests:
disk type=block device=diskdriver name=qemu type=raw
cache=none/source
On 07/17/2015 02:43 PM, Laine Stump wrote:
This uses the new subelement/attribute in two ways:
1) If a pci-bridge pci controller has no chassisNr attribute, it
will automatically be set to the controller's index during
qemuDomainAssignPCIAddresses()
2) when creating the commandline for
On 07/17/2015 02:43 PM, Laine Stump wrote:
The function that auto-assigns PCI addresses was written with the
hardcoded assumptions that any PCI bus would have slots available
starting at 1 and ending at 31. This isn't true for many types of
controller (some have a single slot/port at 0, some
On 07/17/2015 02:43 PM, Laine Stump wrote:
This loop occurs just after we've assured that all devices that
require a PCI device have been assigned and all necessary PCI
controllers have been added. It is the perfect place to add other
potentially auto-generated PCI controller attributes that
On 07/17/2015 02:43 PM, Laine Stump wrote:
This patch provides qemu support for the contents of model in
controller for the two existing PCI controller types that need it
(i.e. the two controller types that are backed by a device that must
be specified on the qemu commandline):
1)
On 07/17/2015 02:43 PM, Laine Stump wrote:
There are some configuration options to some types of pci
controllers that are currently automatically derived from other parts
of the controller's configuration. For example, a pci-bridge
controller has an option that is called chassis_nr in qemu;
On 07/17/2015 02:43 PM, Laine Stump wrote:
The one oddity of all this is that if the controller configuration
is changed (for example to change the index or the pci address
where the controller is plugged in), the items in target will
*not* be re-generated, which might lead to conflict. I
On Mon, Jul 20, 2015 at 18:37:25 +0200, Andrea Bolognani wrote:
Not all users of this API will need the size of the returned
bitmap; those who do can simply call virBitmapSize() themselves.
---
src/nodeinfo.c | 12 +---
src/nodeinfo.h | 2 +-
2 files changed, 6 insertions(+), 8
On Mon, Jul 20, 2015 at 18:37:28 +0200, Andrea Bolognani wrote:
No need to look up the online status of each CPU separately when we
can get all the information in one go.
---
src/nodeinfo.c | 16 +++-
1 file changed, 7 insertions(+), 9 deletions(-)
diff --git a/src/nodeinfo.c
https://bugzilla.redhat.com/show_bug.cgi?id=1245476
We won't return the errno after commit 0d7f45ae, and
the more clearly error will be set in the code in vircgroup*.
Also We will always report error Operation not permitted,
because the return is -1.
Signed-off-by: Luyao Huang lhu...@redhat.com
On Tue, Jul 21, 2015 at 04:36:45PM +0100, Daniel P. Berrange wrote:
On Tue, Jul 21, 2015 at 11:34:08AM -0400, Laine Stump wrote:
On 07/21/2015 09:41 AM, Daniel P. Berrange wrote:
On Tue, Jul 21, 2015 at 03:35:50PM +0200, Martin Kletzander wrote:
On Tue, Jul 21, 2015 at 01:50:22PM +0100,
On Mon, Jul 20, 2015 at 18:37:30 +0200, Andrea Bolognani wrote:
Move the calls to the respective functions from virNodeParseNode(),
which is executed once for every NUMA node, to
linuxNodeInfoCPUPopulate(), which is executed just once per host.
---
src/nodeinfo.c | 53
On Wed, 2015-07-22 at 10:34 +0200, Peter Krempa wrote:
@@ -432,6 +432,9 @@ virNodeParseNode(const char *sysfs_prefix,
present_cpumap = nodeGetPresentCPUBitmap(sysfs_prefix);
if (!present_cpumap)
goto cleanup;
+online_cpus_map =
On Mon, Jul 20, 2015 at 18:37:20 +0200, Andrea Bolognani wrote:
This should take care of Peter's remarks, except the ones
that I've addressed separately.
This series is pushed now.
Peter
signature.asc
Description: Digital signature
--
libvir-list mailing list
libvir-list@redhat.com
This reverts commit 7b401c3bdacdf8367a0070e625d73eafb802045d.
Until libvirt is able to differentiate whether heads='1' is just a
leftover from previous libvirt or whether that's added by user on
purpose and also whether the domain was started with the support for
qxl's max_outputs, we cannot
On Wed, Jul 22, 2015 at 03:35:14PM +0800, Luyao Huang wrote:
https://bugzilla.redhat.com/show_bug.cgi?id=1245476
We won't return the errno after commit 0d7f45ae, and
the more clearly error will be set in the code in vircgroup*.
Also We will always report error Operation not permitted,
because
On Tue, Jun 16, 2015 at 06:03:39PM +0200, Martin Kletzander wrote:
So now that we have the Admin API backend merged in, the code is
prepared to have new APIs added in. There are many things to be
added, but we should start out slowly with the most desired ones.
I'll try to outline what I have
On 07/22/2015 05:06 PM, Martin Kletzander wrote:
On Wed, Jul 22, 2015 at 03:35:14PM +0800, Luyao Huang wrote:
https://bugzilla.redhat.com/show_bug.cgi?id=1245476
We won't return the errno after commit 0d7f45ae, and
the more clearly error will be set in the code in vircgroup*.
Also We will
On Wed, 2015-07-22 at 10:44 +0200, Peter Krempa wrote:
-present_cpumap = nodeGetPresentCPUBitmap(sysfs_prefix);
-if (!present_cpumap)
-goto cleanup;
-online_cpus_map = nodeGetOnlineCPUBitmap(sysfs_prefix);
-if (!online_cpus_map)
-goto cleanup;
-
-
Hey,
On Fri, Jul 17, 2015 at 09:01:46AM +0200, Christophe Fergeau wrote:
On Thu, Jul 09, 2015 at 10:13:16AM +0200, Christophe Fergeau wrote:
Hey,
This patch series makes tests/test-gconfig valgrind-clean, and refactors two
setters in GVirConfigDomainVideo to make them use the helpers
On Wed, Jul 22, 2015 at 10:14:27AM +0100, Daniel P. Berrange wrote:
I'm not sure what you are suggesting by features here, but I'd prefer
if we didn't introduce a chunk of XML which would contain an ever growing
set of hacks. It seems sufficient for us to just record the libvirt
version number
On Wed, Jul 22, 2015 at 11:02:11AM +0100, Daniel P. Berrange wrote:
On Tue, Jun 16, 2015 at 06:03:39PM +0200, Martin Kletzander wrote:
So now that we have the Admin API backend merged in, the code is
prepared to have new APIs added in. There are many things to be
added, but we should start out
On Wed, Jul 22, 2015 at 09:59:00AM +0200, Martin Kletzander wrote:
On Tue, Jul 21, 2015 at 04:36:45PM +0100, Daniel P. Berrange wrote:
On Tue, Jul 21, 2015 at 11:34:08AM -0400, Laine Stump wrote:
On 07/21/2015 09:41 AM, Daniel P. Berrange wrote:
On Tue, Jul 21, 2015 at 03:35:50PM +0200,
On Wed, Jul 22, 2015 at 10:05:48AM +0200, Martin Kletzander wrote:
This reverts commit 7b401c3bdacdf8367a0070e625d73eafb802045d.
Until libvirt is able to differentiate whether heads='1' is just a
leftover from previous libvirt or whether that's added by user on
purpose and also whether the
On Wed, Jul 22, 2015 at 10:12:02AM +0100, Daniel P. Berrange wrote:
On Wed, Jul 22, 2015 at 10:05:48AM +0200, Martin Kletzander wrote:
This reverts commit 7b401c3bdacdf8367a0070e625d73eafb802045d.
Until libvirt is able to differentiate whether heads='1' is just a
leftover from previous libvirt
On Wed, Jul 22, 2015 at 11:41 AM, Christophe Fergeau
cferg...@redhat.com wrote:
Hey,
On Fri, Jul 17, 2015 at 09:01:46AM +0200, Christophe Fergeau wrote:
On Thu, Jul 09, 2015 at 10:13:16AM +0200, Christophe Fergeau wrote:
Hey,
This patch series makes tests/test-gconfig valgrind-clean, and
On Wed, Jul 22, 2015 at 01:27:45PM +0100, Zeeshan Ali (Khattak) wrote:
On Wed, Jul 22, 2015 at 11:41 AM, Christophe Fergeau
cferg...@redhat.com wrote:
Hey,
On Fri, Jul 17, 2015 at 09:01:46AM +0200, Christophe Fergeau wrote:
On Thu, Jul 09, 2015 at 10:13:16AM +0200, Christophe Fergeau
Based on the distro target policy we have the following
min versions in various distros
libvirt glib2gobject-introspection
RHEL 7.0: 1.1.12.36.3 1.36.0
Fedora 21: 1.2.92.42.1 1.42.0
Ubuntu 14.10: 1.2.82.42.0 1.41.0
Ubuntu LTS 14.04:
On Wed, Jul 22, 2015 at 2:02 PM, Daniel P. Berrange berra...@redhat.com wrote:
Give users an indication of what distro platforms the project
intends to be buildable on. This policy will be used to decide
when it is appropriate to increase the minimum required versions
of external dependancies.
On Wed, Jul 22, 2015 at 02:51:44PM +0100, Daniel P. Berrange wrote:
Based on the distro target policy we have the following
min versions in various distros
libvirt glib2gobject-introspection
RHEL 7.0: 1.1.12.36.3 1.36.0
Fedora 21: 1.2.9
On Mon, Jul 20, 2015 at 18:37:26 +0200, Andrea Bolognani wrote:
The new name makes it clear that the returned bitmap contains the
information about which CPUs are online, not eg. which CPUs are
present.
No behavioral change.
---
src/libvirt_private.syms | 2 +-
src/nodeinfo.c |
On Mon, Jul 20, 2015 at 18:37:27 +0200, Andrea Bolognani wrote:
Swap out all instances of cpu_set_t and replace them with virBitmap,
which some of the code was already using anyway.
The changes are pretty mechanical, with one notable exception: an
assumption has been added on the max value
On Mon, Jul 20, 2015 at 18:37:29 +0200, Andrea Bolognani wrote:
Keep track of what CPUs belong to the current node while walking
through the sysfs node entry, so we don't need to do it a second
time immediately afterwards.
This also allows us to loop through all CPUs that are part of a
node
On Wed, Jul 22, 2015 at 01:40:25PM +0200, Paolo Bonzini wrote:
On 22/07/2015 12:19, Michael S. Tsirkin wrote:
SCSI passthrough was no longer supported in virtio 1.0, so this patch
fail the get_features() when both 1.0 and scsi is set. And also only
advertise VIRTIO_BLK_F_SCSI for
On Wed, Jul 22, 2015 at 01:43:12PM +0200, Boris Fiuczynski wrote:
I ran into a problem that was caused by a missing leading slash (/) in the
value of the file attribute of a disks source element.
Defining the domain worked without a problem.
That's because 'virsh define' does not turn on
On 22/07/2015 13:46, Daniel P. Berrange wrote:
IIUC, the SCSI passthrough feature for virtio-blk is enabled by
setting the 'scsi=on' property on the virtio-blk device, which is
exposed by libvirt with XML:
disk type='block' device='lun'
driver name='qemu' type='raw'/
The program exits right after this, so it's no big deal, but this gives
us a clean valgrind --leak-check=full output.
---
examples/conn-test.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/examples/conn-test.c b/examples/conn-test.c
index adc6434..ac5880a 100644
---
Give users an indication of what distro platforms the project
intends to be buildable on. This policy will be used to decide
when it is appropriate to increase the minimum required versions
of external dependancies.
Signed-off-by: Daniel P. Berrange berra...@redhat.com
---
README | 65
I ran into a problem that was caused by a missing leading slash (/) in
the value of the file attribute of a disks source element.
Defining the domain worked without a problem.
Editing the domain and trying to save it resulted in a very generic
error message:
error: XML document failed to
On Wed, Jul 22, 2015 at 02:56:53PM +0200, Christophe Fergeau wrote:
The program exits right after this, so it's no big deal, but this gives
us a clean valgrind --leak-check=full output.
Ah, messed up my push of the 4 patches which were ACK'ed earlier, and
pushed that one too :(
Christophe
On 07/17/2015 02:43 PM, Laine Stump wrote:
This is backed by the qemu device ioh3420.
chassis and port from the model subelement are used to store/set the
respective qemu device options for the ioh3420. Currently, chassis is
set to be the index of the controller, and port is set to
(slot
On 07/17/2015 02:43 PM, Laine Stump wrote:
This new subelement is used in PCI controllers: the toplevel
*attribute* model of a controller denotes what kind of PCI
controller is being described, e.g. a dmi-to-pci-bridge,
pci-bridge, or pci-root. But in the future there will be different
On 07/22/2015 04:25 PM, John Ferlan wrote:
On 07/17/2015 02:43 PM, Laine Stump wrote:
The one oddity of all this is that if the controller configuration
is changed (for example to change the index or the pci address
where the controller is plugged in), the items in target will
*not* be
On 07/17/2015 02:43 PM, Laine Stump wrote:
This controller can be connected (at domain startup time only - not
hotpluggable) only to a port on the pcie root complex (pcie-root in
libvirt config), hence the new connect type
VIR_PCI_CONNECT_TYPE_PCIE_ROOT. It provides a hotpluggable port that
On Wed, Jul 22, 2015 at 02:53:31PM -0500, Clark Laughlin wrote:
I am running Openstack Tempest on an arm64 platform and am seeing some
test failures related to attaching volumes to an instance. This is an
example of the disk XML generated by one of the tests:
disk type=block
On 07/17/2015 02:43 PM, Laine Stump wrote:
This is a PCIE root port. It connects only to a port of the
integrated pcie.0 bus of a Q35 machine (can't be hotplugged), and
provides a single PCIe port that can have PCI or PCIe devices
hotplugged into it.
This device will be used to implement
Hi everyone,
commit cc3d52e[1] has apparently broken 'make dist' for at least some
platforms: Fedora 20 is fine[2], but both Fedora 21 and rawhide[3][4]
are currently failing. My laptop is running Fedora 22 and can make
dist just fine, which is of course very confusing.
The issue is caused by
v1 here:
http://www.redhat.com/archives/libvir-list/2015-June/msg01104.html
Some followups into July resulted in the request to move the Hostdev
and Disk default (or _NONE) address creation/assignment into domain/
device post processing rather than during XML parsing.
Changes in v2 are numerous,
Since the only way virDomainHostdevAssignAddress can be called is from
within virDomainHostdevDefParseXML when hostdev-source.subsys.type is
VIR_DOMAIN_HOSTDEV_SUBSYS_TYPE_SCSI, thus there's no need for redundancy.
Signed-off-by: John Ferlan jfer...@redhat.com
---
src/conf/domain_conf.c | 3 ---
Add the xmlopt parameter that was saved during virDomainDefPostParse
to the parameters. A future patch will use it.
Signed-off-by: John Ferlan jfer...@redhat.com
---
src/conf/domain_conf.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/src/conf/domain_conf.c
Modify virDomainDriveAddressIsUsedBy{Disk|Hostdev} and
virDomainSCSIDriveAddressIsUsed to take 'bus' and 'target'
parameters. Will be used by future patches for more complete
address conflict checks
Signed-off-by: John Ferlan jfer...@redhat.com
---
src/conf/domain_conf.c | 28
Remove unused xmlopt param
Signed-off-by: John Ferlan jfer...@redhat.com
---
src/conf/domain_conf.c | 11 +--
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git a/src/conf/domain_conf.c b/src/conf/domain_conf.c
index eabba68..44ce71b 100644
--- a/src/conf/domain_conf.c
+++
Rather than calling virDomainDiskDefAssignAddress during the parsing of
the XML, moving the setting of disk addresses into the domain/device post
processing.
Commit id '37588b25' which introduced VIR_DOMAIN_DEF_PARSE_DISK_SOURCE
in order to avoid generating the address which wasn't required will
Move the functions above the post processing for upcoming patch
Signed-off-by: John Ferlan jfer...@redhat.com
---
src/conf/domain_conf.c | 284 +
1 file changed, 145 insertions(+), 139 deletions(-)
diff --git a/src/conf/domain_conf.c
https://bugzilla.redhat.com/show_bug.cgi?id=1210587 (partial)
If a SCSI subsystem hostdev element address is provided, we need to
make sure the address provided doesn't conflict with an existing or
libvirt generated address for a SCSI disk element.
This will fix the issue where the domain XML
If virDomainControllerSCSINextUnit failed to find a slot on the current
VIR_DOMAIN_CONTROLLER_TYPE_SCSI controller(s), try to add a new controller;
otherwise, there may be multiple unit=0 entries for the same next
controller.
Signed-off-by: John Ferlan jfer...@redhat.com
---
Create local controller/bus variables to be used by a future patch
Signed-off-by: John Ferlan jfer...@redhat.com
---
src/conf/domain_conf.c | 24 +++-
1 file changed, 15 insertions(+), 9 deletions(-)
diff --git a/src/conf/domain_conf.c b/src/conf/domain_conf.c
index
On Wed, Jul 22, 2015 at 01:53:14PM +0200, Paolo Bonzini wrote:
On 22/07/2015 13:46, Daniel P. Berrange wrote:
IIUC, the SCSI passthrough feature for virtio-blk is enabled by
setting the 'scsi=on' property on the virtio-blk device, which is
exposed by libvirt with XML:
disk
Rather than calling virDomainHostdevAssignAddress during the parsing
of the XML, move the setting of a default hostdev address to domain/
device post processing.
Since the parse code no longer generates an address, we can remove
the virDomainDefMaybeAddHostdevSCSIcontroller since the call to
https://bugzilla.redhat.com/show_bug.cgi?id=1210587 (completed)
When generating the default drive address for a SCSI disk device,
check the generated address to ensure it doesn't conflict with a SCSI
hostdev address. The disk address generation algorithm uses the
target dev name in order to
Give users an indication of what distro platforms the project
intends to be buildable on. This policy will be used to decide
when it is appropriate to increase the minimum required versions
of external dependancies.
Signed-off-by: Daniel P. Berrange berra...@redhat.com
---
README | 67
On Wed, Jul 22, 2015 at 02:54:17PM +0100, Zeeshan Ali (Khattak) wrote:
On Wed, Jul 22, 2015 at 2:02 PM, Daniel P. Berrange berra...@redhat.com
wrote:
Give users an indication of what distro platforms the project
intends to be buildable on. This policy will be used to decide
when it is
This sets out a policy for deciding when it is reasonable to
increase the min required versions of external deps, and then
updates current min versions accordingly.
The aim is to ensure libvirt-glib is easily buildable on latest
enterprise and community distros, to maximise the pool of
possible
Based on the distro target policy we have the following
min versions in various distros
libvirt glib2gobject-introspection
RHEL 7.0: 1.1.12.36.3 1.36.0
Fedora 21: 1.2.92.42.1 1.42.0
Ubuntu 14.10: 1.2.82.42.0 1.41.0
Ubuntu LTS 14.04:
On Tue, Jul 21, 2015 at 4:09 PM, Daniel P. Berrange berra...@redhat.com wrote:
On Tue, Jul 21, 2015 at 03:56:54PM +0100, Zeeshan Ali (Khattak) wrote:
On Tue, Jul 21, 2015 at 3:20 PM, Daniel P. Berrange berra...@redhat.com
wrote:
Previously the use of virDomainOpenGraphicsFD API from libvirt
85 matches
Mail list logo
