- Devel - libvirt List Archives

[libvirt] Executing scripts when bridge interface becomes available
by Felix Schwarz 20 Dec '09

20 Dec '09

Hi, I'm using libvirt on a CentOS 5.4 host (so my libvirt is quite old) with a routed setup. My configuration is easy and works reliable as far as I can tell now. As far as I know, I have to add routes manually (so that the host knows which IPs need to be routed to the virbr1). My ip command looks like this: /sbin/ip route add <guest ip> dev virbr1 scope link Currently I have really problems finding the right spot where I should configure the routes and it looks like libvirt does not offer any support for that. 1. I can add the route when my network comes up because virbr1 is not available at that time. 2. If I switch my vm to the 'ethernet' interface, I can use a custom script but then I have to do all the network setup myself which looks like overkill and time-consuming (as I have to rebuild things that libvirt already does perfectly). I just want to add some routes... To me the perfect solution would be either: a) have start/stop scripts defined in the network configuration b) have start/stop scripts defined in the vm configuration - Does libvirt 0.7 offer things like that? (I could not find something in the documentation) - Is there an obvious way that I missed when it comes to route configuration? fs

1 0

Re: [libvirt] New libvirt API for domain memory statistics reporting (V4)
by Daniel Veillard 20 Dec '09

20 Dec '09

On Fri, Dec 18, 2009 at 01:17:03PM -0500, Adam Litke wrote: > Daniel, this should be ready for you to merge... Okidoc, done ! There was a bit of tweaking since this conflicted with another new API, but this was eay to solve. I double checked the new src/remote/remote_protocol.x description and that looks fine, I think the only thing missing is a description of the new virsh command in tools/virsh.pod and I think this will be complete. Ah and other bindings need to be updated to export the new function, but that's seaparate. thanks ! Daniel > Changes since V3: > * Fixed remote_protocol.x so rpcgen generates the right code > * Updated stat constants and names in python api > * Incorporate flags into the rpc wire format > > Changes since V2: > * Ported to GIT HEAD for easier merging :) > * Amounts of memory are now reported in kilobytes > * Added flags parameter to API (currently unused) > * Moved to less awkward xdr wire format for remote driver > * Stats 'Free' and 'Total' renamed to 'Unused' and 'Available' > * Various small fixups: constant names, data types, etc > > Changes since V1: > * New system for maintaining ABI compatibility and API extensibility: > Rather than passing around a fixed-size stats structure, work with arrays > of stats. An enum of known statistic tags (SWAP_IN, SWAP_OUT, TOTAL_MEM, > etc) is defined. A stat is defined as a tag/value pair. When making a > call to the API, the caller provides an array of stats and the size of the > array. That array is filled with up to the requested number of stats > (depending on hypervisor and guest support). The number of stats provided > is returned. > > * Miscellaneous changes: > Changed the API function from virDomainMemStats to virDomainMemoryStats > Added documentation for each memory stat > > -- > > When using ballooning to manage overcommitted memory on a host, a system for > guests to communicate their memory usage to the host can provide information > that will minimize the impact of ballooning on the guests while maximizing > efficient use of host memory. > > The design of such a communication channel was recently added to version 0.8.2 > of the VirtIO Spec (See Appendix G): > - http://ozlabs.org/~rusty/virtio-spec/virtio-spec-0.8.2.pdf > > Host-side and guest-side implementations have been accepted for inclusion in > their respective projects: > - Guest: http://lkml.org/lkml/2009/11/30/274 > - Host: http://lists.gnu.org/archive/html/qemu-devel/2009-12/msg00380.html > > The following patch series implements a new libvirt interface to expose these > memory statistics. Thank you for your review and comments. > > > [PATCH 1/6] domMemoryStats: Add domainMemoryStats method to struct _virDriver > [PATCH 2/6] domMemoryStats: Add public symbol to libvirt API > [PATCH 3/6] qemu-driver: Enable domainMemStats in the qemu driver > [PATCH 4/6] remote-driver: Add domainMemoryStats support > [PATCH 5/6] virsh: Enable virDomainMemoryStats as a new command > [PATCH 6/6] python: Add python bindings for virDomainMemoryStats -- Daniel Veillard | libxml Gnome XML XSLT toolkit http://xmlsoft.org/ daniel(a)veillard.com | Rpmfind RPM search engine http://rpmfind.net/ http://veillard.com/ | virtualization library http://libvirt.org/

1 0

[libvirt] [PATCH 00/13] esx: Automatic question handling and other improvements
by Matthias Bolte 18 Dec '09

18 Dec '09

Automatic question handling is the most important part of this series, see src/esx/README for more details. Matthias Bolte (13): esx: Add automatic question handling esx: Improve domain lookup by UUID esx: Use more suitable error code in esxVI_LookupVirtualMachineByUuid() esx: Replace libxml1 'xmlChildrenNode' with libxml2 'children' esx: Removed unused inttypes.h include esx: Extend vCenter query parameter esx: Extend documentation about 'vcenter' and add some about 'auto_answer' esx: Fix occurence typo esx: Use occurrence enum to specify expected result of a SOAP call esx: Don't warn about '/' paths esx: Undefine virtual machine on a vCenter if available esx: Destroy virtual machine on a vCenter if available esx: Add more links to external documentation docs/drvesx.html.in | 52 ++++- src/esx/README | 77 +++++++ src/esx/esx_driver.c | 533 +++++++++++++++++++++++--------------------- src/esx/esx_util.c | 22 ++- src/esx/esx_util.h | 2 +- src/esx/esx_vi.c | 546 ++++++++++++++++++++++++++++++++++++++++------ src/esx/esx_vi.h | 53 ++++- src/esx/esx_vi_methods.c | 185 ++++++++++++---- src/esx/esx_vi_methods.h | 7 + src/esx/esx_vi_types.c | 231 +++++++++++++++++++- src/esx/esx_vi_types.h | 106 +++++++++ src/esx/esx_vmx.c | 2 +- 12 files changed, 1420 insertions(+), 396 deletions(-) create mode 100644 src/esx/README

2 25

[libvirt] [PATCH] Fix compilation with gcrypt < 1.4.2
by Matthias Bolte 18 Dec '09

18 Dec '09

Commit 33a198c1f6a4a1bc7f34d50a31032e03bec10fee increased the gcrypt version requirement to 1.4.2 because the GCRY_THREAD_OPTION_VERSION define was added in this version. The configure script doesn't check for the gcrypt version. To support gcrypt versions < 1.4.2 change the virTLSThreadImpl initialization to use GCRY_THREAD_OPTION_VERSION only if it's defined. --- src/libvirt.c | 5 +++++ 1 files changed, 5 insertions(+), 0 deletions(-) diff --git a/src/libvirt.c b/src/libvirt.c index cad33c2..937cdb4 100644 --- a/src/libvirt.c +++ b/src/libvirt.c @@ -291,7 +291,12 @@ static int virTLSMutexUnlock(void **priv) } static struct gcry_thread_cbs virTLSThreadImpl = { + /* GCRY_THREAD_OPTION_VERSION was added in gcrypt 1.4.2 */ +#ifdef GCRY_THREAD_OPTION_VERSION (GCRY_THREAD_OPTION_PTHREAD | (GCRY_THREAD_OPTION_VERSION << 8)), +#else + GCRY_THREAD_OPTION_PTHREAD, +#endif NULL, virTLSMutexInit, virTLSMutexDestroy, -- 1.6.0.4

2 2

[libvirt] [PATCH 1/2] Don't make it possible to define HAVE_HAL but not enable it in automake.
by Diego Elio 'Flameeyes' Pettenò 18 Dec '09

18 Dec '09

With the previous logic, if libhal_get_all_devices function was not found, HAVE_HAL would be defined for the preprocessor but it wouldn't be enabled in automake conditionals, causing the final link to fail with missing references to HAL entries. --- configure.in | 7 ++++--- 1 files changed, 4 insertions(+), 3 deletions(-) diff --git a/configure.in b/configure.in index c86ee97..e2a0b00 100644 --- a/configure.in +++ b/configure.in @@ -1703,9 +1703,6 @@ if test "x$with_hal" = "xyes" -o "x$with_hal" = "xcheck"; then fi ]) if test "x$with_hal" = "xyes" ; then - AC_DEFINE_UNQUOTED([HAVE_HAL], 1, - [use HAL for host device enumeration]) - old_CFLAGS=$CFLAGS old_LDFLAGS=$LDFLAGS CFLAGS="$CFLAGS $HAL_CFLAGS" @@ -1715,6 +1712,10 @@ if test "x$with_hal" = "xyes" -o "x$with_hal" = "xcheck"; then CFLAGS="$old_CFLAGS" LDFLAGS="$old_LDFLAGS" fi + if test "x$with_hal" = "xyes" ; then + AC_DEFINE_UNQUOTED([HAVE_HAL], 1, + [use HAL for host device enumeration]) + fi fi AM_CONDITIONAL([HAVE_HAL], [test "x$with_hal" = "xyes"]) AC_SUBST([HAL_CFLAGS]) -- 1.6.6.rc3

3 4

[libvirt] RE: [virt-tools-list] Questions about virt-manager running on Arch of Itanium 64
by Dustin Xiong 18 Dec '09

18 Dec '09

> Date: Mon, 30 Nov 2009 09:43:27 +0000 > From: rjones(a)redhat.com > To: x_k_123(a)hotmail.com > CC: berrange(a)redhat.com; virt-tools-list(a)redhat.com > Subject: Re: [virt-tools-list] Questions about virt-manager running on Arch of Itanium 64 > > On Mon, Nov 30, 2009 at 05:07:00PM +0800, Dustin Xiong wrote: > > But when I run virsh ,it failed as below: > > [root@kvm bin]# ./virsh > > error: unable to connect to '/usr/local/dlibvirt/var/run/libvirt/libvirt-sock': No such file or directory > ^^ > Is there really a 'd' in the path there? > > Anyway you can either change the default path that libvirt uses, > by configuring it with: > > ./configure --prefix=/usr > > or you can change the socket path virsh uses at runtime with: > > ./virsh -c qemu+unix:///system?socket=/var/run/libvirt/libvirt-sock Thank you for your advice. And I compiled the libvirt-0.7.4 again ./configure make make install After reboot the machine, I run the binary virsh, the result is as below: [root@kvm bin]#virsh error: unable to connect to '/usr/local/var/run/libvirt/libvirt-sock': No such file or directory error: failed to connect to the hypervisor Then I run the virsh -c ,the result is as below: [root@kvm bin]#virsh -c qemu+unix:///system?socket=/var/run/libvirt/libvirt-sock error: unable to connect to '/var/run/libvirt/libvirt-sock': No such file or directory error: failed to connect to the hypervisor At the same time, I found the libvird didn't running, I don't know whether this caused the error or not. I don't know why this error occurs. Maybe the reason is the libvirt didn't support the use kvm virtualization on ia64 as berrange said before. But I modify the qemu_conf.c and add ia64 information into the struct arch_info_hvm. Then compiled again. The errors remain. Please forgive my poor program skills, I can't add the ia64 into the libvirt kvm supports. Will you want to do some works on this? Thanks a lot. _________________________________________________________________ Windows Live Hotmail: Your friends can get your Facebook updates, right from Hotmail®. http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action/so…

1 0

[libvirt] [PATCH] Fix reporting of TLS connection errors
by Daniel P. Berrange 18 Dec '09

18 Dec '09

The code for connecting to a server tries each socket in turn until it finds one that connects. Unfortunately for TLS sockets if it connected, but failed TLS handshake it would treat that as a failure to connect, and try the next socket. This is bad, it should have reported the TLS failure immediately. $ virsh -c qemu://somehost.com/system error: unable to connect to libvirtd at 'somehost.com': Invalid argument error: failed to connect to the hypervisor $ ./tools/virsh -c qemu://somehost.com/system error: server certificate failed validation: The certificate hasn't got a known issuer. error: failed to connect to the hypervisor * src/remote/remote_driver.c: Stop trying to connect if the TLS handshake fails --- src/remote/remote_driver.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/src/remote/remote_driver.c b/src/remote/remote_driver.c index 77962fe..584de36 100644 --- a/src/remote/remote_driver.c +++ b/src/remote/remote_driver.c @@ -632,7 +632,7 @@ doRemoteOpen (virConnectPtr conn, if (!priv->session) { close (priv->sock); priv->sock = -1; - continue; + goto failed; } } goto tcp_connected; -- 1.6.5.2

2 1

Re: [libvirt] getSchedulerParameters() always returning nullpointerexception in JAVA
by Frederic Dang Tran 18 Dec '09

18 Dec '09

Hi, I came across the same problem: Domain.getSchedulerParameters() throws a NullPointerException systematically. getSchedulerParameters The culprit is the org.libvirt.jna.virSchedParameterValue class which should inherit from jna.Union instead of Structure: public class virSchedParameterValue extends Union { ... } Regards, Frederic On 12/14/2009 04:22 AM, Marc Gonzalez Mateo wrote: OK, let's see if Bryan has an idea/solution about this. Thanks guys! MARC El 11/12/2009, a las 14:29, Daniel Veillard escribió: On Fri, Dec 11, 2009 at 02:01:36PM +0100, Marc Gonzalez Mateo wrote: Hi everyvody, I'm developing a new API based on libvirt. I'm currently stucked using getSchedulerParameters, always is returning a nullpointerexception, no matter which Xen Domain I'm passing to the function. Enclosing both the code and the error console: public int getCPUPriority(String name) { int res=-1; try { Domain d = getDomain(name); SchedParameter[] pars = d.getSchedulerParameters(); Hum, it seems Domain.getSchedulerParameters() does SchedParameter[] returnValue = new SchedParameter[0]; and public static SchedParameter create(virSchedParameter vParam) { SchedParameter returnValue = null; switch (vParam.type) { case (1): and the create method getting there gets a null pointer as the initialization argument, which it first dereference ... so not surprizing looking at the code, maybe Bryan has an idea of what is going on there, I'm a bit lost in this initialization process ... Daniel for (SchedParameter pri : pars) { if (pri.field=="weight") res=Integer.parseInt(pri.getValueAsString()); } } catch (LibvirtException e) { log.error(" Error: getting CPU priority of \""+name+"\"." + e.getClass()); e.printStackTrace(); } return res; } Dec 11, 2009 1:04:18 PM net.emotivecloud.virtmonitor.VirtMonitor getCPUCapacity SEVERE: Error: getting CPU capacity of "XenTest". java.lang.NullPointerException at org.libvirt.SchedParameter.create(Unknown Source) at org.libvirt.Domain.getSchedulerParameters(Unknown Source) at net.emotivecloud.virtmonitor.VirtMonitor.getCPUCapacity(VirtMonitor.java:462) at net.emotivecloud.virtmonitor.VirtMonitor.main(VirtMonitor.java:763) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:283) at java.lang.Thread.run(Thread.java:636) Any ideas? Thanks in advance, Marc Gonzalez Mateo -- Libvir-list mailing list Libvir-list redhat com https://www.redhat.com/mailman/listinfo/libvir-list -- Daniel Veillard | libxml Gnome XML XSLT toolkit http://xmlsoft.org/ daniel veillard com | Rpmfind RPM search engine http://rpmfind.net/ http://veillard.com/ | virtualization library http://libvirt.org/ Frederic Dang Tran

1 0

[libvirt] [RFC] New libvirt API for domain memory statistics reporting (V2)
by Adam Litke 17 Dec '09

17 Dec '09

Thanks for the review and comments on V1. This series tries to address most of the feedback I received. I did not add any additional memory stats yet (I feel that with my new method of expanding the API, that can be handled separately). I am not convinced that every memory stat that any hypervisor exports should necessarily be included in this API. I tried to focus on statistics that are useful in the context of managing domains at the hypervisor level. Changes since V1: * New system for maintaining ABI compatibility and API extensibility: Rather than passing around a fixed-size stats structure, work with arrays of stats. An enum of known statistic tags (SWAP_IN, SWAP_OUT, TOTAL_MEM, etc) is defined. A stat is defined as a tag/value pair. When making a call to the API, the caller provides an array of stats and the size of the array. That array is filled with up to the requested number of stats (depending on hypervisor and guest support). The number of stats provided is returned. * Miscellaneous changes: Changed the API function from virDomainMemStats to virDomainMemoryStats Added documentation for each memory stat -- When using ballooning to manage overcommitted memory on a host, a system for guests to communicate their memory usage to the host can provide information that will minimize the impact of ballooning on the guests while maximizing efficient use of host memory. The design of such a communication channel was recently added to version 0.8.2 of the VirtIO Spec (See Appendix G): - http://ozlabs.org/~rusty/virtio-spec/virtio-spec-0.8.2.pdf Host-side and guest-side implementations have been accepted for inclusion in their respective projects: - Guest: http://lkml.org/lkml/2009/11/30/274 - Host: http://lists.gnu.org/archive/html/qemu-devel/2009-12/msg00380.html The following patch series implements a new libvirt interface to expose these memory statistics. Thank you for your review and comments. [PATCH 1/6] domMemStats: Add domainMemoryStats method to struct _virDriver [PATCH 2/6] domMemoryStats: Add public symbol to libvirt API [PATCH 3/6] qemu-driver: Enable domainMemStats in the qemu driver [PATCH 4/6] remote-driver: Add domainMemoryStats support [PATCH 5/6] virsh: Enable virDomainMemoryStats as a new command [PATCH 6/6] python: Add python bindings for virDomainMemoryStats

4 18

[libvirt] Licensing of the schemas?
by Diego Elio “Flameeyes” Pettenò 17 Dec '09

17 Dec '09

Hi, I've finally found the time to backport the schema fixes and I'm going to add the nxml-libvirt-schemas package to Portage so that those like me who like to edit the XML files with Emacs can do so with some support. But I didn't pay enough attention before that the .rng files lack a license header. I'd assume that the license of the package (LGPL-2.1) apply to the schema, but it would be nice if somebody could confirm that for me (and eventually somebody, me even, could add the proper headers to them). Thanks, -- Diego Elio Pettenò — “Flameeyes” http://blog.flameeyes.eu/ If you found a .asc file in this mail and know not what it is, it's a GnuPG digital signature: http://www.gnupg.org/

4 6