- Devel - libvirt List Archives

[libvirt] [libvirt-snmp][PATCH v2] Remove the hard coded connection URI.
by Michal Privoznik 10 Feb '11

10 Feb '11

So now we rely on libvirt LIBVIRT_DEFAULT_URI environment variable. --- src/libvirtSnmp.c | 3 ++- 1 files changed, 2 insertions(+), 1 deletions(-) diff --git a/src/libvirtSnmp.c b/src/libvirtSnmp.c index ce21369..39b74bd 100644 --- a/src/libvirtSnmp.c +++ b/src/libvirtSnmp.c @@ -180,7 +180,8 @@ int libvirtSnmpInit(void) /* virConnectOpenAuth is called here with all default parameters, * except, possibly, the URI of the hypervisor. */ /* TODO: configure the URI */ - conn = virConnectOpenAuth("qemu:///system", virConnectAuthPtrDefault, 0); + /* Use libvirt env variable LIBVIRT_DEFAULT_URI by default*/ + conn = virConnectOpenAuth("", virConnectAuthPtrDefault, 0); if (NULL == conn) { printf("No connection to hypervisor\n"); -- 1.7.3.5

3 2

[libvirt] [PATCH] Fix spice's passwdValidTo setting
by Michal Privoznik 10 Feb '11

10 Feb '11

This fix the typo in the source. https://bugzilla.redhat.com/show_bug.cgi?id=676374 --- src/conf/domain_conf.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/src/conf/domain_conf.c b/src/conf/domain_conf.c index 7c1fb47..59adf36 100644 --- a/src/conf/domain_conf.c +++ b/src/conf/domain_conf.c @@ -3873,7 +3873,7 @@ virDomainGraphicsDefParseXML(xmlNodePtr node, int flags) { def->data.spice.listenAddr = virXMLPropString(node, "listen"); def->data.spice.keymap = virXMLPropString(node, "keymap"); - if (virDomainGraphicsAuthDefParseXML(node, &def->data.vnc.auth) < 0) + if (virDomainGraphicsAuthDefParseXML(node, &def->data.spice.auth) < 0) goto error; cur = node->children; -- 1.7.3.5

2 1

[libvirt] [libvirt-snmp][PATCH] New environment variable managing connection URI.
by Michal Privoznik 10 Feb '11

10 Feb '11

Add environment variable LIBVIRT_MIB_CONNECT_URI to control URI which snmp agent is connecting to. It is now possible to connect to all hypervisors (including test:///) instead of hardcoded qemu:///system, which is used now by default when variable is not set. --- src/libvirtSnmp.c | 5 ++++- src/libvirtSnmp.h | 3 +++ 2 files changed, 7 insertions(+), 1 deletions(-) diff --git a/src/libvirtSnmp.c b/src/libvirtSnmp.c index ce21369..7652da0 100644 --- a/src/libvirtSnmp.c +++ b/src/libvirtSnmp.c @@ -180,7 +180,10 @@ int libvirtSnmpInit(void) /* virConnectOpenAuth is called here with all default parameters, * except, possibly, the URI of the hypervisor. */ /* TODO: configure the URI */ - conn = virConnectOpenAuth("qemu:///system", virConnectAuthPtrDefault, 0); + /* A simple workaround for testing - environment variable */ + char *connect_uri = getenv(CONNECT_URI_ENV); + + conn = virConnectOpenAuth((connect_uri ? connect_uri : "qemu:///system"), virConnectAuthPtrDefault, 0); if (NULL == conn) { printf("No connection to hypervisor\n"); diff --git a/src/libvirtSnmp.h b/src/libvirtSnmp.h index 4ac6130..67b6125 100644 --- a/src/libvirtSnmp.h +++ b/src/libvirtSnmp.h @@ -10,6 +10,9 @@ #include <net-snmp/net-snmp-includes.h> #include <net-snmp/agent/net-snmp-agent-includes.h> +/* Environment variable to control connection URI */ +#define CONNECT_URI_ENV "LIBVIRT_MIB_CONNECT_URI" + /* * Populate libvirtGuestTable into given container. */ -- 1.7.3.5

3 2

[libvirt] [PATCH libvirt-site v2] Add information about libvirt-php new location [was Change PHP binding link to new one hosted on libvirt.org]
by Michal Novotny 10 Feb '11

10 Feb '11

Signed-off-by: Michal Novotny <minovotn(a)redhat.com> --- docs/bindings.html.in | 8 +++--- docs/php.html.in | 57 ++---------------------------------------------- 2 files changed, 7 insertions(+), 58 deletions(-) diff --git a/docs/bindings.html.in b/docs/bindings.html.in index 87d894d..2d936a0 100644 --- a/docs/bindings.html.in +++ b/docs/bindings.html.in @@ -28,16 +28,16 @@ <li> PHP: Radek Hladik started developing - <a href="http://phplibvirt.cybersales.cz/">PHP bindings</a> in 2010. + <a href="http://libvirt.org/php">PHP bindings</a> in 2010. - In February 2011 the binding development has been moved to the - <a href="http://libvirt.org/git/?p=libvirt-php.git;a=summary">libvirt.org as libvirt-php project</a>. + In February 2011 the binding development has been moved to the libvirt.org website as + libvirt-php project. The project is now maintained by Michal Novotny and it's heavily based on Radek's version. For more information including the information on posting - the patches you to libvirt-php please refer to <a href="php.html">PHP binding page</a>. + the patches you to libvirt-php please refer to <a href="http://libvirt.org/php">PHP binding</a>. </li> <li> diff --git a/docs/php.html.in b/docs/php.html.in index ea4f76a..5283e67 100644 --- a/docs/php.html.in +++ b/docs/php.html.in @@ -24,60 +24,9 @@ It can also be browsed at </pre> -<h2>Building</h2> -The code is using autotools to generate the files necessary for compilation. The preferred way of building is - to run autogen.sh to generate configure script and then go on with the standard linux make commands, i.e. - -<pre> -$ cd libvirt-php -$ ./autogen.sh -$ make -</pre> - - -<h2>Enabling the module in PHP</h2> -Before you start using the module you have to install the module first. The module -php_libvirt.so is being generated when you compile it. This is necessary to be loaded -in the extensions sections of php.ini file for PHP version older than PHP-5. - -Starting with PHP-5 you can create a file called libvirt.ini in /etc/php.d having just -one line <code>extension=php_libvirt.so</code> to enable the extension. Of course, you -need to have this module copied in the directory with the rest of your PHP modules to -make PHP find the module for you. - -If you're using PHP as a module (mod_php5.so) in the Apache webserver you need to -restart your Apache to trigger configuration reload for PHP. - - -If you're not sure that you have everything set up right and you don't want to restart -your Apache webserver before you're sure everything will be working fine you could try -running the test using cli-based PHP interpreter. There are some example scripts coming -along the source codes in the <code>example</code> subdirectory so you can try to run -php on the index.php script to check whether it's working fine to establish connection or not. - - -When you're having some issues with the connection make sure the apache user is having -access to libvirt. For more information please see <a href="auth.html">Libvirt access control</a> page. - -<h2>Contribution</h2> - -If you would like to contribute to the libvirt-php project you could write patches for it but please -make sure you're following the procedure below: - -<ol> - <li>Sign up to libvirt list if you're not on it yet (libvir-list(a)redhat.com)</li> - <li>Clone the repository from libvirt.org site using: - <pre>git clone git://libvirt.org/libvirt-php</pre> - </li> - <li>Set your git username and e-mail and also set the subject prefix in the project's repository using: - <pre>git config --local format.subjectprefix "libvirt-php"</pre> - </li> - <li>Create the patch in the form of the commits and include also information about usage (example source codes maybe) and testing</li> - <li>Format it using <code>git format-patch -X</code> where X is the number of patch parts to be posted, for multipart patch (X is greater than 1) please use also numbering (-n) option and include the cover-letter (--cover-letter).</li> - <li>Send to libvir-list(a)redhat.com using the <code>git send-email <files> --to libvir-list(a)redhat.com</code> command where <files> can be 000* to send all the patches formatted by git format-patch since git format-patch names the files starting with the 4 digit numbers.</li> -</ol> - -When you send the patch you're patch will be reviewed and later committed to the libvirt-php repository. You'll be contacted in case some flaws are found during the review. +<h2>Project pages</h2> +Since February 2011 the project have it's own pages hosted at libvirt.org. For more information on the project + please refer to <a href="http://libvirt.org/php">http://libvirt.org/php</a>. -- 1.7.3.2

2 2

Re: [libvirt] [PATCH] Basic support for VDE networking
by LiuCougar 09 Feb '11

09 Feb '11

On 12/01/2011, at 11:29 PM, Daniel P. Berrange wrote: > On Tue, Jan 11, 2011 at 04:12:57PM +0100, Renzo Davoli wrote: >> I have seen several messages asking for VDE networking support. >> There is an item also in your todo web page. >> http://libvirt.org/todo.html >> I have developed a patch to provide a basic support for VDE. >> It defines and manages the syntax: >> >> <domain ....> >> <device> >> <interface type='vde'> >> ... >> <switch path='/tmp/vde.ctl'/> >> </interface> >> </device> >> </domain> >> >> the switch tag can be omitted: vde uses the default switch. >> I have tested the qemu/kvm support. >> user-mode linux support is included but not tested yet. >> libvirt vde support for virtualbox has not been coded yet (virtualbox >> itself supports vde). ... > eg, so you'd be able to create/delete/manage VDE daemon instances > using the 'virsh net-XXX' command set. The guest domains would be > connected to VDE using the existing <interface type='network'> > syntax, and not expose any 'vde' syntax in the guest XML directly. > I think letting apps manage VDE daemon instances via the libvirt > APi would make this functionality much more friendly & useful The patch as it's submitted in this thread is very useful for all users of qemu/kvm with VDE: it makes it possible for these users to directly migrated to libvirt to manage VMs without too much hassle. If it can be managed automatically by libvirt, that would be a plus, but even then, I think it would be good to still support exposing VDE directly in the XML so users can manually handle VDE configuration if they choose to do so. Is it possible to merge this patch into libvirt so VDE users can benefit from libvirt? thanks, liucougar

1 0

[libvirt] [PATCH] build: distribute 'make syntax-check' tweaks
by Eric Blake 09 Feb '11

09 Feb '11

* Makefile.am (EXTRA_DIST): Distribute cfg.mk. --- I noticed that the 0.8.7 tarball lacks cfg.mk, so running 'make syntax-check' on that tarball is bound to have problems (without that file, you don't exempt tests in gnulib's maint.mk that libvirt is not interested in, and you miss out on lots of other tests that are libvirt-specific). Tested with 'make distcheck', then inspecting the resulting tarball. I almost pushed this under a trivial rule, but restrained myself to wait for a proper review. :) Makefile.am | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/Makefile.am b/Makefile.am index 597ec61..882e676 100644 --- a/Makefile.am +++ b/Makefile.am @@ -51,6 +51,7 @@ EXTRA_DIST = \ autobuild.sh \ Makefile.nonreentrant \ autogen.sh \ + cfg.mk \ examples/domain-events/events-python \ $(syntax_check_exceptions) \ $(XML_EXAMPLES) -- 1.7.3.5

2 3

[libvirt] [PATCH] maint: whitespace cleanup
by Eric Blake 09 Feb '11

09 Feb '11

* cfg.mk (sc_TAB_in_indentation): Check more files. * .dir-locals.el (html-mode): Let emacs help out. * docs/internals/command.html.in: Fix offenders. * docs/formatdomain.html.in: Likewise. * docs/internals.html.in: Likewise. Reported by Jiri Denemark. --- Here's the git diff -b output; actual patch below the diffstat. diff --git c/.dir-locals.el w/.dir-locals.el index 7c483d2..f24ec61 100644 --- c/.dir-locals.el +++ w/.dir-locals.el @@ -5,4 +5,7 @@ (c-indent-level . 4) (c-basic-offset . 4) )) + (html-mode . ( + (indent-tabs-mode . nil) + )) ) diff --git c/cfg.mk w/cfg.mk index 7664bdf..120f452 100644 --- c/cfg.mk +++ w/cfg.mk @@ -322,13 +322,13 @@ sc_prohibit_ctype_h: halt="don't use ctype.h; instead, use c-ctype.h" \ $(_sc_search_regexp) -# Ensure that no C source file or rng schema uses TABs for +# Ensure that no C source file, docs, or rng schema uses TABs for # indentation. Also match *.h.in files, to get libvirt.h.in. Exclude # files in gnulib, since they're imported. sc_TAB_in_indentation: @prohibit='^ * ' \ - in_vc_files='(\.(rng|[ch](\.in)?)|(daemon|tools)/.*\.in)$$' \ - halt='use spaces, not TAB, for indentation in C, sh, and RNG schemas' \ + in_vc_files='(\.(rng|[ch](\.in)?|html.in)|(daemon|tools)/.*\.in)$$' \ + halt='use leading spaces, not TAB, in C, sh, html, and RNG schemas' \ $(_sc_search_regexp) ctype_re = isalnum|isalpha|isascii|isblank|iscntrl|isdigit|isgraph|islower\ .dir-locals.el | 3 + cfg.mk | 6 +- docs/formatdomain.html.in | 224 ++++++++++++++++++++-------------------- docs/internals.html.in | 4 +- docs/internals/command.html.in | 32 +++--- 5 files changed, 136 insertions(+), 133 deletions(-) diff --git a/.dir-locals.el b/.dir-locals.el index 7c483d2..f24ec61 100644 --- a/.dir-locals.el +++ b/.dir-locals.el @@ -5,4 +5,7 @@ (c-indent-level . 4) (c-basic-offset . 4) )) + (html-mode . ( + (indent-tabs-mode . nil) + )) ) diff --git a/cfg.mk b/cfg.mk index 7664bdf..120f452 100644 --- a/cfg.mk +++ b/cfg.mk @@ -322,13 +322,13 @@ sc_prohibit_ctype_h: halt="don't use ctype.h; instead, use c-ctype.h" \ $(_sc_search_regexp) -# Ensure that no C source file or rng schema uses TABs for +# Ensure that no C source file, docs, or rng schema uses TABs for # indentation. Also match *.h.in files, to get libvirt.h.in. Exclude # files in gnulib, since they're imported. sc_TAB_in_indentation: @prohibit='^ * ' \ - in_vc_files='(\.(rng|[ch](\.in)?)|(daemon|tools)/.*\.in)$$' \ - halt='use spaces, not TAB, for indentation in C, sh, and RNG schemas' \ + in_vc_files='(\.(rng|[ch](\.in)?|html.in)|(daemon|tools)/.*\.in)$$' \ + halt='use leading spaces, not TAB, in C, sh, html, and RNG schemas' \ $(_sc_search_regexp) ctype_re = isalnum|isalpha|isascii|isblank|iscntrl|isdigit|isgraph|islower\ diff --git a/docs/formatdomain.html.in b/docs/formatdomain.html.in index 43c78fc..b048bb5 100644 --- a/docs/formatdomain.html.in +++ b/docs/formatdomain.html.in @@ -304,20 +304,20 @@ omitted, it defaults to the OS provided defaults.</dd> <dt><code>hard_limit</code></dt> <dd> The optional <code>hard_limit</code> element is the maximum memory - the guest can use. The units for this value are kilobytes (i.e. blocks - of 1024 bytes)</dd> + the guest can use. The units for this value are kilobytes (i.e. blocks + of 1024 bytes)</dd> <dt><code>soft_limit</code></dt> <dd> The optional <code>soft_limit</code> element is the memory limit to - enforce during memory contention. The units for this value are - kilobytes (i.e. blocks of 1024 bytes)</dd> + enforce during memory contention. The units for this value are + kilobytes (i.e. blocks of 1024 bytes)</dd> <dt><code>swap_hard_limit</code></dt> <dd> The optional <code>swap_hard_limit</code> element is the maximum - swap the guest can use. The units for this value are kilobytes - (i.e. blocks of 1024 bytes)</dd> + swap the guest can use. The units for this value are kilobytes + (i.e. blocks of 1024 bytes)</dd> <dt><code>min_guarantee</code></dt> <dd> The optional <code>min_guarantee</code> element is the guaranteed - minimum memory allocation for the guest. The units for this value are - kilobytes (i.e. blocks of 1024 bytes)</dd> + minimum memory allocation for the guest. The units for this value are + kilobytes (i.e. blocks of 1024 bytes)</dd> <dt><code>vcpu</code></dt> <dd>The content of this element defines the maximum number of virtual CPUs allocated for the guest OS, which must be between 1 and @@ -387,8 +387,8 @@ match the specification.</dd> </dl> - Since 0.8.5 the <code>match</code> - attribute can be omitted and will default to <code>exact</code>. + Since 0.8.5 the <code>match</code> + attribute can be omitted and will default to <code>exact</code>. </dd> <dt><code>model</code></dt> @@ -436,8 +436,8 @@ CPU.</dd> </dl> - Since 0.8.5 the <code>policy</code> - attribute can be omitted and will default to <code>require</code>. + Since 0.8.5 the <code>policy</code> + attribute can be omitted and will default to <code>require</code>. </dd> </dl> @@ -566,101 +566,101 @@ <dl> <dt><code>clock</code></dt> <dd> - The <code>offset</code> attribute takes four possible - values, allowing fine grained control over how the guest - clock is synchronized to the host. NB, not all hypervisors - support all modes. - <dl> - <dt><code>utc</code></dt> - <dd> - The guest clock will always be synchronized to UTC when - booted</dd> - <dt><code>localtime</code></dt> - <dd> - The guest clock will be synchronized to the host's configured - timezone when booted, if any. - </dd> - <dt><code>timezone</code></dt> - <dd> - The guest clock will be synchronized to the requested timezone - using the <code>timezone</code> attribute. - Since 0.7.7 - </dd> - <dt><code>variable</code></dt> - <dd> - The guest clock will have an arbitrary offset applied - relative to UTC. The delta relative to UTC is specified - in seconds, using the <code>adjustment</code> attribute. - The guest is free to adjust the RTC over time an expect - that it will be honoured at next reboot. This is in - contrast to 'utc' mode, where the RTC adjustments are - lost at each reboot. Since 0.7.7 - </dd> - </dl> - - A <code>clock</code> may have zero or more - <code>timer</code>sub-elements. Since - 0.8.0 - + The <code>offset</code> attribute takes four possible + values, allowing fine grained control over how the guest + clock is synchronized to the host. NB, not all hypervisors + support all modes. + <dl> + <dt><code>utc</code></dt> + <dd> + The guest clock will always be synchronized to UTC when + booted</dd> + <dt><code>localtime</code></dt> + <dd> + The guest clock will be synchronized to the host's configured + timezone when booted, if any. + </dd> + <dt><code>timezone</code></dt> + <dd> + The guest clock will be synchronized to the requested timezone + using the <code>timezone</code> attribute. + Since 0.7.7 + </dd> + <dt><code>variable</code></dt> + <dd> + The guest clock will have an arbitrary offset applied + relative to UTC. The delta relative to UTC is specified + in seconds, using the <code>adjustment</code> attribute. + The guest is free to adjust the RTC over time an expect + that it will be honoured at next reboot. This is in + contrast to 'utc' mode, where the RTC adjustments are + lost at each reboot. Since 0.7.7 + </dd> + </dl> + + A <code>clock</code> may have zero or more + <code>timer</code>sub-elements. Since + 0.8.0 + </dd> <dt><code>timer</code></dt> <dd> - - Each timer element requires a <code>name</code> attribute, - and has other optional attributes that depend on - the <code>name</code> specified. Various hypervisors - support different combinations of attributes. - - <dl> - <dt><code>name</code></dt> - <dd> - The <code>name</code> attribute selects which timer is - being modified, and can be one of "platform", "pit", - "rtc", "hpet", or "tsc". - </dd> - <dt><code>track</code></dt> - <dd> - The <code>track</code> attribute specifies what the timer - tracks, and can be "boot", "guest", or "wall". - Only valid for <code>name="rtc"</code> - or <code>name="platform"</code>. - </dd> - <dt><code>tickpolicy</code></dt> - <dd> - The <code>tickpolicy</code> attribute determines how - missed ticks in the guest are handled, and can be "delay", - "catchup", "merge", or "discard". If the policy is - "catchup", there can be further details in - the <code>catchup</code> sub-element. - <dl> - <dt><code>catchup</code></dt> - <dd> - The <code>catchup</code> element has three optional - attributes, each a positive integer. The attributes - are <code>threshold</code>, <code>slew</code>, - and <code>limit</code>. - </dd> - </dl> - </dd> - <dt><code>frequency</code></dt> - <dd> - The <code>frequency</code> attribute is an unsigned - integer specifying the frequency at - which <code>name="tsc"</code> runs. - </dd> - <dt><code>mode</code></dt> - <dd> - The <code>mode</code> attribute controls how - the <code>name="tsc"</code> timer is managed, and can be - "auto", "native", "emulate", "paravirt", or "smpsafe". - Other timers are always emulated. - </dd> - <dt><code>present</code></dt> - <dd> - The <code>present</code> attribute can be "yes" or "no" to - specify whether a particular timer is available to the guest. - </dd> - </dl> + + Each timer element requires a <code>name</code> attribute, + and has other optional attributes that depend on + the <code>name</code> specified. Various hypervisors + support different combinations of attributes. + + <dl> + <dt><code>name</code></dt> + <dd> + The <code>name</code> attribute selects which timer is + being modified, and can be one of "platform", "pit", + "rtc", "hpet", or "tsc". + </dd> + <dt><code>track</code></dt> + <dd> + The <code>track</code> attribute specifies what the timer + tracks, and can be "boot", "guest", or "wall". + Only valid for <code>name="rtc"</code> + or <code>name="platform"</code>. + </dd> + <dt><code>tickpolicy</code></dt> + <dd> + The <code>tickpolicy</code> attribute determines how + missed ticks in the guest are handled, and can be "delay", + "catchup", "merge", or "discard". If the policy is + "catchup", there can be further details in + the <code>catchup</code> sub-element. + <dl> + <dt><code>catchup</code></dt> + <dd> + The <code>catchup</code> element has three optional + attributes, each a positive integer. The attributes + are <code>threshold</code>, <code>slew</code>, + and <code>limit</code>. + </dd> + </dl> + </dd> + <dt><code>frequency</code></dt> + <dd> + The <code>frequency</code> attribute is an unsigned + integer specifying the frequency at + which <code>name="tsc"</code> runs. + </dd> + <dt><code>mode</code></dt> + <dd> + The <code>mode</code> attribute controls how + the <code>name="tsc"</code> timer is managed, and can be + "auto", "native", "emulate", "paravirt", or "smpsafe". + Other timers are always emulated. + </dd> + <dt><code>present</code></dt> + <dd> + The <code>present</code> attribute can be "yes" or "no" to + specify whether a particular timer is available to the guest. + </dd> + </dl> </dd> </dl> @@ -1490,7 +1490,7 @@ qemu-kvm -net nic,model=? /dev/null </dd> <dt><code>"spice"</code></dt> <dd> - + Starts a SPICE server. The <code>port</code> attribute specifies the TCP port number (with -1 as legacy syntax indicating that it should be auto-allocated), while <code>tlsPort</code> gives an alternative @@ -1502,8 +1502,8 @@ qemu-kvm -net nic,model=? /dev/null to use. It is possible to set a limit on the validity of the password be giving an timestamp <code>passwdValidTo='2010-04-09T15:51:00'</code> assumed to be in UTC. NB, this may not be supported by all hypervisors. - - + + When SPICE has both a normal and TLS secured TCP port configured, it can be desirable to restrict what channels can be run on each port. This is achieved by adding one or more <channel> elements inside @@ -1511,8 +1511,8 @@ qemu-kvm -net nic,model=? /dev/null <code>main</code>, <code>display</code>, <code>inputs</code>, <code>cursor</code>, <code>playback</code>, <code>record</code>; and since 0.8.8: <code>smartcard</code>. - - <pre> + + <pre> <graphics type='spice' port='-1' tlsPort='-1' autoport='yes'> <channel name='main' mode='secure'/> <channel name='record' mode='insecure'/> @@ -1569,7 +1569,7 @@ qemu-kvm -net nic,model=? /dev/null <dd> The <code>model</code> element has a mandatory <code>type</code> attribute which takes the value "vga", "cirrus", "vmvga", "qxl", - "xen" or "vbox", depending on the hypervisor features available. + "xen" or "vbox", depending on the hypervisor features available. You can also provide the amount of video memory in kilobytes using <code>vram</code> and the number of screen with <code>heads</code>. </dd> @@ -2167,8 +2167,8 @@ qemu-kvm -net nic,model=? /dev/null <dd> The required <code>model</code> attribute specifies what type - of balloon device is provided. Valid values are specific to - the virtualization platform + of balloon device is provided. Valid values are specific to + the virtualization platform <ul> <li>'virtio' — default with QEMU/KVM</li> diff --git a/docs/internals.html.in b/docs/internals.html.in index dc88eab..6fa2de3 100644 --- a/docs/internals.html.in +++ b/docs/internals.html.in @@ -10,10 +10,10 @@ <ul> <li>Introduction to basic rules and guidelines for <a href="hacking.html">hacking<a> - on libvirt code</li> + on libvirt code</li> <li>Guide to adding <a href="api_extension.html">public APIs<a></li> <li>Approach for <a href="internals/command.html">spawning commands</a> from - libvirt driver code</li> + libvirt driver code</li> </ul> </body> diff --git a/docs/internals/command.html.in b/docs/internals/command.html.in index 95d2b81..27dcf9c 100644 --- a/docs/internals/command.html.in +++ b/docs/internals/command.html.in @@ -20,27 +20,27 @@ <ul> <li><code>fork+exec</code>: The lowest & most flexible - level, but very hard to use correctly / safely. It - is easy to leak file descriptors, have unexpected - signal handler behaviour and not handle edge cases. - Furthermore, it is not portable to mingw. - </li> + level, but very hard to use correctly / safely. It + is easy to leak file descriptors, have unexpected + signal handler behaviour and not handle edge cases. + Furthermore, it is not portable to mingw. + </li> <li><code>system</code>: Convenient if you don't care - about capturing command output, but has the serious - downside that the command string is interpreted by - the shell. This makes it very dangerous to use, because - improperly validated user input can lead to exploits - via shell meta characters. + about capturing command output, but has the serious + downside that the command string is interpreted by + the shell. This makes it very dangerous to use, because + improperly validated user input can lead to exploits + via shell meta characters. </li> <li><code>popen</code>: Inherits the flaws of - <code>system</code>, and has no option for bi-directional - communication. + <code>system</code>, and has no option for bi-directional + communication. </li> <li><code>posix_spawn</code>: A half-way house between - simplicity of system() and the flexibility of fork+exec. - It does not allow for a couple of important features - though, such as running a hook between the fork+exec - stage, or closing all open file descriptors.</li> + simplicity of system() and the flexibility of fork+exec. + It does not allow for a couple of important features + though, such as running a hook between the fork+exec + stage, or closing all open file descriptors.</li> </ul> -- 1.7.4

2 3

[libvirt] [PATCH libvirt-site v2] Add information about libvirt-php new location [was Change PHP binding link to new one hosted on libvirt.org]
by Michal Novotny 09 Feb '11

09 Feb '11

Signed-off-by: Michal Novotny <minovotn(a)redhat.com> --- docs/bindings.html.in | 8 +++--- docs/php.html.in | 57 ++---------------------------------------------- 2 files changed, 7 insertions(+), 58 deletions(-) diff --git a/docs/bindings.html.in b/docs/bindings.html.in index 87d894d..2d936a0 100644 --- a/docs/bindings.html.in +++ b/docs/bindings.html.in @@ -28,16 +28,16 @@ <li> PHP: Radek Hladik started developing - <a href="http://phplibvirt.cybersales.cz/">PHP bindings</a> in 2010. + <a href="http://libvirt.org/php">PHP bindings</a> in 2010. - In February 2011 the binding development has been moved to the - <a href="http://libvirt.org/git/?p=libvirt-php.git;a=summary">libvirt.org as libvirt-php project</a>. + In February 2011 the binding development has been moved to the libvirt.org website as + libvirt-php project. The project is now maintained by Michal Novotny and it's heavily based on Radek's version. For more information including the information on posting - the patches you to libvirt-php please refer to <a href="php.html">PHP binding page</a>. + the patches you to libvirt-php please refer to <a href="http://libvirt.org/php">PHP binding</a>. </li> <li> diff --git a/docs/php.html.in b/docs/php.html.in index ea4f76a..5283e67 100644 --- a/docs/php.html.in +++ b/docs/php.html.in @@ -24,60 +24,9 @@ It can also be browsed at </pre> -<h2>Building</h2> -The code is using autotools to generate the files necessary for compilation. The preferred way of building is - to run autogen.sh to generate configure script and then go on with the standard linux make commands, i.e. - -<pre> -$ cd libvirt-php -$ ./autogen.sh -$ make -</pre> - - -<h2>Enabling the module in PHP</h2> -Before you start using the module you have to install the module first. The module -php_libvirt.so is being generated when you compile it. This is necessary to be loaded -in the extensions sections of php.ini file for PHP version older than PHP-5. - -Starting with PHP-5 you can create a file called libvirt.ini in /etc/php.d having just -one line <code>extension=php_libvirt.so</code> to enable the extension. Of course, you -need to have this module copied in the directory with the rest of your PHP modules to -make PHP find the module for you. - -If you're using PHP as a module (mod_php5.so) in the Apache webserver you need to -restart your Apache to trigger configuration reload for PHP. - - -If you're not sure that you have everything set up right and you don't want to restart -your Apache webserver before you're sure everything will be working fine you could try -running the test using cli-based PHP interpreter. There are some example scripts coming -along the source codes in the <code>example</code> subdirectory so you can try to run -php on the index.php script to check whether it's working fine to establish connection or not. - - -When you're having some issues with the connection make sure the apache user is having -access to libvirt. For more information please see <a href="auth.html">Libvirt access control</a> page. - -<h2>Contribution</h2> - -If you would like to contribute to the libvirt-php project you could write patches for it but please -make sure you're following the procedure below: - -<ol> - <li>Sign up to libvirt list if you're not on it yet (libvir-list(a)redhat.com)</li> - <li>Clone the repository from libvirt.org site using: - <pre>git clone git://libvirt.org/libvirt-php</pre> - </li> - <li>Set your git username and e-mail and also set the subject prefix in the project's repository using: - <pre>git config --local format.subjectprefix "libvirt-php"</pre> - </li> - <li>Create the patch in the form of the commits and include also information about usage (example source codes maybe) and testing</li> - <li>Format it using <code>git format-patch -X</code> where X is the number of patch parts to be posted, for multipart patch (X is greater than 1) please use also numbering (-n) option and include the cover-letter (--cover-letter).</li> - <li>Send to libvir-list(a)redhat.com using the <code>git send-email <files> --to libvir-list(a)redhat.com</code> command where <files> can be 000* to send all the patches formatted by git format-patch since git format-patch names the files starting with the 4 digit numbers.</li> -</ol> - -When you send the patch you're patch will be reviewed and later committed to the libvirt-php repository. You'll be contacted in case some flaws are found during the review. +<h2>Project pages</h2> +Since February 2011 the project have it's own pages hosted at libvirt.org. For more information on the project + please refer to <a href="http://libvirt.org/php">http://libvirt.org/php</a>. -- 1.7.3.2

1 0

[libvirt] [PATCH libvirt site] Change PHP binding link to new one hosted on libvirt.org
by Michal Novotny 09 Feb '11

09 Feb '11

Signed-off-by: Michal Novotny <minovotn(a)redhat.com> --- docs/bindings.html.in | 8 ++++---- docs/sitemap.html.in | 4 ---- 2 files changed, 4 insertions(+), 8 deletions(-) diff --git a/docs/bindings.html.in b/docs/bindings.html.in index 87d894d..2d936a0 100644 --- a/docs/bindings.html.in +++ b/docs/bindings.html.in @@ -28,16 +28,16 @@ <li> PHP: Radek Hladik started developing - <a href="http://phplibvirt.cybersales.cz/">PHP bindings</a> in 2010. + <a href="http://libvirt.org/php">PHP bindings</a> in 2010. - In February 2011 the binding development has been moved to the - <a href="http://libvirt.org/git/?p=libvirt-php.git;a=summary">libvirt.org as libvirt-php project</a>. + In February 2011 the binding development has been moved to the libvirt.org website as + libvirt-php project. The project is now maintained by Michal Novotny and it's heavily based on Radek's version. For more information including the information on posting - the patches you to libvirt-php please refer to <a href="php.html">PHP binding page</a>. + the patches you to libvirt-php please refer to <a href="http://libvirt.org/php">PHP binding</a>. </li> <li> diff --git a/docs/sitemap.html.in b/docs/sitemap.html.in index ac0af71..c987c49 100644 --- a/docs/sitemap.html.in +++ b/docs/sitemap.html.in @@ -266,10 +266,6 @@ <a href="csharp.html">C#</a> overview of the C# API bindings </li> - <li> - <a href="php.html">PHP</a> - overview of the PHP API bindings - </li> </ul> </li> <li> -- 1.7.3.2

2 4

Re: [libvirt] [virt-tools-list] difference between blkid of a system and uuid of virtual machine by virt-manager
by Cole Robinson 09 Feb '11

09 Feb '11

On 02/08/2011 02:06 PM, Tapas Mishra wrote: > I want to know what is the difference between the output blkid command > shows and the uuid which is set by virt-manager > while creating a guest. > Suppose in case of a re installation sort of situation I want to do a > fresh install and restore things from a backup then > where does this UUID thing comes into picture and what is its role > with respect to Virtual Machines. > > AFAIU it's just a unique identifier for use with libvirt, though nowadays it might be passed down to the guest for other purposes. cc-ing libvirt-list - Cole

1 0