- Devel - libvirt List Archives

[libvirt] [PATCH] docs: minor whitespace cleanups
by Eric Blake 07 Jul '11

07 Jul '11

No change in wording. One spacing change in a <pre>, noticed because of odd XML formatting online; the rest is in free-flowing text to make it easier to see nesting levels in the document. * docs/formatdomain.html.in: Adjust spacing. Break long lines. --- I'll probably push this under the trivial rule. The <pre> change is in the hunk at line 296, for <numatune>. docs/formatdomain.html.in | 195 ++++++++++++++++++++++++++------------------- 1 files changed, 112 insertions(+), 83 deletions(-) diff --git a/docs/formatdomain.html.in b/docs/formatdomain.html.in index fe8d74c..10d87a9 100644 --- a/docs/formatdomain.html.in +++ b/docs/formatdomain.html.in @@ -46,7 +46,8 @@ <dt><code>uuid</code></dt> <dd>The content of the <code>uuid</code> element provides a globally unique identifier for the virtual machine. - The format must be RFC 4122 compliant, eg <code>3e3fce45-4f53-4fa7-bb32-11f34168b82b</code>. + The format must be RFC 4122 compliant, + eg <code>3e3fce45-4f53-4fa7-bb32-11f34168b82b</code>. If omitted when defining/creating a new machine, a random UUID is generated. It is also possible to provide the UUID via a <a href="#elementsSysinfo"><code>sysinfo</code></a> @@ -96,13 +97,16 @@ on bare metal, so requires full virtualization. <code>linux</code> (badly named!) refers to an OS that supports the Xen 3 hypervisor guest ABI. There are also two optional attributes, <code>arch</code> - specifying the CPU architecture to virtualization, and <code>machine</code> - referring to the machine type. The <a href="formatcaps.html">Capabilities XML</a> - provides details on allowed values for these. Since 0.0.1</dd> + specifying the CPU architecture to virtualization, + and <code>machine</code> referring to the machine + type. The <a href="formatcaps.html">Capabilities XML</a> + provides details on allowed values for + these. Since 0.0.1</dd> <dt><code>loader</code></dt> <dd>The optional <code>loader</code> tag refers to a firmware blob used to assist the domain creation process. At this time, it is - only needed by Xen fully virtualized domains. Since 0.1.0</dd> + only needed by Xen fully virtualized + domains. Since 0.1.0</dd> <dt><code>boot</code></dt> <dd>The <code>dev</code> attribute takes one of the values "fd", "hd", "cdrom" or "network" and is used to specify the next boot device @@ -296,7 +300,7 @@ <shares>2048</shares> </cputune> <numatune> - <memory mode="strict" nodeset="1-4,^3"/> + <memory mode="strict" nodeset="1-4,^3"/> </numatune> ...</pre> @@ -372,7 +376,8 @@ physical CPUS the domain VCPU will be pinned to. If this is ommited, each VCPU pinned to all the physical CPUS by default. It contains two required attributes, the attribute <code>vcpu</code> specifies vcpu id, - and the attribute <code>cpuset</code> is same as attribute <code>cpuset</code> + and the attribute <code>cpuset</code> is same as + attribute <code>cpuset</code> of element <code>vcpu</code>. (NB: Only qemu driver support) Since 0.9.0 </dd> @@ -380,8 +385,9 @@ <dd> The optional <code>shares</code> element specifies the proportional weighted share for the domain. If this is ommited, it defaults to - the OS provided defaults. NB, There is no unit for the value, it's a relative - measure based on the setting of other VM, e.g. A VM configured with value + the OS provided defaults. NB, There is no unit for the value, + it's a relative measure based on the setting of other VM, + e.g. A VM configured with value 2048 will get twice as much CPU time as a VM configured with value 1024. Since 0.9.0 </dd> @@ -395,7 +401,8 @@ <dd> The optional <code>memory</code> element specify how to allocate memory for the domain process on a NUMA host. It contains two attributes, - attribute <code>mode</code> is either 'interleave', 'strict', or 'preferred', + attribute <code>mode</code> is either 'interleave', 'strict', + or 'preferred', attribute <code>nodeset</code> specifies the NUMA nodes, it leads same syntax with attribute <code>cpuset</code> of element <code>vcpu</code>. Since 0.9.3 @@ -825,12 +832,14 @@ to connect. Since 0.0.3</dd> <dt><code>target</code></dt> - <dd>The <code>target</code> element controls the bus / device under which the - disk is exposed to the guest OS. The <code>dev</code> attribute indicates - the "logical" device name. The actual device name specified is not guaranteed to map to - the device name in the guest OS. Treat it as a device ordering hint. - The optional <code>bus</code> attribute specifies the type of disk device - to emulate; possible values are driver specific, with typical values being + <dd>The <code>target</code> element controls the bus / device + under which the disk is exposed to the guest + OS. The <code>dev</code> attribute indicates the "logical" + device name. The actual device name specified is not + guaranteed to map to the device name in the guest OS. Treat it + as a device ordering hint. The optional <code>bus</code> + attribute specifies the type of disk device to emulate; + possible values are driver specific, with typical values being "ide", "scsi", "virtio", "xen" or "usb". If omitted, the bus type is inferred from the style of the device name. eg, a device named 'sda' will typically be exported using a SCSI bus. @@ -905,7 +914,8 @@ </dd> <dt><code>serial</code></dt> <dd>If present, this specify serial number of virtual hard drive. - For example, it may look as <code><serial>WD-WMAP9A966149</serial></code>. + For example, it may look + like <code><serial>WD-WMAP9A966149</serial></code>. Since 0.7.1 </dd> <dt><code>host</code></dt> @@ -1146,7 +1156,8 @@ <h4><a name="elementsUSB">USB and PCI devices</a></h4> - USB and PCI devices attached to the host can be passed through to the guest using + USB and PCI devices attached to the host can be passed through + to the guest using the <code>hostdev</code> element. since after 0.4.4 for USB and 0.6.0 for PCI (KVM only): @@ -1774,12 +1785,12 @@ qemu-kvm -net nic,model=? /dev/null ...</pre> - If no target is specified, certain hypervisors will automatically - generate a name for the created tun device. This name can be manually - specifed, however the name must not start with either 'vnet' or - 'vif', which are prefixes reserved by libvirt and certain - hypervisors. Manually specified targets using these prefixes will be - ignored. + If no target is specified, certain hypervisors will + automatically generate a name for the created tun device. This + name can be manually specifed, however the name must not + start with either 'vnet' or 'vif', which are prefixes + reserved by libvirt and certain hypervisors. Manually specified + targets using these prefixes will be ignored. <h5><a name="elementsNICSBoot">Specifying boot order</a></h5> @@ -1808,9 +1819,10 @@ qemu-kvm -net nic,model=? /dev/null <h4><a name="elementsInput">Input devices</a></h4> - Input devices allow interaction with the graphical framebuffer in the guest - virtual machine. When enabling the framebuffer, an input device is automatically - provided. It may be possible to add additional devices explicitly, for example, + Input devices allow interaction with the graphical framebuffer + in the guest virtual machine. When enabling the framebuffer, an + input device is automatically provided. It may be possible to + add additional devices explicitly, for example, to provide a graphics tablet for absolute cursor movement. @@ -1823,8 +1835,9 @@ qemu-kvm -net nic,model=? /dev/null <dl> <dt><code>input</code></dt> - <dd>The <code>input</code> element has one mandatory attribute, the <code>type</code> - whose value can be either 'mouse' or 'tablet'. The latter provides absolute + <dd>The <code>input</code> element has one mandatory attribute, + the <code>type</code> whose value can be either 'mouse' or + 'tablet'. The latter provides absolute cursor movement, while the former uses relative movement. The optional <code>bus</code> attribute can be used to refine the exact device type. It takes values "xen" (paravirtualized), "ps2" and "usb".</dd> @@ -1858,56 +1871,67 @@ qemu-kvm -net nic,model=? /dev/null <dl> <dt><code>graphics</code></dt> <dd>The <code>graphics</code> element has a mandatory <code>type</code> - attribute which takes the value "sdl", "vnc", "rdp" or "desktop": + attribute which takes the value "sdl", "vnc", "rdp" or "desktop": <dl> <dt><code>"sdl"</code></dt> <dd> - This displays a window on the host desktop, it can take 3 optional arguments: - a <code>display</code> attribute for the display to use, an <code>xauth</code> - attribute for the authentication identifier, and an optional <code>fullscreen</code> - attribute accepting values 'yes' or 'no'. + This displays a window on the host desktop, it can take 3 + optional arguments: a <code>display</code> attribute for + the display to use, an <code>xauth</code> attribute for + the authentication identifier, and an + optional <code>fullscreen</code> attribute accepting + values 'yes' or 'no'. </dd> <dt><code>"vnc"</code></dt> <dd> - Starts a VNC server. The <code>port</code> attribute specifies the TCP - port number (with -1 as legacy syntax indicating that it should be - auto-allocated). The <code>autoport</code> attribute is the new - preferred syntax for indicating autoallocation of the TCP port to use. - The <code>listen</code> attribute is an IP address for the server to - listen on. The <code>passwd</code> attribute provides a VNC password - in clear text. The <code>keymap</code> attribute specifies the keymap - 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. - - Rather than using listen/port, QEMU supports a <code>socket</code> - attribute for listening on a unix domain socket path. - Since 0.8.8 + Starts a VNC server. The <code>port</code> attribute + specifies the TCP port number (with -1 as legacy syntax + indicating that it should be + auto-allocated). The <code>autoport</code> attribute is + the new preferred syntax for indicating autoallocation of + the TCP port to use. The <code>listen</code> attribute is + an IP address for the server to listen + on. The <code>passwd</code> attribute provides a VNC + password in clear text. The <code>keymap</code> attribute + specifies the keymap 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. Rather than using listen/port, + QEMU supports a <code>socket</code> attribute for + listening on a unix domain socket + path.Since 0.8.8 </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 - secure port number. The <code>autoport</code> attribute is the new - preferred syntax for indicating autoallocation of both port numbers. - The <code>listen</code> attribute is an IP address for the server to - listen on. The <code>passwd</code> attribute provides a SPICE password - in clear text. The <code>keymap</code> attribute specifies the keymap - 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. - "spice" since 0.8.6. + 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 secure + port number. The <code>autoport</code> attribute is the + new preferred syntax for indicating autoallocation of + both port numbers. The <code>listen</code> attribute is + an IP address for the server to listen + on. The <code>passwd</code> attribute provides a SPICE + password in clear text. The <code>keymap</code> + attribute specifies the keymap 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."spice" since 0.8.6. - 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 - the main <graphics> element. Valid channel names include - <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>. + 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 the + main <graphics> element. Valid channel names + include <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> <graphics type='spice' port='-1' tlsPort='-1' autoport='yes'> @@ -1951,23 +1975,27 @@ qemu-kvm -net nic,model=? /dev/null </dd> <dt><code>"rdp"</code></dt> <dd> - Starts a RDP server. The <code>port</code> attribute - specifies the TCP port number (with -1 as legacy syntax indicating - that it should be auto-allocated). The <code>autoport</code> attribute - is the new preferred syntax for indicating autoallocation of the TCP - port to use. The <code>replaceUser</code> attribute is a boolean deciding - whether multiple simultaneous connections to the VM are permitted. - The <code>multiUser</code> whether the existing connection must be dropped - and a new connection must be established by the VRDP server, when a new - client connects in single connection mode. - + Starts a RDP server. The <code>port</code> attribute + specifies the TCP port number (with -1 as legacy syntax + indicating that it should be + auto-allocated). The <code>autoport</code> attribute is + the new preferred syntax for indicating autoallocation of + the TCP port to use. The <code>replaceUser</code> + attribute is a boolean deciding whether multiple + simultaneous connections to the VM are permitted. + The <code>multiUser</code> whether the existing connection + must be dropped and a new connection must be established + by the VRDP server, when a new client connects in single + connection mode. </dd> <dt><code>"desktop"</code></dt> <dd> - This value is reserved for VirtualBox domains for the moment. It displays - a window on the host desktop, similarly to "sdl", but using the VirtualBox - viewer. Just like "sdl", it accepts the optional attributes <code>display</code> - and <code>fullscreen</code>. + This value is reserved for VirtualBox domains for the + moment. It displays a window on the host desktop, + similarly to "sdl", but using the VirtualBox viewer. Just + like "sdl", it accepts the optional + attributes <code>display</code> + and <code>fullscreen</code>. </dd> </dl> </dd> @@ -2389,8 +2417,9 @@ qemu-kvm -net nic,model=? /dev/null ...</pre> - Alternatively you can use <code>telnet</code> instead of <code>raw</code> TCP. - Since 0.8.5 you can also use <code>telnets</code> + Alternatively you can use <code>telnet</code> instead + of <code>raw</code> TCP. Since 0.8.5 + you can also use <code>telnets</code> (secure telnet) and <code>tls</code>. -- 1.7.4.4

2 1

[libvirt] Virsh Command Reference is out of date
by Gui Jianfeng 07 Jul '11

07 Jul '11

Hi, Virsh Command Reference on libvirt.org seems out of date, it's at libvirt 0.8.7 http://libvirt.org/sources/virshcmdref/html-single/ Any one can help to update it to latest stable libvirt? Thanks, Gui

2 1

Re: [libvirt] php-virt-control
by Michal Novotny 07 Jul '11

07 Jul '11

On 07/03/2011 05:28 PM, Andreas Cymbal wrote: > > Hello i have some problem with php-virt-control > > */Message:/**/ /*/Cannot connect to hypervisor. Please change > connection information. /(Local)// > > Virt-manager run without Problems > > Virsh run only with sudo virsh > > My System is Ubuntu 10.04 LTS 64 > > With Xen 4.1.1 and 2.6.32.40 > > Libvirt 0.9.2 > > How does xen+ssh work without any password or ssh keys? > > Yours AndrewCat > Hi Andrew, it can't. The xen+ssh or anything+ssh is requiring the keys since libvirt is using ssh command directly and not libssh2 so it doesn't work even with the password specified. The only thing you have to do it to provide the SSH keys to the apache. You can run the 'tools/apache-key-copy' tool from the repository which will automatically generate the keys for user "apache" if it doesn't exist and copy it to the remote host which is required. If you see the message about libvirt-php cannot connect to the hypervisor then you should try setting up the connection information in the form at the bottom of the page. Is the system having the PolicyKit or something similar to this? You need to enable the authentication for virsh not to require password for the connection to 'xen:///' (which should be the local Xen connection URI). For more information about authentication please see the libvirt authentication page at http://libvirt.org/auth.html . Thanks, Michal -- Michal Novotny <minovotn(a)redhat.com>, RHCE, Red Hat Virtualization | libvirt-php bindings | php-virt-control.org

1 0

[libvirt] 腾讯 could you give me any suggestions when running libvirtd in the container
by kevenzhu(朱以军) 07 Jul '11

07 Jul '11

Hi all: we manage the contaienr vms using libvirt, and we want to mornitor the vms by running the libvirtd in the container. but there is something wrong with it, a lock in the kernel is crashed. if you run the "sudo" or "ping" .etc, the system call can NOT be returned, the status of the command is D. would you like to give me the hand. Thank you BR.

1 0

[libvirt] Fwd: cvs commit: ports/devel/libvirt Makefile distinfo ports/devel/libvirt/files patch-docs__apibuild.py patch-libvirtd.h
by Jason Helfman 07 Jul '11

07 Jul '11

libvirt has been updated for FreeBSD to the latest. -jgh -- Jason Helfman System Administrator experts-exchange.com http://www.experts-exchange.com/M_4830110.html E4AD 7CF1 1396 27F6 79DD 4342 5E92 AD66 8C8C FBA5

1 0

[libvirt] [PATCHv2 0/2] delete unnecessary white space of sysinfo.
by Minoru Usui 07 Jul '11

07 Jul '11

sysinfo: delete unnecessary white space of sysinfo. This is v2 of delete unnecessary white space of sysinfo. Changes v1->v2: - Rebase latest libvirt GIT tree. - Use c_isspace() in virSkipSpacesBackwards(). Minoru Usui (2): sysinfo: add virSkipSpacesBackwards() sysinfo: delete unnecessary white space of sysinfo. src/util/sysinfo.c | 21 +++++++++++++++++++++ src/util/util.c | 25 +++++++++++++++++++++++++ src/util/util.h | 1 + 3 files changed, 47 insertions(+), 0 deletions(-) -- Minoru Usui <usui(a)mxm.nes.nec.co.jp>

2 10

[libvirt] building error
by Wen Congyang 07 Jul '11

07 Jul '11

When I build libvirt, I meet the following error: make[3]: Entering directory `/home/wency/rpmbuild/BUILD/libvirt-0.9.2/daemon' CC libvirtd-libvirtd.o CC libvirtd-remote.o remote.c: In function 'remoteDispatchAuthPolkit': remote.c:2043: error: invalid initializer make[3]: *** [libvirtd-remote.o] Error 1 This patch can fix the problem. But I do not know whether it is right. >From b03a5c08b751440460bf4cb02fea061b77fb3ef5 Mon Sep 17 00:00:00 2001 From: Wen Congyang <wency(a)cn.fujitsu.com> Date: Wed, 29 Jun 2011 19:04:19 +0800 Subject: [PATCH 1/2] daemon: Fix building error with polkit1 --- daemon/remote.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/daemon/remote.c b/daemon/remote.c index 9e6cf77..042894b 100644 --- a/daemon/remote.c +++ b/daemon/remote.c @@ -2041,7 +2041,7 @@ remoteDispatchAuthPolkit(virNetServerPtr server ATTRIBUTE_UNUSED, goto authdeny; } PROBE(CLIENT_AUTH_ALLOW, "fd=%d, auth=%d, username=%s", - virNetServerClientGetFD(client), REMOTE_AUTH_POLKIT, ident); + virNetServerClientGetFD(client), REMOTE_AUTH_POLKIT, (char *)ident); VIR_INFO("Policy allowed action %s from pid %d, uid %d", action, callerPid, callerUid); ret->complete = 1; -- 1.7.1

4 13

[libvirt] libvirt 0.9.3, missing header
by Jason Helfman 06 Jul '11

06 Jul '11

When building the latest code in a clean building environment, with sasl disabled, I get this error: gmake[3]: Entering directory `/work/a/ports/devel/libvirt/work/libvirt-0.9.3/daemon' CC libvirtd-libvirtd.o In file included from libvirtd.h:41, from libvirtd.c:41: ../src/rpc/virnetsaslcontext.h:24:24: error: sasl/sasl.h: No such file or directory In file included from libvirtd.h:41, from libvirtd.c:41: ../src/rpc/virnetsaslcontext.h:54: warning: type defaults to 'int' in declaration of 'sasl_callback_t' ../src/rpc/virnetsaslcontext.h:54: error: expected ';', ',' or ')' before '*' token ../src/rpc/virnetsaslcontext.h:78: error: expected declaration specifiers or '...' before 'sasl_interact_t' ../src/rpc/virnetsaslcontext.h:86: error: expected declaration specifiers or '...' before 'sasl_interact_t' gmake[3]: *** [libvirtd-libvirtd.o] Error 1 gmake[3]: Leaving directory `/work/a/ports/devel/libvirt/work/libvirt-0.9.3/daemon' gmake[2]: *** [all] Error 2 gmake[2]: Leaving directory `/work/a/ports/devel/libvirt/work/libvirt-0.9.3/daemon' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/work/a/ports/devel/libvirt/work/libvirt-0.9.3' gmake: *** [all] Error 2 *** Error code 1 Any ideas? Thanks, Jason -- Jason Helfman System Administrator experts-exchange.com http://www.experts-exchange.com/M_4830110.html E4AD 7CF1 1396 27F6 79DD 4342 5E92 AD66 8C8C FBA5

2 2

[libvirt] Strange failure of commandtest when doing F15 build
by Laine Stump 06 Jul '11

06 Jul '11

Today I added some patches to the f15 branch of Fedora libvirt, ran "fedpkg local" to be sure it was all in order, then did a "fedpkg commit -p" and "fedpkg build". When I came back awhile later, I found that it had failed. Looking in the logs, I could see that the failure was due to tests/commandtest. Since the failure says almost nothing (and there was nothing even remotely related in any of the changes), I decided to try and build 1) the older libvirt and 2) with debugging turned on in the tests. I had no idea how to do this, but nirik in #fedora-devel helped me out, and I did the following: 1) reverted the libvirt.spec file locally (so that I'm working with source that previously built) 2) added the following lines just prior to "make check" in the specfile: export VIR_TEST_VERBOSE=1 export LIBVIRT_LOG_OUTPUTS=3:stderr export LIBVIRT_LOG_FILTERS="1:command" export VIR_TEST_DEBUG=2 3) added something identifiable to the version string in libvirt.spec: Release: 4.test%{?dist}%{?extra_release} 4) fedpkg srpm 5) koji build --scratch dist-f15 libvirt-0.8.8-4.test.fc15.src.rpm This build also failed. The results are here: http://koji.fedoraproject.org/koji/taskinfo?taskID=3182099 (search for "... FAIL") So it appears that some other package on the build machine has been updated, and it's causing most of the tests in commandtest to fail. Unfortunately, even when debugging is turned on the tests don't say anything about why they failed. Any ideas?

2 1

[libvirt] [PATCH] Reduce code duplication in virFileMakePath(Helper)
by Matthias Bolte 06 Jul '11

06 Jul '11

Move stat and mkdir to virFileMakePathHelper. Also use the stat result to detect whether the existing path is a directory and set errno accordingly if it's not. --- src/util/util.c | 44 ++++++++++++++------------------------------ 1 files changed, 14 insertions(+), 30 deletions(-) diff --git a/src/util/util.c b/src/util/util.c index 4710fc5..d944123 100644 --- a/src/util/util.c +++ b/src/util/util.c @@ -1013,11 +1013,17 @@ int virDirCreate(const char *path ATTRIBUTE_UNUSED, static int virFileMakePathHelper(char *path) { struct stat st; - char *p = NULL; + char *p; - if (stat(path, &st) >= 0) - return 0; - else if (errno != ENOENT) + if (stat(path, &st) >= 0) { + if (S_ISDIR(st.st_mode)) + return 0; + + errno = ENOTDIR; + return -1; + } + + if (errno != ENOENT) return -1; if ((p = strrchr(path, '/')) == NULL) { @@ -1049,39 +1055,17 @@ static int virFileMakePathHelper(char *path) int virFileMakePath(const char *path) { int ret = -1; - struct stat st; - char *parent = NULL; - char *p; - - if (stat(path, &st) >= 0) - return 0; - else if (errno != ENOENT) - goto cleanup; + char *tmp; - if ((parent = strdup(path)) == NULL) { + if ((tmp = strdup(path)) == NULL) { errno = ENOMEM; goto cleanup; } - if ((p = strrchr(parent, '/')) == NULL) { - errno = EINVAL; - goto cleanup; - } - - if (p != parent) { - *p = '\0'; - - if (virFileMakePathHelper(parent) < 0) - goto cleanup; - } - - if (mkdir(path, 0777) < 0 && errno != EEXIST) - goto cleanup; - - ret = 0; + ret = virFileMakePathHelper(tmp); cleanup: - VIR_FREE(parent); + VIR_FREE(tmp); return ret; } -- 1.7.4.1

2 3