| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
| |
(cherry picked from commit 9c2b9c2df6c3c10b090d71bc808d755dbf625cbe)
|
|
|
|
|
|
|
| |
Add proper dependencies for these files, but also use 'cmp' to ensure
they only get overwritten if the new files have actually changed, so
we don't rebuild the appliance unnecessarily.
(cherry picked from commit b25aea33fa314857c8094e09af9654f925fb935f)
|
|
|
|
|
|
|
| |
Just make gcc happy.
Signed-off-by: Wanlong Gao <gaowanlong@cn.fujitsu.com>
(cherry picked from commit 2f89f584c0203023f8a829ff9796dc2c14ddeb68)
|
|
|
|
|
| |
This fixes commit 1e17a32060feb937b3972f61b37f9116ad7d8d9a.
(cherry picked from commit 8e75e21b23f18ec0b0fa4f07f96c31dd56a50f25)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
case_sensitive_path is undefined when the final path element doesn't
exist. Currently it returns an error, but this means that creating a
new file doesn't work as expected:
$ guestfish --rw -i -d windows touch 'win:c:\blah'
libguestfs: error: case_sensitive_path: blah no file or directory found with this name
We should allow this case (provided there is no trailing slash) so
that new files or directories can be created.
(cherry picked from commit 973581780d8a006f336684fef6762801402d775d)
|
|
|
|
|
| |
This is just code motion.
(cherry picked from commit ac0373bdecfabe6acf99d3662e5117de73fa2aef)
|
|
|
|
|
|
| |
Instead of working around bugs, podwrapper has been fixed so that
links work in all output formats.
(cherry picked from commit 4bc110e2bc738bde9b9c09bc602ef13c06b60e90)
|
|
|
|
| |
(cherry picked from commit 182b4a66609ffd5366575d72351cd8174cf68145)
|
|
|
|
|
|
| |
The superclass sometimes uses this and will give an undefined
error if it's missing.
(cherry picked from commit 9967ad3fa13178c70afd5da77f77a4115808733d)
|
|
|
|
|
|
|
|
| |
Messages now look like this:
podwrapper.pl: wrote guestfs-examples.3
podwrapper.pl: wrote ../html/guestfs-examples.3.html
(cherry picked from commit 60c42dd2a1a173ec1161502762bc33ae7a1cf190)
|
|
|
|
| |
(cherry picked from commit f6846d74c947bd8b711ef0b29148fa1e90580354)
|
|
|
|
|
|
| |
$g is the "standard" name for libguestfs handles.
(cherry picked from commit a99ea198b24745c49cdb42645c3497ac3b0e6a2f)
|
|
|
|
| |
(cherry picked from commit 8d0baf7b859fbbe40bdb072b2009d77c02cee7c3)
|
|
|
|
|
|
|
|
|
| |
This uses Pod::Simple so it properly parses the input POD and can
generate proper custom output as required specifically by libguestfs.
One immediate benefit is that links between and within manual pages
now work mostly correctly.
(cherry picked from commit 1e17a32060feb937b3972f61b37f9116ad7d8d9a)
|
|
|
|
|
|
| |
There used to be a <div> around the table of contents, but that
is no longer present.
(cherry picked from commit 0bf1e5b6650e71434430bf119b486a779516886d)
|
|
|
|
|
| |
Some of the generated files anyway.
(cherry picked from commit 3a442e66170518f725b92a1041546d81fde95492)
|
|
|
|
|
|
| |
This will allow us to easily change the location of this
script in future.
(cherry picked from commit f2ea617e224cd82496e56a41b5878063d6f02e3d)
|
|
|
|
|
| |
Set MBR partition type byte accordingly.
(cherry picked from commit 24b7979ea25cbe5f08494cc4580c1341e78e090e)
|
|
|
|
|
|
|
|
|
| |
RHBZ#838081."
This reverts commit ad7c4498f66f37c4219242c6df04d28e9ee7877f.
Reverted because we still see core dumps.
(cherry picked from commit d69a03e44832d8a8da84696bd4e2aaf3cd5d6cff)
|
|
|
|
| |
(cherry picked from commit 98f2d221cfe184535a493057f5b2b38d8bee34e4)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
For example the existing method:
public void mkfs_opts (String fstype, String device, Map<..> optargs);
is now accompanied by this overloaded method which is a simple wrapper:
public void mkfs_opts (String fstype, String device)
throws LibGuestFSException
{
mkfs_opts (fstype, device, null);
}
(cherry picked from commit 0da2dbef26a9efddbc1f4cd6cbe796b3b5f98d13)
|
|
|
|
| |
(cherry picked from commit 7a0478bed0fe3ccbdf16087552f3d6ea196f29ec)
|
|
|
|
| |
(cherry picked from commit 196742cd46a8d80f0298f9f58c540482919306a3)
|
|
|
|
| |
(cherry picked from commit cf0defedb8121a0ff39c1d4c6d9f3eee9fd7ee72)
|
|
|
|
| |
(cherry picked from commit ec0c7e0a1aafd145309ab53749d910ad837d8745)
|
|
|
|
| |
(cherry picked from commit f883e4d8d3ea65c5cd4c2dc5d557989c00aafc56)
|
|
|
|
|
| |
This fixes commit f9a5e3ed86ee7bcd13619f13b4d4de6ce46ac8c3.
(cherry picked from commit 33bb7408f684bf0d4eff0a0e99c53449fa4923e4)
|
|
|
|
| |
(cherry picked from commit f9a5e3ed86ee7bcd13619f13b4d4de6ce46ac8c3)
|
| |
|
|
|
|
| |
(cherry picked from commit 8df259496a80bc74edbab4436e3679d0900bd173)
|
|
|
|
| |
(cherry picked from commit 5546ea6d68532caa69fbede1f29385afe34e7362)
|
|
|
|
| |
(cherry picked from commit bfbfe6dd788ee3705383b544c5bc238a7dd5ca53)
|
|
|
|
|
|
| |
See also:
https://bugzilla.redhat.com/show_bug.cgi?id=835466#c9
(cherry picked from commit 1cde66165aac222f1a07ad4c3873c61d49eabb02)
|
|
|
|
| |
(cherry picked from commit b749dc70742e749dbd7c0c20e6e7191fdd199170)
|
|
|
|
|
|
|
| |
This reverts commit 6e5a85bb9b6557bc337625a339728e23f5f2dd94.
It turns out this is a bug in QEMU after all.
(cherry picked from commit bd3e42a8ded1ed7a4177ad03646572eb6155a49c)
|
|
|
|
| |
(cherry picked from commit e6dec159488f589df62c9f59477281f8264a19c8)
|
| |
|
|
|
|
| |
(cherry picked from commit 1596b6026ddd1e343efc6a74fc23f46e4975868f)
|
|
|
|
|
|
|
|
| |
https://bugs.launchpad.net/qemu/+bug/1021649 is invalid, probably
caused by a Fedora ROM.
This updates commit 52d188e32fb8addb45bf926df07e34ab35898f85.
(cherry picked from commit 6e5a85bb9b6557bc337625a339728e23f5f2dd94)
|
|
|
|
| |
(cherry picked from commit ad7c4498f66f37c4219242c6df04d28e9ee7877f)
|
|
|
|
| |
(cherry picked from commit 52d188e32fb8addb45bf926df07e34ab35898f85)
|
|
|
|
|
|
|
|
|
| |
Earlier versions of qemu contained a bug in the qcow2 code which
causes qemu to segfault when shutting down and flushing its internal
cache, and this can result in data loss.
Cherry picked from commit 7996e0882442dc7bac2ab573e2fcac0b488c8cc7
and changed to suit stable-1.18 releases.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The new API splits orderly close into a two-step process:
if (guestfs_shutdown (g) == -1) {
/* handle the error, eg. qemu error */
}
guestfs_close (g);
Note that the explicit shutdown step is only necessary in the case
where you have made changes to the disk image and want to handle write
errors. Read the documentation for further information.
This change also:
- deprecates guestfs_kill_subprocess
- turns guestfs_kill_subprocess into the same as guestfs_shutdown
- changes guestfish and other tools to call shutdown + close
where necessary (not for read-only tools)
- updates documentation
- updates examples
(cherry picked from commit ffbf1475f7ae7c462db289ad4834391469e72edd)
|
|
|
|
|
|
| |
Currently guestfs_close has no method to return an error indication,
so this commit simply prints the error on stderr.
(cherry picked from commit bcc4ffb52b9f4b5db7861682905ec32844f4603b)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The order is now:
- remove the handle from the list of handles
- send close trace message
- sync and shutdown qemu
- run user close callback
- free temporary directory
- free memory
This commit ought to be no functional change.
(cherry picked from commit fc3c6fff4b0a6ffeb75aa78b1d73241a14a03cd1)
|
|
|
|
|
|
|
|
| |
Make the comments consistent.
Also make the Perl example call $g->close explicitly so it is
consistent with the other examples.
(cherry picked from commit 27ebf517fae972eee49ae5911a03fabe5f4b6e54)
|
|
|
|
|
|
| |
This is now set by default in all supported versions of libguestfs.
It's just confusing if the examples refer to it.
(cherry picked from commit 917550a117904ec1a06b77a7870a147014d71adb)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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)
|
|
|
|
|
| |
No functional change.
(cherry picked from commit cb24ceedd8a8ef7da71cfcce6db10669de47685c)
|
|
|
|
|
| |
This is just a comment and has no functional effect.
(cherry picked from commit 0437a7905619b8370e25fbae1a3e6388c5277be9)
|