---
src/qemu/qemu_migration.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/src/qemu/qemu_migration.c b/src/qemu/qemu_migration.c
index 7aeea69..4d0e062 100644
--- a/src/qemu/qemu_migration.c
+++ b/src/qemu/qemu_migration.c
@@ -257,7 +257,7 @@
The 02/08/11, Nicolas Sebrecht wrote:
I'm stuck!
As told before, I have one working (in production) system and others
failing Gentoo systems (including the testing machine).
I've check the working system against the testing machine and looked for
differences. I did remove differences one
This patch introduces a internal RPC API virNetServerClose, which
is standalone with virNetServerFree. it closes all the socket fds,
and unlinks the unix socket paths, regardless of whether the socket
is still referenced or not.
This is to address regression bug:
On 08/03/2011 04:08 AM, Jiri Denemark wrote:
---
src/qemu/qemu_migration.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/src/qemu/qemu_migration.c b/src/qemu/qemu_migration.c
index 7aeea69..4d0e062 100644
--- a/src/qemu/qemu_migration.c
+++
On 08/03/2011 07:37 AM, Osier Yang wrote:
This patch introduces a internal RPC API virNetServerClose, which
is standalone with virNetServerFree. it closes all the socket fds,
and unlinks the unix socket paths, regardless of whether the socket
is still referenced or not.
This is to address
When to make use of any SASL authentication for TCP sockets by
setting auth_tls = sasl in libvirtd.conf on server side,The
client will hange because of the sasl session relocking other than
dropping it in virNetSASLSessionExtKeySize()
---
src/rpc/virnetsaslcontext.c |2 +-
1 files changed, 1
Hi All,
I've had user reports of libvirt limiting KVM core dumps. This isn't
quite true since libvirt just uses the default migration speed defined
in qemu's migration.c
/* Migration speed throttling */
static int64_t max_throttle = (32 20);
AFAIK, there's not much interest in changing the
On 08/03/2011 08:22 AM, Matthias Bolte wrote:
Detection based on gnutls_session doesn't work because GnuTLS 2.x.y
comes with a compat.h that defines gnutls_session to gnutls_session_t.
Instead detect this based on LIBGNUTLS_VERSION_MAJOR.
---
configure.ac | 22 +++---
1
Add a generator script to generate the structs and serialization
information for OpenWSMAN.
openwsman.h collects workarounds for problems in OpenWSMAN = 2.2.6.
There are also disabled sections that would use ws_serializer_free_mem
but can't because it's broken in OpenWSMAN = 2.2.6. Patches to fix
---
v2:
- move microsoft.com link to drvhyperv.html.in
docs/drivers.html.in |1 +
docs/drvhyperv.html.in | 112
docs/index.html.in |3 +
docs/sitemap.html.in |4 ++
src/README |3 +-
5 files changed, 122
Domain listing, basic information retrieval and domain life cycle
management is implemented. But currently the domian XML output
lacks the complete devices section.
The driver uses OpenWSMAN to directly communicate with an Hyper-V
server over its WS-Management interface exposed via Microsoft
Version 2 of the Hyper-V driver. See the individual patches for
the changes from version 1. Complete version 1 can be found here
https://www.redhat.com/archives/libvir-list/2011-July/msg00766.html
This series adds the basic driver and supports listing and retrieving
information about existing
---
v2:
- move libvirt.spec.in change to 1/5
cfg.mk |1 +
include/libvirt/virterror.h |1 +
po/POTFILES.in |1 +
src/Makefile.am | 29 +
src/driver.h |1 +
On 08/03/2011 08:37 AM, Jim Fehlig wrote:
http://lists.nongnu.org/archive/html/qemu-devel/2011-02/msg01156.html
I thought there were more discussions on the topic but can only find the
above thread ATM.
Do folks here have objections to increasing the migration speed prior to
core dump? If
---
v2:
- relax OpenWSMAN requirement to 2.2.3
- move libvirt.spec.in change from 2/5 here and fix OpenWSMAN package name
- qoute all PKG_CHECK_MODULES parameters
configure.ac| 38 ++
libvirt.spec.in |9 +
2 files changed, 47 insertions(+),
On 08/03/2011 10:28 AM, Matthias Bolte wrote:
2011/8/3 Eric Blakeebl...@redhat.com:
On 08/03/2011 08:22 AM, Matthias Bolte wrote:
Detection based on gnutls_session doesn't work because GnuTLS 2.x.y
comes with a compat.h that defines gnutls_session to gnutls_session_t.
Instead detect this
2011/8/3 Eric Blake ebl...@redhat.com:
On 08/03/2011 08:22 AM, Matthias Bolte wrote:
Detection based on gnutls_session doesn't work because GnuTLS 2.x.y
comes with a compat.h that defines gnutls_session to gnutls_session_t.
Instead detect this based on LIBGNUTLS_VERSION_MAJOR.
---
I noticed that with 0.9.4, gnulib ended up replacing pthread_sigmask
on glibc, even though glibc's works perfectly fine. It turns out
to have been an upstream gnulib bug.
* .gnulib: Update to latest, for pthread_sigmask fix.
---
This missed the 0.9.4 release; oh well.
* .gnulib
2011/8/3 Eric Blake ebl...@redhat.com:
On 08/03/2011 10:28 AM, Matthias Bolte wrote:
2011/8/3 Eric Blakeebl...@redhat.com:
On 08/03/2011 08:22 AM, Matthias Bolte wrote:
Detection based on gnutls_session doesn't work because GnuTLS 2.x.y
comes with a compat.h that defines gnutls_session to
2011/8/3 Eric Blake ebl...@redhat.com:
I noticed that with 0.9.4, gnulib ended up replacing pthread_sigmask
on glibc, even though glibc's works perfectly fine. It turns out
to have been an upstream gnulib bug.
* .gnulib: Update to latest, for pthread_sigmask fix.
---
This missed the 0.9.4
On 08/03/2011 11:28 AM, Matthias Bolte wrote:
2011/8/3 Eric Blakeebl...@redhat.com:
I noticed that with 0.9.4, gnulib ended up replacing pthread_sigmask
on glibc, even though glibc's works perfectly fine. It turns out
to have been an upstream gnulib bug.
* .gnulib: Update to latest, for
This addresses https://bugzilla.redhat.com/show_bug.cgi?id=713728
When defining a new network (or one that exists but isn't currently
active) the new definition is stored in network-def, but for a
network that already exists and is active, the new definition is
stored in network-newDef, and then
On 03/08/2011, at 1:43 PM, Daniel Veillard wrote:
With an extra day of delay but allowing to pick all coverity checks
related patches from Eric, the release is out, I hope it's solid :-)
available as usual at:
ftp://libvirt.org/libvirt/libvirt-0.9.4.tar.gz
along with signed RPMs
Homebrew
于 2011年08月03日 21:04, Eric Blake 写道:
On 08/03/2011 07:37 AM, Osier Yang wrote:
This patch introduces a internal RPC API virNetServerClose, which
is standalone with virNetServerFree. it closes all the socket fds,
and unlinks the unix socket paths, regardless of whether the socket
is still
On 08/03/2011 01:16 AM, Zdenek Styblik wrote:
Hello,
I'm wondering what might be behind qemu-kvm=0.14 is unable to boot
except from PXE and perhaps virtio HDD.
I mean, is somebody running qemu-kvm=0.14 and libvirt-0.9.3/0.9.4
around here, thus is my setup broken?
I had the problem that
Eric Blake wrote:
On 08/03/2011 08:37 AM, Jim Fehlig wrote:
http://lists.nongnu.org/archive/html/qemu-devel/2011-02/msg01156.html
I thought there were more discussions on the topic but can only find the
above thread ATM.
Do folks here have objections to increasing the migration speed prior
Value stored to 'ret' is never read, so remove this dead assignment.
* src/qemu/qemu_monitor_text.c: kill dead assignment.
Signed-off-by: Alex Jia a...@redhat.com
---
src/qemu/qemu_monitor_text.c |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git
Value stored to 'ret' is never read, in fact, 'cleanup' section will
directly return -1 when function is fail, so remove this dead assignment.
* src/qemu/qemu_process.c: kill dead assignment.
Signed-off-by: Alex Jia a...@redhat.com
---
src/qemu/qemu_process.c |3 ---
1 files changed, 0
Value stored to 'ret' is never read. If Confirm3 returns -1, there's nothing
more we can do, here should remove this dead assignment.
* src/qemu/qemu_migration.c: kill dead assignment.
Signed-off-by: Alex Jia a...@redhat.com
---
src/qemu/qemu_migration.c |6 +++---
1 files changed, 3
29 matches
Mail list logo
