From: Chen Hanxiao
Currently --maximum was possible if and only if
--config was specified.
This patch makes setvcpus --maximum imply --config.
Signed-off-by: Chen Hanxiao
---
tools/virsh-domain.c | 7 ---
tools/virsh.pod | 9 +
2 files changed, 9 insertions(+), 7 deletions
Dear list,
as you've noticed, libvirt changed the versioning strategy and slowly
other subprojects are adapting it too. I mean, the version number is
changed right after the release and not just before it. It makes sense
and therefore I'm letting you know that libvirt-php is adapting this
scheme t
On 05/26/2017 04:32 PM, Dawid Zamirski wrote:
> this function takes only resource argument.
> ---
> src/libvirt-php.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/src/libvirt-php.c b/src/libvirt-php.c
> index bfc9b7d..99d6397 100644
> --- a/src/libvirt-php.c
> +++ b/sr
In 48d9e6cdcc and friends we've allowed users to back guest
memory by a file inside the host. And in order to keep things
manageable the memory_backing_dir variable was introduced to
qemu.conf to specify the directory where the files are kept.
However, libvirt's policy is that directories are creat
---
libvirt-sandbox/libvirt-sandbox-builder-machine.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/libvirt-sandbox/libvirt-sandbox-builder-machine.c
b/libvirt-sandbox/libvirt-sandbox-builder-machine.c
index bdec490..7204f71 100644
--- a/libvirt-sandbox/libvirt-sandbox-builder-machine.c
+++
If one pastes from the output of virt-sansbox-image
$ virt-sandbox-image list
docker:/library/ubuntu?tag=17.04
docker:/library/debian?tag=latest
verbatim
$ virt-sandbox-image run -c qemu:///session docker:/library/debian?tag=latest
This fails like
/home//.local/share/libvirt/images/l
---
libvirt-sandbox/image/sources/docker.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libvirt-sandbox/image/sources/docker.py
b/libvirt-sandbox/image/sources/docker.py
index 43e9c32..aa5675e 100755
--- a/libvirt-sandbox/image/sources/docker.py
+++ b/libvirt-sandbox/image
So as planned I tagged the release candidate 1 in git and pushed signed
tarball and rpms to the usual place:
ftp://libvirt.org/libvirt/
Everything seems to work fine for me with RC1 on my limited testing
but as usual please give it some attention to find out issues and check
portability o
Em 26/05/2017 04:15, Martin Kletzander escreveu:
On Thu, May 25, 2017 at 07:54:13PM -0300, Claudio André wrote:
The workers available in Travis are really old. That said, I plan to
workaround your finding and propose a patch:
- to build and test libvirt using a more updated distro (using
`servi
Em 26/05/2017 04:12, Martin Kletzander escreveu:
Oh, so it's saved in your profile on the travis website. That makes
sense. I was just wondering where this environment variable gets
defined, that's it. And I didn't check the documentation because I
didn't like the fact that coveralls.io wanted
10 matches
Mail list logo