| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Complete the attach-method libvirt backend.
This backend uses libvirt to create a transient KVM domain to run the
appliance.
Note that this still will only work with local libvirt URIs since the
<kernel>, <initrd> and appliance links in the libvirt XML refer to
local files, and virtio serial only works locally (limitation of
libvirt). Remote support will be added later.
|
| |
|
|
|
| |
With this commit, you can set the attach method to libvirt,
but calling launch will give an error.
|
| |
|
|
| |
This is just code motion.
|
| |
|
|
|
|
|
|
|
| |
Since we will be calling guestfs___build_appliance from the libvirt
code in future, there's no point having two places where we have to
acquire the lock. Push the lock down into this function instead.
Because "glthread/lock.h" includes <errno.h> we have to add this
header to the file too.
|
| |
|
|
|
|
| |
Just make gcc happy when fuse is not available.
Signed-off-by: Wanlong Gao <gaowanlong@cn.fujitsu.com>
|
| |
|
|
|
|
| |
g->attach_ops points to a structure which contains the
operations supported by each attach method backend
(ie. appliance, unix, etc.).
|
| |
|
|
|
| |
Although we still use the handle as convenient temporary
storage.
|
| |
|
|
|
|
| |
Move and rewrite guestfs_config so it accumulates a list of qemu
parameters in the handle. These are added to the appliance at launch
time (with attach method == unix:... you'll now get an error).
|
| | |
|
| | |
|
| |
|
|
| |
Arrange the fields more logically. This is just code motion.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
launch-appliance.c contains the code associated with the 'appliance'
attach-method. Mostly. In fact there are a few APIs which don't fit
so nicely:
- config: deprecated API which fiddles with the qemu command
line directly
- max-disks: depends on the qemu implementation (virtio-scsi
or not)
- debug-drives: used for testing only
launch-unix.c contains the code associated with 'unix:<path>'.
launch.c is the common code for launching, along with a few other APIs
such as guestfs_add_drive_opts.
This commit also reduces the number of headers to just those
which are required.
|
| |
|
|
|
| |
Note that debug* calls are not part of the stable API and can be
removed or changed at any time.
|
| |
|
|
| |
Just a small code cleanup / simplification.
|
| |
|
|
|
|
|
| |
This is just code motion.
Some files cannot be renamed. Notably rpcgen input and output files
must not contain dash characters, else rpcgen breaks.
|
| |
|
|
|
| |
This file handles the -d option for guestfish and other C command line
utilities. Renaming this file makes it less confusing.
|
| |
|
|
|
| |
This file contains the code implementing guestfs_add_domain
(for adding a libvirt domain) so this name is less confusing.
|
| | |
|
| | |
|
| |
|
|
| |
This fixes commit 1e17a32060feb937b3972f61b37f9116ad7d8d9a.
|
| |
|
|
|
|
|
| |
COPYING from https://www.gnu.org/licenses/gpl-2.0.txt
COPYING.LIB from https://www.gnu.org/licenses/lgpl-2.1.txt
(Note this change shouldn't alter the licensing of libguestfs)
|
| |
|
|
|
| |
Includes rebuilt gnulib to work around test problems with
test-getlogin_r.
|
| |
|
|
|
| |
See:
https://lists.gnu.org/archive/html/bug-gnulib/2012-07/msg00194.html
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Unfortunately the parallel test keeps hitting this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=838081
which could be a bug in the OCaml runtime.
Just test simple mount-local. We will write a parallel test in C to
replace this.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
doesn't support chown (RHBZ#840572).
When using tar-in or tools built around it such as virt-make-fs, if
the target filesystem is vfat then unpacking the tarball would fail
because tar tries to chown(2) files and fails.
You would see errors such as:
tar: <file>: Cannot change ownership to uid 500, gid 500: Operation not permitted
This change detects whether the target filesystem supports chown(2).
If not, it adds the --no-same-owner flag to tar to stop it from trying
to change the ownership of newly created files.
|
| |
|
|
|
| |
This is mostly code motion, although the precise contract of this
function changes slightly to make it more generally useful
|
| | |
|
| |
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Add xfs_info to show the geometry of the xfs filesystem.
Signed-off-by: Wanlong Gao <gaowanlong@cn.fujitsu.com>
RWMJ:
- Updated po/POTFILES.
- Use xfs_ prefix for all struct fields.
- Return uninitialized fields as -1 / empty string.
- Copyedit the description.
|
| |
|
|
|
|
| |
Just make gcc happy.
Signed-off-by: Wanlong Gao <gaowanlong@cn.fujitsu.com>
|
| |
|
|
| |
This fixes commit 1e17a32060feb937b3972f61b37f9116ad7d8d9a.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
| |
This is just code motion.
|
| |
|
|
|
| |
Instead of working around bugs, podwrapper has been fixed so that
links work in all output formats.
|
| | |
|
| |
|
|
|
| |
The superclass sometimes uses this and will give an undefined
error if it's missing.
|
| |
|
|
|
|
|
| |
Messages now look like this:
podwrapper.pl: wrote guestfs-examples.3
podwrapper.pl: wrote ../html/guestfs-examples.3.html
|
| | |
|
| |
|
|
| |
$g is the "standard" name for libguestfs handles.
|
| | |
|
| |
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
| |
There used to be a <div> around the table of contents, but that
is no longer present.
|
