- Devel - libvirt List Archives

[libvirt] [PATCH 0/9 v2] Refactor the configure.ac to reduce duplication
by Daniel P. Berrange 11 Jan '13

11 Jan '13

This is an update to https://www.redhat.com/archives/libvir-list/2012-September/msg01443.html Aside from the rebase, the main changes are all in the first patch, where I believe I addresses all Erics feedback with one exception. The exception was about the suggestion to support action-if-found, action-if-not-found, instead of the 2nd variant of macro. This is not actually possible, since the 2nd variant is not equivalent to a pair of calls to the 1st variant. To avoid flooding the list I've reduced this to just the first 9 patches. If these are approved there are another 30 patches to follow doing more conversions :-)

2 23

[libvirt] [PATCH] docs: add some more hacking tips
by Eric Blake 11 Jan '13

11 Jan '13

Based on a suggestion by John Ferlan: https://www.redhat.com/archives/libvir-list/2013-January/msg00158.html * docs/hacking.html.in: Add some commit message instructions. Mention the ./run script. * HACKING: Regenerate. --- I don't know how to make docs/hacking2.xsl delay the line wrapping until after the '(3) ' prefix due to the <li> is inserted; as a result, there is a line longer than 80 columns. Suggestions on improving the template are welcome. HACKING | 26 ++++++++++++++++++++++---- docs/hacking.html.in | 19 ++++++++++++++++++- 2 files changed, 40 insertions(+), 5 deletions(-) diff --git a/HACKING b/HACKING index 0ee988a..1b4dea3 100644 --- a/HACKING +++ b/HACKING @@ -58,7 +58,19 @@ though). -(3) Split large changes into a series of smaller patches, self-contained if +(3) In your commit message, make the summary line reasonably short (60 characters +is typical), followed by a blank line, followed by any longer description of +why your patch makes sense. If the patch fixes a regression, and you know what +commit introduced the problem, mentioning that is useful. If the patch +resolves a bugzilla report, mentioning the URL of the bug number is useful; +but also summarize the issue rather than making all readers follow the link. +You can use 'git shortlog -30' to get an idea of typical summary lines. +Libvirt does not currently attach any meaning to Signed-off-by: lines, so it +is up to you if you want to include or omit them in the commit message. + + + +(4) Split large changes into a series of smaller patches, self-contained if possible, with an explanation of each patch and an explanation of how the sequence of patches fits together. Moreover, please keep in mind that it's required to be able to compile cleanly (*including* "make check" and "make @@ -69,10 +81,10 @@ things). -(4) Make sure your patches apply against libvirt GIT. Developers only follow GIT +(5) Make sure your patches apply against libvirt GIT. Developers only follow GIT and don't care much about released versions. -(5) Run the automated tests on your code before submitting any changes. In +(6) Run the automated tests on your code before submitting any changes. In particular, configure with compile warnings set to -Werror. This is done automatically for a git checkout; from a tarball, use: @@ -97,7 +109,13 @@ Also, individual tests can be run from inside the "tests/" directory, like: ./qemuxml2xmltest -(6) Update tests and/or documentation, particularly if you are adding a new +There is also a "./run" script at the top level, to make it easier to run +uninstalled programs, as well as to wrap invocations of various tests under +gdb or valgrind. + + + +(7) Update tests and/or documentation, particularly if you are adding a new feature or changing the output of a program. diff --git a/docs/hacking.html.in b/docs/hacking.html.in index 40acdbb..17136f0 100644 --- a/docs/hacking.html.in +++ b/docs/hacking.html.in @@ -59,6 +59,21 @@ version if needed though). </li> + <li>In your commit message, make the summary line reasonably + short (60 characters is typical), followed by a blank line, + followed by any longer description of why your patch makes + sense. If the patch fixes a regression, and you know what + commit introduced the problem, mentioning that is useful. + If the patch resolves a bugzilla report, mentioning the URL + of the bug number is useful; but also summarize the issue + rather than making all readers follow the link. You can use + 'git shortlog -30' to get an idea of typical summary lines. + Libvirt does not currently attach any meaning to + Signed-off-by: lines, so it is up to you if you want to + include or omit them in the commit message. + + </li> + <li>Split large changes into a series of smaller patches, self-contained if possible, with an explanation of each patch and an explanation of how the sequence of patches fits @@ -110,7 +125,9 @@ <pre> ./qemuxml2xmltest </pre> - + There is also a <code>./run</code> script at the top level, + to make it easier to run uninstalled programs, as well as to + wrap invocations of various tests under gdb or valgrind. </li> <li>Update tests and/or documentation, particularly if you are adding a new feature or changing the output of a program.</li> -- 1.8.0.2

3 6

[libvirt] [PATCH] build: fix incomplete WITH_SASL conversion
by Eric Blake 11 Jan '13

11 Jan '13

Commit 321a7d53 missed a spot. * src/rpc/virnetsocket.c (virNetSocketPreExecRestart): Use right conditional. --- Pushing under the build-breaker rule. src/rpc/virnetsocket.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/rpc/virnetsocket.c b/src/rpc/virnetsocket.c index 549aabe..00c6121 100644 --- a/src/rpc/virnetsocket.c +++ b/src/rpc/virnetsocket.c @@ -1,7 +1,7 @@ /* * virnetsocket.c: generic network socket handling * - * Copyright (C) 2006-2012 Red Hat, Inc. + * Copyright (C) 2006-2013 Red Hat, Inc. * Copyright (C) 2006 Daniel P. Berrange * * This library is free software; you can redistribute it and/or @@ -943,7 +943,7 @@ virJSONValuePtr virNetSocketPreExecRestart(virNetSocketPtr sock) virMutexLock(&sock->lock); -#if HAVE_SASL +#if WITH_SASL if (sock->saslSession) { virReportError(VIR_ERR_OPERATION_INVALID, "%s", _("Unable to save socket state when SASL session is active")); -- 1.8.0.2

1 0

[libvirt] [libvirt-glib] gobject: API to open read-only connection to libvirt
by Zeeshan Ali (Khattak) 11 Jan '13

11 Jan '13

From: "Zeeshan Ali (Khattak)" <zeeshanak(a)gnome.org> --- libvirt-gobject/libvirt-gobject-connection.c | 99 +++++++++++++++++++++++++--- libvirt-gobject/libvirt-gobject-connection.h | 10 +++ libvirt-gobject/libvirt-gobject.sym | 7 ++ 3 files changed, 107 insertions(+), 9 deletions(-) diff --git a/libvirt-gobject/libvirt-gobject-connection.c b/libvirt-gobject/libvirt-gobject-connection.c index 3157a66..558ed2a 100644 --- a/libvirt-gobject/libvirt-gobject-connection.c +++ b/libvirt-gobject/libvirt-gobject-connection.c @@ -407,14 +407,10 @@ static int domain_event_cb(virConnectPtr conn G_GNUC_UNUSED, return 0; } -/** - * gvir_connection_open: - * @conn: a #GVirConnection - * @cancellable: (allow-none)(transfer none): cancellation object - */ -gboolean gvir_connection_open(GVirConnection *conn, - GCancellable *cancellable, - GError **err) +static gboolean _gvir_connection_open(GVirConnection *conn, + gboolean read_only, + GCancellable *cancellable, + GError **err) { GVirConnectionPrivate *priv; @@ -438,7 +434,11 @@ gboolean gvir_connection_open(GVirConnection *conn, return FALSE; } - if (!(priv->conn = virConnectOpen(priv->uri))) { + if (read_only) + priv->conn = virConnectOpenReadOnly(priv->uri); + else + priv->conn = virConnectOpen(priv->uri); + if (!priv->conn) { gvir_set_error(err, GVIR_CONNECTION_ERROR, 0, "Unable to open %s", @@ -472,6 +472,24 @@ gboolean gvir_connection_open(GVirConnection *conn, return TRUE; } +/** + * gvir_connection_open: + * @conn: a #GVirConnection + * @cancellable: (allow-none)(transfer none): cancellation object + */ +gboolean gvir_connection_open(GVirConnection *conn, + GCancellable *cancellable, + GError **err) +{ + return _gvir_connection_open(conn, FALSE, cancellable, err); +} + +gboolean gvir_connection_open_read_only(GVirConnection *conn, + GCancellable *cancellable, + GError **err) +{ + return _gvir_connection_open(conn, TRUE, cancellable, err); +} static void gvir_connection_open_helper(GSimpleAsyncResult *res, @@ -537,6 +555,69 @@ gboolean gvir_connection_open_finish(GVirConnection *conn, return TRUE; } +static void +gvir_connection_open_read_only_helper(GSimpleAsyncResult *res, + GObject *object, + GCancellable *cancellable) +{ + GVirConnection *conn = GVIR_CONNECTION(object); + GError *err = NULL; + + if (!gvir_connection_open_read_only(conn, cancellable, &err)) { + g_simple_async_result_set_from_error(res, err); + g_error_free(err); + } +} + + +/** + * gvir_connection_open_read_only_async: + * @conn: a #GVirConnection + * @cancellable: (allow-none)(transfer none): cancellation object + * @callback: (scope async): completion callback + * @user_data: (closure): opaque data for callback + */ +void gvir_connection_open_read_only_async(GVirConnection *conn, + GCancellable *cancellable, + GAsyncReadyCallback callback, + gpointer user_data) +{ + GSimpleAsyncResult *res; + + g_return_if_fail(GVIR_IS_CONNECTION(conn)); + g_return_if_fail((cancellable == NULL) || G_IS_CANCELLABLE(cancellable)); + + res = g_simple_async_result_new(G_OBJECT(conn), + callback, + user_data, + gvir_connection_open_read_only_async); + g_simple_async_result_run_in_thread(res, + gvir_connection_open_read_only_helper, + G_PRIORITY_DEFAULT, + cancellable); + g_object_unref(res); +} + + +/** + * gvir_connection_open_read_only_finish: + * @conn: a #GVirConnection + * @result: (transfer none): async method result + */ +gboolean gvir_connection_open_read_only_finish(GVirConnection *conn, + GAsyncResult *result, + GError **err) +{ + g_return_val_if_fail(GVIR_IS_CONNECTION(conn), FALSE); + g_return_val_if_fail(g_simple_async_result_is_valid(result, G_OBJECT(conn), + gvir_connection_open_read_only_async), + FALSE); + + if (g_simple_async_result_propagate_error(G_SIMPLE_ASYNC_RESULT(result), err)) + return FALSE; + + return TRUE; +} gboolean gvir_connection_is_open(GVirConnection *conn) { diff --git a/libvirt-gobject/libvirt-gobject-connection.h b/libvirt-gobject/libvirt-gobject-connection.h index f91ca05..d2b0a9f 100644 --- a/libvirt-gobject/libvirt-gobject-connection.h +++ b/libvirt-gobject/libvirt-gobject-connection.h @@ -88,6 +88,9 @@ GVirConnection *gvir_connection_new(const char *uri); gboolean gvir_connection_open(GVirConnection *conn, GCancellable *cancellable, GError **err); +gboolean gvir_connection_open_read_only(GVirConnection *conn, + GCancellable *cancellable, + GError **err); void gvir_connection_open_async(GVirConnection *conn, GCancellable *cancellable, GAsyncReadyCallback callback, @@ -95,6 +98,13 @@ void gvir_connection_open_async(GVirConnection *conn, gboolean gvir_connection_open_finish(GVirConnection *conn, GAsyncResult *result, GError **err); +void gvir_connection_open_read_only_async(GVirConnection *conn, + GCancellable *cancellable, + GAsyncReadyCallback callback, + gpointer user_data); +gboolean gvir_connection_open_read_only_finish(GVirConnection *conn, + GAsyncResult *result, + GError **err); gboolean gvir_connection_is_open(GVirConnection *conn); void gvir_connection_close(GVirConnection *conn); diff --git a/libvirt-gobject/libvirt-gobject.sym b/libvirt-gobject/libvirt-gobject.sym index 8743b88..b02b365 100644 --- a/libvirt-gobject/libvirt-gobject.sym +++ b/libvirt-gobject/libvirt-gobject.sym @@ -224,4 +224,11 @@ LIBVIRT_GOBJECT_0.1.4 { gvir_storage_pool_undefine_finish; } LIBVIRT_GOBJECT_0.1.3; +LIBVIRT_GOBJECT_0.1.5 { + global: + gvir_connection_open_read_only; + gvir_connection_open_read_only_async; + gvir_connection_open_read_only_finish; +} LIBVIRT_GOBJECT_0.1.4; + # .... define new API here using predicted next version number .... -- 1.8.0.2

2 4

[libvirt] [libvirt-java] git commit: Fix memory leaks for libvirt functions returning newly allocated memory. (3220de)
by Wido den Hollander 11 Jan '13

11 Jan '13

Hi, I just wanted to build the latest libvirt-java master on my Ubuntu 12.04 laptop and it failed due to this commit. The commit message says: "Use JNA's Native.free() method to free memory. This requires JNA version 3.3.0 or later." Ubuntu 12.04 comes with JNA 3.2.7-4, so the build fails. Is there a way to still build and run on Ubuntu 12.04? This is a 5-year LTS release from Ubuntu so we'll be seeing this around until 2017. I'm working on the patches I sent last week and got some good feedback. We (the Apache CloudStack project) rely heavily on libvirt-java for virtual machine management when using the KVM Hypervisor, so I'd like to keep the bindings working on Ubuntu 12.04 :) Thanks, Wido

1 0

[libvirt] [PATCH 0/3] Fix various issues with libvirt networks
by Peter Krempa 11 Jan '13

11 Jan '13

This patchset fixes various non-related issues with libvirt networking: Peter Krempa (3): network: bridge: Fix regression when defining persistent networks virsh: Reformat output of virsh net-list network: Report real error if addition of firewall rules fails src/network/bridge_driver.c | 10 ++++++++++ tools/virsh-network.c | 7 ++++--- 2 files changed, 14 insertions(+), 3 deletions(-) -- 1.8.1

2 5

[libvirt] [RFC] Overriding graphics relocation URI
by Jiri Denemark 11 Jan '13

11 Jan '13

Hi all. Graphics relocation URI is currently transmitted within migration cookie in the form of graphics type, address, port, tlsPort, and certificate subject. The cookie is generated by target libvirtd and consumed by source libvirtd which than forwards this data through QEMU to the graphics client. In case the target libvirtd is not able to provide the data in a way usable by the client (e.g., because it needs to use different address), we need to provide a way to override the graphics URI. We already support similar thing for migration URI. So the question is how we can support $SUBJ? The only way I came up with is to introduce another set of migration APIs (such as virDomainMigrateToURI3, ...) with an additional graphics URI parameter. The URI would be formed as type "://" address ":" port "?tlsPort=" tlsPort "&subject=" cert with various parts being optional. That would allow us to override any part of the graphics cookie we need. However, I don't like the addition of another set of migration APIs and I'd be glad to hear better ideas :-) Jirka

3 2

Re: [libvirt] feature suggestion: migration network
by Dan Kenigsberg 11 Jan '13

11 Jan '13

On Thu, Jan 10, 2013 at 10:45:42AM +0800, Mark Wu wrote: > On 01/08/2013 10:46 PM, Yaniv Kaul wrote: > >On 08/01/13 15:04, Dan Kenigsberg wrote: > >>There's talk about this for ages, so it's time to have proper discussion > >>and a feature page about it: let us have a "migration" network role, and > >>use such networks to carry migration data > >> > >>When Engine requests to migrate a VM from one node to another, the VM > >>state (Bios, IO devices, RAM) is transferred over a TCP/IP connection > >>that is opened from the source qemu process to the destination qemu. > >>Currently, destination qemu listens for the incoming connection on the > >>management IP address of the destination host. This has serious > >>downsides: a "migration storm" may choke the destination's management > >>interface; migration is plaintext and ovirtmgmt includes Engine which > >>sits may sit the node cluster. > >> > >>With this feature, a cluster administrator may grant the "migration" > >>role to one of the cluster networks. Engine would use that network's IP > >>address on the destination host when it requests a migration of a VM. > >>With proper network setup, migration data would be separated to that > >>network. > >> > >>=== Benefit to oVirt === > >>* Users would be able to define and dedicate a separate network for > >> migration. Users that need quick migration would use nics with high > >> bandwidth. Users who want to cap the bandwidth consumed by migration > >> could define a migration network over nics with bandwidth limitation. > >>* Migration data can be limited to a separate network, that has no > >> layer-2 access from Engine > >> > >>=== Vdsm === > >>The "migrate" verb should be extended with an additional parameter, > >>specifying the address that the remote qemu process should listen on. A > >>new argument is to be added to the currently-defined migration > >>arguments: > >>* vmId: UUID > >>* dst: management address of destination host > >>* dstparams: hibernation volumes definition > >>* mode: migration/hibernation > >>* method: rotten legacy > >>* ''New'': migration uri, according to > >>http://libvirt.org/html/libvirt-libvirt.html#virDomainMigrateToURI2 > >>such as tcp://<ip of migration network on remote node> > >> > >>=== Engine === > >>As usual, complexity lies here, and several changes are required: > >> > >>1. Network definition. > >>1.1 A new network role - not unlike "display network" should be > >> added.Only one migration network should be defined on a cluster. > >>1.2 If none is defined, the legacy "use ovirtmgmt for migration" > >> behavior would apply. > >>1.3 A migration network is more likely to be a ''required'' network, but > >> a user may opt for non-required. He may face unpleasant > >>surprises if he > >> wants to migrate his machine, but no candidate host has the network > >> available. > >>1.4 The "migration" role can be granted or taken on-the-fly, when hosts > >> are active, as long as there are no currently-migrating VMs. > >> > >>2. Scheduler > >>2.1 when deciding which host should be used for automatic > >> migration, take into account the existence and availability of the > >> migration network on the destination host. > >>2.2 For manual migration, let user migrate a VM to a host with no > >> migration network - if the admin wants to keep jamming the > >> management network with migration traffic, let her. > >> > >>3. VdsBroker migration verb. > >>3.1 For the a modern cluster level, with migration network defined on > >> the destination host, an additional ''miguri'' parameter > >>should be added > >> to the "migrate" command > >> > >>_______________________________________________ > >>Arch mailing list > >>Arch(a)ovirt.org > >>http://lists.ovirt.org/mailman/listinfo/arch > > > >How is the authentication of the peers handled? Do we need a cert > >per each source/destination logical interface? > >Y. > In my understanding, using a separate migration network doesn't > change the current peers authentication. We still use the URI > ''qemu+tls://remoeHost/system' to connect the target libvirt service > if ssl enabled, and the remote host should be the ip address of > management interface. But we can choose other interfaces except the > manage interface to transport the migration data. We just change the > migrateURI, so the current authentication mechanism should still > work for this new feature. vdsm-vdsm and libvirt-libvirt communication is authenticated, but I am not sure at all that qemu-qemu communication is. After qemu is sprung up on the destination with -incoming <some ip>:<some port> , anything with access to that address could hijack the process. Our migrateURI starts with "tcp://" with all the consequences of this. That a good reason to make sure <some ip> has as limited access as possible. But maybe I'm wrong here, and libvir-list can show me the light. Dan.

3 2

[libvirt] [PATCH] libvirt: lxc: fix incorrect parameter of lxcContainerMountProcFuse
by Gao feng 11 Jan '13

11 Jan '13

when we have no host's src mapped to container's root. there is not .oldroot dir,we should pass "/" to lxcContainerMountProcFuse in function lxcContainerSetupExtraMounts. Signed-off-by: Gao feng <gaofeng(a)cn.fujitsu.com> --- src/lxc/lxc_container.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/lxc/lxc_container.c b/src/lxc/lxc_container.c index d234426..09a4365 100644 --- a/src/lxc/lxc_container.c +++ b/src/lxc/lxc_container.c @@ -2059,7 +2059,7 @@ static int lxcContainerSetupExtraMounts(virDomainDefPtr vmDef, goto cleanup; /* Mounts /proc/meminfo etc sysinfo */ - if (lxcContainerMountProcFuse(vmDef, "/.oldroot") < 0) + if (lxcContainerMountProcFuse(vmDef, "/") < 0) goto cleanup; /* Now we can re-mount the cgroups controllers in the -- 1.7.11.7

4 8

[libvirt] libvirt RPC error
by Parakkal, Navin S 11 Jan '13

11 Jan '13

Hi, I'm using qemu+ssh://username@hostname/system as the remote URI. Libvirt seems to be communicating fine until some 2 minutes (we poll every 5 seconds) and then it throws up RPC error and many counters are wrong. But if I collect on localhost the counters seems to be coming fine. Test and testvm are guests on the local machine where as Win8 and Ubuntu* are remote URI's connected through ssh. What causes this error "libvir: RPC error : End of file while reading data: : Input/output error" and how do we fix it ? I've pasted the logfile inline. Localhost from which we are connecting: uname -aLinux iwf0044110 3.2.0-23-generic #36-Ubuntu SMP Tue Apr 10 20:39:51 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux root@iwf0044110:/home1/parakkal/COLLABNET_11.10_NEW/hpsw-oa/PA/numsVob/linux/2.2/Linux2.6_64_debug# cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=12.04 DISTRIB_CODENAME=precise DISTRIB_DESCRIPTION="Ubuntu 12.04 LTS" root@iwf0044110:/home1/parakkal/COLLABNET_11.10_NEW/hpsw-oa/PA/numsVob/linux/2.2/Linux2.6_64_debug# virsh version Compiled against library: libvir 0.9.8 Using library: libvir 0.9.8 Using API: QEMU 0.9.8 Running hypervisor: QEMU 1.0.0 Remote host: root@iwf004461:/home1/parakkal/COLLABNET_11.10_NEW/hpsw-oa/PA/numsVob/linux/2.2# uname -a Linux iwf004461 3.0.0-12-server #20-Ubuntu SMP Fri Oct 7 16:36:30 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux root@iwf004461:/home1/parakkal/COLLABNET_11.10_NEW/hpsw-oa/PA/numsVob/linux/2.2# cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=11.10 DISTRIB_CODENAME=oneiric DISTRIB_DESCRIPTION="Ubuntu 11.10" root@iwf004461:/home1/parakkal/COLLABNET_11.10_NEW/hpsw-oa/PA/numsVob/linux/2.2# virsh version Compiled against library: libvir 0.9.2 Using library: libvir 0.9.2 Using API: QEMU 0.9.2 Running hypervisor: QEMU 0.14.1 Note: libvirt.so not present, using /usr/lib/libvirt.so.0 libvir: error : no connection driver available for No connection for URI xen:/// No Xen on this system NOTE: 1 memory stats available out of 8 libvir: error : internal error getaddrinfo failed for 'iwf004461': Name or service not known libvir: QEMU error : Requested operation is not valid: cgroup CPU controller is not mounted NOTE: scheduler type not available libvir: error : internal error getaddrinfo failed for 'iwf004461': Name or service not known libvir: error : internal error getaddrinfo failed for 'iwf004461': Name or service not known libvir: error : internal error getaddrinfo failed for 'iwf004461': Name or service not known libvir: error : internal error getaddrinfo failed for 'iwf004461': Name or service not known libvir: error : internal error getaddrinfo failed for 'iwf004461': Name or service not known 04:23:07 | testvm | Running 04:23:07 | test | Running 04:23:07 | Win8 | Running 04:23:07 | Ubuntu11.10 | Running 04:23:07 | Ubuntu12.04 | Running libvir: error : internal error getaddrinfo failed for 'iwf004461': Name or service not known libvir: error : internal error getaddrinfo failed for 'iwf004461': Name or service not known libvir: error : internal error getaddrinfo failed for 'iwf004461': Name or service not known 04:23:18 | testvm | Running 04:23:18 | test | Running 04:23:18 | Win8 | Running 04:23:18 | Ubuntu11.10 | Running 04:23:18 | Ubuntu12.04 | Running libvir: error : internal error getaddrinfo failed for 'iwf004461': Name or service not known libvir: error : internal error getaddrinfo failed for 'iwf004461': Name or service not known libvir: error : internal error getaddrinfo failed for 'iwf004461': Name or service not known 04:23:25 | testvm | Running 04:23:25 | test | Running 04:23:25 | Win8 | Running 04:23:25 | Ubuntu11.10 | Running 04:23:25 | Ubuntu12.04 | Running libvir: error : internal error getaddrinfo failed for 'iwf004461': Name or service not known libvir: error : internal error getaddrinfo failed for 'iwf004461': Name or service not known libvir: error : internal error getaddrinfo failed for 'iwf004461': Name or service not known 04:23:32 | testvm | Running 04:23:32 | test | Running 04:23:32 | Win8 | Running 04:23:32 | Ubuntu11.10 | Running 04:23:32 | Ubuntu12.04 | Running libvir: error : internal error getaddrinfo failed for 'iwf004461': Name or service not known libvir: error : internal error getaddrinfo failed for 'iwf004461': Name or service not known libvir: error : internal error getaddrinfo failed for 'iwf004461': Name or service not known 04:23:40 | testvm | Running 04:23:40 | test | Running 04:23:40 | Win8 | Running 04:23:40 | Ubuntu11.10 | Running 04:23:40 | Ubuntu12.04 | Running libvir: error : internal error getaddrinfo failed for 'iwf004461': Name or service not known libvir: error : internal error getaddrinfo failed for 'iwf004461': Name or service not known libvir: error : internal error getaddrinfo failed for 'iwf004461': Name or service not known 04:23:47 | testvm | Running 04:23:47 | test | Running 04:23:47 | Win8 | Running 04:23:47 | Ubuntu11.10 | Running 04:23:47 | Ubuntu12.04 | Running libvir: error : internal error getaddrinfo failed for 'iwf004461': Name or service not known libvir: error : internal error getaddrinfo failed for 'iwf004461': Name or service not known libvir: error : internal error getaddrinfo failed for 'iwf004461': Name or service not known 04:23:55 | testvm | Running 04:23:55 | test | Running 04:23:55 | Win8 | Running 04:23:55 | Ubuntu11.10 | Running 04:23:55 | Ubuntu12.04 | Running libvir: error : internal error getaddrinfo failed for 'iwf004461': Name or service not known libvir: error : internal error getaddrinfo failed for 'iwf004461': Name or service not known libvir: error : internal error getaddrinfo failed for 'iwf004461': Name or service not known 04:24:02 | testvm | Running 04:24:02 | test | Running 04:24:02 | Win8 | Running 04:24:02 | Ubuntu11.10 | Running 04:24:02 | Ubuntu12.04 | Running libvir: error : internal error getaddrinfo failed for 'iwf004461': Name or service not known libvir: error : internal error getaddrinfo failed for 'iwf004461': Name or service not known libvir: error : internal error getaddrinfo failed for 'iwf004461': Name or service not known 04:24:10 | testvm | Running 04:24:10 | test | Running 04:24:10 | Win8 | Running 04:24:10 | Ubuntu11.10 | Running 04:24:10 | Ubuntu12.04 | Running libvir: error : internal error getaddrinfo failed for 'iwf004461': Name or service not known libvir: error : internal error getaddrinfo failed for 'iwf004461': Name or service not known libvir: error : internal error getaddrinfo failed for 'iwf004461': Name or service not known 04:24:17 | testvm | Running 04:24:17 | test | Running 04:24:17 | Win8 | Running 04:24:17 | Ubuntu11.10 | Running 04:24:17 | Ubuntu12.04 | Running libvir: error : internal error getaddrinfo failed for 'iwf004461': Name or service not known libvir: error : internal error getaddrinfo failed for 'iwf004461': Name or service not known libvir: error : internal error getaddrinfo failed for 'iwf004461': Name or service not known 04:24:24 | testvm | Running 04:24:24 | test | Running 04:24:24 | Win8 | Running 04:24:24 | Ubuntu11.10 | Running 04:24:24 | Ubuntu12.04 | Running libvir: error : internal error getaddrinfo failed for 'iwf004461': Name or service not known libvir: error : internal error getaddrinfo failed for 'iwf004461': Name or service not known libvir: error : internal error getaddrinfo failed for 'iwf004461': Name or service not known 04:24:32 | testvm | Running 04:24:32 | test | Running 04:24:32 | Win8 | Running 04:24:32 | Ubuntu11.10 | Running 04:24:32 | Ubuntu12.04 | Running libvir: error : internal error getaddrinfo failed for 'iwf004461': Name or service not known libvir: error : internal error getaddrinfo failed for 'iwf004461': Name or service not known libvir: error : internal error getaddrinfo failed for 'iwf004461': Name or service not known 04:24:39 | testvm | Running 04:24:39 | test | Running 04:24:39 | Win8 | Running 04:24:39 | Ubuntu11.10 | Running 04:24:39 | Ubuntu12.04 | Running libvir: error : internal error getaddrinfo failed for 'iwf004461': Name or service not known libvir: error : internal error getaddrinfo failed for 'iwf004461': Name or service not known libvir: error : internal error getaddrinfo failed for 'iwf004461': Name or service not known 04:24:46 | testvm | Running 04:24:46 | test | Running 04:24:46 | Win8 | Running 04:24:46 | Ubuntu11.10 | Running 04:24:46 | Ubuntu12.04 | Running libvir: error : internal error getaddrinfo failed for 'iwf004461': Name or service not known libvir: error : internal error getaddrinfo failed for 'iwf004461': Name or service not known libvir: error : internal error getaddrinfo failed for 'iwf004461': Name or service not known 04:24:54 | testvm | Running 04:24:54 | test | Running 04:24:54 | Win8 | Running 04:24:54 | Ubuntu11.10 | Running 04:24:54 | Ubuntu12.04 | Running libvir: error : internal error getaddrinfo failed for 'iwf004461': Name or service not known libvir: error : internal error getaddrinfo failed for 'iwf004461': Name or service not known libvir: error : internal error getaddrinfo failed for 'iwf004461': Name or service not known 04:25:01 | testvm | Running 04:25:01 | test | Running 04:25:01 | Win8 | Running 04:25:01 | Ubuntu11.10 | Running 04:25:01 | Ubuntu12.04 | Running libvir: error : internal error getaddrinfo failed for 'iwf004461': Name or service not known libvir: error : internal error getaddrinfo failed for 'iwf004461': Name or service not known libvir: error : internal error getaddrinfo failed for 'iwf004461': Name or service not known 04:25:09 | testvm | Running 04:25:09 | test | Running 04:25:09 | Win8 | Running 04:25:09 | Ubuntu11.10 | Running 04:25:09 | Ubuntu12.04 | Running libvir: RPC error : End of file while reading data: : Input/output error 04:25:16 | testvm | Running 04:25:16 | test | Running 04:25:16 | Win8 | Nostate 04:25:16 | Ubuntu11.10 | Nostate 04:25:16 | Ubuntu12.04 | Nostate libvir: RPC error : End of file while reading data: : Input/output error 04:25:20 | testvm | Running 04:25:20 | test | Running 04:25:20 | Win8 | Nostate 04:25:20 | Ubuntu11.10 | Nostate 04:25:20 | Ubuntu12.04 | Nostate libvir: RPC error : End of file while reading data: : Input/output error 04:25:25 | testvm | Running 04:25:25 | test | Running 04:25:25 | Win8 | Nostate 04:25:25 | Ubuntu11.10 | Nostate 04:25:25 | Ubuntu12.04 | Nostate Regards, Navin P.S. Please use reply all as I'm not subscribed to this list .

2 2