On Mon, Jun 23, 2014 at 04:08:42PM +0200, Martin Kletzander wrote:
Signed-off-by: Martin Kletzander
---
Notes:
To be honest, I have no idea why this fails for me in one situation,
but it prevents the following error during compilation:
/usr/lib/gcc/x86_64-pc-linux-gnu/4.9.0/../../../
On Thu, 2014-06-26 at 07:35 +0200, Martin Kletzander wrote:
> On Thu, Jun 26, 2014 at 01:50:22AM +, chen.fan.f...@cn.fujitsu.com wrote:
> >On Wed, 2014-06-04 at 16:56 +0200, Martin Kletzander wrote:
> >> Currently we are only able to bind the whole domain to some host nodes
> >> using the /dom
On Thu, Jun 26, 2014 at 01:50:22AM +, chen.fan.f...@cn.fujitsu.com wrote:
On Wed, 2014-06-04 at 16:56 +0200, Martin Kletzander wrote:
Currently we are only able to bind the whole domain to some host nodes
using the /domain/numatune/memory element. Numerous requests were
made to support host
On 06/25/2014 10:55 AM, Peter Krempa wrote:
> When creating a new disk mirror the new struct is stored in a separate
> variable until everything went well. The removed hunk would actually
> remove existing mirror information for example when the api would be run
> if a mirror still exists.
> ---
>
As we are doing with the enum structures, a cleanup in
"src/nwfilter/" directory was done now. All the enums that were
defined in the header files were converted to typedefs in this
directory. This patch includes all the adjustments to remove
conflicts when you do this kind of change. "Enum-to-type
On 06/25/2014 10:55 AM, Peter Krempa wrote:
> There's a lot of places where we skip doing actions based on the
> locality of given storage type. The usual pattern is to skip it if:
>
> virStorageSourceGetActualType(src) == VIR_STORAGE_TYPE_NETWORK
>
> Add a simple helper to simplify the pattern t
On Wed, Jun 25, 2014 at 07:36:41PM -0600, Eric Blake wrote:
> On 06/25/2014 02:46 PM, Eric Blake wrote:
> > Nehal discovered by accident that our libvirt-api.xml file is broken,
> > which in turn leads to broken python bindings.
> >
>
> > fix the root cause. It's not my area of expertise, so I'd
On 06/25/2014 10:54 AM, Peter Krempa wrote:
> Add helper APIs to manage individual image files rather than disks. To
> simplify the addition some parts of the code were refactored in this
> patch.
> ---
> src/libvirt_private.syms | 2 ++
> src/locking/domain_lock.c | 65
> ++
As stated yesterday, we just entered freeze for libvirt-1.2.6,
I have pushed a first release candidate tarball and signed rpms
at the usual place:
ftp://libvirt.org/libvirt/
I gave it a try and with my limited testing it looks okay, but
please have a look and test. The goal is to make the r
On 06/25/2014 10:54 AM, Peter Krempa wrote:
> Only the top level gets writes, so the rest of the backing chain
> requires only read-only access.
> ---
> src/qemu/qemu_cgroup.c | 26 --
> 1 file changed, 20 insertions(+), 6 deletions(-)
>
ACK
--
Eric Blake eblake redha
On 06/25/2014 10:54 AM, Peter Krempa wrote:
> Add functions that will allow to set all the required cgroup stuff on
> individual images taking a virStorageSourcePtr. Also convert functions
> designed to setup whole backing chain to take advantage of the chagne.
s/chagne/change/
> ---
> src/qemu/
On Wed, 2014-06-04 at 16:56 +0200, Martin Kletzander wrote:
> Currently we are only able to bind the whole domain to some host nodes
> using the /domain/numatune/memory element. Numerous requests were
> made to support host<->guest numa node bindings, so this series tries
> to pinch an idea on ho
On 06/25/2014 02:46 PM, Eric Blake wrote:
> Nehal discovered by accident that our libvirt-api.xml file is broken,
> which in turn leads to broken python bindings.
>
> fix the root cause. It's not my area of expertise, so I'd appreciate a
> hand in finding the problem spot, although I'm still try
On 06/25/2014 10:54 AM, Peter Krempa wrote:
> Cgroups code uses VIR_CGROUP_DEVICE_* flags to specify the mode but in
> the end it needs to be converted to a string. Add a helper to do it and
> use it in the cgroup code before introducing it into the rest of the
> code.
> ---
> src/libvirt_private.
On Wed, 2014-06-25 at 12:43 -0600, Eric Blake wrote:
> On 06/25/2014 02:45 AM, Chen Fan wrote:
>
> Long subject line. Please try to fit subjects in 60 characters or less
> (look at 'git shortlog -30' for a good example).
>
> > Signed-off-by: Chen Fan
> > ---
> > src/conf/domain_conf.c | 2 +-
On 06/25/2014 06:09 PM, Jim Fehlig wrote:
> libxl does not support save, restore, or migrate on all architectures,
> notably ARM. Detect whether libxl supports these operations using
> LIBXL_HAVE_NO_SUSPEND_RESUME. If not supported, drop advertisement of
> .
>
> Found by Ian Campbell while impro
Eric Blake wrote:
> On 06/25/2014 12:13 PM, Jim Fehlig wrote:
>
>> libxl does not support save, restore, or migrate on all architectures,
>> notably ARM. Detect whether libxl supports these operations using
>> LIBXL_HAVE_NO_SUSPEND_RESUME. If not supported, drop advertisement of
>> .
>>
>> Fou
libxl does not support save, restore, or migrate on all architectures,
notably ARM. Detect whether libxl supports these operations using
LIBXL_HAVE_NO_SUSPEND_RESUME. If not supported, drop advertisement of
.
Found by Ian Campbell while improving Xen's OSSTEST infrastructure
http://lists.xen.or
On 06/25/2014 03:09 PM, Eric Blake wrote:
> We publish libvirt-api.xml for others to use, and in fact, the
> libvirt-python bindings use it to generate enum values. However,
> we had an off-by-one bug that any enum that relied on C's rules
> for implicit initialization of the first enum member to
On 06/25/2014 10:54 AM, Peter Krempa wrote:
> Now that we have pointers to store disk source information and thus can
> easily exchange the structs behind we need a function to copy all the
> data.
> ---
> src/libvirt_private.syms | 1 +
> src/util/virstoragefile.c | 143
>
On 06/25/2014 10:54 AM, Peter Krempa wrote:
> They will be reused to transfer disk labels from snapshotted disks to
> the new disk definitions.
> ---
> src/libvirt_private.syms | 1 +
> src/util/virstoragefile.c | 45 ++---
> src/util/virstoragefile.h | 3
On Wed, Jun 25, 2014 at 14:34:42 +0200, Jiri Denemark wrote:
> When CPU virConnectCompareCPU returns VIR_CPU_COMPARE_INCOMPATIBLE, the
> caller has no clue why the CPU is considered incompatible with host CPU.
> And in some cases, it would be nice to be able to get such info in a
> client rather th
These APIs return a list of dhcp leases for all network interfaces connected
to the given virtual network or limited output just for one interface if mac
is specified.
Example Output:
[{'iface': 'virbr3', 'ipaddr': '192.168.150.181', 'hostname': 'ubuntu14',
'expirytime': 1403737495L, 'prefix':
On Wed, Jun 25, 2014 at 14:21:18 +0200, Peter Krempa wrote:
> On 06/25/14 14:15, Jiri Denemark wrote:
> > Signed-off-by: Jiri Denemark
> > ---
> > src/cpu/cpu_generic.c | 19 ---
> > 1 file changed, 8 insertions(+), 11 deletions(-)
> >
>
> ACK,
Thanks, pushed.
Jirka
--
libvir
On Wed, Jun 25, 2014 at 14:25:27 +0200, Peter Krempa wrote:
> On 06/25/14 14:14, Jiri Denemark wrote:
> > Let's just open the file right away and deal with errors. Moreover,
> > there's no reason to forbid logging to, e.g., a pipe.
> >
> > Signed-off-by: Jiri Denemark
> > ---
> > tools/virsh.c |
On Wed, Jun 25, 2014 at 14:19:19 +0200, Peter Krempa wrote:
> On 06/25/14 14:15, Jiri Denemark wrote:
> > Only types and macros are documented in libvirt.h, APIs are documented
> > in the *.c file they are implemented in.
> >
> > Signed-off-by: Jiri Denemark
> > ---
> > include/libvirt/libvirt.h
On 06/25/2014 10:54 AM, Peter Krempa wrote:
> In the future we might need to track state of individual images. Move
> the readonly and shared flags to the virStorageSource struct so that we
> can keep them in a per-image basis.
> ---
My immediate reaction is that all backing files are generally re
On 06/25/2014 10:54 AM, Peter Krempa wrote:
> The function headers contain type on the same line as the name. When
> combined with usage of ATTRIBUTE_UNUSED, the function headers were very
> long. Shorten them by breaking the line after the type.
> ---
> src/security/security_nop.c | 147
> ++
On 06/25/2014 10:54 AM, Peter Krempa wrote:
> Some of the functions in the storage driver had their headers formatted
> incorrectly.
> ---
> src/security/security_driver.h | 6 +++---
> src/security/security_manager.h | 9 -
> src/security/security_stack.c | 4 ++--
> 3 files changed, 9
On 06/25/2014 10:54 AM, Peter Krempa wrote:
> virSecurityManagerSetDiskLabel and virSecurityManagerRestoreDiskLabel
> don't have complementary semantics. Document the semantics to avoid
> possible problems.
> ---
> src/security/security_manager.c | 22 ++
> 1 file changed, 22 i
On 06/25/2014 10:54 AM, Peter Krempa wrote:
> ---
> src/security/security_manager.c | 248
> +---
> 1 file changed, 157 insertions(+), 91 deletions(-)
>
ACK
--
Eric Blake eblake redhat com+1-919-301-3266
Libvirt virtualization library http://libvirt.o
On 06/25/2014 10:54 AM, Peter Krempa wrote:
> ---
> src/security/security_manager.c | 21 +++--
> 1 file changed, 11 insertions(+), 10 deletions(-)
>
ACK.
--
Eric Blake eblake redhat com+1-919-301-3266
Libvirt virtualization library http://libvirt.org
signature.asc
Des
We publish libvirt-api.xml for others to use, and in fact, the
libvirt-python bindings use it to generate enum values. However,
we had an off-by-one bug that any enum that relied on C's rules
for implicit initialization of the first enum member to 0 got
listed in the xml as having a value of 1 (an
Nehal discovered by accident that our libvirt-api.xml file is broken,
which in turn leads to broken python bindings.
Right now, if you look at docs/libvirt-api.xml, you'll find:
but if you look at the libvirt.h.in file, you see:
typedef enum {
VIR_IP_ADDR_TYPE_IPV4,
VIR_IP_ADDR_TYP
On 06/25/2014 10:54 AM, Peter Krempa wrote:
> I'm going to add functions that will deal with individual image files
> rather than whole disks. Rename the security function to make room for
> the new one.
> ---
> src/libvirt_private.syms | 2 +-
> src/qemu/qemu_driver.c | 4 ++--
On Wed, 2014-06-25 at 13:10 -0600, Eric Blake wrote:
> On 06/25/2014 12:13 PM, Jim Fehlig wrote:
> > libxl does not support save, restore, or migrate on all architectures,
> > notably ARM. Detect whether libxl supports these operations using
> > LIBXL_HAVE_NO_SUSPEND_RESUME. If not supported, dro
On 06/25/2014 12:13 PM, Adam Litke wrote:
> On 25/06/14 10:27 -0600, Eric Blake wrote:
>> On 06/19/2014 07:59 AM, Peter Krempa wrote:
>>> Now that we are able to select images from the backing chain via indexed
>>> access we should also convert possible network sources to
>>> qemu-compatible string
On 06/25/2014 12:13 PM, Jim Fehlig wrote:
> libxl does not support save, restore, or migrate on all architectures,
> notably ARM. Detect whether libxl supports these operations using
> LIBXL_HAVE_NO_SUSPEND_RESUME. If not supported, drop advertisement of
> .
>
> Found by Ian Campbell while impro
On 06/25/2014 10:54 AM, Peter Krempa wrote:
> Rename them to comply with the naming policy.
> ---
> src/libvirt_private.syms | 2 +-
> src/qemu/qemu_domain.c| 2 +-
> src/qemu/qemu_driver.c| 2 +-
> src/util/virstoragefile.c | 6 +++---
> src/util/virstoragefile.h | 2 +-
> 5 files change
On 06/25/2014 06:34 AM, Jiri Denemark wrote:
> The new VIR_CONNECT_COMPARE_CPU_FAIL_INCOMPATIBLE flag for
> virConnectCompareCPU can be used to get an error
> (VIR_ERR_CPU_INCOMPATIBLE) describing the incompatibility instead of the
> usual VIR_CPU_COMPARE_INCOMPATIBLE return code.
>
> Signed-off-b
On 06/25/2014 06:41 AM, Jiri Denemark wrote:
> Signed-off-by: Jiri Denemark
> ---
>
> Notes:
> The corresponding patch [1] for QEMU is not usptream yet but nobody
> seems to be complaining about that model. And chances are the patch gets
> in before QEMU enters hard freeze for 2.1. So
On 06/25/2014 12:42 AM, Michal Privoznik wrote:
> On 24.06.2014 21:34, Eric Blake wrote:
>> On 06/24/2014 03:39 AM, Daniel P. Berrange wrote:
>>
We also have a subelement of in the
XML which is used for a similar thing although it doesn't support a
per-machine-type output, on
On 06/25/2014 02:45 AM, Chen Fan wrote:
Long subject line. Please try to fit subjects in 60 characters or less
(look at 'git shortlog -30' for a good example).
> Signed-off-by: Chen Fan
> ---
> src/conf/domain_conf.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
ACK and pushed, afte
Ian Campbell wrote:
> On Wed, 2014-06-25 at 09:25 -0600, Jim Fehlig wrote:
>
>> With the fixup, does this work for you? Is omitted
>> from the capabilities?
>>
>
> Yes, it is omitted. On ARM:
>
> # virsh capabilities
>
>
>
>
>
On 25/06/14 10:34 -0600, Eric Blake wrote:
On 06/19/2014 07:59 AM, Peter Krempa wrote:
Now that we are able to select images from the backing chain via indexed
access we should also convert possible network sources to
qemu-compatible strings before passing them to qemu.
---
src/qemu/qemu_driver
On 25/06/14 10:27 -0600, Eric Blake wrote:
On 06/19/2014 07:59 AM, Peter Krempa wrote:
Now that we are able to select images from the backing chain via indexed
access we should also convert possible network sources to
qemu-compatible strings before passing them to qemu.
Eventually, we'll want
libxl does not support save, restore, or migrate on all architectures,
notably ARM. Detect whether libxl supports these operations using
LIBXL_HAVE_NO_SUSPEND_RESUME. If not supported, drop advertisement of
.
Found by Ian Campbell while improving Xen's OSSTEST infrastructure
http://lists.xen.or
Ján Tomko (2):
Add test for virtio serial port assignment
Implement virtio serial address allocation
src/conf/domain_addr.c | 426 +
src/conf/domain_addr.h | 49 +++
src/conf/domain_conf.c
Add a test to demonstrate the effect of the next patch.
---
.../qemuxml2argv-channel-virtio-autoassign.args| 20 +
.../qemuxml2argv-channel-virtio-autoassign.xml | 50 ++
tests/qemuxml2argvtest.c | 2 +
3 files changed, 72 insertions(+
Over-engineered to allow non-contiguous indexes.
Free ports of a controller are stored in a virBitmap.
These bitmaps are stored in a hash table, indexed by
the controller index formatted as a string.
Buses are ignored for now, QEMU doesn't seem
to support anything else than .0
For virtconsoles, a
On 06/25/2014 11:08 AM, Scott Sullivan wrote:
> I am trying to build v1.2.5-maint, however I have one test failing
> causing the build to fail:
>
>
> TEST: securityselinuxlabeltest
> !!!. 4 FAIL
>
Can you rerun this to give more details on the failure
On 06/25/2014 10:59 AM, Peter Krempa wrote:
> On 06/25/14 18:53, Eric Blake wrote:
>> Thanks to Dan's recent work in libvirt.git, it is much easier to
>> develop against uninstalled libvirt. Mention how.
>>
>> * README: More details.
>>
>> Signed-off-by: Eric Blake
>> ---
>> README | 15
I am trying to build v1.2.5-maint, however I have one test failing
causing the build to fail:
TEST: securityselinuxlabeltest
!!!. 4 FAIL
PASS: virsh-undefine
===
1 of 112 tests failed
Please report to libvir-list@
On 25.6.2014 08:45, Jincheng Miao wrote:
> Currently, only LXC has hostdev mode 'capabilities' support,
> so the other drivers should forbid to define it in XML.
> The hostdev mode check is added to devicesPostParseCallback()
> for each hypervisor driver.
>
> But there are some drivers lack functi
On 06/25/14 18:53, Eric Blake wrote:
> Thanks to Dan's recent work in libvirt.git, it is much easier to
> develop against uninstalled libvirt. Mention how.
>
> * README: More details.
>
> Signed-off-by: Eric Blake
> ---
> README | 15 +++
> 1 file changed, 15 insertions(+)
>
ACK,
Use the source struct and the corresponding function so that we can
avoid using the path separately. Now that
qemuDomainPrepareDiskChainElementPath isn't use anywhere, we can safely
remove it.
Additionally, the removal fixes a misaligned comment as the removed
function was added under a comment fo
Refactor the existing code to allow re-using it for the per-image label
restore too.
---
src/security/security_apparmor.c | 18 ++
1 file changed, 14 insertions(+), 4 deletions(-)
diff --git a/src/security/security_apparmor.c b/src/security/security_apparmor.c
index b4cbc61..72d1e
Instead of just returning the parent path, return the complete parent
source structure.
---
src/qemu/qemu_driver.c| 16 -
src/util/virstoragefile.c | 17 --
src/util/virstoragefile.h | 2 +-
tests/virstoragetest.c| 86 ++-
4 file
Refactor the code and reuse it to implement the functionality.
---
src/security/security_apparmor.c | 38 +++---
1 file changed, 23 insertions(+), 15 deletions(-)
diff --git a/src/security/security_apparmor.c b/src/security/security_apparmor.c
index 72d1e16..fb41c5
Add security driver functions to label separate storage images using the
virStorageSource definition. This will help to avoid the need to do ugly
changes to the disk struct and use the source directly.
---
src/libvirt_private.syms| 2 ++
src/security/security_driver.h | 10
src/
The function headers contain type on the same line as the name. When
combined with usage of ATTRIBUTE_UNUSED, the function headers were very
long. Shorten them by breaking the line after the type.
---
src/security/security_nop.c | 147 ++--
1 file changed, 8
Add helper APIs to manage individual image files rather than disks. To
simplify the addition some parts of the code were refactored in this
patch.
---
src/libvirt_private.syms | 2 ++
src/locking/domain_lock.c | 65 ++-
src/locking/domain_lock.h | 8 +
They will be reused to transfer disk labels from snapshotted disks to
the new disk definitions.
---
src/libvirt_private.syms | 1 +
src/util/virstoragefile.c | 45 ++---
src/util/virstoragefile.h | 3 +++
3 files changed, 42 insertions(+), 7 deletions(-)
virSecurityManagerSetDiskLabel and virSecurityManagerRestoreDiskLabel
don't have complementary semantics. Document the semantics to avoid
possible problems.
---
src/security/security_manager.c | 22 ++
1 file changed, 22 insertions(+)
diff --git a/src/security/security_manager
In the future we might need to track state of individual images. Move
the readonly and shared flags to the virStorageSource struct so that we
can keep them in a per-image basis.
---
src/conf/domain_conf.c | 18 ++
src/conf/domain_conf.h | 2 --
src/libxl/libxl_co
When creating a new disk mirror the new struct is stored in a separate
variable until everything went well. The removed hunk would actually
remove existing mirror information for example when the api would be run
if a mirror still exists.
---
src/qemu/qemu_driver.c | 4
1 file changed, 4 dele
There's a lot of places where we skip doing actions based on the
locality of given storage type. The usual pattern is to skip it if:
virStorageSourceGetActualType(src) == VIR_STORAGE_TYPE_NETWORK
Add a simple helper to simplify the pattern to
virStorageSourceIsLocalStorage(src)
---
src/libvirt_p
Refactor the existing code to allow re-using it for the per-image label
restore too.
---
src/security/security_dac.c | 60 -
1 file changed, 32 insertions(+), 28 deletions(-)
diff --git a/src/security/security_dac.c b/src/security/security_dac.c
index 3
Add a few checks and avoid resolving relative links on networked
storage.
---
src/util/virstoragefile.c | 27 +++
1 file changed, 15 insertions(+), 12 deletions(-)
diff --git a/src/util/virstoragefile.c b/src/util/virstoragefile.c
index 965c3ea..e154f92 100644
--- a/src/ut
---
src/security/security_manager.c | 21 +++--
1 file changed, 11 insertions(+), 10 deletions(-)
diff --git a/src/security/security_manager.c b/src/security/security_manager.c
index d57bab9..84d90ac 100644
--- a/src/security/security_manager.c
+++ b/src/security/security_manager.
Refactor the existing code to allow re-using it for the per-image label
restore too.
---
src/security/security_selinux.c | 60 -
1 file changed, 35 insertions(+), 25 deletions(-)
diff --git a/src/security/security_selinux.c b/src/security/security_selinux.c
Only the top level gets writes, so the rest of the backing chain
requires only read-only access.
---
src/qemu/qemu_cgroup.c | 26 --
1 file changed, 20 insertions(+), 6 deletions(-)
diff --git a/src/qemu/qemu_cgroup.c b/src/qemu/qemu_cgroup.c
index 1deafb7..97229c4 100644
Some of the functions in the storage driver had their headers formatted
incorrectly.
---
src/security/security_driver.h | 6 +++---
src/security/security_manager.h | 9 -
src/security/security_stack.c | 4 ++--
3 files changed, 9 insertions(+), 10 deletions(-)
diff --git a/src/security
Refactor the code and reuse it to implement the functionality.
---
src/security/security_dac.c | 53 ++---
1 file changed, 26 insertions(+), 27 deletions(-)
diff --git a/src/security/security_dac.c b/src/security/security_dac.c
index 69b51c1..3ff7817 100644
In my quest to fix various issues with image chain handling I've set out to
fix labelling of the image files. While I'm not far enough yet, the series has
grown
rather large and contains a few fixes of other stuff.
I'm posting it incomplete to star review on the trivial parts.
Peter Krempa (26):
Add functions that will allow to set all the required cgroup stuff on
individual images taking a virStorageSourcePtr. Also convert functions
designed to setup whole backing chain to take advantage of the chagne.
---
src/qemu/qemu_cgroup.c | 104 -
sr
I'm going to add functions that will deal with individual image files
rather than whole disks. Rename the security function to make room for
the new one.
---
src/libvirt_private.syms | 2 +-
src/qemu/qemu_driver.c | 4 ++--
src/qemu/qemu_hotplug.c | 24
Now that we have pointers to store disk source information and thus can
easily exchange the structs behind we need a function to copy all the
data.
---
src/libvirt_private.syms | 1 +
src/util/virstoragefile.c | 143 ++
src/util/virstoragefile.h | 3
Rename them to comply with the naming policy.
---
src/libvirt_private.syms | 2 +-
src/qemu/qemu_domain.c| 2 +-
src/qemu/qemu_driver.c| 2 +-
src/util/virstoragefile.c | 6 +++---
src/util/virstoragefile.h | 2 +-
5 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/src/libvirt
---
src/security/security_manager.c | 248 +---
1 file changed, 157 insertions(+), 91 deletions(-)
diff --git a/src/security/security_manager.c b/src/security/security_manager.c
index 84d90ac..bb12e8e 100644
--- a/src/security/security_manager.c
+++ b/src/secur
Cgroups code uses VIR_CGROUP_DEVICE_* flags to specify the mode but in
the end it needs to be converted to a string. Add a helper to do it and
use it in the cgroup code before introducing it into the rest of the
code.
---
src/libvirt_private.syms | 1 +
src/util/vircgroup.c | 62 +
Refactor the code and reuse it to implement the functionality.
---
src/security/security_selinux.c | 92 -
1 file changed, 54 insertions(+), 38 deletions(-)
diff --git a/src/security/security_selinux.c b/src/security/security_selinux.c
index 7b534b2..97f91f
Thanks to Dan's recent work in libvirt.git, it is much easier to
develop against uninstalled libvirt. Mention how.
* README: More details.
Signed-off-by: Eric Blake
---
README | 15 +++
1 file changed, 15 insertions(+)
diff --git a/README b/README
index ad50828..df1de59 100644
---
On 06/25/2014 10:18 AM, Nehal J Wani wrote:
Long subject line, and a typo. Better is:
build: use correct int conversion in GetFreePages
then exposing the longer details in the commit body.
> Introduced by commit c8ba859bc78f5e3b0ed2590f4e8a7fa6c26ac08f
>
> On compiling libvirt-python against
On Wed, 2014-06-25 at 09:25 -0600, Jim Fehlig wrote:
> Ian Campbell wrote:
> > On Tue, 2014-06-24 at 21:18 -0600, Jim Fehlig wrote:
> >
> >
> >> Something like the attached patch (compile-tested only). You'll need an
> >> updated libvirt.git master to apply cleanly.
> >>
> >
> > Thanks. Bu
On 06/19/2014 07:59 AM, Peter Krempa wrote:
> Now that we are able to select images from the backing chain via indexed
> access we should also convert possible network sources to
> qemu-compatible strings before passing them to qemu.
> ---
> src/qemu/qemu_driver.c | 45
On 06/19/2014 07:59 AM, Peter Krempa wrote:
> Now that we are able to select images from the backing chain via indexed
> access we should also convert possible network sources to
> qemu-compatible strings before passing them to qemu.
Eventually, we'll want to use qemu's node-name functionality, al
Introduced by commit c8ba859bc78f5e3b0ed2590f4e8a7fa6c26ac08f
On compiling libvirt-python against libvirt 1.2.6, we get:
libvirt-override.c: In function ‘libvirt_virNodeGetFreePages’:
libvirt-override.c:7811:9: warning: pointer targets in passing argument 2 of
‘libvirt_intUnwrap’ differ in signe
On 06/19/2014 07:59 AM, Peter Krempa wrote:
> Introduce flag for the block rebase API to allow the rebase operation to
> leave the chain relatively addressed. Also adds a virsh switch to enable
> this behavior.
> ---
> include/libvirt/libvirt.h.in | 2 ++
> src/libvirt.c| 5 +
On 06/19/2014 07:59 AM, Peter Krempa wrote:
> To allow changing the name that is recorded in the top of the current
> image chain used in a block pull/rebase operation, we need to specify
> the backing name to qemu. This is done via the "backing-file" attribute
> to the block-stream commad.
s/comm
On 06/19/2014 07:59 AM, Peter Krempa wrote:
> Introduce flag for the block commit API to allow the commit operation to
> leave the chain relatively addressed. Also adds a virsh switch to enable
> this behavior.
> ---
> include/libvirt/libvirt.h.in | 4
> src/libvirt.c| 5 +
Ian Campbell wrote:
> On Tue, 2014-06-24 at 21:18 -0600, Jim Fehlig wrote:
>
>
>> Something like the attached patch (compile-tested only). You'll need an
>> updated libvirt.git master to apply cleanly.
>>
>
> Thanks. Building on ARM I get:
>
> libxl/libxl_driver.c:4346:1: error: 'libxlDoma
On 06/25/14 14:34, Jiri Denemark wrote:
> When CPU comparison APIs return VIR_CPU_COMPARE_INCOMPATIBLE, the caller
> has no clue why the CPU is considered incompatible with host CPU. And in
> some cases, it would be nice to be able to get such info in a client
> rather than having to look in logs.
Added in the section of LXC domains
configuration. This section can contain elements named after the
capabilities like:
, keep CAP_MKNOD capability
drop CAP_SYS_CHROOT capability
Users can restrict or give more capabilities than the default using
this mechanism.
---
docs/schemas/domaincom
Changes since the previous version are:
* add 'b *:* m' and 'c *:* m' to the device white list is CAP_MKNOD
is requested instead of setting 'a *:* rwm'.
* Add a policy='default|allow|deny' for the features/capabilities
element.
Cédric Bosdonnat (3):
lxc: allow to keep or drop capabil
---
docs/drvlxc.html.in | 47 +++
1 file changed, 47 insertions(+)
diff --git a/docs/drvlxc.html.in b/docs/drvlxc.html.in
index fc4bc20..403ce24 100644
--- a/docs/drvlxc.html.in
+++ b/docs/drvlxc.html.in
@@ -540,6 +540,53 @@ debootstrap, whatever) under
---
src/lxc/lxc_native.c | 25 ++
tests/lxcconf2xmldata/lxcconf2xml-blkiotune.xml| 2 ++
tests/lxcconf2xmldata/lxcconf2xml-cpusettune.xml | 2 ++
tests/lxcconf2xmldata/lxcconf2xml-cputune.xml | 2 ++
tests/lxcconf2xmldata/lxcconf2xml-
On 06/25/14 14:34, Jiri Denemark wrote:
> The new VIR_CONNECT_COMPARE_CPU_FAIL_INCOMPATIBLE flag for
> virConnectCompareCPU can be used to get an error
> (VIR_ERR_CPU_INCOMPATIBLE) describing the incompatibility instead of the
> usual VIR_CPU_COMPARE_INCOMPATIBLE return code.
>
> Signed-off-by: Ji
Signed-off-by: Jiri Denemark
---
Notes:
The corresponding patch [1] for QEMU is not usptream yet but nobody
seems to be complaining about that model. And chances are the patch gets
in before QEMU enters hard freeze for 2.1. So please review this patch
but I won't push it until the
On Tue, 2014-06-24 at 21:18 -0600, Jim Fehlig wrote:
> Something like the attached patch (compile-tested only). You'll need an
> updated libvirt.git master to apply cleanly.
Thanks. Building on ARM I get:
libxl/libxl_driver.c:4346:1: error: 'libxlDomainMigrateBegin3Params' defined
but not use
1 - 100 of 123 matches
Mail list logo
