- 25 4月, 2016 8 次提交
-
-
由 Andrea Bolognani 提交于
Define $(PODFILES) and $(MANINFILES) so that adding a new man page only requires changes in a few, well defined spots.
-
由 Andrea Bolognani 提交于
The generated man pages may contain information that depend on the build configuration, so they should not be shipped but rather always built on the user's machine.
-
由 Andrea Bolognani 提交于
After this commit, all man pages are generated using the same two steps: 1. Process a source $command.pod file with pod2man(1) to obtain a valid man page in $command.$section.in 2. Process $command.$section.in with sed(1) to obtain the final man page in $command.$section
-
由 Andrea Bolognani 提交于
Man pages in daemon/ and src/ are being already subjected to this post-processing step: make it so those in tools/ are as well.
-
由 Andrea Bolognani 提交于
No file should be created inside $(srcdir) during build.
-
由 Andrea Bolognani 提交于
Instead of embedding the pod information inside the respective source files, store them in separate files. This allows us to reduce the number of custom build rules as most of the information can be inferred for the file name; moreover, text editors are more likely to use proper syntax highlighting for standalone pod files.
-
由 Andrea Bolognani 提交于
This is the source file for the virt-admin(1) manual page, so it should be shipped.
-
由 Peter Krempa 提交于
Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1329819
-
- 21 4月, 2016 8 次提交
-
-
由 Andrea Bolognani 提交于
According to the autoconf manual, using '$(LN_S) -f' is not portable; remove the target explicitly beforehand to work around this limitation. Adjust some slightly awkward indentation while at it.
-
由 Cole Robinson 提交于
virsh # list --all Id Name State ---------------------------------------------------- 1 test running virsh # connect frob error: Failed to connect to the hypervisor error: no connection driver available for frob virsh # list --all error: failed to connect to the hypervisor error: no valid connection error: no connection driver available for frob Seems sensible IMO to just not clear out the old connection state until the new virConnectOpen succeeds. https://bugzilla.redhat.com/show_bug.cgi?id=829160
-
由 Roman Bogorodskiy 提交于
Re-do 0217089b so it does not add regression for commit c0726e07 that allowed to print help without making a connection to the daemon.
-
由 Andrea Bolognani 提交于
The autoconf documentation recommends to always use this construct when creating symbolic links with $(LN_S) to avoid unexpected behavior.
-
由 Andrea Bolognani 提交于
The current rule fails if the target already exists: cd /home/jenkins/build/libvirt/lib && \ ln -s libnss_libvirt.so.1 nss_libvirt.so.1 ln: nss_libvirt.so.1: File exists Makefile:3357: recipe for target 'install-exec-hook' failed However, all other rules concerned with installation are idempotent and will happily overwrite an existing target, so this one should as well.
-
由 Peter Krempa 提交于
The only place that uses it doesn't warrant a separate label.
-
由 Peter Krempa 提交于
After failing to parse the perf event list, the code would return failure without freeing the previously acquired object. Rearrange the code to avoid the problem. Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1329046
-
由 Roman Bogorodskiy 提交于
Currently, if a connection URI was specified on the command line by the '-c' switch, virsh connects to it, but after connecting overrides its value with the one it tries to obtain from the VIRSH_DEFAULT_CONNECT_URI environment variable. This makes virsh connecting to the wrong URI if it disconnects from the hypervisor and then tries to reconnect, and also leaks the original connname. Fix by calling virGetEnvBlockSUID() before virshParseArgv().
-
- 20 4月, 2016 2 次提交
-
-
由 Michal Privoznik 提交于
On BSD we are creating this symlink to libnss_libvirt.so called nss_libvirt.so. That's just the way it is on BSD. However, when uninstalling, we try to remove libnss_libvirt.so instead of the symlink. Moreover, if file we are trying to remove does not exist we error out instead of ignoring the error. Signed-off-by: NMichal Privoznik <mprivozn@redhat.com>
-
由 Cole Robinson 提交于
virsh vol-clone is expected to clone a volume within a single pool; it doesn't work for cloning across pools. Clarify the docs https://bugzilla.redhat.com/show_bug.cgi?id=1103714
-
- 18 4月, 2016 1 次提交
-
-
由 Erik Skultety 提交于
Wire up the server threadpool tunable APIs to virt-admin client. Also, provide a man page for both commands. Signed-off-by: NErik Skultety <eskultet@redhat.com>
-
- 16 4月, 2016 1 次提交
-
-
由 John Ferlan 提交于
Coverity found that commit id 'c661b675' needed to create a cleanup path to handle the closing of 'fp' if the virBitmapNewQuiet failed.
-
- 15 4月, 2016 4 次提交
-
-
由 Olga Krishtal 提交于
Ploop image consists of directory with two files: ploop image itself, called root.hds and DiskDescriptor.xml that contains information about ploop device: https://openvz.org/Ploop/format. Such volume are difficult to manipulate in terms of existing volume types because they are neither a single files nor a directory. This patch introduces new volume type - ploop. This volume type is used by ploop volume's exclusively. Signed-off-by: NOlga Krishtal <okrishtal@virtuozzo.com> Signed-off-by: NJán Tomko <jtomko@redhat.com>
-
由 Nitesh Konkar 提交于
Signed-off-by: NNitesh Konkar <nitkon12@linux.vnet.ibm.com>
-
由 Cole Robinson 提交于
Take setlocale/gettext error handling pattern from tools/virsh-* and use it for all standalone binaries via a new shared virGettextInitialize routine. The virsh* pattern differed slightly from other callers. All users now consistently: * Ignore setlocale errors. virsh has done this forever, presumably for good reason. This has been partially responsible for some bug reports: https://bugzilla.redhat.com/show_bug.cgi?id=1312688 https://bugzilla.redhat.com/show_bug.cgi?id=1026514 https://bugzilla.redhat.com/show_bug.cgi?id=1016158 * Report the failed function name * Report strerror
-
-
- 14 4月, 2016 2 次提交
-
-
由 ShaoHe Feng 提交于
Signed-off-by: NNikolay Shirokovskiy <nshirokovskiy@virtuozzo.com>
-
由 Nikolay Shirokovskiy 提交于
Upcoming compression options for migration command patch series hits current limit of 32 possible options for a command. Lets take one step further and support 64 possible options. And all it takes is moving from 32 bit integers to 64 bit ones. The only less then trivial change i found is moving from 'ffs' to 'ffsl'. Signed-off-by: NNikolay Shirokovskiy <nshirokovskiy@virtuozzo.com>
-
- 13 4月, 2016 4 次提交
-
-
由 Peter Krempa 提交于
Since we didn't opt to use one single event for device lifecycle for a VM we are missing one last event if the device removal failed. This event will be emitted once we asked to eject the device but for some reason it is not possible.
-
由 Andrea Bolognani 提交于
virt-host-validate, just like virt-login-shell, doesn't make sense on Windows, so we should avoid building it. Make the tool optional and build it by default on all platforms except Windows, erroring out if the user attempts to build it anyway.
-
由 Andrea Bolognani 提交于
Instead of having separate handling for programs and man pages, deal with both in the same place.
-
由 Maxim Nestratov 提交于
Signed-off-by: NMaxim Nestratov <mnestratov@virtuozzo.com>
-
- 11 4月, 2016 1 次提交
-
-
由 Andrea Bolognani 提交于
Simply checking whether the cgroup name appears somewhere inside /proc/self/cgroup is enough most of the time, but there are some corner cases that require a more mindful parsing.
-
- 09 4月, 2016 1 次提交
-
-
由 Roman Bogorodskiy 提交于
Explicitly add Linux and BSD syms files for nss to EXTRA_DIST instead of using the LIBVIRT_NSS_SYMBOL_FILE variable, because its value will point to either Linux or BSD syms file, but we need to ship both.
-
- 08 4月, 2016 1 次提交
-
-
由 Andrea Bolognani 提交于
The existing code is built on the assumption that no cgroup name can appear as part of another cgroup name; moreover, cgroups are expected to always be listed in a specific order. If that's not the case, eg. 'cpuacct' is listed before 'cpu', the algorithm fails to detect the cgroup mount point. Rewrite it to get rid of such assumptions.
-
- 07 4月, 2016 1 次提交
-
-
由 Andrea Bolognani 提交于
Instead of relying on substring search, tokenize the input and process each CPU flag separately. This ensures CPU flag detection will continue to work correctly even if we start looking for CPU flags whose name might appear as part of other CPU flags' names. The result of processing is stored in a virBitmap, which means we don't have to parse /proc/cpuinfo in its entirety for each single CPU flag we want to check. Moreover, use of the newly-introduced virHostValidateCPUFlag enumeration ensures we don't go looking for random CPU flags which might actually be simple typos.
-
- 06 4月, 2016 3 次提交
-
-
由 Ján Tomko 提交于
There is a LIBVIRT_ADMIN_DEFAULT_URI environment variable which is honored by virAdmConnectOpen and documented in the virt-admin man page. LIBVIRT_DEFAULT_ADMIN_URI is undocumented and this is its only occurrence.
-
由 Ján Tomko 提交于
vshStrdup returns NULL without exiting on NULL input.
-
由 Ján Tomko 提交于
Postpone filling out the default connection in ctl->connname after calling virshInit. This allows printing help without a connection to the daemon.
-
- 01 4月, 2016 1 次提交
-
-
由 Nitesh Konkar 提交于
When using the --start option, the show_count should not be set to max_id as the --start <cpu> means we dont need those many initial cpu stats. Hence, show_count should be adjusted accordingly. https://bugzilla.redhat.com/show_bug.cgi?id=1249441Signed-off-by: NNitesh Konkar <nitkon12@linux.vnet.ibm.com> Signed-off-by: NJán Tomko <jtomko@redhat.com>
-
- 31 3月, 2016 2 次提交
-
-
由 Michal Privoznik 提交于
Now that we have @flags we can support changing perf events just in active or inactive configuration regardless of the other. Previously, calling virDomainSetPerfEvents set events in both active and inactive configuration at once. Even though we allow users to set perf events that are to be enabled once domain is started up. The virDomainGetPerfEvents API was flawed too. It returned just runtime info. Signed-off-by: NMichal Privoznik <mprivozn@redhat.com>
-
由 Michal Privoznik 提交于
Everywhere else we use a comma separated list. There's no good reason to make 'perf' command an exception. Currently, it accepts string list separated by '|'. Signed-off-by: NMichal Privoznik <mprivozn@redhat.com>
-