| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
On Linux, sync(2) does not actually issue a write barrier, thus it
doesn't force a flush of the underlying hardware write cache (or
qemu's disk cache in the virtual case).
This can be a problem, because libguestfs relies on running sync in
the appliance, followed by killing qemu (using SIGTERM).
In most cases, this is fine, because killing qemu with SIGTERM should
cause it to flush out the disk cache before it exits. However we have
found various bugs in qemu which cause qemu to crash while doing the
flush, leaving the data unwritten (see RHBZ#836913).
The solution is to issue fsync(2) to the block devices. This has a
write barrier, so it ensures that qemu writes out its cache long
before we get around to killing qemu.
(cherry picked from commit c0a3c9ce70b98171e737e49e6dccc4457963f2ec)
|
|
|
|
|
|
|
|
|
|
| |
On Debian, the Ruby C extensions library isn't '-lruby', it's
something like '-lruby1.8' or '-lruby-1.9.1' and these can even be
parallel-installed.
Fix detection so we use Ruby's own rbconfig.rb file to find the right
library to use.
(cherry picked from commit cba49169094f04dead9b165b6b5991afa92132ff)
|
|
|
|
|
| |
No functional change.
(cherry picked from commit b07d0968823d008776345a1c724713d2320e1571)
|
|
|
|
| |
(cherry picked from commit b9f858e5eefa0d2abae5ff0a61a39b0d34334bc1)
|
| |
|
|
|
|
|
| |
This function was first added to Ruby in 1.8.7.
(cherry picked from commit 8098d062b4cb70defd4aecba0ba8cd75cf893751)
|
|
|
|
|
|
|
| |
If -lruby was not available, this used to define HAVE_LIBRUBY=0.
However this meant that the later test -n "$HAVE_LIBRUBY" would
be successful, whereas it should fail in this case.
(cherry picked from commit 823ba05ebd8f1a12574a3f154aaf7c8b4f2aeeac)
|
| |
|
|
|
|
|
| |
This didn't exist on ancient autoconf in RHEL 5.
(cherry picked from commit 489da3ccdf96e995d3f53fe68eced37b16baa1d2)
|
|
|
|
|
|
|
|
|
|
|
|
| |
RHEL 5-era FUSE didn't have this function.
I copied the function out of upstream FUSE, since the license is
compatible.
Cherry picked from commit 4846b84476015874d569c14c2c30fcd71aa4d54c
and backported to libguestfs 1.16. This includes more of the
development 'configure.ac' than is strictly necessary, but on the
other hand it brings the code closer to that development branch.
|
|
|
|
|
| |
For our purposes, the two tools are compatible.
(cherry picked from commit 87de36670108a19b832e8f5ded8d413e7b575d70)
|
| |
|
| |
|
| |
|
|
|
|
| |
(cherry picked from commit 77afc92fcd08677f9a9ae3b4f6c6919eb8ec2b33)
|
|
|
|
| |
(cherry picked from commit 0e960614ab0f7d878347d74229ffbb69a4a05540)
|
|
|
|
|
|
|
|
|
|
| |
'./configure --disable-probes' will disable these probes. Otherwise
they are autodetected as before.
The <sys/sdt.h> produces lots of errors when you try to compile with
these probes enabled under clang, so it is necessary to provide a way
to disable them for clang users.
(cherry picked from commit a1680f03b7d38bf007d29ac23035e5af33736b0e)
|
| |
|
|
|
|
| |
(cherry picked from commit 79822d46e3d7785ae7b02272e6661f15a61f4b5e)
|
|
|
|
|
| |
Since it describes the C library, it's better in the src/ directory.
(cherry picked from commit bb73cf0941ba9d34eb2ecf82d10ecb5fc5d2362d)
|
| |
|
|
|
|
|
|
|
|
| |
Fix typos spotted by http://github.com/lyda/misspell-check.
* configure.ac: As above.
* ocaml/examples/guestfs-ocaml.pod: Likewise.
* fish/guestfish.pod: Likewise.
(cherry picked from commit e97b6a1bb15e8cad319dceff53c58f8267e8152f)
|
|
|
|
|
| |
This option didn't exist in RHEL 6 valgrind.
(cherry picked from commit 58a5b5bd944655b028c915a91dad2220176986db)
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
(cherry picked from commit 8111b108d224dda868f257ac0ef23838991b3594)
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Netpbm and icoutils (wrestool) have always been dependencies. Since
they are not always present, make these into optional dependencies
(which they were, sort of, before).
Also document these dependencies in the README file.
(cherry picked from commit 2c9c0525ebda105f37e6a6eea2307db4cb2f0a73)
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
(cherry picked from commit 016ae77e6c2331560a3716ea1ebae82f122b4909)
|
| |
|
|
|
|
|
|
|
|
| |
Check /sbin, /usr/sbin, /bin and /usr/bin to ensure that neither the
directory nor the parent (eg. /usr) is a symlink, and use this
directory for the virtual directory used to store guestfsd in the
appliance.
(cherry picked from commit 3c9ef0e9780443d28a078c49bab80cb13e5608ae)
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This commit allows you to run the daemon under valgrind. You have to
enable it at configure time:
./configure --enable-valgrind-daemon
This should *not* be done for production builds.
When this feature is enabled, valgrind is added to the appliance and
the daemon is run under valgrind. Log messages from valgrind are
passed back over a virtio-serial channel into a file called
'valgrind.log.$PID' in the top build directory.
Running 'make check', 'make extra-tests' etc causes many
valgrind.log.* files to be created which must be examined by hand.
(cherry picked from commit d08806adfc5d111b4b6c761540ff508d3f25b66e)
|
|
|
|
|
|
|
|
|
| |
This fixes...
configure: error: conditional "INSTALL_DAEMON" was never defined.
... when specifying --disable-daemon
(cherry picked from commit 22224254fa4676735985818d2ff3c8feafe4457c)
|
| |
|