- Devel - libvirt List Archives

[libvirt] [PATCH] qemu: Improve some qemu.conf error reporting
by Cole Robinson 02 Jul '10

02 Jul '10

Log some info if we can't find a config file. Make parse failures fatal, and actually raise an error message. Signed-off-by: Cole Robinson <crobinso(a)redhat.com> --- src/qemu/qemu_conf.c | 13 +++++++++---- 1 files changed, 9 insertions(+), 4 deletions(-) diff --git a/src/qemu/qemu_conf.c b/src/qemu/qemu_conf.c index ce42bd6..e2f7b31 100644 --- a/src/qemu/qemu_conf.c +++ b/src/qemu/qemu_conf.c @@ -133,16 +133,21 @@ int qemudLoadDriverConfig(struct qemud_driver *driver, /* Just check the file is readable before opening it, otherwise * libvirt emits an error. */ - if (access (filename, R_OK) == -1) return 0; + if (access (filename, R_OK) == -1) { + VIR_INFO("Could not read qemu config file %s", filename); + return 0; + } conf = virConfReadFile (filename, 0); - if (!conf) return 0; + if (!conf) { + return -1; + } #define CHECK_TYPE(name,typ) if (p && p->type != (typ)) { \ qemuReportError(VIR_ERR_INTERNAL_ERROR, \ - "remoteReadConfigFile: %s: %s: expected type " #typ, \ - filename, (name)); \ + "%s: %s: %s: expected type " #typ, \ + __func__, filename, (name)); \ virConfFree(conf); \ return -1; \ } -- 1.6.6.1

4 5

[libvirt] [PATCH] udev: Parse PCI devices even if libpciaccess fails
by Cole Robinson 02 Jul '10

02 Jul '10

We only use libpciaccess for resolving device product/vendor. If initializing the library fails (say if using qemu:///session), don't warn so loudly, and carry on as usual. Signed-off-by: Cole Robinson <crobinso(a)redhat.com> --- src/node_device/node_device_udev.c | 9 ++++++--- 1 files changed, 6 insertions(+), 3 deletions(-) diff --git a/src/node_device/node_device_udev.c b/src/node_device/node_device_udev.c index 73217c5..f872483 100644 --- a/src/node_device/node_device_udev.c +++ b/src/node_device/node_device_udev.c @@ -363,12 +363,15 @@ static int udevTranslatePCIIds(unsigned int vendor, char **vendor_string, char **product_string) { - int ret = -1; + int ret = -1, pciret; struct pci_id_match m; const char *vendor_name = NULL, *device_name = NULL; - if (pci_system_init() != 0) { - VIR_ERROR0(_("Failed to initialize libpciaccess")); + if ((pciret = pci_system_init()) != 0) { + char ebuf[1024]; + VIR_INFO("Failed to initialize libpciaccess: %s", + virStrerror(pciret, ebuf, sizeof ebuf)); + ret = 0; goto out; } -- 1.6.6.1

2 3

[libvirt] [PATCH v2 REPOST 0/8]: Add arbitrary qemu command-line and monitor commands
by Chris Lalancette 02 Jul '10

02 Jul '10

As we discussed previously, here is the patch series to add the ability to specify arbitrary qemu command-line parameters and environment variables, and also give arbitrary monitor commands to a guest. Because these extra arguments have a good shot at confusing libvirt, the use of them is not supported, but left available for advanced users and developers. They are also in a separate library and have a separate on-the-wire protocol. There is one bug left that I have not yet been able to fix. Because of the complicated way that virsh parses command-line arguments, it is not possible to pass through spaces and quotes when using the qemu-monitor-command. Unfortunately, the qemu monitor commands (and in particular when using QMP) depend heavily on quoting and spacing, so using virsh to send through command-lines is difficult. I'll have to think about how to better resolve this issue, but it should not hold up the rest of the series. I will point out one particular patch that could use some careful review, namely PATCH 6/8. In there, I change the remote_message_hdr to use an unsigned proc instead of a remote_procedure proc. Now, as far as I can tell the two sizes should be the same, so the wire protocol should be the same. Indeed, testing seems to show that older virsh can talk just fine to a libvirtd with this patch applied. However, the regenerated remote_protocol.c file for parsing remote_message_header has some strange bits in it that I don't quite understand. I'm hoping someone else can look at it and confirm that it is OK. Thanks to Dan Berrange and Eric Blake for their reviews already, and to DV for the Relax NG schema changes. Changes since v1 are listed in the individual patches.

2 25

[libvirt] ANNOUNCE: ruby-libvirt bindings 0.2.0
by Chris Lalancette 02 Jul '10

02 Jul '10

Hello all, I'm pleased to announce the release of 0.2.0 of the ruby-libvirt bindings. This release has a number of new features: - Updated Storage class, implementing pool.active?, pool.persistent?, pool.vol_create_xml_from - Updated Connect class, implementing conn.node_free_memory, conn.node_cells_free_memory, conn.node_get_security_model, conn.encrypted?, conn.libversion, and conn.secure? - Updated Network class, implementing network.active? and network.persistent? - Update Domain class, implementing conn.domain_xml_from_native, conn.domain_xml_to_native, dom.migrate_to_uri, dom.migrate_set_max_downtime, dom.managed_save, dom.has_managed_save?, dom.managed_save_remove, dom.security_label, dom.block_stats, dom.memory_stats, dom.blockinfo, dom.block_peek, dom.memory_peek, dom.active?, dom.persistent?, dom.snapshot_create_xml, dom.num_of_snapshots, dom.list_snapshots, dom.lookup_snapshot_by_name, dom.has_current_snapshot?, dom.revert_to_snapshot, dom.current_snapshot, snapshot.xml_desc, snapshot.delete, dom.job_info, and dom.abort_job - Implementation of the NodeDevice class - Implementation of the Secret class - Implementation of the NWFilter class - Implementation of the Interface class - Conversion of the development tree to git - New maintainer (me). David Lutterkort has agreed to transfer maintainership of the bindings over to me, since he is not actively involved in their development anymore. With the above list, almost all of the APIs up to and including libvirt 0.8.1 are covered. There are a few that I have not yet had time to implement; you can look at the list of FIXMEs in the source code to find them. I've uploaded new tarballs and source RPMs to: http://libvirt.org/ruby/download/ The new git repo is here: http://libvirt.org/git/?p=ruby-libvirt.git;a=summary The documentation for the new API's are here: http://libvirt.org/ruby/api/index.html If you have time, and are interested in the bindings, please give these new ones a whirl and let me know if they work for you. As usual, if you have any questions, problems, patches, or bug reports, feel free to email the libvirt development list (and CC me) so that I can take a look at them. -- Chris Lalancette

2 1

Re: [libvirt] Documentation for synchronous hooks
by Jintao Yang 02 Jul '10

02 Jul '10

hi DV, I saw the changelog of 0.7.8, which told the hooks scripts are supported. but is it took away in 0.8.0-4? [root@dhcp-66-70 libvirt]# rpm -ql libvirt | grep etc /etc/libvirt /etc/libvirt/libvirtd.conf /etc/libvirt/lxc.conf /etc/libvirt/nwfilter /etc/libvirt/nwfilter/allow-arp.xml /etc/libvirt/nwfilter/allow-dhcp-server.xml /etc/libvirt/nwfilter/allow-dhcp.xml /etc/libvirt/nwfilter/allow-incoming-ipv4.xml /etc/libvirt/nwfilter/allow-ipv4.xml /etc/libvirt/nwfilter/clean-traffic.xml /etc/libvirt/nwfilter/no-arp-spoofing.xml /etc/libvirt/nwfilter/no-ip-multicast.xml /etc/libvirt/nwfilter/no-ip-spoofing.xml /etc/libvirt/nwfilter/no-mac-broadcast.xml /etc/libvirt/nwfilter/no-mac-spoofing.xml /etc/libvirt/nwfilter/no-other-l2-traffic.xml /etc/libvirt/qemu /etc/libvirt/qemu.conf /etc/libvirt/qemu/networks /etc/libvirt/qemu/networks/autostart /etc/logrotate.d/libvirtd.lxc /etc/logrotate.d/libvirtd.qemu /etc/rc.d/init.d/libvirtd /etc/sysconfig/libvirtd [root@dhcp-66-70 libvirt]# rpm -q libvirt libvirt-0.8.0-4.el6.x86_64 Regards osier ----- Original Message ----- From: "Daniel Veillard" <veillard(a)redhat.com> To: libvir-list(a)redhat.com Sent: Monday, April 12, 2010 11:16:27 PM GMT +08:00 Beijing / Chongqing / Hong Kong / Urumqi Subject: [libvirt] Documentation for synchronous hooks Was still missing from main commits and would be needed for 0.8.0 Add documentation for synchronous hooks * docs/sitemap.html.in: add in navigation under Documentation/Deployment/Hooks * docs/hooks.html.in: new doc describing current support for 0.8.0 diff --git a/docs/hooks.html.in b/docs/hooks.html.in new file mode 100644 index 0000000..4ebeec3 --- /dev/null +++ b/docs/hooks.html.in @@ -0,0 +1,71 @@ +<?xml version="1.0"?> +<html> + <body> + <h1>Hooks for specific system management</h1> + Libvirt includes synchronous hooks starting from version 0.8.0, + this is a way to tie specific tailored system actions at specific + time. This is based on scripts being called on the Host where the + hypervisor is running, if the script is present when the libvirtd + daemon is doing some significant actions. + The scripts are expected to execute quickly, return a zero exit + status if all conditions are set for the daemon to continue the + action (non zero will be considered a failure which may + be ignored but in general will stops the ongoing operation). + The script also should not call back into libvirt as the daemon + is waiting for the script exit and deadlock is likely to occur + otherwise. + The scripts are stored in the directory <code>/etc/libvirt/hooks/</code> + when using a standard installation path + (<code>$SYSCONF_DIR/libvirt/hook/</code> in general). + The scripts gets arguments as parameter on their command line: + <ul> + <li> the first argument is the name of the object involved in the + operation or '-' if there is none. + <li> the second argument is the name of the operation. + <li> the third argument is a suboperation indication like 'start' + 'end' or '-' if there is none. + <li> the last argument is an extra argument string or '-' if there + is none. + </ul> + There is currently scripts for 3 domains of operation: + <ul> + <li><code>/etc/libvirt/hooks/daemon</code> script if + present is called at 3 points in time: + at daemon startup, typically started with the following + arguments: + <pre>/etc/libvirt/hooks/daemon - start - start</pre> + at daemon shutdown when it is about to exit, with the following + arguments: + <pre>/etc/libvirt/hooks/daemon - shutdown - shutdown</pre> + When the daemon is asked to reload its driver state when + receiving the SIGHUP signal, arguments are: + <pre>/etc/libvirt/hooks/daemon - reload begin SIGHUP</pre> + </li> + <li><code>/etc/libvirt/hooks/qemu</code> script and + <code>/etc/libvirt/hooks/lxc</code> to associate hooks for domain + operation on the respective QEmu/KVM and LXC drivers. + The domain related hooks also receive the full XML description + for the concerned domain on their stdin, which allows to get + all the informations from the domain, including UUID or storage + if that is needed for the script operation. + Currently only domain startup and domain end operations + involve the hook, the first one just before the domain gets + created. + For example if starting a QEmu domain named <code>test</code> + the following script will get called: + <pre>/etc/libvirt/hooks/qemu test start begin -</pre> + note that a non-zero return value from the script will abort the + domain startup operation, and if an error string is passed on + stderr by the hook script, it will be provided back to the user + at the libvirt API level. + For domain shutdown, the script will be called just after the + domain has finished execution, and the script will get: + <pre>/etc/libvirt/hooks/qemu test stopped end -</pre> + It is expected that other operation will be associated to hooks + but at the time of 0.8.0 only those 2 are associated to domains + lifecycle + </li> + </ul> + + </body> +</html> diff --git a/docs/sitemap.html.in b/docs/sitemap.html.in index 0c3f0c3..0117c8d 100644 --- a/docs/sitemap.html.in +++ b/docs/sitemap.html.in @@ -50,6 +50,10 @@ <a href="logging.html">Logging</a> The library and the daemon logging support </li> + <li> + <a href="hooks.html">Hooks</a> + Hooks for system specific management + </li> </ul> </li> <li> -- 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/ -- libvir-list mailing list libvir-list(a)redhat.com https://www.redhat.com/mailman/listinfo/libvir-list

5 6

Re: [libvirt] [libvirt-users] C API example
by Dave Allan 02 Jul '10

02 Jul '10

On Thu, Jul 01, 2010 at 01:43:55PM -0700, steven765(a)yahoo.com wrote: > Hi Dave, > Thanks for the reply after getting some sleep the question I should have asked is what libraries do I need to link the application against? If I just try gcc -o a.out hellolibvirt.c it can't find any of the libvirt calls. [cc'ing the list again so the answer gets archived] Libvirt's no different from any other library, you need to link against libvirt, and you need to have the libvirt headers installed. On Fedora, that's: yum install libvirt-devel If you want to build hellolibvirt without using make, you'll need to edit hellolibvirt.c and take out config.h, which is unused. Then you can do: gcc -o hellolibvirt -lvirt hellolibvirt.c Then you just need to learn the API and decide what you want to do with it. ;-) The API is documented at: http://libvirt.org/html/libvirt-libvirt.html Dave > Thanks, > Steve > > --- On Thu, 7/1/10, Dave Allan <dallan(a)redhat.com> wrote: > > > From: Dave Allan <dallan(a)redhat.com> > > Subject: Re: [libvirt-users] C API example > > To: steven765(a)yahoo.com > > Cc: "Justin Clift" <justin(a)salasaga.org>, libvirt-users(a)redhat.com > > Date: Thursday, July 1, 2010, 2:06 PM > > On Wed, Jun 30, 2010 at 07:37:27PM > > -0700, steven765(a)yahoo.com > > wrote: > > > I think so, but I'm locked out at home. I'll have to > > try at school tomorrow. It gave me a remote error, but > > with the correct directory so fingers crossed thanks! > > > > > > > > btw might you or anyone know what I have to include to > > start a clean project of my own? So if I want to just > > build an application that uses the API with nothing else but > > what's necessary? > > > > If you're talking about a C application, you're pretty much > > describing > > hellolibvirt. I tried to put enough in there to > > demonstrate a couple > > of different calls, but hopefully not so much that it's > > overwhelming. > > If it seems like there's a lot there, cut some of it > > out. You don't > > need the showDomains function, for example. Remove > > it, compile and > > see what happens. > > > > Dave > > > > > > > Thanks, > > > Steve > > > > > > --- On Wed, 6/30/10, Justin Clift <justin(a)salasaga.org> > > wrote: > > > > > > > From: Justin Clift <justin(a)salasaga.org> > > > > Subject: Re: [libvirt-users] C API example > > > > To: "Dave Allan" <dallan(a)redhat.com> > > > > Cc: steven765(a)yahoo.com, > > libvirt-users(a)redhat.com > > > > Date: Wednesday, June 30, 2010, 10:09 PM > > > > On 07/01/2010 11:54 AM, Dave Allan > > > > wrote: > > > > <snip> > > > > > ./hellolibvirt \ > > > > > > > > > > > qemu+unix:///system?socket=/var/run/libvirt/libvirt-sock > > > > > > > > Thanks Dave. The +unix:// and ?socket=xxx bits > > are > > > > what I'd not been picking up on. Should be good > > now. > > > > > > > > Steven, is it working for you? > > > > > > > > Regards and best wishes, > > > > > > > > Justin Clift > > > > > > > > -- Salasaga - Open Source eLearning IDE > > > > http://www.salasaga.org > > > > > > > > > > > > > > > > > >

1 0

[libvirt] [PATCH] ruby-libvirt: virNodeGetFreeMemory and virGetLibVersion
by Jaromír Červenka 02 Jul '10

02 Jul '10

Author is Michal Hrušecký <mhrusecky(a)suse.cz>. He was unsure about second patch, maybe adds duplicate functionality, please check it. Greetings, Jaromir.

3 2

[libvirt] make check fails on CentOS 5
by Daniel Berteaud 02 Jul '10

02 Jul '10

Hi. I'm using libvirt on a CentOS 5.4 x86_64 host without issue, until libvirt 0.8.1. I usually just rebuild the available src rpm with the following args: --without xen --without xen-proxy \ --without lxc --without vbox --without esx \ --without phyp --without one --without avahi \ --without openvz --without uml (I only use KVM) But, with libvirt 0.8.1, the buiild process now include make check, and one of the check fails: interfaceschematest Attached is the full build log, you can see the failure line 1841. I really don't know how to debug this. For now, I've just added interfaceschematest to the list of check to skip in the spec file (for i in nodeinfotest daemon-conf seclabeltest interfaceschematest). With this modification, everything works, and I'm actually using it this way. Anybody knows why this test fails ? Regards, Daniel -- Daniel Berteaud FIREWALL-SERVICES SARL. Société de Services en Logiciels Libres Technopôle Montesquieu 33650 MARTILLAC Tel : 05 56 64 15 32 Fax : 05 56 64 15 32 Mail: daniel(a)firewall-services.com Web : http://www.firewall-services.com

3 3

[libvirt] Ask for help about libvirt error: can't get physical interface data for kvm.
by Feng Dan Liu 01 Jul '10

01 Jul '10

Hi I find this mail address from the internet and hope I can get the reply from anyone of you, that will be very appreciated. I'm using virsh to manage the KVM(qemu-kvm 0.12.4, libvirt 0.8.1), but I encounter an error as below: I saw both libvirt api and virsh commands support to get the physical interfaces data, but it always fail when I using them for KVM hypervisor. I was thought that it was due to the old version of libvirt/KVM hypervisor, but the error still exist when using the latest libvirt and kvm hypervisor. So I wonder if the following functions of libvirt haven't been implemented for KVM, could you pls help me get the answer about this? Thanks in advance! virConnectListInterfaces virConnectNumOfDefinedInterfaces virConnectNumOfInterfaces virConnectListDefinedInterfaces virInterfaceLookupByName Best Regards, Fengdan Liu Tivoli ITCAM Solution, IBM China Software Development Lab, Tel: 13811762746 Email: liufengd(a)cn.ibm.com 3/F, Haohai Bldg., No.7, 5th Street, Shangdi, Haidian District, Beijing 100085, P.R.China

2 2

[libvirt] Maintenance of ruby bindings
by Neil Wilson 01 Jul '10

01 Jul '10

Hi, Is there anybody looking after the Ruby bindings? Are you still taking patches? It seems quite out of date wrt. the current interface. Rgs Neil Wilson

4 6