- Devel - libvirt List Archives

[libvirt] [PATCH] docs: revamp api_extension example, using vcpu patch series
by Eric Blake 28 Oct '10

28 Oct '10

Complete patch is compressed and attached, because it is so large. But the bulk of it consisted mainly of running 'git format-patch -15 b0137887' to pick up the top of my vcpu series, then replacing the contents of docs/api_extension/ with the new patches. The meat of the patch is the overview html file, copied here if you don't want to unzip the attachment: 2010-10-20 Eric Blake <eblake(a)redhat.com> docs: revamp api_extension example, using vcpu patch series * docs/api_extension/*: Replace example files. * docs/api_extension.html.in: Rewrite to match new example files. diff --git c/docs/api_extension.html.in w/docs/api_extension.html.in index de6eedc..1396e91 100644 --- c/docs/api_extension.html.in +++ w/docs/api_extension.html.in @@ -10,8 +10,12 @@ <p> This document walks you through the process of implementing a new - API in libvirt. It uses as an example the addition of the node device - create and destroy APIs. + API in libvirt. It uses as an example the addition of + separating maximum from current vcpu usage of a domain. + Remember that new API includes any new public functions, but it + also includes addition of flags or extension of XML used through + existing functions. The example in this document adds both + types of API, and not all extensions require quite as many patches. </p> <p> @@ -23,7 +27,12 @@ added to libvirt. Someone may already be working on the feature you want. Also, recognize that everything you write is likely to undergo significant rework as you discuss it with the other developers, so - don't wait too long before getting feedback. + don't wait too long before getting feedback. In the vcpu example + below, list feedback was first requested + <a href="https://www.redhat.com/archives/libvir-list/2010-September/msg00423.html">here</a>, + and resulted in several rounds of improvements before coding + began, and this example is slightly rearranged from the actual + order of the commits. </p> <p> @@ -46,11 +55,22 @@ <li>define the public API</li> <li>define the internal driver API</li> <li>implement the public API</li> - <li>define the wire protocol format</li> - <li>implement the RPC client</li> - <li>implement the server side dispatcher</li> - <li>implement the driver methods</li> + <li>implement the remote protocol: + <ol> + <li>define the wire protocol format</li> + <li>implement the RPC client</li> + <li>implement the server side dispatcher</li> + </ol> + </li> + <li>use new API where appropriate in drivers</li> <li>add virsh support</li> + <li>add common handling for new API</li> + <li>for each driver that can support the new API: + <ol> + <li>add prerequisite support</li> + <li>fully implement new API</li> + </ol> + </li> </ol> <p> @@ -66,11 +86,10 @@ functionality--get the whole thing working and make sure you're happy with it. Then use git or some other version control system that lets you rewrite your commit history and break patches into pieces so you - don't drop a big blob of code on the mailing list at one go. For - example, I didn't follow my own advice when I originally submitted the - example code to the libvirt list but rather submitted it in several - large chunks. I've used git's ability to rewrite my commit history to - break the code apart into the example patches shown. + don't drop a big blob of code on the mailing list at one go. + The example code used in this document was rebased several + times between the original list posting and the final committed + version. </p> <p> @@ -86,9 +105,23 @@ <h2><a name='publicapi'>Defining the public API</a></h2> - <p>The first task is to define the public API and add it to:</p> + <p>The first task is to define the public API. If the addition + involves XML, this includes enhancing the RelaxNG schema and + documenting the new elements or attributes:</p> - <p><code>include/libvirt/libvirt.h.in</code></p> + <p><code> + docs/schemas/domain.rng<br/> + docs/formatdomain.html.in + </code></p> + + <p>If the addition involves a new function, this involves adding + a declaration in the public header, and arranging to export the + symbol:</p> + + <p><code> + include/libvirt/libvirt.h.in + src/libvirt_public.syms + </code></p> <p> This task is in many ways the most important to get right, since once @@ -99,12 +132,9 @@ rework it as you go through the process of implementing it. </p> - <p>Once you have defined the API, you have to add the symbol names to:</p> - - <p><code>src/libvirt_public.syms</code></p> - - <p class="example">See <a href="api_extension/0001-Step-1-of-8-Define-the-public-API.patch">0001-Step-1-of-8-Define-the-public-API.patch</a> for example code.</p> - + <p class="example">See <a href="api_extension/0001-Step-1-of-15-add-to-xml.patch">0001-Step-1-of-15-add-to-xml.patch</a> + and <a href="api_extension/0002-Step-2-of-15-add-new-public-API.patch">0002-Step-2-of-15-add-new-public-API.patch</a> + for example code.</p> <h2><a name='internalapi'>Defining the internal API</a></h2> @@ -118,7 +148,7 @@ <p> Of course, it's possible that the new API will involve the creation of - an entire new driver type, in which case the changes will include the + an entirely new driver type, in which case the changes will include the creation of a new struct type to represent the new driver type. </p> @@ -129,10 +159,11 @@ <p> To define the internal API, first typedef the driver function prototype and then add a new field for it to the relevant driver - struct. + struct. Then, update all existing instances of the driver to + provide a <code>NULL</code> stub for the new function. </p> - <p class="example">See <a href="api_extension/0002-Step-2-of-8-Define-the-internal-driver-API.patch">0002-Step-2-of-8-Define-the-internal-driver-API.patch</a></p> + <p class="example">See <a href="api_extension/0003-Step-3-of-15-define-internal-driver-API.patch">0003-Step-3-of-15-define-internal-driver-API.patch</a></p> <h2><a name='implpublic'>Implementing the public API</a></h2> @@ -166,16 +197,23 @@ <p><code>src/libvirt.c</code></p> - <p class="example">See <a href="api_extension/0003-Step-3-of-8-Implement-the-public-API.patch">0003-Step-3-of-8-Implement-the-public-API.patch</a></p> + <p class="example">See <a href="api_extension/0004-Step-4-of-15-implement-the-public-APIs.patch">0004-Step-4-of-15-implement-the-public-APIs.patch</a></p> + + <h2><a name='remoteproto'>Implementing the remote protocol</a></h2> + + <p> + Implementing the remote protocol is essentially a + straightforward exercise which is probably most easily + understood by referring to the existing code and the example + patch. It involves several related changes, followed by + regenerating derived files.</p> + <p class="example">See <a href="api_extension/0005-Step-5-of-15-implement-the-remote-protocol.patch">0005-Step-5-of-15-implement-the-remote-protocol.patch</a></p> - <h2><a name='wireproto'>Defining the wire protocol format</a></h2> + <h3><a name='wireproto'>Defining the wire protocol format</a></h3> <p> - Defining the wire protocol is essentially a straightforward exercise - which is probably most easily understood by referring to the existing - remote protocol wire format definitions and the example patch. It - involves making two additions to: + Defining the wire protocol involves making additions to: </p> <p><code>src/remote/remote_protocol.x</code></p> @@ -185,7 +223,7 @@ to the API. One struct describes the parameters to be passed to the remote function, and a second struct describes the value returned by the remote function. The one exception to this rule is that functions - that return only integer status do not require a struct for returned + that return only 0 or -1 for status do not require a struct for returned data. </p> @@ -194,23 +232,19 @@ added to the API. </p> - <p class="example">See <a href="api_extension/0004-Step-4-of-8-Define-the-wire-protocol-format.patch">0004-Step-4-of-8-Define-the-wire-protocol-format.patch</a></p> - <p> Once these changes are in place, it's necessary to run 'make rpcgen' in the src directory to create the .c and .h files required by the remote protocol code. This must be done on a Linux host using the GLibC rpcgen program. Other rpcgen versions may generate code which - results in bogus compile time warnings + results in bogus compile time warnings. </p> - - <h2><a name='rpcclient'>Implement the RPC client</a></h2> + <h3><a name='rpcclient'>Implement the RPC client</a></h3> <p> - Implementing the RPC client is also relatively mechanical, so refer to - the exising code and example patch for guidance. The RPC client uses - the rpcgen generated .h files. The remote method calls go in: + Implementing the uses the rpcgen generated .h files. The remote + method calls go in: </p> <p><code>src/remote/remote_internal.c</code></p> @@ -227,17 +261,10 @@ <li>unlocks the remote driver.</li> </ol> - <p> - Once you have created the remote method calls, you have to add fields - for them to the driver structs for the appropriate remote driver. - </p> - - <p class="example">See <a href="api_extension/0005-Step-5-of-8-Implement-the-RPC-client.patch">0005-Step-5-of-8-Implement-the-RPC-client.patch</a></p> - - <h2><a name="serverdispatch">Implement the server side dispatcher</a></h2> + <h3><a name="serverdispatch">Implement the server side dispatcher</a></h3> <p> - Implementing the server side of the remote function calls is simply a + Implementing the server side of the remote function call is simply a matter of deserializing the parameters passed in from the remote caller and passing them to the corresponding internal API function. The server side dispatchers are implemented in: @@ -247,8 +274,65 @@ <p>Again, this step uses the .h files generated by make rpcgen.</p> - <p class="example">See <a href="api_extension/0006-Step-6-of-8-Implement-the-server-side-dispatcher.patch">0006-Step-6-of-8-Implement-the-server-side-dispatcher.patch</a></p> + <p> + After all three pieces of the remote protocol are complete, and + the generated files have been updated, it will be necessary to + update the file:</p> + + <p><code>src/remote_protocol-structs</code></p> + + <p> + This file should only have new lines added; modifications to + existing lines probably imply a backwards-incompatible API change. + </p> + + <p class="example">See <a href="api_extension/0005-Step-5-of-15-implement-the-remote-protocol.patch">0005-Step-5-of-15-implement-the-remote-protocol.patch</a></p> + + <h2><a name="internaluseapi">Use the new API internally</a></h2> + + <p> + Many times, a new API is merely an extension of existing + concepts that accomplished a subset of the same actions. When + this is the case, it makes sense to share a common + implementation by making the older API become a trivial wrapper + around the new API, rather than duplicating the common code. + This step should not introduce any semantic differences for the + old API. This step is optional if the new API has no relation + to existing API. + </p> + + <p class="example">See <a href="api_extension/0006-Step-6-of-15-make-old-API-trivially-wrap-to-new-API.patch">0006-Step-6-of-15-make-old-API-trivially-wrap-to-new-API.patch</a></p> + + <h2><a name="virshuseapi">Expose the new API in virsh</a></h2> + + <p> + All new API should be manageable from the virsh command line + shell. This proves that the API is sufficient for the purpose, + and makes it possible to identify if the proposed API needs slight + changes for easier usage. However, remember that virsh is used + to connect to hosts running older versions of libvirtd, so the + new commands should have fallbacks to the older API when + possible; implementing the virsh hooks at this point makes it + very easy to test these fallbacks. Also remember to document + virsh additions. + </p> + + <p> + A virsh command is composed of a few pieces of code. You need to + define an array of vshCmdInfo structs for each new command that + contain the help text and the command description text. You also need + an array of vshCmdOptDef structs to describe the command options. + Once you have those pieces of data in place you can write the function + implementing the virsh command. Finally, you need to add the new + command to the commands[] array. The following files need changes: + </p> + <p><code> + tools/virsh.c<br/> + tools/virsh.pod + </code></p> + + <p class="example">See <a href="api_extension/0007-Step-7-of-15-add-virsh-support.patch">0007-Step-7-of-15-add-virsh-support.patch</a></p> <h2><a name="driverimpl">Implement the driver methods</a></h2> @@ -261,42 +345,72 @@ adding. </p> + <h3><a name="commonimpl">Implement common handling</a></h3> + <p> - In the example code, the extension is only an additional two function - calls in the node device API, so most of the new code is additions to - existing files. The only new files are there for multi-platform - implementation convenience, as some of the new code is Linux specific. + If the new API is applicable to more than one driver, it may + make sense to provide some utility routines, or to factor some + of the work into the dispatcher, to avoid reimplementing the + same code in every driver. In the example code, this involved + adding a member to the virDomainDefPtr struct for mapping + between the XML API addition and the in-memory representation of + a domain, along with updating all clients to use the new member. + Up to this point, there have been no changes to existing + semantics, and the new APIs will fail unless they are used in + the same way as the older API wrappers. </p> + <p class="example">See <a href="api_extension/0008-Step-8-of-15-support-new-xml.patch">0008-Step-8-of-15-support-new-xml.patch</a></p> + + <h3><a name="drivercode">Implement driver handling</a></h3> + <p> - The example code is probably uninteresting unless you're concerned - with libvirt storage, but I've included it here to show how new files - are added to the build environment. + The remaining patches should only touch one driver at a time. + It is possible to implement all changes for a driver in one + patch, but for review purposes, it may still make sense to break + things into simpler steps. Here is where the new APIs finally + start working. </p> - <p class="example">See <a href="api_extension/0007-Step-7-of-8-Implement-the-driver-methods.patch">0007-Step-7-of-8-Implement-the-driver-methods.patch</a></p> + <p> + In the example patches, three separate drivers are supported: + test, qemu, and xen. It is always a good idea to patch the test + driver in addition to the target driver, to prove that the API + can be used for more than one driver. The example updates the + test driver in one patch: + </p> - <h2><a name="virsh">Implement virsh commands</a></h2> + <p class="example">See <a href="api_extension/0009-Step-9-of-15-support-all-flags-in-test-driver.patch">0009-Step-9-of-15-support-all-flags-in-test-driver.patch</a></p> <p> - Once you have the new functionality in place, the easiest way to test - it and also to provide it to end users is to implement support for it - in virsh. + The qemu changes were easier to split into two phases, one for + updating the mapping between the new XML and the hypervisor + command line arguments, and one for supporting all possible + flags of the new API: </p> + <p class="example">See <a href="api_extension/0010-Step-10-of-15-improve-vcpu-support-in-qemu-command-line.patch">0010-Step-10-of-15-improve-vcpu-support-in-qemu-command-line.patch</a> + and <a href="api_extension/0011-Step-11-of-15-complete-vcpu-support-in-qemu-driver.patch">0011-Step-11-of-15-complete-vcpu-support-in-qemu-driver.patch</a></p> + <p> - A virsh command is composed of a few pieces of code. You need to - define an array of vshCmdInfo structs for each new command that - contain the help text and the command description text. You also need - an array of vshCmdOptDef structs to describe the command options. - Once you have those pieces of data in place you can write the function - implementing the virsh command. Finally, you need to add the new - command to the commands[] array. + Finally, the example breaks the xen driver changes across four + patches, mapping the XML changes to the hypervisor command + lines, implementing the getter API independently of the setter + API, and cleanup of up code rendered dead by the new API: </p> - <p class="example">See <a href="api_extension/0008-Step-8-of-8-Add-virsh-support.patch">0008-Step-8-of-8-Add-virsh-support.patch</a></p> + <p class="example">See <a href="api_extension/0012-Step-12-of-15-improve-vcpu-support-in-xen-command-line.patch">0012-Step-12-of-15-improve-vcpu-support-in-xen-command-line.patch</a>, + <a href="api_extension/0013-Step-13-of-15-improve-support-for-getting-xen-vcpu-counts.patch">0013-Step-13-of-15-improve-support-for-getting-xen-vcpu-counts.patch</a>, + <a href="api_extension/0014-Step-14-of-15-improve-support-for-setting-xen-vcpu-counts.patch">0014-Step-14-of-15-improve-support-for-setting-xen-vcpu-counts.patch</a>, + and <a href="api_extension/0015-Step-15-of-15-remove-dead-xen-code.patch">0015-Step-15-of-15-remove-dead-xen-code.patch</a></p> + + <p> + The exact details of the example code are probably uninteresting + unless you're concerned with virtual cpu management. + </p> <p>Once you have working functionality, run make check and make - syntax-check before generating patches.</p> + syntax-check on each patch of the series before submitting + patches.</p> </body> </html> -- Eric Blake eblake(a)redhat.com +1-801-349-2682 Libvirt virtualization library http://libvirt.org

5 12

[libvirt] [PATCH] docs: reworded and reordered the bindings page, plus minor tweaks
by Justin Clift 28 Oct '10

28 Oct '10

Reordered the bindings into alphabetical order, added a link to the php-libvirt source on Github, plus gave the direct package names needed for Python usage on RHEL/Fedora, and Ubuntu. --- At some point the "Windows" statement on this page should be reworded or made a bit neater too. Not just yet though. :) docs/bindings.html.in | 62 +++++++++++++++++++++++++++++++++--------------- 1 files changed, 42 insertions(+), 20 deletions(-) diff --git a/docs/bindings.html.in b/docs/bindings.html.in index 0bc997e..7a90ad6 100644 --- a/docs/bindings.html.in +++ b/docs/bindings.html.in @@ -4,42 +4,64 @@ <h1 >Bindings for other languages</h1> <p> - Libvirt comes with bindings to support other languages than - pure <strong>C</strong>. First the headers embeds the necessary - declarations to allow direct access from <strong>C++</strong> - code, but also we have bindings for higher level kind of languages: + Libvirt supports C and C++ directly, and has bindings available + for other languages: </p> <ul> <li> - <strong>Python</strong>: Libvirt comes with direct support for - the Python language (just make sure you installed the libvirt-python - package if not compiling from sources). See below for more - information about using libvirt with python + <strong>C#</strong>: Arnaud Champion develops + <a href="csharp.html">C# bindings</a>. </li> <li> - <strong>Perl</strong>: Daniel Berrange provides - <a href="http://search.cpan.org/dist/Sys-Virt/">bindings for Perl</a>. + <strong>Java</strong>: Daniel Veillard develops + <a href="java.html">Java bindings</a>. </li> <li> - <strong>OCaml</strong>: Richard Jones supplies - <a href="http://libvirt.org/ocaml/">bindings for OCaml</a>. + <strong>OCaml</strong>: Richard Jones develops + <a href="http://libvirt.org/ocaml/">OCaml bindings</a>. </li> <li> - <strong>Ruby</strong>: David Lutterkort provides - <a href="http://libvirt.org/ruby/">bindings for Ruby</a>. + <strong>Perl</strong>: Daniel Berrange develops + <a href="http://search.cpan.org/dist/Sys-Virt/">Perl bindings</a>. </li> <li> - <strong>Java</strong>: Daniel Veillard maintains - <a href="java.html">Java bindings</a>. + <p> + <strong>PHP</strong>: Radek Hladik develops + <a href="http://phplibvirt.cybersales.cz/">PHP bindings</a>. + </p> + <p> + The php-libvirt bindings also have their source online + <a href="http://github.com/Kedarius/php-libvirt">here in Github</a>. + </p> + <p> + This allows you to easily see the code, make comments on it, + create your own forks, and contribute the changes back. + </p> </li> <li> - <strong>C#</strong>: Arnaud Champion maintains - <a href="csharp.html">C# bindings</a>. + <p> + <strong>Python</strong>: Libvirt comes with direct support for + the Python language. + </p> + <p> + If your libvirt is installed as packages, rather than compiled + by you from source code, ensure you have the appropriate + package installed. + </p> + <p> + This is named <b>libvirt-python</b> on RHEL/Fedora, + <a href="http://packages.ubuntu.com/search?keywords=python-libvirt"><b>python-libvirt</b></a> + on Ubuntu, and may be named differently on others. + </p> + <p> + For usage information, see the + <a href="python.html">Python API bindings</a> page. + </p> </li> <li> - <strong>PHP</strong>: Radek Hladik is developing - <a href="http://phplibvirt.cybersales.cz/">PHP bindings</a>. + <strong>Ruby</strong>: David Lutterkort develops + <a href="http://libvirt.org/ruby/">Ruby bindings</a>. </li> </ul> -- 1.7.2.3

2 2

[libvirt] [PATCH] mingw: Add body for virFork and remove double virDriverLoadModule export
by Matthias Bolte 27 Oct '10

27 Oct '10

Commit 9bd3cce0d2d54e6ab893bb8137218b83d9294714 added virFork and virDriverLoadModule to libvirt_private.syms, but virFork didn't have a body on Win32 and virDriverLoadModule was already correctly exported conditional via libvirt_driver_modules.syms. --- src/libvirt_private.syms | 4 ---- src/util/util.c | 9 +++++++++ 2 files changed, 9 insertions(+), 4 deletions(-) diff --git a/src/libvirt_private.syms b/src/libvirt_private.syms index 1a71e79..670e9f2 100644 --- a/src/libvirt_private.syms +++ b/src/libvirt_private.syms @@ -314,10 +314,6 @@ virDomainConfNWFilterTeardown; virDomainConfVMNWFilterTeardown; -# driver.h -virDriverLoadModule; - - # ebtables.h ebtablesAddForwardAllowIn; ebtablesAddForwardPolicyReject; diff --git a/src/util/util.c b/src/util/util.c index 586baee..fd4d6d4 100644 --- a/src/util/util.c +++ b/src/util/util.c @@ -927,6 +927,15 @@ virExecDaemonize(const char *const*argv ATTRIBUTE_UNUSED, return -1; } +int +virFork(pid_t *pid) +{ + *pid = -1; + errno = ENOTSUP; + + return -1; +} + # endif /* WIN32 */ int -- 1.7.0.4

2 2

[libvirt] [libvirt-csharp][PATCH] add new sample "virEventRegisterImpl"
by arnaud.champion＠devatom.fr 27 Oct '10

27 Oct '10

?Hi, this patch add a new sample code for Visual Studio and Mono. The sample show how to use domain callbacks via virEventRegisterImpl (he old way, deprecated method for domain events). Regards, Arnaud

2 1

[libvirt] [libvirt-csharp][PATCH] Make examples works on mono compiled in 64 bits, simply the ConnectOpenAuth process, and finalise renaming
by arnaud.champion＠devatom.fr 27 Oct '10

27 Oct '10

?Hi, I have finally find the problem with examples on mono compiled in 64 bits. The problem was the "ToInt32" method of an IntPtr which failed on mono 64 bits (have to use ToInt64 instead). This path solve this problem. Also, I have put marshaling complexity of the ConnectOpenAuth callback in bindings, this make the callback of ConnectOpenAuth more simple to achieve the authentification. In the example, the callback is treated like this : private static int AuthCallback(ref ConnectCredential[] creds, IntPtr cbdata) { AuthData authData = (AuthData)Marshal.PtrToStructure(cbdata, typeof(AuthData)); foreach (ConnectCredential cred in creds) { switch (cred.type) { case ConnectCredentialType.VIR_CRED_AUTHNAME: // Fill the user name cred.Result = authData.user_name; break; case ConnectCredentialType.VIR_CRED_PASSPHRASE: // Fill the password cred.Result = authData.password; break; default: return -1; } } return 0; } The bindings user has no marshaling to do, and believe me, it's simpler. Finally, this patch finalize renaming. Best regards, Arnaud Champion

2 3

[libvirt] Xen: Stream-API or XML-RPC or XenAPI for managedSave, snapshots
by Philipp Hahn 27 Oct '10

27 Oct '10

Hello, for our project I need libvirts "managed save" functionality for Xen-3.4. In my implementation I tried to use Xens 'suspend' and 'resume', which would nicely match, but these two functions are not available throu the legacy streaming API (xend-http-server, xend-unix-server), which libvirt seems to still use. They are available throu the XML-RPC interface and the XenAPI interface, which libvirt doesn't seem to use. Are there any plans to convert libvirt to use one of the newer interfaces? My other option would be to either implement another subdriver for xenUnified*, which would implement domainManagedSave(), domainHasManagedSaveImage() and domainManagedSaveRemove() using XML-RPC (or XenAPI), or to implement suspend() and resume() in Xend. I also will need to look at snapshots next: Has someone already investigated adding snapshot support to Xen(-3.4)? Sincerely Philipp Hahn -- Philipp Hahn Open Source Software Engineer hahn(a)univention.de Univention GmbH Linux for Your Business fon: +49 421 22 232- 0 Mary-Somerville-Str.1 28359 Bremen fax: +49 421 22 232-99 http://www.univention.de Besuchen Sie uns auf unseren nächsten Veranstaltungen: 26. - 28.10.: IT & Business 2010 in Stuttgart 27. - 28.10.: MODERNER STAAT 2010 in Berlin http://www.univention.de/univention/termine/veranstaltungstermin/

2 2

[libvirt] dommemstat won't work
by 黄亮 27 Oct '10

27 Oct '10

Hi all. I try "virsh dommemstat <domain>" and it returns as follows :Failed to get memory statistics for domain vm_unfw :this function is not supported by the connection driver: virDomainMemoryStats So what may be the problem? I'm using CentOS release 5.5. Updated it's libvirt from 0.6.3 to 0.8.4 through "./configure; make; make install" procedure, and ran "autobuild.sh" in the directory of libvirt-0.8.4. Using "virsh version", it tells xen api version is 3.0.1, and xm version is 3.3.0 Thanks! 2010-10-27 黄亮

2 1

[libvirt] [PATCH 0/7]: Rewrite all the auditing hooks
by Daniel P. Berrange 27 Oct '10

27 Oct '10

This patch series reverts two previous commits which added auditing hooks to the daemon/remote.c dispatcher code. This is then replaced with hooks added directly to the QEMU driver code. This has the downside that auditing only works for the QEMU driver, but it is unavoidable because the dispatcher code has insufficient information to properly generate audit records. It also handles escaping of strings which contain user supplied arbitrary formatted data. It finishes up by adding auditing of disk/net resources.

2 15

[libvirt] [PATCH] Tell automake to use tar-pax instead of tar-v7 for make dist
by Matthias Bolte 27 Oct '10

27 Oct '10

Commit 66a04090673a5e21700d11bdea0084f1ee870c24 updated the API extention example patch series and added files that results in filenames longer than 99 chars during make dist. This is a problem because automake uses tar with the old v7 format during make dist. The v7 format is limited to 99 chars per filename. Use the newer and unlimited POSIX format instead. --- configure.ac | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/configure.ac b/configure.ac index d942d3c..838dac7 100644 --- a/configure.ac +++ b/configure.ac @@ -6,7 +6,7 @@ AC_CONFIG_AUX_DIR([build-aux]) AC_CONFIG_HEADERS([config.h]) AC_CONFIG_MACRO_DIR([m4]) dnl Make automake keep quiet about wildcards & other GNUmake-isms -AM_INIT_AUTOMAKE([-Wno-portability]) +AM_INIT_AUTOMAKE([1.9 -Wno-portability tar-pax]) # Use the silent-rules feature when possible. m4_ifndef([AM_SILENT_RULES], [m4_define([AM_SILENT_RULES],[])]) -- 1.7.0.4

4 4

[libvirt] [PATCH] Fix xen API documentation.
by Philipp Hahn 27 Oct '10

27 Oct '10

Add missing 'on'. Change 'dom' to 'domain' as used in xenDaemonDomainBlockPeek() Signed-off-by: Philipp Hahn <hahn(a)univention.de> --- src/xen/xend_internal.c | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-)

2 1

[libvirt] Gtk# help
by arnaud.champion＠devatom.fr 27 Oct '10

27 Oct '10

?Hi, As you maybe have seen in my csharp sample code, I'm not an expert with Gtk# under mono, it's really different from windows form. Can anyone help me with Gtk# to make the bindings samples better ? Arnaud

1 0

[libvirt] Libvirt.org "Docs" page (top level)
by Justin Clift 27 Oct '10

27 Oct '10

Hi us, The top level libvir.org Docs page is blank: http://libvirt.org/docs.html Looks like it's only purpose is to show the menu on the left hand side, where people can click documentation headings. The completely empty page content though, kind of looks "wrong", so I'm thinking we should fit it with something. Initial thought is to have an autogenerated list of all the docs pages, expanded out. Pretty much a table of contents kind of thing. But open to suggestions too if someone has better ideas? :) Regards and best wishes, Justin Clift

3 3

Re: [libvirt] How to start a defined domain
by 黄亮 27 Oct '10

27 Oct '10

yes, and it works now, both "virsh start vm01" and my program. A lot of thanks to you. But there is still something disturbing. I'm using putty on windows xp connecting to another computer running CentOS which has xen and libvirt on it. After I type "virsh start vm01" or run my program, the terminal freezes, I can't input anything to terminal. And then the network connection to server is closed. Have you been into this? 2010-10-27 黄亮发件人： Osier 发送时间： 2010-10-27 11:25:54 收件人：黄亮抄送：主题： Re: [libvirt] How to start a defined domain ----- "黄亮" <lancerhuang(a)163.com> wrote: > > > nope. > > "vm01" can be seen after I started it using "xm create vm01". > But, if I shut it down using "xm shutdown vm01", it can't be seen > using "virsh list --all" > > I assume that, "vm01" only have a xm config file stored in /etc/xen/, > and libvirt or virsh need a XML style config file. So I can't start > vm01 using "virsh start vm01" nor can I see it using "virsh list > --all". > > Is it like this? Do correct me if I'm wrong :-) so it becomes clear now, I guess you didn't 'define' the guest from libvirt side, that means'vm01' is not a persistent domain, so after you shutdown the vm01 using xm, yes, libvirt can't see it anymore. actually even if after you use "virsh destroy" or "virsh shutdown", libvirt can't see it either.. :-) the way to define a domain to be persistent,(assume the domain is running) # virsh dumpxml vm01 > vm01.xml # virsh define vm01.xml then think you can start it via: # virsh start vm01 - Osier > > 2010-10-27 > > 黄亮 > > 发件人： Osier > 发送时间： 2010-10-27 10:56:54 > 收件人：黄亮 > 抄送： > 主题： Re: [libvirt] How to start a defined domain > > > > ----- "黄亮" <lancerhuang(a)163.com> wrote: > > > > > Oh, yeah, you're right, it's "make uninstall" :-) > > > > after uninstall 0.8.4 and reinstall 0.6.3, it still won't work. > > > > but one thing I should mention is that while using "virsh start > vm01", > > it reports the same error, saying can't find domain "vm01" with > > "xenUnifiedDomainLookupByName ". > > So I think maybe there is something I'm missing in define a domain. > > > > Would you give me some hints so I can see where I go wrong? Really > > appreciated > > > > ah, well, so let us check lower, can you see the guest "vm01" by > "virsh list --all"? > > - Osier > > > > 2010-10-27 > > > > 黄亮 > > > > 发件人： Osier > > 发送时间： 2010-10-26 22:29:40 > > 收件人：黄亮 > > 抄送： libvir-list > > 主题： Re: [libvirt] How to start a defined domain > > > > > > > > ----- "黄亮" <lancerhuang(a)163.com> wrote: > > > > > > > > Well, after "make clean", I run the compiled start.c, still won't > > > work. > > > > "make clean" won't uninstall the installed stuffs, use "make > > uninstall" > > instead, or you just made a typo? :-) > > > > after that, suggest re-installing 0.6.3 if you are not sure if it's > > injured. > > > > - Osier > > > > > And I forget to metion, an error msg is shown: > > > > > > libvir: Xen error : Domain not found: xenUnifiedDomainLookupByName > > > > > > is that means I missed something? > > > > > > > > > 2010-10-26 > > > > > > 黄亮 > > > > > > 发件人： Osier > > > 发送时间： 2010-10-26 18:05:46 > > > 收件人：黄亮 > > > 抄送： > > > 主题： Re: [libvirt] How to start a defined domain > > > > > > > > > > > > ----- "黄亮" <lancerhuang(a)163.com> wrote: > > > > > > > > > > > Accroding to your case, it seems I have no need to upgrade > libvirt > > > to > > > > 0.8.4 > > > > Will that work if I erase 0.8.4 using "make clean" and draw back > > to > > > > 0.6.3 ? > > > > > > yep, think so, if you don't need the new features, and 0.6.3 is > > enough > > > for your project requirement.. :-) > > > > > > - Osier > > > > > > > > > > > > > > > > 2010-10-26 > > > > > > > > 黄亮 > > > > > > > > 发件人： Osier > > > > 发送时间： 2010-10-26 17:10:40 > > > > 收件人：黄亮 > > > > 抄送： > > > > 主题： Re: [libvirt] How to start a defined domain > > > > > > > > > > > > > > > > ----- "黄亮" <lancerhuang(a)163.com> wrote: > > > > > > > > > > > > > > Thanks for your reply, Osier. > > > > > > > > > > > > > > > The distro I'm using is CentOS release 5.5 (Final) > > > > > > > > > > I'm not quite sure about the version of libvirt. At first, it > > > seems > > > > to > > > > > be 0.6.3, because /usr/lib64/libvirt.so.0 points to > > > > > /usr/lib64/libvirt.so.0.6.3 > > > > > Then I downloaded the src of libvirt_0.8.4 from offical > website, > > > and > > > > > configure, make, make install. > > > > > But now it show errors when I type "virsh". The error message > > lies > > > > > below: > > > > > > > > > > virsh: /usr/local/lib/libvirt.so.0: version `LIBVIRT_0.8.2' > not > > > > found > > > > > (required by virsh) > > > > > virsh: /usr/local/lib/libvirt.so.0: version `LIBVIRT_0.7.1' > not > > > > found > > > > > (required by virsh) > > > > > virsh: /usr/local/lib/libvirt.so.0: version `LIBVIRT_0.7.5' > not > > > > found > > > > > (required by virsh) > > > > > virsh: /usr/local/lib/libvirt.so.0: version `LIBVIRT_0.8.1' > not > > > > found > > > > > (required by virsh) > > > > > virsh: /usr/local/lib/libvirt.so.0: version `LIBVIRT_0.7.0' > not > > > > found > > > > > (required by virsh) > > > > > virsh: /usr/local/lib/libvirt.so.0: version `LIBVIRT_0.7.2' > not > > > > found > > > > > (required by virsh) > > > > > virsh: /usr/local/lib/libvirt.so.0: version `LIBVIRT_0.7.3' > not > > > > found > > > > > (required by virsh) > > > > > virsh: /usr/local/lib/libvirt.so.0: version `LIBVIRT_0.8.0' > not > > > > found > > > > > (required by virsh) > > > > > virsh: /usr/local/lib/libvirt.so.0: version > > > `LIBVIRT_PRIVATE_0.8.4' > > > > > not found (required by virsh) > > > > > virsh: /usr/local/lib/libvirt.so.0: version `LIBVIRT_0.7.7' > not > > > > found > > > > > (required by virsh) > > > > > virsh: /usr/local/lib/libvirt.so.0: version `LIBVIRT_0.6.4' > not > > > > found > > > > > (required by virsh) > > > > > > > > probly you should try to erase the 0.6.3, then compile and > install > > > > libvirt > > > > like: > > > > > > > > # ./configure --prefix=/usr --libdir=/usr/lib64 > > > > # make > > > > # make install > > > > > > > > your test program has no problem on my box. the libvirt on my > box > > > also > > > > is > > > > 0.6.3. > > > > > > > > Regards > > > > > > > > - Osier > > > > > > > > > > As for xen, it is 3.3.2. The full "xm info" message is listed > > > below: > > > > > host : testbed01 > > > > > release : 2.6.18-194.11.4.el5xen > > > > > version : #1 SMP Tue Sep 21 05:40:24 EDT 2010 > > > > > machine : x86_64 > > > > > nr_cpus : 8 > > > > > nr_nodes : 1 > > > > > cores_per_socket : 4 > > > > > threads_per_core : 2 > > > > > cpu_mhz : 2793 > > > > > hw_caps : > > > > > > > > > > > > > > > bfebfbff:28100800:00000000:00000140:0098e3fd:00000000:00000001:00000000 > > > > > virt_caps : hvm > > > > > total_memory : 4055 > > > > > free_memory : 533 > > > > > node_to_cpu : node0:0-7 > > > > > node_to_memory : node0:533 > > > > > xen_major : 3 > > > > > xen_minor : 3 > > > > > xen_extra : .2 > > > > > xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 > > > > > hvm-3.0-x86_32p hvm-3.0-x86_64 > > > > > xen_scheduler : credit > > > > > xen_pagesize : 4096 > > > > > platform_params : virt_start=0xffff800000000000 > > > > > xen_changeset : unavailable > > > > > cc_compiler : gcc version 4.1.2 20080704 (Red Hat 4.1.2-44) > > > > > cc_compile_by : root > > > > > cc_compile_domain : gitco.tld > > > > > cc_compile_date : Tue Aug 18 21:07:28 CEST 2009 > > > > > xend_config_format : 4 > > > > > > > > > > I've write a simple c program to test the api, and it is > listed > > > > below: > > > > > > > > > > 1 // This program aims to test the api which can start the VM > > > > > 2 > > > > > 3 #include "stdio.h" > > > > > 4 #include "stdlib.h" > > > > > 5 #include "libvirt/libvirt.h" > > > > > 6 > > > > > 7 int main(int argc ,char* argv[]) > > > > > 8 { > > > > > 9 virConnectPtr conn; > > > > > 10 conn = virConnectOpen( "xen+tcp://localhost?no_Verify=1" ); > > > > > 11 if( conn == NULL ) > > > > > 12 { > > > > > 13 printf( "Failed to Connect\n" ); > > > > > 14 return 1; > > > > > 15 } > > > > > 16 const char* host = "vm01"; > > > > > 17 virDomainPtr dom; > > > > > 18 dom = virDomainLookupByName( conn, host ); > > > > > 19 if( dom == NULL ) > > > > > 20 { > > > > > 21 printf( "can't find dom\n" ); > > > > > 22 return 1; > > > > > 23 } > > > > > 24 // else > > > > > 25 // { > > > > > 26 // virDomainFree( dom ); > > > > > 27 // virConnectClose( conn ); > > > > > 28 // printf("done\n"); > > > > > 29 // return 0; > > > > > 30 // } > > > > > 31 if( virDomainCreate( dom ) == -1 ) > > > > > 32 { > > > > > 33 printf( "failed to Start\n" ); > > > > > 34 virDomainFree( dom ); > > > > > 35 virConnectClose( conn ); > > > > > 36 return 1; > > > > > 37 } > > > > > 38 else > > > > > 39 { > > > > > 40 printf( "Started\n" ); > > > > > 41 virDomainFree( dom ); > > > > > 42 virConnectClose( conn ); > > > > > 43 return 0; > > > > > 44 } > > > > > 45 } > > > > > > > > > > 2010-10-26 > > > > > > > > > > Lancer > > > > > > > > > > 发件人： Osier > > > > > 发送时间： 2010-10-26 11:35:31 > > > > > 收件人：黄亮 > > > > > 抄送： libvir-list > > > > > 主题： Re: [libvirt] How to start a defined domain > > > > > > > > > > > > > > > > > > > > ----- "黄亮" <lancerhuang(a)163.com> wrote: > > > > > > > > > > > I've create a domain called "vm01" using Virt-Manager, the > GUI > > > > tool. > > > > > > Now I wanna use libvirt api to control the life cycle of > vm01. > > > > > > It went on well with shutdown and reboot, but how to start > it > > > > became > > > > > a > > > > > > problem. > > > > > > > > > > > > I was intended to get the virDomainPtr by using > > > > > virDomainLookupByName > > > > > > api, and then start it using virDomainCreate api. > > > > > > But it turns out that virDomainLookupByName api cannot > return > > a > > > > > > virDomainPtr for a defined but not running domain. > > > > > > > > > > > > > > > > no, it can :-) > > > > > > > > > > If it really doesn't work for you, could you write a simple > > > program > > > > to > > > > > reproduce it? and try to explain what's the version of libvirt > > you > > > > > use, > > > > > on which distro, etc, any helpful info is welcomed. :-) > > > > > > > > > > Thanks > > > > > > > > > > - Osier > > > > > > > > > > > That's my situation, what do you suggest I do now? > > > > > > Thanks in advance. > > > > > > > > > > > > 2010-10-26 > > > > > > > > > > > > Lancer > > > > > > -- > > > > > > libvir-list mailing list > > > > > > libvir-list(a)redhat.com > > > > > > https://www.redhat.com/mailman/listinfo/libvir-list > > > > > > > > > > __________ Information from ESET Smart Security, version of > > virus > > > > > signature database 5562 (20101025) __________ > > > > > > > > > > The message was checked by ESET Smart Security. > > > > > > > > > > http://www.eset.com > > > > > > > > __________ Information from ESET Smart Security, version of > virus > > > > signature database 5562 (20101025) __________ > > > > > > > > The message was checked by ESET Smart Security. > > > > > > > > http://www.eset.com > > > > > > __________ Information from ESET Smart Security, version of virus > > > signature database 5563 (20101026) __________ > > > > > > The message was checked by ESET Smart Security. > > > > > > http://www.eset.com > > > > __________ Information from ESET Smart Security, version of virus > > signature database 5565 (20101026) __________ > > > > The message was checked by ESET Smart Security. > > > > http://www.eset.com > > __________ Information from ESET Smart Security, version of virus > signature database 5566 (20101027) __________ > > The message was checked by ESET Smart Security. > > http://www.eset.com __________ Information from ESET Smart Security, version of virus signature database 5566 (20101027) __________ The message was checked by ESET Smart Security. http://www.eset.com

1 0

Re: [libvirt] --checksum-fill error on Ubuntu 10.04
by Osier 27 Oct '10

27 Oct '10

caused by network filter driver depends on the newer iptables, there is no "--checksum-fill" option indeed in older iptables. The following commit log is from iptables git. commit 9d1b11102b53103c00b7fddf4658a4d2bdee1338 Author: Michael S. Tsirkin <mst(a)redhat.com> Date: Thu Jul 15 17:23:24 2010 +0200 extensions: libxt_CHECKSUM extension This adds a `CHECKSUM' target, which can be used in the iptables mangle table. You can use this target to compute and fill in the checksum in a packet that lacks a checksum. This is particularly useful, if you need to work around old applications such as dhcp clients, that do not work well with checksum offloads, but don't want to disable checksum offload in your device. The problem happens in the field with virtualized applications. For reference, see Red Hat bz 605555, as well as http://www.spinics.net/lists/kvm/msg37660.html Typical expected use (helps old dhclient binary running in a VM): iptables -A POSTROUTING -t mangle -p udp --dport bootpc \ -j CHECKSUM --checksum-fill Includes fixes by Jan Engelhardt <jengelh(a)medozas.de> Signed-off-by: Michael S. Tsirkin <mst(a)redhat.com> Signed-off-by: Patrick McHardy <kaber(a)trash.net> Even on my FC13, it's without "CHECKSUM" support, the build date is 'Thu 08 Apr 2010 06:30:45 PM CST', :-) Could we treat the error message as warnings? or make it only works for newer iptables? - Osier ----- "Justin Clift" <jclift(a)redhat.com> wrote: > Hi us, > > Just noticed an error message when manually starting libvirtd (built > from git) on Ubuntu 10.04, while checking something else: > > iptables v1.4.4: unknown option `--checksum-fill' > > It shows up in the initial default network setup: > > 10:40:19.807: error : virRunWithHook:855 : internal error > '/sbin/iptables --table mangle --insert POSTROUTING --out-interface > virbr0 --protocol udp --destination-port 68 --jump CHECKSUM > --checksum-fill' exited with non-zero status 2 and signal 0: iptables > v1.4.4: unknown option `--checksum-fill' > Try `iptables -h' or 'iptables --help' for more information. > > Just a FYI, in case someone wants to look into it. > > Regards and best wishes, > > Justin Clift > > -- > libvir-list mailing list > libvir-list(a)redhat.com > https://www.redhat.com/mailman/listinfo/libvir-list

3 2

[libvirt] [PATCH] docs: added a table of contents to the first 11 docs files
by Justin Clift 27 Oct '10

27 Oct '10

There are a 58 docs files, so adding an autogeneratec Table Of Contents to them all will take some time. This is the first piece of the work done. --- docs/api.html.in | 17 +++-------------- docs/apps.html.in | 29 ++++++++++++++++++----------- docs/architecture.html.in | 42 +++++++++++++++++++----------------------- docs/archnetwork.html.in | 9 ++++++--- docs/auth.html.in | 41 ++++++++++++++--------------------------- docs/bugs.html.in | 12 ++++++++---- docs/contact.html.in | 6 ++++-- docs/deployment.html.in | 10 ++++++---- docs/devguide.html.in | 6 ++++-- docs/downloads.html.in | 18 ++++++++++-------- docs/drivers.html.in | 28 ++++++++++++++++++++++------ 11 files changed, 114 insertions(+), 104 deletions(-) diff --git a/docs/api.html.in b/docs/api.html.in index ad43fa3..e8bbeed 100644 --- a/docs/api.html.in +++ b/docs/api.html.in @@ -5,20 +5,9 @@ <p> This page describes the main principles and architecture choices behind the definition of the libvirt API: - <ul> - <li> - <a href="#Objects">Objects exposed</a> - </li> - <li> - <a href="#Functions">Functions and naming conventions</a> - </li> - <li> - <a href="#Driver">The drivers</a> - </li> - <li> - <a href="#Remote">Daemon and remote access</a> - </li> - </ul> + + <ul id="toc"></ul> + <h2><a name="Objects">Objects exposed</a></h2> <p> As defined in the <a href="goals.html">goals section</a>, libvirt API need to expose all the resources needed to manage the virtualization diff --git a/docs/apps.html.in b/docs/apps.html.in index 215c9b2..792c145 100644 --- a/docs/apps.html.in +++ b/docs/apps.html.in @@ -4,19 +4,26 @@ <p> This page provides an illustration of the wide variety of - applications using the libvirt management API. If you know - of interesting applications not listed on this page, send - a message to the <a href="contact.html">mailing list</a> - to request that it be added here. If your application uses - libvirt as its API, the following graphic is available for - your website to advertise support for libvirt: + applications using the libvirt management API. + </p> + + <ul id="toc"></ul> + + <h2><a name="add">Add an application</a></h2> + + <p> + To add an application not listed on this page, send a message + to the <a href="contact.html">mailing list</a>, requesting it + be added here. If your application uses libvirt as its API, + the following graphic is available for your website to advertise + support for libvirt: </p> <p class="image"> <img src="madeWith.png" alt="Made with libvirt"/> </p> - <h2>Command line tools</h2> + <h2><a name="command">Command line tools</a></h2> <dl> <dt>virsh</dt> @@ -60,7 +67,7 @@ </dd> </dl> - <h2>Desktop applications</h2> + <h2><a name="desktop">Desktop applications</a></h2> <dl> <dt><a href="http://virt-manager.org/">virt-manager</a></dt> @@ -79,7 +86,7 @@ </dd> </dl> - <h2>Web applications</h2> + <h2><a name="web">Web applications</a></h2> <dl> <dt><a href="http://ovirt.org/">oVirt</a></dt> @@ -99,7 +106,7 @@ </dd> </dl> - <h2>LiveCD / Appliances</h2> + <h2><a name="livecd">LiveCD / Appliances</a></h2> <dl> <dt><a href="http://et.redhat.com/~rjones/virt-p2v/">virt-p2v</a></dt> @@ -111,7 +118,7 @@ </dd> </dl> - <h2>Monitoring plugins</h2> + <h2><a name="monitoring">Monitoring plugins</a></h2> <dl> <dt><a href="http://honk.sigxcpu.org/projects/libvirt/#munin">for munin</a></dt> <dd> diff --git a/docs/architecture.html.in b/docs/architecture.html.in index a3e91a5..12d7e04 100644 --- a/docs/architecture.html.in +++ b/docs/architecture.html.in @@ -1,23 +1,19 @@ +<?xml version="1.0"?> <html> <body> <h1 >libvirt architecture</h1> - <p>Currently libvirt supports 2 kind of virtualization, and its -internal structure is based on a driver model which simplifies adding new -engines:</p> - <ul> - <li> - <a href="#Xen">Xen hypervisor</a> - </li> - <li> - <a href="#QEmu">QEmu and KVM based virtualization</a> - </li> - <li> - <a href="#drivers">the driver architecture</a> - </li> - </ul> - <h3> - <a name="Xen">Libvirt Xen support</a> - </h3> + + <p> + Currently libvirt supports 2 kind of virtualization, and its + internal structure is based on a driver model which simplifies + adding new + engines: + </p> + + <ul id="toc"></ul> + + <h2><a name="Xen">Xen support</a></h2> + <p>When running in a Xen environment, programs using libvirt have to execute in "Domain 0", which is the primary Linux OS loaded on the machine. That OS kernel provides most if not all of the actual drivers used by the set of @@ -48,9 +44,9 @@ privilege access).</p> connect to initialize the library. It will then fork a libvirt_proxy program running as root and providing read_only access to the API, this is then only useful for reporting and monitoring.</p> - <h3> - <a name="QEmu">Libvirt QEmu and KVM support</a> - </h3> + + <h2><a name="QEmu">QEmu and KVM support</a></h2> + <p>The model for QEmu and KVM is completely similar, basically KVM is based on QEmu for the process controlling a new domain, only small details differs between the two. In both case the libvirt API is provided by a controlling @@ -62,9 +58,9 @@ emulations models of QEmu, the selection is done when creating the new domain, by specifying the architecture and machine type targeted.</p> <p>The code controlling the QEmu process is available in the <code>qemud/</code> directory.</p> - <h3> - <a name="drivers">the driver based architecture</a> - </h3> + + <h2><a name="drivers">Driver based architecture</a></h2> + <p>As the previous section explains, libvirt can communicate using different channels with the current hypervisor, and should also be able to use different kind of hypervisor. To simplify the internal design, code, ease diff --git a/docs/archnetwork.html.in b/docs/archnetwork.html.in index 22e8697..57b8f3d 100644 --- a/docs/archnetwork.html.in +++ b/docs/archnetwork.html.in @@ -1,8 +1,11 @@ +<?xml version="1.0"?> <html> <body> <h1>Network management architecture</h1> - <h2>Architecture illustration</h2> + <ul id="toc"></ul> + + <h2><a name="architecture">Architecture illustration</a></h2> <p> The diagrams below illustrate some of the network configurations @@ -34,13 +37,13 @@ </li> </ul> - <h3>Logical diagram</h3> + <h3><a name="logical">Logical diagram</a></h3> <p class="image"> <img src="libvirt-net-logical.png" alt="Logical network architecture"/> </p> - <h3>Physical diagram</h3> + <h3><a name="physical">Physical diagram</a></h3> <p class="image"> <img src="libvirt-net-physical.png" alt="Physical network architecture"/> diff --git a/docs/auth.html.in b/docs/auth.html.in index 13731eb..2163959 100644 --- a/docs/auth.html.in +++ b/docs/auth.html.in @@ -1,30 +1,17 @@ +<?xml version="1.0"?> <html> <body> <h1 >Access control</h1> <p> -When connecting to libvirt, some connections may require client -authentication before allowing use of the APIs. The set of possible -authentication mechanisms is administrator controlled, independent -of applications using libvirt. -</p> - <ul> - <li> - <a href="#ACL_server_config">Server configuration</a> - </li> - <li> - <a href="#ACL_server_unix_perms">UNIX socket permissions/group</a> - </li> - <li> - <a href="#ACL_server_polkit">UNIX socket PolicyKit auth</a> - </li> - <li> - <a href="#ACL_server_username">Username/password auth</a> - </li> - <li> - <a href="#ACL_server_kerberos">Kerberos auth</a> - </li> - </ul> - <h3><a name="ACL_server_config">Server configuration</a></h3> + When connecting to libvirt, some connections may require client + authentication before allowing use of the APIs. The set of possible + authentication mechanisms is administrator controlled, independent + of applications using libvirt. + </p> + + <ul id="toc"></ul> + + <h2><a name="ACL_server_config">Server configuration</a></h2> <p> The libvirt daemon allows the administrator to choose the authentication mechanisms used for client connections on each network socket independently. @@ -35,7 +22,7 @@ currently a choice of <code>none</code>, <code>polkit</code>, and <code>sasl</co The SASL scheme can be further configured to choose between a large number of different mechanisms. </p> - <h3><a name="ACL_server_unix_perms">UNIX socket permissions/group</a></h3> + <h2><a name="ACL_server_unix_perms">UNIX socket permissions/group</a></h2> <p> If libvirt does not contain support for PolicyKit, then access control for the UNIX domain socket is done using traditional file user/group ownership @@ -52,7 +39,7 @@ parameter. For example, setting the former to mode <code>0770</code> and the latter <code>wheel</code> would let any user in the wheel group connect to the libvirt daemon. </p> - <h3><a name="ACL_server_polkit">UNIX socket PolicyKit auth</a></h3> + <h2><a name="ACL_server_polkit">UNIX socket PolicyKit auth</a></h2> <p> If libvirt contains support for PolicyKit, then access control options are more advanced. The <code>unix_sock_auth</code> parameter will default to @@ -86,7 +73,7 @@ ResultActive=yes</pre> Further examples of PolicyKit setup can be found on the <a href="http://wiki.libvirt.org/page/SSHPolicyKitSetup">wiki page</a>. </p> - <h3><a name="ACL_server_username">Username/password auth</a></h3> + <h2><a name="ACL_server_username">Username/password auth</a></h2> <p> The plain TCP socket of the libvirt daemon defaults to using SASL for authentication. The SASL mechanism configured by default is DIGEST-MD5, which provides a basic @@ -123,7 +110,7 @@ again: <pre> # saslpasswd2 -a libvirt -d fred </pre> - <h3><a name="ACL_server_kerberos">Kerberos auth</a></h3> + <h2><a name="ACL_server_kerberos">Kerberos auth</a></h2> <p> The plain TCP socket of the libvirt daemon defaults to using SASL for authentication. The SASL mechanism configured by default is DIGEST-MD5, which provides a basic diff --git a/docs/bugs.html.in b/docs/bugs.html.in index fa557a8..201705b 100644 --- a/docs/bugs.html.in +++ b/docs/bugs.html.in @@ -4,14 +4,18 @@ <h1>Bug reporting</h1> + <ul id="toc"></ul> + + <h2><a name="bugzilla">Bug Tracking</a></h2> + <p> The <a href="http://bugzilla.redhat.com">Red Hat Bugzilla Server</a> - should be used to report bugs and request features against libvirt. + should be used to report bugs and request features in libvirt. Before submitting a ticket, check the existing tickets to see if the bug/feature is already tracked. </p> - <h2>General libvirt bug reports</h2> + <h2><a name="general">General libvirt bug reports</a></h2> <p> If you are using official libvirt binaries from a Linux distribution @@ -27,7 +31,7 @@ <li><a href="http://bugzilla.redhat.com/bugzilla/enter_bug.cgi?product=Virtualization%20…">New libvirt ticket</a></li> </ul> - <h2>Linux Distribution specific bug reports</h2> + <h2><a name="distribution">Linux Distribution specific bug reports</a></h2> <ul> <li> If you are using official binaries from a <strong>Fedora distribution</strong>, enter @@ -54,7 +58,7 @@ </ul> - <h2>How to file high quality bug reports</h2> + <h2><a name="quality">How to file high quality bug reports</a></h2> <p> To increase the likelihood of your bug report being addressed it is diff --git a/docs/contact.html.in b/docs/contact.html.in index c9dceda..1a9f79a 100644 --- a/docs/contact.html.in +++ b/docs/contact.html.in @@ -3,7 +3,9 @@ <body> <h1>Contacting the development team</h1> - <h2>Mailing lists</h2> + <ul id="toc"></ul> + + <h2><a name="email">Mailing lists</a></h2> <p> There are two mailing-lists: @@ -45,7 +47,7 @@ clone. </p> - <h2>IRC discussion</h2> + <h2><a name="irc">IRC discussion</a></h2> <p> Some of the libvirt developers may be found on IRC on the <a href="http://oftc.net">OFTC IRC</a> diff --git a/docs/deployment.html.in b/docs/deployment.html.in index 94c480f..8ef383b 100644 --- a/docs/deployment.html.in +++ b/docs/deployment.html.in @@ -2,16 +2,18 @@ <body> <h1>Deployment</h1> - <h2>Pre-packaged releases</h2> + <ul id="toc"></ul> + + <h2><a name="packages">Pre-packaged releases</a></h2> <p> - The libvirt API is now available in all major Linux distributions + The libvirt API is now available in all major Linux distributions, so the simplest deployment approach is to use your distributions' package management software to install the <code>libvirt</code> module. </p> - <h2>Self-built releases</h2> + <h2><a name="tarball">Self-built releases</a></h2> <p> libvirt uses GNU autotools for its build system, so deployment @@ -25,7 +27,7 @@ # make install </pre> - <h2>Built from GIT</h2> + <h2><a name="git">Built from GIT</a></h2> <p> When building from GIT it is necessary to generate the autotools diff --git a/docs/devguide.html.in b/docs/devguide.html.in index 6c51c36..ba499db 100644 --- a/docs/devguide.html.in +++ b/docs/devguide.html.in @@ -3,6 +3,8 @@ <body> <h1>libvirt Application Development Guide</h1> + <ul id="toc"></ul> + <p> The guide is both a learning tool for developing with libvirt and an API reference document. It is a work in progress, composed by a @@ -16,7 +18,7 @@ contribution to the content here will do it. :) </p> - <h2>Browsable online</h2> + <h2><a name="online">Browsable online</a></h2> <ul> <li><a href="http://libvirt.org/guide/html/"> @@ -33,7 +35,7 @@ Source RPM format</a></li> </ul> - <h2>GIT source repository</h2> + <h2><a name="git">GIT source repository</a></h2> <p> The source is in a git repository: diff --git a/docs/downloads.html.in b/docs/downloads.html.in index 4b37d07..709bee8 100644 --- a/docs/downloads.html.in +++ b/docs/downloads.html.in @@ -3,7 +3,9 @@ <body> <h1>Downloads</h1> - <h2>Official Releases</h2> + <ul id="toc"></ul> + + <h2><a name="releases">Official Releases</a></h2> <p> The latest versions of the libvirt C library can be downloaded from: @@ -14,7 +16,7 @@ <li><a href="http://libvirt.org/sources/">libvirt.org HTTP server</a></li> </ul> - <h2>Hourly development snapshots</h2> + <h2><a name="hourly">Hourly development snapshots</a></h2> <p> Once an hour, an automated snapshot is made from the git server @@ -27,7 +29,7 @@ <li><a href="http://libvirt.org/sources/libvirt-git-snapshot.tar.gz">libvirt.org HTTP server</a></li> </ul> - <h2>GIT source repository</h2> + <h2><a name="git">GIT source repository</a></h2> <p> Libvirt code source is now maintained in a <a href="http://git-scm.com/">git</a> @@ -61,7 +63,7 @@ contribution to the content here will do it. :) </p> - <h2>Downloadable PDF</h2> + <h2><a name="appdevpdf">Application Development Guide PDF</a></h2> <p> PDF download is available here: @@ -71,7 +73,7 @@ <li><a href="http://libvirt.org/guide/pdf/Application_Development_Guide.pdf">libvirt App Dev Guide</a> (PDF)</li> </ul> - <h2>GIT source repository</h2> + <h2><a name="appdevgit">Application Development Guide source GIT repository</a></h2> <p> The source is also in a git repository: @@ -89,9 +91,9 @@ <br /> - <h1>libvirt Installation</h1> + <h1><a name="installation">libvirt Installation</a></h1> - <h2><a name="Compilatio">Compilation</a></h2> + <h2><a name="Compilatio">Compiling a release tarball</a></h2> <p> libvirt uses the standard configure/make/install steps: @@ -116,7 +118,7 @@ update your list of installed shared libs. </p> - <h2>Building from a source code checkout</h2> + <h2><a name="build">Building from a GIT checkout</a></h2> <p> The libvirt build process uses GNU autotools, so after obtaining a diff --git a/docs/drivers.html.in b/docs/drivers.html.in index 7e31434..b97200c 100644 --- a/docs/drivers.html.in +++ b/docs/drivers.html.in @@ -2,6 +2,8 @@ <body> <h1>Internal drivers</h1> + <ul id="toc"></ul> + <p> The libvirt public API delegates its implementation to one or more internal drivers, depending on the <a href="uri.html">connection URI</a> @@ -10,21 +12,35 @@ network and storage driver active. </p> - <h2>Hypervisor drivers</h2> + <h2><a name="hypervisor">Hypervisor drivers</a></h2> <p> The hypervisor drivers currently supported by libvirt are: </p> <ul> - <li><strong><a href="drvxen.html">Xen</a></strong></li> - <li><strong><a href="drvqemu.html">QEMU</a></strong></li> - <li><strong><a href="drvlxc.html">LXC</a></strong></li> - <li><strong><a href="drvtest.html">Test</a></strong></li> + <li><strong><a href="drvlxc.html">LXC</a></strong> - Linux Containers</li> + <li><strong><a href="drvone.html">OpenNebula</a></strong></li> <li><strong><a href="drvopenvz.html">OpenVZ</a></strong></li> + <li><strong><a href="drvqemu.html">QEMU</a></strong></li> + <li><strong><a href="drvtest.html">Test</a></strong> - Used for testing</li> + <li><strong><a href="drvuml.html">UML</a></strong> - User Mode Linux</li> <li><strong><a href="drvvbox.html">VirtualBox</a></strong></li> - <li><strong><a href="drvone.html">OpenNebula</a></strong></li> <li><strong><a href="drvesx.html">VMware ESX</a></strong></li> + <li><strong><a href="drvxen.html">Xen</a></strong></li> + </ul> + + <h2><a name="stroage">Storage drivers</a></h2> + + <ul> + <li><strong><a href="storage.html#StorageBackendDir">Directory backend</a></strong></li> + <li><strong><a href="storage.html#StorageBackendFS">Local filesystem backend</a></strong></li> + <li><strong><a href="storage.html#StorageBackendNetFS">Network filesystem backend</a></strong></li> + <li><strong><a href="storage.html#StorageBackendLogical">Logical Volume Manager (LVM) backend</a></strong></li> + <li><strong><a href="storage.html#StorageBackendDisk">Disk backend</a></strong></li> + <li><strong><a href="storage.html#StorageBackendISCSI">iSCSI backend</a></strong></li> + <li><strong><a href="storage.html#StorageBackendSCSI">SCSI backend</a></strong></li> + <li><strong><a href="storage.html#StorageBackendMultipath">Multipath backend</a></strong></li> </ul> </body> </html> -- 1.7.2.3

3 3

Re: [libvirt] How to start a defined domain
by 黄亮 27 Oct '10

27 Oct '10

nope. "vm01" can be seen after I started it using "xm create vm01". But, if I shut it down using "xm shutdown vm01", it can't be seen using "virsh list --all" I assume that, "vm01" only have a xm config file stored in /etc/xen/, and libvirt or virsh need a XML style config file. So I can't start vm01 using "virsh start vm01" nor can I see it using "virsh list --all". Is it like this? Do correct me if I'm wrong :-) 2010-10-27 黄亮发件人： Osier 发送时间： 2010-10-27 10:56:54 收件人：黄亮抄送：主题： Re: [libvirt] How to start a defined domain ----- "黄亮" <lancerhuang(a)163.com> wrote: > > Oh, yeah, you're right, it's "make uninstall" :-) > > after uninstall 0.8.4 and reinstall 0.6.3, it still won't work. > > but one thing I should mention is that while using "virsh start vm01", > it reports the same error, saying can't find domain "vm01" with > "xenUnifiedDomainLookupByName ". > So I think maybe there is something I'm missing in define a domain. > > Would you give me some hints so I can see where I go wrong? Really > appreciated > ah, well, so let us check lower, can you see the guest "vm01" by "virsh list --all"? - Osier > > 2010-10-27 > > 黄亮 > > 发件人： Osier > 发送时间： 2010-10-26 22:29:40 > 收件人：黄亮 > 抄送： libvir-list > 主题： Re: [libvirt] How to start a defined domain > > > > ----- "黄亮" <lancerhuang(a)163.com> wrote: > > > > > Well, after "make clean", I run the compiled start.c, still won't > > work. > > "make clean" won't uninstall the installed stuffs, use "make > uninstall" > instead, or you just made a typo? :-) > > after that, suggest re-installing 0.6.3 if you are not sure if it's > injured. > > - Osier > > > And I forget to metion, an error msg is shown: > > > > libvir: Xen error : Domain not found: xenUnifiedDomainLookupByName > > > > is that means I missed something? > > > > > > 2010-10-26 > > > > 黄亮 > > > > 发件人： Osier > > 发送时间： 2010-10-26 18:05:46 > > 收件人：黄亮 > > 抄送： > > 主题： Re: [libvirt] How to start a defined domain > > > > > > > > ----- "黄亮" <lancerhuang(a)163.com> wrote: > > > > > > > > Accroding to your case, it seems I have no need to upgrade libvirt > > to > > > 0.8.4 > > > Will that work if I erase 0.8.4 using "make clean" and draw back > to > > > 0.6.3 ? > > > > yep, think so, if you don't need the new features, and 0.6.3 is > enough > > for your project requirement.. :-) > > > > - Osier > > > > > > > > > > > > 2010-10-26 > > > > > > 黄亮 > > > > > > 发件人： Osier > > > 发送时间： 2010-10-26 17:10:40 > > > 收件人：黄亮 > > > 抄送： > > > 主题： Re: [libvirt] How to start a defined domain > > > > > > > > > > > > ----- "黄亮" <lancerhuang(a)163.com> wrote: > > > > > > > > > > > Thanks for your reply, Osier. > > > > > > > > > > > > The distro I'm using is CentOS release 5.5 (Final) > > > > > > > > I'm not quite sure about the version of libvirt. At first, it > > seems > > > to > > > > be 0.6.3, because /usr/lib64/libvirt.so.0 points to > > > > /usr/lib64/libvirt.so.0.6.3 > > > > Then I downloaded the src of libvirt_0.8.4 from offical website, > > and > > > > configure, make, make install. > > > > But now it show errors when I type "virsh". The error message > lies > > > > below: > > > > > > > > virsh: /usr/local/lib/libvirt.so.0: version `LIBVIRT_0.8.2' not > > > found > > > > (required by virsh) > > > > virsh: /usr/local/lib/libvirt.so.0: version `LIBVIRT_0.7.1' not > > > found > > > > (required by virsh) > > > > virsh: /usr/local/lib/libvirt.so.0: version `LIBVIRT_0.7.5' not > > > found > > > > (required by virsh) > > > > virsh: /usr/local/lib/libvirt.so.0: version `LIBVIRT_0.8.1' not > > > found > > > > (required by virsh) > > > > virsh: /usr/local/lib/libvirt.so.0: version `LIBVIRT_0.7.0' not > > > found > > > > (required by virsh) > > > > virsh: /usr/local/lib/libvirt.so.0: version `LIBVIRT_0.7.2' not > > > found > > > > (required by virsh) > > > > virsh: /usr/local/lib/libvirt.so.0: version `LIBVIRT_0.7.3' not > > > found > > > > (required by virsh) > > > > virsh: /usr/local/lib/libvirt.so.0: version `LIBVIRT_0.8.0' not > > > found > > > > (required by virsh) > > > > virsh: /usr/local/lib/libvirt.so.0: version > > `LIBVIRT_PRIVATE_0.8.4' > > > > not found (required by virsh) > > > > virsh: /usr/local/lib/libvirt.so.0: version `LIBVIRT_0.7.7' not > > > found > > > > (required by virsh) > > > > virsh: /usr/local/lib/libvirt.so.0: version `LIBVIRT_0.6.4' not > > > found > > > > (required by virsh) > > > > > > probly you should try to erase the 0.6.3, then compile and install > > > libvirt > > > like: > > > > > > # ./configure --prefix=/usr --libdir=/usr/lib64 > > > # make > > > # make install > > > > > > your test program has no problem on my box. the libvirt on my box > > also > > > is > > > 0.6.3. > > > > > > Regards > > > > > > - Osier > > > > > > > > As for xen, it is 3.3.2. The full "xm info" message is listed > > below: > > > > host : testbed01 > > > > release : 2.6.18-194.11.4.el5xen > > > > version : #1 SMP Tue Sep 21 05:40:24 EDT 2010 > > > > machine : x86_64 > > > > nr_cpus : 8 > > > > nr_nodes : 1 > > > > cores_per_socket : 4 > > > > threads_per_core : 2 > > > > cpu_mhz : 2793 > > > > hw_caps : > > > > > > > > > > bfebfbff:28100800:00000000:00000140:0098e3fd:00000000:00000001:00000000 > > > > virt_caps : hvm > > > > total_memory : 4055 > > > > free_memory : 533 > > > > node_to_cpu : node0:0-7 > > > > node_to_memory : node0:533 > > > > xen_major : 3 > > > > xen_minor : 3 > > > > xen_extra : .2 > > > > xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 > > > > hvm-3.0-x86_32p hvm-3.0-x86_64 > > > > xen_scheduler : credit > > > > xen_pagesize : 4096 > > > > platform_params : virt_start=0xffff800000000000 > > > > xen_changeset : unavailable > > > > cc_compiler : gcc version 4.1.2 20080704 (Red Hat 4.1.2-44) > > > > cc_compile_by : root > > > > cc_compile_domain : gitco.tld > > > > cc_compile_date : Tue Aug 18 21:07:28 CEST 2009 > > > > xend_config_format : 4 > > > > > > > > I've write a simple c program to test the api, and it is listed > > > below: > > > > > > > > 1 // This program aims to test the api which can start the VM > > > > 2 > > > > 3 #include "stdio.h" > > > > 4 #include "stdlib.h" > > > > 5 #include "libvirt/libvirt.h" > > > > 6 > > > > 7 int main(int argc ,char* argv[]) > > > > 8 { > > > > 9 virConnectPtr conn; > > > > 10 conn = virConnectOpen( "xen+tcp://localhost?no_Verify=1" ); > > > > 11 if( conn == NULL ) > > > > 12 { > > > > 13 printf( "Failed to Connect\n" ); > > > > 14 return 1; > > > > 15 } > > > > 16 const char* host = "vm01"; > > > > 17 virDomainPtr dom; > > > > 18 dom = virDomainLookupByName( conn, host ); > > > > 19 if( dom == NULL ) > > > > 20 { > > > > 21 printf( "can't find dom\n" ); > > > > 22 return 1; > > > > 23 } > > > > 24 // else > > > > 25 // { > > > > 26 // virDomainFree( dom ); > > > > 27 // virConnectClose( conn ); > > > > 28 // printf("done\n"); > > > > 29 // return 0; > > > > 30 // } > > > > 31 if( virDomainCreate( dom ) == -1 ) > > > > 32 { > > > > 33 printf( "failed to Start\n" ); > > > > 34 virDomainFree( dom ); > > > > 35 virConnectClose( conn ); > > > > 36 return 1; > > > > 37 } > > > > 38 else > > > > 39 { > > > > 40 printf( "Started\n" ); > > > > 41 virDomainFree( dom ); > > > > 42 virConnectClose( conn ); > > > > 43 return 0; > > > > 44 } > > > > 45 } > > > > > > > > 2010-10-26 > > > > > > > > Lancer > > > > > > > > 发件人： Osier > > > > 发送时间： 2010-10-26 11:35:31 > > > > 收件人：黄亮 > > > > 抄送： libvir-list > > > > 主题： Re: [libvirt] How to start a defined domain > > > > > > > > > > > > > > > > ----- "黄亮" <lancerhuang(a)163.com> wrote: > > > > > > > > > I've create a domain called "vm01" using Virt-Manager, the GUI > > > tool. > > > > > Now I wanna use libvirt api to control the life cycle of vm01. > > > > > It went on well with shutdown and reboot, but how to start it > > > became > > > > a > > > > > problem. > > > > > > > > > > I was intended to get the virDomainPtr by using > > > > virDomainLookupByName > > > > > api, and then start it using virDomainCreate api. > > > > > But it turns out that virDomainLookupByName api cannot return > a > > > > > virDomainPtr for a defined but not running domain. > > > > > > > > > > > > > no, it can :-) > > > > > > > > If it really doesn't work for you, could you write a simple > > program > > > to > > > > reproduce it? and try to explain what's the version of libvirt > you > > > > use, > > > > on which distro, etc, any helpful info is welcomed. :-) > > > > > > > > Thanks > > > > > > > > - Osier > > > > > > > > > That's my situation, what do you suggest I do now? > > > > > Thanks in advance. > > > > > > > > > > 2010-10-26 > > > > > > > > > > Lancer > > > > > -- > > > > > libvir-list mailing list > > > > > libvir-list(a)redhat.com > > > > > https://www.redhat.com/mailman/listinfo/libvir-list > > > > > > > > __________ Information from ESET Smart Security, version of > virus > > > > signature database 5562 (20101025) __________ > > > > > > > > The message was checked by ESET Smart Security. > > > > > > > > http://www.eset.com > > > > > > __________ Information from ESET Smart Security, version of virus > > > signature database 5562 (20101025) __________ > > > > > > The message was checked by ESET Smart Security. > > > > > > http://www.eset.com > > > > __________ Information from ESET Smart Security, version of virus > > signature database 5563 (20101026) __________ > > > > The message was checked by ESET Smart Security. > > > > http://www.eset.com > > __________ Information from ESET Smart Security, version of virus > signature database 5565 (20101026) __________ > > The message was checked by ESET Smart Security. > > http://www.eset.com __________ Information from ESET Smart Security, version of virus signature database 5566 (20101027) __________ The message was checked by ESET Smart Security. http://www.eset.com

1 0

[libvirt] [PATCH] docs: reformated the bindings page html markup to match other pages
by Justin Clift 27 Oct '10

27 Oct '10

--- Looks the same when processed, but the previous messy HTML got on my nerves while I was looking at other stuff. docs/bindings.html.in | 74 +++++++++++++++++++++++++++++++++--------------- 1 files changed, 51 insertions(+), 23 deletions(-) diff --git a/docs/bindings.html.in b/docs/bindings.html.in index bdcd231..0bc997e 100644 --- a/docs/bindings.html.in +++ b/docs/bindings.html.in @@ -1,31 +1,59 @@ +<?xml version="1.0"?> <html> <body> <h1 >Bindings for other languages</h1> - <p>Libvirt comes with bindings to support other languages than -pure <strong>C</strong>. First the headers embeds the necessary declarations to -allow direct access from <strong>C++</strong> code, but also we have bindings for -higher level kind of languages:</p> + + <p> + Libvirt comes with bindings to support other languages than + pure <strong>C</strong>. First the headers embeds the necessary + declarations to allow direct access from <strong>C++</strong> + code, but also we have bindings for higher level kind of languages: + </p> + <ul> - <li><strong>Python</strong>: Libvirt comes with direct support for the Python language - (just make sure you installed the libvirt-python package if not - compiling from sources). See below for more information about - using libvirt with python</li> - <li><strong>Perl</strong>: Daniel Berrange provides <a href="http://search.cpan.org/dist/Sys-Virt/">bindings for - Perl</a>.</li> - <li><strong>OCaml</strong>: Richard Jones supplies <a href="http://libvirt.org/ocaml/">bindings for OCaml</a>.</li> - <li><strong>Ruby</strong>: David Lutterkort provides <a href="http://libvirt.org/ruby/">bindings for Ruby</a>.</li> - <li><strong>Java</strong>: Daniel Veillard maintains <a href="java.html">Java bindings</a>.</li> - <li><strong>C#</strong>: Arnaud Champion maintains <a href="csharp.html">C# bindings</a>.</li> - <li><strong>PHP</strong>: Radek Hladik is developing <a href="http://phplibvirt.cybersales.cz/">PHP bindings</a>.</li> + <li> + <strong>Python</strong>: Libvirt comes with direct support for + the Python language (just make sure you installed the libvirt-python + package if not compiling from sources). See below for more + information about using libvirt with python + </li> + <li> + <strong>Perl</strong>: Daniel Berrange provides + <a href="http://search.cpan.org/dist/Sys-Virt/">bindings for Perl</a>. + </li> + <li> + <strong>OCaml</strong>: Richard Jones supplies + <a href="http://libvirt.org/ocaml/">bindings for OCaml</a>. + </li> + <li> + <strong>Ruby</strong>: David Lutterkort provides + <a href="http://libvirt.org/ruby/">bindings for Ruby</a>. + </li> + <li> + <strong>Java</strong>: Daniel Veillard maintains + <a href="java.html">Java bindings</a>. + </li> + <li> + <strong>C#</strong>: Arnaud Champion maintains + <a href="csharp.html">C# bindings</a>. + </li> + <li> + <strong>PHP</strong>: Radek Hladik is developing + <a href="http://phplibvirt.cybersales.cz/">PHP bindings</a>. + </li> </ul> - <p>For information on using libvirt on <strong>Windows</strong> - <a href="windows.html">please see the Windows - support page</a>. + + <p> + For information on using libvirt on <strong>Windows</strong> + <a href="windows.html">please see the Windows support page</a>. + </p> + + <p> + Support, requests or help for libvirt bindings are welcome on the + <a href="https://www.redhat.com/mailman/listinfo/libvir-list/">mailing list</a>, + as usual try to provide enough background information and make sure + you use recent version, see the <a href="bugs.html">help page</a>. </p> - <p>Support, requests or help for libvirt bindings are welcome on -the <a href="https://www.redhat.com/mailman/listinfo/libvir-list/">mailing -list</a>, as usual try to provide enough background information -and make sure you use recent version, see the <a href="bugs.html">help -page</a>.</p> + </body> </html> -- 1.7.2.3

2 3

Re: [libvirt] How to start a defined domain
by 黄亮 27 Oct '10

27 Oct '10

Oh, yeah, you're right, it's "make uninstall" :-) after uninstall 0.8.4 and reinstall 0.6.3, it still won't work. but one thing I should mention is that while using "virsh start vm01", it reports the same error, saying can't find domain "vm01" with "xenUnifiedDomainLookupByName ". So I think maybe there is something I'm missing in define a domain. Would you give me some hints so I can see where I go wrong? Really appreciated 2010-10-27 黄亮发件人： Osier 发送时间： 2010-10-26 22:29:40 收件人：黄亮抄送： libvir-list 主题： Re: [libvirt] How to start a defined domain ----- "黄亮" <lancerhuang(a)163.com> wrote: > > Well, after "make clean", I run the compiled start.c, still won't > work. "make clean" won't uninstall the installed stuffs, use "make uninstall" instead, or you just made a typo? :-) after that, suggest re-installing 0.6.3 if you are not sure if it's injured. - Osier > And I forget to metion, an error msg is shown: > > libvir: Xen error : Domain not found: xenUnifiedDomainLookupByName > > is that means I missed something? > > > 2010-10-26 > > 黄亮 > > 发件人： Osier > 发送时间： 2010-10-26 18:05:46 > 收件人：黄亮 > 抄送： > 主题： Re: [libvirt] How to start a defined domain > > > > ----- "黄亮" <lancerhuang(a)163.com> wrote: > > > > > Accroding to your case, it seems I have no need to upgrade libvirt > to > > 0.8.4 > > Will that work if I erase 0.8.4 using "make clean" and draw back to > > 0.6.3 ? > > yep, think so, if you don't need the new features, and 0.6.3 is enough > for your project requirement.. :-) > > - Osier > > > > > > > > 2010-10-26 > > > > 黄亮 > > > > 发件人： Osier > > 发送时间： 2010-10-26 17:10:40 > > 收件人：黄亮 > > 抄送： > > 主题： Re: [libvirt] How to start a defined domain > > > > > > > > ----- "黄亮" <lancerhuang(a)163.com> wrote: > > > > > > > > Thanks for your reply, Osier. > > > > > > > > > The distro I'm using is CentOS release 5.5 (Final) > > > > > > I'm not quite sure about the version of libvirt. At first, it > seems > > to > > > be 0.6.3, because /usr/lib64/libvirt.so.0 points to > > > /usr/lib64/libvirt.so.0.6.3 > > > Then I downloaded the src of libvirt_0.8.4 from offical website, > and > > > configure, make, make install. > > > But now it show errors when I type "virsh". The error message lies > > > below: > > > > > > virsh: /usr/local/lib/libvirt.so.0: version `LIBVIRT_0.8.2' not > > found > > > (required by virsh) > > > virsh: /usr/local/lib/libvirt.so.0: version `LIBVIRT_0.7.1' not > > found > > > (required by virsh) > > > virsh: /usr/local/lib/libvirt.so.0: version `LIBVIRT_0.7.5' not > > found > > > (required by virsh) > > > virsh: /usr/local/lib/libvirt.so.0: version `LIBVIRT_0.8.1' not > > found > > > (required by virsh) > > > virsh: /usr/local/lib/libvirt.so.0: version `LIBVIRT_0.7.0' not > > found > > > (required by virsh) > > > virsh: /usr/local/lib/libvirt.so.0: version `LIBVIRT_0.7.2' not > > found > > > (required by virsh) > > > virsh: /usr/local/lib/libvirt.so.0: version `LIBVIRT_0.7.3' not > > found > > > (required by virsh) > > > virsh: /usr/local/lib/libvirt.so.0: version `LIBVIRT_0.8.0' not > > found > > > (required by virsh) > > > virsh: /usr/local/lib/libvirt.so.0: version > `LIBVIRT_PRIVATE_0.8.4' > > > not found (required by virsh) > > > virsh: /usr/local/lib/libvirt.so.0: version `LIBVIRT_0.7.7' not > > found > > > (required by virsh) > > > virsh: /usr/local/lib/libvirt.so.0: version `LIBVIRT_0.6.4' not > > found > > > (required by virsh) > > > > probly you should try to erase the 0.6.3, then compile and install > > libvirt > > like: > > > > # ./configure --prefix=/usr --libdir=/usr/lib64 > > # make > > # make install > > > > your test program has no problem on my box. the libvirt on my box > also > > is > > 0.6.3. > > > > Regards > > > > - Osier > > > > > > As for xen, it is 3.3.2. The full "xm info" message is listed > below: > > > host : testbed01 > > > release : 2.6.18-194.11.4.el5xen > > > version : #1 SMP Tue Sep 21 05:40:24 EDT 2010 > > > machine : x86_64 > > > nr_cpus : 8 > > > nr_nodes : 1 > > > cores_per_socket : 4 > > > threads_per_core : 2 > > > cpu_mhz : 2793 > > > hw_caps : > > > > > > bfebfbff:28100800:00000000:00000140:0098e3fd:00000000:00000001:00000000 > > > virt_caps : hvm > > > total_memory : 4055 > > > free_memory : 533 > > > node_to_cpu : node0:0-7 > > > node_to_memory : node0:533 > > > xen_major : 3 > > > xen_minor : 3 > > > xen_extra : .2 > > > xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 > > > hvm-3.0-x86_32p hvm-3.0-x86_64 > > > xen_scheduler : credit > > > xen_pagesize : 4096 > > > platform_params : virt_start=0xffff800000000000 > > > xen_changeset : unavailable > > > cc_compiler : gcc version 4.1.2 20080704 (Red Hat 4.1.2-44) > > > cc_compile_by : root > > > cc_compile_domain : gitco.tld > > > cc_compile_date : Tue Aug 18 21:07:28 CEST 2009 > > > xend_config_format : 4 > > > > > > I've write a simple c program to test the api, and it is listed > > below: > > > > > > 1 // This program aims to test the api which can start the VM > > > 2 > > > 3 #include "stdio.h" > > > 4 #include "stdlib.h" > > > 5 #include "libvirt/libvirt.h" > > > 6 > > > 7 int main(int argc ,char* argv[]) > > > 8 { > > > 9 virConnectPtr conn; > > > 10 conn = virConnectOpen( "xen+tcp://localhost?no_Verify=1" ); > > > 11 if( conn == NULL ) > > > 12 { > > > 13 printf( "Failed to Connect\n" ); > > > 14 return 1; > > > 15 } > > > 16 const char* host = "vm01"; > > > 17 virDomainPtr dom; > > > 18 dom = virDomainLookupByName( conn, host ); > > > 19 if( dom == NULL ) > > > 20 { > > > 21 printf( "can't find dom\n" ); > > > 22 return 1; > > > 23 } > > > 24 // else > > > 25 // { > > > 26 // virDomainFree( dom ); > > > 27 // virConnectClose( conn ); > > > 28 // printf("done\n"); > > > 29 // return 0; > > > 30 // } > > > 31 if( virDomainCreate( dom ) == -1 ) > > > 32 { > > > 33 printf( "failed to Start\n" ); > > > 34 virDomainFree( dom ); > > > 35 virConnectClose( conn ); > > > 36 return 1; > > > 37 } > > > 38 else > > > 39 { > > > 40 printf( "Started\n" ); > > > 41 virDomainFree( dom ); > > > 42 virConnectClose( conn ); > > > 43 return 0; > > > 44 } > > > 45 } > > > > > > 2010-10-26 > > > > > > Lancer > > > > > > 发件人： Osier > > > 发送时间： 2010-10-26 11:35:31 > > > 收件人：黄亮 > > > 抄送： libvir-list > > > 主题： Re: [libvirt] How to start a defined domain > > > > > > > > > > > > ----- "黄亮" <lancerhuang(a)163.com> wrote: > > > > > > > I've create a domain called "vm01" using Virt-Manager, the GUI > > tool. > > > > Now I wanna use libvirt api to control the life cycle of vm01. > > > > It went on well with shutdown and reboot, but how to start it > > became > > > a > > > > problem. > > > > > > > > I was intended to get the virDomainPtr by using > > > virDomainLookupByName > > > > api, and then start it using virDomainCreate api. > > > > But it turns out that virDomainLookupByName api cannot return a > > > > virDomainPtr for a defined but not running domain. > > > > > > > > > > no, it can :-) > > > > > > If it really doesn't work for you, could you write a simple > program > > to > > > reproduce it? and try to explain what's the version of libvirt you > > > use, > > > on which distro, etc, any helpful info is welcomed. :-) > > > > > > Thanks > > > > > > - Osier > > > > > > > That's my situation, what do you suggest I do now? > > > > Thanks in advance. > > > > > > > > 2010-10-26 > > > > > > > > Lancer > > > > -- > > > > libvir-list mailing list > > > > libvir-list(a)redhat.com > > > > https://www.redhat.com/mailman/listinfo/libvir-list > > > > > > __________ Information from ESET Smart Security, version of virus > > > signature database 5562 (20101025) __________ > > > > > > The message was checked by ESET Smart Security. > > > > > > http://www.eset.com > > > > __________ Information from ESET Smart Security, version of virus > > signature database 5562 (20101025) __________ > > > > The message was checked by ESET Smart Security. > > > > http://www.eset.com > > __________ Information from ESET Smart Security, version of virus > signature database 5563 (20101026) __________ > > The message was checked by ESET Smart Security. > > http://www.eset.com __________ Information from ESET Smart Security, version of virus signature database 5565 (20101026) __________ The message was checked by ESET Smart Security. http://www.eset.com

1 0

[libvirt] [PATCH] virsh: use - not _ in memtune option names
by Eric Blake 26 Oct '10

26 Oct '10

* tools/virsh.c (opts_memtune): All other options in virsh use - for separating words. --- tools/virsh.c | 8 ++++---- 1 files changed, 4 insertions(+), 4 deletions(-) diff --git a/tools/virsh.c b/tools/virsh.c index cafd304..b616eef 100644 --- a/tools/virsh.c +++ b/tools/virsh.c @@ -2890,13 +2890,13 @@ static const vshCmdInfo info_memtune[] = { static const vshCmdOptDef opts_memtune[] = { {"domain", VSH_OT_DATA, VSH_OFLAG_REQ, N_("domain name, id or uuid")}, - {VIR_DOMAIN_MEMORY_HARD_LIMIT, VSH_OT_INT, VSH_OFLAG_NONE, + {"hard-limit", VSH_OT_INT, VSH_OFLAG_NONE, N_("Max memory in kilobytes")}, - {VIR_DOMAIN_MEMORY_SOFT_LIMIT, VSH_OT_INT, VSH_OFLAG_NONE, + {"soft-limit", VSH_OT_INT, VSH_OFLAG_NONE, N_("Memory during contention in kilobytes")}, - {VIR_DOMAIN_MEMORY_SWAP_HARD_LIMIT, VSH_OT_INT, VSH_OFLAG_NONE, + {"swap-hard-limit", VSH_OT_INT, VSH_OFLAG_NONE, N_("Max swap in kilobytes")}, - {VIR_DOMAIN_MEMORY_MIN_GUARANTEE, VSH_OT_INT, VSH_OFLAG_NONE, + {"min-guarantee", VSH_OT_INT, VSH_OFLAG_NONE, N_("Min guaranteed memory in kilobytes")}, {NULL, 0, 0, NULL} }; -- 1.7.2.3

2 5

[libvirt] [PATCH] build: silence configure warning if ksh is missing
by Eric Blake 26 Oct '10

26 Oct '10

* configure.ac (lv_cv_wrapper_shell): Fix logic error if candidate shell is not available. Reported by Matthias Bolte. --- On IRC, Matthias reported a noisy configure run: eblake: checking for shell that supports <> redirection... ./configure: line 31581: ksh: command not found Worse, if a shell is missing, it doesn't change the contents of conftest.a, so that missing shell would be selected in the loop. This patch fixes both the noise and the wrong selection. configure.ac | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/configure.ac b/configure.ac index 86a864b..7e7f295 100644 --- a/configure.ac +++ b/configure.ac @@ -616,7 +616,7 @@ if test "$with_qemu" = yes; then test $lv_cv_wrapper_shell = none && AC_MSG_ERROR([could not find decent shell]) echo a > conftest.a - $lv_cv_wrapper_shell -c ': 1<>conftest.a' + ($lv_cv_wrapper_shell -c ': 1<>conftest.a') 2>/dev/null && case `cat conftest.a`.$lv_cv_wrapper_shell in a./*) break;; dnl /bin/sh is good enough a.*) dnl bash, ksh, and zsh all understand 'command', use that -- 1.7.2.3

2 4

[libvirt] [PATCH] maint: fix syntax-check failure of previous patch
by Eric Blake 26 Oct '10

26 Oct '10

* cfg.mk (sc_prohibit_trailing_blank_lines): Delete; this is adequately covered by maint.mk's sc_prohibit_empty_lines_at_EOF. * .x-sc_prohibit_empty_lines_at_EOF: New file, to exempt raw patches. * Makefile.am (EXTRA_DIST): Include new exemption. --- I'm pushing this under the build-breaker rule, since my previous patch made 'make syntax-check' fail for not one, but two identical syntax checks. .x-sc_prohibit_empty_lines_at_EOF | 1 + Makefile.am | 1 + cfg.mk | 9 --------- 3 files changed, 2 insertions(+), 9 deletions(-) create mode 100644 .x-sc_prohibit_empty_lines_at_EOF diff --git a/.x-sc_prohibit_empty_lines_at_EOF b/.x-sc_prohibit_empty_lines_at_EOF new file mode 100644 index 0000000..f481a09 --- /dev/null +++ b/.x-sc_prohibit_empty_lines_at_EOF @@ -0,0 +1 @@ +^docs/api_extension/.* diff --git a/Makefile.am b/Makefile.am index b51bd2b..26c6488 100644 --- a/Makefile.am +++ b/Makefile.am @@ -25,6 +25,7 @@ EXTRA_DIST = \ .x-sc_avoid_write \ .x-sc_m4_quote_check \ .x-sc_prohibit_asprintf \ + .x-sc_prohibit_empty_lines_at_EOF \ .x-sc_prohibit_gethostby \ .x-sc_prohibit_gethostname \ .x-sc_prohibit_gettext_noop \ diff --git a/cfg.mk b/cfg.mk index d50ffb7..d238a5f 100644 --- a/cfg.mk +++ b/cfg.mk @@ -406,15 +406,6 @@ sc_prohibit_newline_at_end_of_diagnostic: && { echo '$(ME): newline at end of message(s)' 1>&2; \ exit 1; } || : -# Disallow trailing blank lines. -sc_prohibit_trailing_blank_lines: - @$(VC_LIST_EXCEPT) | xargs perl -ln -0777 -e \ - '/\n\n+$$/ and print $$ARGV' > $@-t - @found=0; test -s $@-t && { found=1; cat $@-t 1>&2; \ - echo '$(ME): found trailing blank line(s)' 1>&2; }; \ - rm -f $@-t; \ - test $$found = 0 - # Regex for grep -E that exempts generated files from style rules. preprocessor_exempt = ((qemu|remote)_(driver|protocol)\.h)$$ # Enforce recommended preprocessor indentation style. -- 1.7.2.3

1 0

[libvirt] [PATCH] qemu: Fix detection of drive readonly option
by Jiri Denemark 26 Oct '10

26 Oct '10

So far, readonly=on option is used when qemu supports -device. However, there are qemu versions which support readonly option with -drive although they don't have support for -device. --- src/qemu/qemu_conf.c | 12 ++- src/qemu/qemu_conf.h | 1 + tests/qemuhelpdata/kvm-83-rhel56 | 141 ++++++++++++++++++++ tests/qemuhelptest.c | 26 ++++ ...qemuxml2argv-disk-drive-readonly-no-device.args | 1 + .../qemuxml2argv-disk-drive-readonly-no-device.xml | 31 +++++ tests/qemuxml2argvtest.c | 5 +- 7 files changed, 214 insertions(+), 3 deletions(-) create mode 100644 tests/qemuhelpdata/kvm-83-rhel56 create mode 100644 tests/qemuxml2argvdata/qemuxml2argv-disk-drive-readonly-no-device.args create mode 100644 tests/qemuxml2argvdata/qemuxml2argv-disk-drive-readonly-no-device.xml diff --git a/src/qemu/qemu_conf.c b/src/qemu/qemu_conf.c index e2c67a3..00e89a1 100644 --- a/src/qemu/qemu_conf.c +++ b/src/qemu/qemu_conf.c @@ -1187,6 +1187,8 @@ static unsigned long long qemudComputeCmdFlags(const char *help, flags |= QEMUD_CMD_FLAG_DRIVE_CACHE_V2; if (strstr(help, "format=")) flags |= QEMUD_CMD_FLAG_DRIVE_FORMAT; + if (strstr(help, "readonly=")) + flags |= QEMUD_CMD_FLAG_DRIVE_READONLY; } if (strstr(help, "-vga") && !strstr(help, "-std-vga")) flags |= QEMUD_CMD_FLAG_VGA; @@ -1202,8 +1204,14 @@ static unsigned long long qemudComputeCmdFlags(const char *help, flags |= QEMUD_CMD_FLAG_CHARDEV; if (strstr(help, "-balloon")) flags |= QEMUD_CMD_FLAG_BALLOON; - if (strstr(help, "-device")) + if (strstr(help, "-device")) { flags |= QEMUD_CMD_FLAG_DEVICE; + /* + * When -device was introduced, qemu already supported drive's + * readonly option but didn't advertise that. + */ + flags |= QEMUD_CMD_FLAG_DRIVE_READONLY; + } if (strstr(help, "-nodefconfig")) flags |= QEMUD_CMD_FLAG_NODEFCONFIG; /* The trailing ' ' is important to avoid a bogus match */ @@ -2688,7 +2696,7 @@ qemuBuildDriveStr(virDomainDiskDefPtr disk, disk->bus != VIR_DOMAIN_DISK_BUS_IDE) virBufferAddLit(&opt, ",boot=on"); if (disk->readonly && - qemuCmdFlags & QEMUD_CMD_FLAG_DEVICE) + qemuCmdFlags & QEMUD_CMD_FLAG_DRIVE_READONLY) virBufferAddLit(&opt, ",readonly=on"); if (disk->driverType && *disk->driverType != '\0' && disk->type != VIR_DOMAIN_DISK_TYPE_DIR && diff --git a/src/qemu/qemu_conf.h b/src/qemu/qemu_conf.h index 005031d..530dcdb 100644 --- a/src/qemu/qemu_conf.h +++ b/src/qemu/qemu_conf.h @@ -96,6 +96,7 @@ enum qemud_cmd_flags { QEMUD_CMD_FLAG_FSDEV = (1LL << 40), /* -fstype filesystem passthrough */ QEMUD_CMD_FLAG_NESTING = (1LL << 41), /* -enable-nesting (SVM/VMX) */ QEMUD_CMD_FLAG_NAME_PROCESS = (1LL << 42), /* Is -name process= available */ + QEMUD_CMD_FLAG_DRIVE_READONLY = (1LL << 43), /* -drive readonly=on|off */ }; /* Main driver state */ diff --git a/tests/qemuhelpdata/kvm-83-rhel56 b/tests/qemuhelpdata/kvm-83-rhel56 new file mode 100644 index 0000000..b2cefa9 --- /dev/null +++ b/tests/qemuhelpdata/kvm-83-rhel56 @@ -0,0 +1,141 @@ +QEMU PC emulator version 0.9.1 (kvm-83-maint-snapshot-20090205), Copyright (c) 2003-2008 Fabrice Bellard +usage: qemu [options] [disk_image] + +'disk_image' is a raw hard image image for IDE hard disk 0 + +Standard options: +-M machine select emulated machine (-M ? for list) +-cpu cpu select CPU (-cpu ? for list) +-fda/-fdb file use 'file' as floppy disk 0/1 image +-hda/-hdb file use 'file' as IDE hard disk 0/1 image +-hdc/-hdd file use 'file' as IDE hard disk 2/3 image +-cdrom file use 'file' as IDE cdrom image (cdrom is ide1 master) +-drive [file=file][,if=type][,bus=n][,unit=m][,media=d][,index=i] + [,cyls=c,heads=h,secs=s[,trans=t]][,snapshot=on|off] + [,cache=writethrough|writeback|none|unsafe][,format=f][,serial=s] + [,boot=on|off][,readonly=on|off] + use 'file' as a drive image +-mtdblock file use 'file' as on-board Flash memory image +-sd file use 'file' as SecureDigital card image +-pflash file use 'file' as a parallel flash image +-boot [a|c|d|n] boot on floppy (a), hard disk (c), CD-ROM (d), or network (n) +-snapshot write to temporary files instead of disk image files +-no-frame open SDL window without a frame and window decorations +-alt-grab use Ctrl-Alt-Shift to grab mouse (instead of Ctrl-Alt) +-no-quit disable SDL window close capability +-no-fd-bootchk disable boot signature checking for floppy disks +-m megs set virtual RAM size to megs MB [default=128] +-smp n set the number of CPUs to 'n' [default=1] +-nographic disable graphical output and redirect serial I/Os to console +-portrait rotate graphical output 90 deg left (only PXA LCD) +-k language use keyboard layout (for example "fr" for French) +-audio-help print list of audio drivers and their options +-soundhw c1,... enable audio support + and only specified sound cards (comma separated list) + use -soundhw ? to get the list of supported cards + use -soundhw all to enable all of them +-vga [std|cirrus] + select video card type +-localtime set the real time clock to local time [default=utc] +-full-screen start in full screen +-win2k-hack use it when installing Windows 2000 to avoid a disk full bug +-rtc-td-hack use it to fix time drift in Windows ACPI HAL +-usb enable the USB driver (will be the default soon) +-usbdevice name add the host or guest USB device 'name' +-name string set the name of the guest +-uuid %08x-%04x-%04x-%04x-%012x specify machine UUID +-notify event enable async-notifications for event +-qxl <num>[,ram=megs] + use 'num' qxl display devices, each with RAM size of 'megs' MB + [default=64] +-spice <args> use spice +-spice-help show spice usage + +Network options: +-net nic[,vlan=n][,macaddr=addr][,model=type][,name=str] + create a new Network Interface Card and connect it to VLAN 'n' +-net user[,vlan=n][,name=str][,hostname=host] + connect the user mode network stack to VLAN 'n' and send + hostname 'host' to DHCP clients +-net tap[,vlan=n][,name=str][,fd=h][,ifname=name][,script=file][,downscript=dfile] + connect the host TAP network interface to VLAN 'n' and use the + network scripts 'file' (default=/etc/qemu-ifup) + and 'dfile' (default=/etc/qemu-ifdown); + use '[down]script=no' to disable script execution; + use 'fd=h' to connect to an already opened TAP interface +-net socket[,vlan=n][,name=str][,fd=h][,listen=[host]:port][,connect=host:port] + connect the vlan 'n' to another VLAN using a socket connection +-net socket[,vlan=n][,name=str][,fd=h][,mcast=maddr:port] + connect the vlan 'n' to multicast maddr and port +-net none use it alone to have zero network devices; if no -net option + is provided, the default is '-net nic -net user' + +-tftp dir allow tftp access to files in dir [-net user] +-bootp file advertise file in BOOTP replies +-redir [tcp|udp]:host-port:[guest-host]:guest-port + redirect TCP or UDP connections from host to guest [-net user] + +Linux boot specific: +-kernel bzImage use 'bzImage' as kernel image +-append cmdline use 'cmdline' as kernel command line +-initrd file use 'file' as initial ram disk + +Debug/Expert options: +-monitor dev redirect the monitor to char device 'dev' +-vmchannel di:DI,dev redirect the hypercall device with device id DI, to char device 'dev' +-serial dev redirect the serial port to char device 'dev' +-parallel dev redirect the parallel port to char device 'dev' +-pidfile file Write PID to 'file' +-S freeze CPU at startup (use 'c' to start execution) +-s wait gdb connection to port +-p port set gdb connection port [default=1234] +-d item1,... output log to /tmp/qemu.log (use -d ? for a list of log items) +-hdachs c,h,s[,t] force hard disk 0 physical geometry and the optional BIOS + translation (t=none or lba) (usually qemu can guess them) +-L path set the directory for the BIOS, VGA BIOS and keymaps +-no-kvm disable KVM hardware virtualization +-no-kvm-irqchip disable KVM kernel mode PIC/IOAPIC/LAPIC +-no-kvm-pit disable KVM kernel mode PIT +-no-kvm-pit-reinjection disable KVM kernel mode PIT interrupt reinjection +-pcidevice host=bus:dev.func[,dma=none][,name=string] + expose a PCI device to the guest OS. + dma=none: don't perform any dma translations (default is to use an iommu) + 'string' is used in log output. +-no-acpi disable ACPI +-no-hpet disable HPET +-balloon none disable balloon device +-balloon virtio + enable virtio balloon device (default) +-acpitable [sig=str][,rev=n][,oem_id=str][,oem_table_id=str][,oem_rev=n][,asl_compiler_id=str][,asl_compiler_rev=n][,data=file1[:file2]...] + ACPI table description +-smbios file=binary + Load SMBIOS entry from binary file +-smbios type=0[,vendor=str][,version=str][,date=str][,release=%d.%d] + Specify SMBIOS type 0 fields +-smbios type=1[,manufacturer=str][,product=str][,version=str][,serial=str] + [,uuid=uuid][,sku=str][,family=str] + Specify SMBIOS type 1 fields +-no-reboot exit instead of rebooting +-no-shutdown stop before shutdown +-loadvm [tag|id] start right away with a saved state (loadvm in monitor) +-vnc display start a VNC server on display +-daemonize daemonize QEMU after initializing +-tdf inject timer interrupts that got lost +-kvm-shadow-memory megs set the amount of shadow pages to be allocated +-mem-path set the path to hugetlbfs/tmpfs mounted directory, also + enables allocation of guest memory with huge pages +-mem-prealloc toggles preallocation of -mem-path backed physical memory + at startup. Default is enabled. +-option-rom rom load a file, rom, into the option ROM space +-clock force the use of the given methods for timer alarm. + To see what timers are available use -clock ? +-startdate select initial date of the clock +-icount [N|auto] + Enable virtual instruction counter with 2^N clock ticks per instruction + +During emulation, the following keys are useful: +ctrl-alt-f toggle full screen +ctrl-alt-n switch to virtual console 'n' +ctrl-alt toggle mouse and keyboard grab + +When using -nographic, press 'ctrl-a h' to get some help. diff --git a/tests/qemuhelptest.c b/tests/qemuhelptest.c index d4453db..97531ff 100644 --- a/tests/qemuhelptest.c +++ b/tests/qemuhelptest.c @@ -130,6 +130,30 @@ mymain(int argc, char **argv) QEMUD_CMD_FLAG_MEM_PATH | QEMUD_CMD_FLAG_TDF, 9001, 1, 74); + DO_TEST("kvm-83-rhel56", + QEMUD_CMD_FLAG_VNC_COLON | + QEMUD_CMD_FLAG_NO_REBOOT | + QEMUD_CMD_FLAG_DRIVE | + QEMUD_CMD_FLAG_DRIVE_BOOT | + QEMUD_CMD_FLAG_NAME | + QEMUD_CMD_FLAG_UUID | + QEMUD_CMD_FLAG_VNET_HDR | + QEMUD_CMD_FLAG_MIGRATE_QEMU_TCP | + QEMUD_CMD_FLAG_MIGRATE_QEMU_EXEC | + QEMUD_CMD_FLAG_DRIVE_CACHE_V2 | + QEMUD_CMD_FLAG_KVM | + QEMUD_CMD_FLAG_DRIVE_FORMAT | + QEMUD_CMD_FLAG_DRIVE_SERIAL | + QEMUD_CMD_FLAG_VGA | + QEMUD_CMD_FLAG_PCIDEVICE | + QEMUD_CMD_FLAG_MEM_PATH | + QEMUD_CMD_FLAG_BALLOON | + QEMUD_CMD_FLAG_RTC_TD_HACK | + QEMUD_CMD_FLAG_NO_HPET | + QEMUD_CMD_FLAG_NO_KVM_PIT | + QEMUD_CMD_FLAG_TDF | + QEMUD_CMD_FLAG_DRIVE_READONLY, + 9001, 1, 83); DO_TEST("qemu-0.10.5", QEMUD_CMD_FLAG_KQEMU | QEMUD_CMD_FLAG_VNC_COLON | @@ -238,6 +262,7 @@ mymain(int argc, char **argv) QEMUD_CMD_FLAG_DRIVE_CACHE_V2 | QEMUD_CMD_FLAG_DRIVE_FORMAT | QEMUD_CMD_FLAG_DRIVE_SERIAL | + QEMUD_CMD_FLAG_DRIVE_READONLY | QEMUD_CMD_FLAG_VGA | QEMUD_CMD_FLAG_0_10 | QEMUD_CMD_FLAG_ENABLE_KVM | @@ -267,6 +292,7 @@ mymain(int argc, char **argv) QEMUD_CMD_FLAG_KVM | QEMUD_CMD_FLAG_DRIVE_FORMAT | QEMUD_CMD_FLAG_DRIVE_SERIAL | + QEMUD_CMD_FLAG_DRIVE_READONLY | QEMUD_CMD_FLAG_VGA | QEMUD_CMD_FLAG_0_10 | QEMUD_CMD_FLAG_PCIDEVICE | diff --git a/tests/qemuxml2argvdata/qemuxml2argv-disk-drive-readonly-no-device.args b/tests/qemuxml2argvdata/qemuxml2argv-disk-drive-readonly-no-device.args new file mode 100644 index 0000000..fb99a7c --- /dev/null +++ b/tests/qemuxml2argvdata/qemuxml2argv-disk-drive-readonly-no-device.args @@ -0,0 +1 @@ +LC_ALL=C PATH=/bin HOME=/home/test USER=test LOGNAME=test /usr/bin/qemu -S -M pc -m 214 -smp 1 -nographic -monitor unix:/tmp/test-monitor,server,nowait -no-acpi -boot c -drive file=/dev/HostVG/QEMUGuest1,if=ide,bus=0,unit=0 -drive file=/dev/sr0,if=ide,media=cdrom,bus=1,unit=0,readonly=on -net none -serial none -parallel none -usb diff --git a/tests/qemuxml2argvdata/qemuxml2argv-disk-drive-readonly-no-device.xml b/tests/qemuxml2argvdata/qemuxml2argv-disk-drive-readonly-no-device.xml new file mode 100644 index 0000000..1f193c9 --- /dev/null +++ b/tests/qemuxml2argvdata/qemuxml2argv-disk-drive-readonly-no-device.xml @@ -0,0 +1,31 @@ +<domain type='qemu'> + <name>QEMUGuest1</name> + <uuid>c7a5fdbd-edaf-9455-926a-d65c16db1809</uuid> + <memory>219200</memory> + <currentMemory>219200</currentMemory> + <vcpu>1</vcpu> + <os> + <type arch='i686' machine='pc'>hvm</type> + <boot dev='hd'/> + </os> + <clock offset='utc'/> + <on_poweroff>destroy</on_poweroff> + <on_reboot>restart</on_reboot> + <on_crash>destroy</on_crash> + <devices> + <emulator>/usr/bin/qemu</emulator> + <disk type='block' device='disk'> + <source dev='/dev/HostVG/QEMUGuest1'/> + <target dev='hda' bus='ide'/> + <address type='drive' controller='0' bus='0' unit='0'/> + </disk> + <disk type='block' device='cdrom'> + <source dev='/dev/sr0'/> + <target dev='hdc' bus='ide'/> + <readonly/> + <address type='drive' controller='0' bus='1' unit='0'/> + </disk> + <controller type='ide' index='0'/> + <memballoon model='virtio'/> + </devices> +</domain> diff --git a/tests/qemuxml2argvtest.c b/tests/qemuxml2argvtest.c index 4eb3cc6..f719f12 100644 --- a/tests/qemuxml2argvtest.c +++ b/tests/qemuxml2argvtest.c @@ -276,7 +276,10 @@ mymain(int argc, char **argv) DO_TEST("disk-drive-fat", QEMUD_CMD_FLAG_DRIVE | QEMUD_CMD_FLAG_DRIVE_BOOT | QEMUD_CMD_FLAG_DRIVE_FORMAT, false); DO_TEST("disk-drive-readonly-disk", QEMUD_CMD_FLAG_DRIVE | - QEMUD_CMD_FLAG_DEVICE | QEMUD_CMD_FLAG_NODEFCONFIG, false); + QEMUD_CMD_FLAG_DRIVE_READONLY | QEMUD_CMD_FLAG_DEVICE | + QEMUD_CMD_FLAG_NODEFCONFIG, false); + DO_TEST("disk-drive-readonly-no-device", QEMUD_CMD_FLAG_DRIVE | + QEMUD_CMD_FLAG_DRIVE_READONLY | QEMUD_CMD_FLAG_NODEFCONFIG, false); DO_TEST("disk-drive-fmt-qcow", QEMUD_CMD_FLAG_DRIVE | QEMUD_CMD_FLAG_DRIVE_BOOT | QEMUD_CMD_FLAG_DRIVE_FORMAT, false); DO_TEST("disk-drive-shared", QEMUD_CMD_FLAG_DRIVE | -- 1.7.3.2

4 6

[libvirt] [PATCH] Don't use %.3d format for bus/addr of USB devices.
by Diego Elio Pettenò 26 Oct '10

26 Oct '10

When using 0-prefixed numbers, QEmu will interpret them as octal numbers (as C convention says); this means that if you attach a device that has addr > 10 (decimal) you're going to attach a different device. --- src/qemu/qemu_conf.c | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/src/qemu/qemu_conf.c b/src/qemu/qemu_conf.c index 00e89a1..5bd3d4c 100644 --- a/src/qemu/qemu_conf.c +++ b/src/qemu/qemu_conf.c @@ -3266,7 +3266,7 @@ qemuBuildUSBHostdevDevStr(virDomainHostdevDefPtr dev) return NULL; } - if (virAsprintf(&ret, "usb-host,hostbus=%.3d,hostaddr=%.3d,id=%s", + if (virAsprintf(&ret, "usb-host,hostbus=%d,hostaddr=%d,id=%s", dev->source.subsys.u.usb.bus, dev->source.subsys.u.usb.device, dev->info.alias) < 0) @@ -3288,7 +3288,7 @@ qemuBuildUSBHostdevUsbDevStr(virDomainHostdevDefPtr dev) return NULL; } - if (virAsprintf(&ret, "host:%.3d.%.3d", + if (virAsprintf(&ret, "host:%d.%d", dev->source.subsys.u.usb.bus, dev->source.subsys.u.usb.device) < 0) virReportOOMError(); -- 1.7.3.2

2 1

[libvirt] [PATCH] virsh: consolidate memtune docs
by Eric Blake 26 Oct '10

26 Oct '10

* tools/virsh.pod (memtune): Drop second copy, fill to 80 columns, enhance wording. --- Seeing memtune twice in the man page is a bit confusing. This patch doesn't touch the pending issue of whether --min_guarantee makes sense, or should be deleted before it becomes a pre-mature API addition. Also, should memtune be changed to use VSH_OT_INT rather than VSH_OT_STRING? The current 'virsh help memtune' output looks weird: OPTIONS [--domain] <string> domain name, id or uuid --hard_limit <string> Max memory in kilobytes --soft_limit <string> Memory during contention in kilobytes --swap_hard_limit <string> Max swap in kilobytes --min_guarantee <string> Min guaranteed memory in kilobytes tools/virsh.pod | 15 ++++++++------- 1 files changed, 8 insertions(+), 7 deletions(-) diff --git a/tools/virsh.pod b/tools/virsh.pod index 943a563..bc68146 100644 --- a/tools/virsh.pod +++ b/tools/virsh.pod @@ -513,13 +513,14 @@ Change the maximum memory allocation limit in the guest domain. This should not change the current memory use. The memory limit is specified in kilobytes. -=item B<memtune> I<domain-id> - -Displays the domain memory parameters. - -=item B<memtune> I<domain-id> optional I<--hard-limit> B<kilobytes> optional I<--soft-limit> B<kilobytes> optional I<--swap-hard-limit> B<kilobytes> -I<--min-guarantee> B<kilobytes> - -Allows you to set the domain memory parameters. LXC and QEMU/KVM supports these parameters. +=item B<memtune> I<domain-id> optional I<--hard-limit> B<kilobytes> +optional I<--soft-limit> B<kilobytes> optional I<--swap-hard-limit> +B<kilobytes> -I<--min-guarantee> B<kilobytes> + +Allows you to display or set the domain memory parameters. Without +flags, the current settings are displayed; with a flag, the +appropriate limit is adjusted if supported by the hypervisor. LXC and +QEMU/KVM supports I<--hard-limit>, I<--soft-limit>, and I<--swap-hard-limit>. =item B<setvcpus> I<domain-id> I<count> -- 1.7.2.3

3 7

[libvirt] [PATCH v4 00/13] Implement memory control api
by Nikunj A. Dadhania 26 Oct '10

26 Oct '10

Changelog from v3: * Add unsigned int flags to the public api and make corresponding changes further down till the drivers(qemu, lxc and remote) * Move exporting of the api's to patch two * Added memtune test in tests/qemuxml2xmltest.c * Fix: src/conf/domain_conf.c - print memtune element only if tunable is present * Fix: src/qemu/qemu_driver.c - call cgroup apis only if nonzero * Fix: src/lxc/lxc_controller.c - call cgroup apis only if nonzero Changelog from v2: * Implement virDomainGetMemoryParameters api * Add virDomainGetMemoryParameters to memtune command in virsh * Provide domainGetMemoryParameters implementation for remote, QEmu and LXC drivers * Auto-generate code using rpcgen and remote_generate_stubs.pl * Squash all the changes related to remote driver and remote protocol into one single patch. * Patch re-ordering Changelog from v1: * Patch re-ordering for compilation * Folded python bindings changes to patch 01 * Added defines for string constants for memory tunables * Typo fix: min_guarantee * Moved initialization of function pointers in driver.h patch This patch series implement public api for controlling various memory tunables exported by the OS. This is based on the following RFC[1]. * Implement virDomainSetMemoryParameters api * Provide implementation for remote, QEmu and LXC drivers * Enable memory controller support fro QEmu * virsh command for runtime changes to the memory parameters * Domain configuration parsing for memory control parameters * Cgroup memory controller code for memory hard_limit/soft_limit, swap hard_limit To Do * Python bindings is just a place holder, need to implement 1. https://www.redhat.com/archives/libvir-list/2010-August/msg00607.html 2. https://www.redhat.com/archives/libvir-list/2010-August/msg00699.html --- Nikunj A. Dadhania (13): Adding structure and defines for virDomainSet/GetMemoryParameters Adding virDomainSetMemoryParameters and virDomainGetMemoryParameters API Adds xml entries for memory tunables XML parsing for memory tunables Implement cgroup memory controller tunables Implement driver interface domainSetMemoryParamters for QEmu Implement driver interface domainGetMemoryParamters for QEmu Adding memtunables to qemuSetupCgroup Adding memtunables to libvirt-lxc command Implement driver interface domainSetMemoryParamters for LXC Implement driver interface domainGetMemoryParamters for LXC Adding memtune command to virsh tool Remote protocol changes and implements virDomainSet/GetMemoryParameters daemon/remote.c | 162 +++++++++++++ daemon/remote_dispatch_args.h | 2 daemon/remote_dispatch_prototypes.h | 16 + daemon/remote_dispatch_ret.h | 1 daemon/remote_dispatch_table.h | 10 + docs/schemas/domain.rng | 31 +++ include/libvirt/libvirt.h.in | 63 +++++ python/generator.py | 2 python/libvirt-override-api.xml | 12 + python/libvirt-override.c | 14 + src/conf/domain_conf.c | 54 ++++ src/conf/domain_conf.h | 12 + src/driver.h | 14 + src/esx/esx_driver.c | 2 src/esx/esx_vmx.c | 30 +- src/libvirt.c | 104 +++++++++ src/libvirt_private.syms | 6 src/libvirt_public.syms | 6 src/lxc/lxc_controller.c | 32 +++ src/lxc/lxc_driver.c | 215 +++++++++++++++++- src/openvz/openvz_driver.c | 10 - src/phyp/phyp_driver.c | 2 src/qemu/qemu.conf | 4 src/qemu/qemu_conf.c | 11 - src/qemu/qemu_driver.c | 265 +++++++++++++++++++++- src/remote/remote_driver.c | 151 +++++++++++++ src/remote/remote_protocol.c | 88 +++++++ src/remote/remote_protocol.h | 58 +++++ src/remote/remote_protocol.x | 44 ++++ src/test/test_driver.c | 14 + src/uml/uml_conf.c | 2 src/uml/uml_driver.c | 16 + src/util/cgroup.c | 106 +++++++++ src/util/cgroup.h | 7 + src/xen/xen_driver.c | 2 tests/qemuxml2argvdata/qemuxml2argv-memtune.args | 1 tests/qemuxml2argvdata/qemuxml2argv-memtune.xml | 30 ++ tests/qemuxml2xmltest.c | 1 tools/virsh.c | 130 +++++++++++ 39 files changed, 1662 insertions(+), 68 deletions(-) create mode 100644 tests/qemuxml2argvdata/qemuxml2argv-memtune.args create mode 100644 tests/qemuxml2argvdata/qemuxml2argv-memtune.xml

6 47