5 guestfs - Library for accessing and modifying virtual machine images
11 guestfs_h *g = guestfs_create ();
12 guestfs_add_drive (g, "guest.img");
14 guestfs_mount (g, "/dev/sda1", "/");
15 guestfs_touch (g, "/hello");
16 guestfs_umount (g, "/");
20 cc prog.c -o prog -lguestfs
22 cc prog.c -o prog `pkg-config libguestfs --cflags --libs`
26 Libguestfs is a library for accessing and modifying guest disk images.
27 Amongst the things this is good for: making batch configuration
28 changes to guests, getting disk used/free statistics (see also:
29 virt-df), migrating between virtualization systems (see also:
30 virt-p2v), performing partial backups, performing partial guest
31 clones, cloning guests and changing registry/UUID/hostname info, and
34 Libguestfs uses Linux kernel and qemu code, and can access any type of
35 guest filesystem that Linux and qemu can, including but not limited
36 to: ext2/3/4, btrfs, FAT and NTFS, LVM, many different disk partition
37 schemes, qcow, qcow2, vmdk.
39 Libguestfs provides ways to enumerate guest storage (eg. partitions,
40 LVs, what filesystem is in each LV, etc.). It can also run commands
41 in the context of the guest. Also you can access filesystems over
44 Libguestfs is a library that can be linked with C and C++ management
45 programs (or management programs written in OCaml, Perl, Python, Ruby,
46 Java, PHP, Haskell or C#). You can also use it from shell scripts or the
49 You don't need to be root to use libguestfs, although obviously you do
50 need enough permissions to access the disk images.
52 Libguestfs is a large API because it can do many things. For a gentle
53 introduction, please read the L</API OVERVIEW> section next.
57 This section provides a gentler overview of the libguestfs API. We
58 also try to group API calls together, where that may not be obvious
59 from reading about the individual calls in the main section of this
64 Before you can use libguestfs calls, you have to create a handle.
65 Then you must add at least one disk image to the handle, followed by
66 launching the handle, then performing whatever operations you want,
67 and finally closing the handle. By convention we use the single
68 letter C<g> for the name of the handle variable, although of course
69 you can use any name you want.
71 The general structure of all libguestfs-using programs looks like
74 guestfs_h *g = guestfs_create ();
76 /* Call guestfs_add_drive additional times if there are
77 * multiple disk images.
79 guestfs_add_drive (g, "guest.img");
81 /* Most manipulation calls won't work until you've launched
82 * the handle 'g'. You have to do this _after_ adding drives
83 * and _before_ other commands.
87 /* Now you can examine what partitions, LVs etc are available.
89 char **partitions = guestfs_list_partitions (g);
90 char **logvols = guestfs_lvs (g);
92 /* To access a filesystem in the image, you must mount it.
94 guestfs_mount (g, "/dev/sda1", "/");
96 /* Now you can perform filesystem actions on the guest
99 guestfs_touch (g, "/hello");
101 /* You only need to call guestfs_sync if you have made
102 * changes to the guest image. (But if you've made changes
103 * then you *must* sync). See also: guestfs_umount and
104 * guestfs_umount_all calls.
108 /* Close the handle 'g'. */
111 The code above doesn't include any error checking. In real code you
112 should check return values carefully for errors. In general all
113 functions that return integers return C<-1> on error, and all
114 functions that return pointers return C<NULL> on error. See section
115 L</ERROR HANDLING> below for how to handle errors, and consult the
116 documentation for each function call below to see precisely how they
117 return error indications.
121 The image filename (C<"guest.img"> in the example above) could be a
122 disk image from a virtual machine, a L<dd(1)> copy of a physical hard
123 disk, an actual block device, or simply an empty file of zeroes that
124 you have created through L<posix_fallocate(3)>. Libguestfs lets you
125 do useful things to all of these.
127 The call you should use in modern code for adding drives is
128 L</guestfs_add_drive_opts>. To add a disk image, allowing writes, and
129 specifying that the format is raw, do:
131 guestfs_add_drive_opts (g, filename,
132 GUESTFS_ADD_DRIVE_OPTS_FORMAT, "raw",
135 You can add a disk read-only using:
137 guestfs_add_drive_opts (g, filename,
138 GUESTFS_ADD_DRIVE_OPTS_FORMAT, "raw",
139 GUESTFS_ADD_DRIVE_OPTS_READONLY, 1,
142 or by calling the older function L</guestfs_add_drive_ro>. In either
143 case libguestfs won't modify the file.
145 Be extremely cautious if the disk image is in use, eg. if it is being
146 used by a virtual machine. Adding it read-write will almost certainly
147 cause disk corruption, but adding it read-only is safe.
149 You must add at least one disk image, and you may add multiple disk
150 images. In the API, the disk images are usually referred to as
151 C</dev/sda> (for the first one you added), C</dev/sdb> (for the second
154 Once L</guestfs_launch> has been called you cannot add any more images.
155 You can call L</guestfs_list_devices> to get a list of the device
156 names, in the order that you added them. See also L</BLOCK DEVICE
161 Before you can read or write files, create directories and so on in a
162 disk image that contains filesystems, you have to mount those
163 filesystems using L</guestfs_mount>. If you already know that a disk
164 image contains (for example) one partition with a filesystem on that
165 partition, then you can mount it directly:
167 guestfs_mount (g, "/dev/sda1", "/");
169 where C</dev/sda1> means literally the first partition (C<1>) of the
170 first disk image that we added (C</dev/sda>). If the disk contains
171 Linux LVM2 logical volumes you could refer to those instead (eg. C</dev/VG/LV>).
173 If you are given a disk image and you don't know what it contains then
174 you have to find out. Libguestfs can do that too: use
175 L</guestfs_list_partitions> and L</guestfs_lvs> to list possible
176 partitions and LVs, and either try mounting each to see what is
177 mountable, or else examine them with L</guestfs_vfs_type> or
178 L</guestfs_file>. Libguestfs also has a set of APIs for inspection of
179 disk images (see L</INSPECTION> below). But you might find it easier
180 to look at higher level programs built on top of libguestfs, in
181 particular L<virt-inspector(1)>.
183 To mount a disk image read-only, use L</guestfs_mount_ro>. There are
184 several other variations of the C<guestfs_mount_*> call.
186 =head2 FILESYSTEM ACCESS AND MODIFICATION
188 The majority of the libguestfs API consists of fairly low-level calls
189 for accessing and modifying the files, directories, symlinks etc on
190 mounted filesystems. There are over a hundred such calls which you
191 can find listed in detail below in this man page, and we don't even
192 pretend to cover them all in this overview.
194 Specify filenames as full paths, starting with C<"/"> and including
197 For example, if you mounted a filesystem at C<"/"> and you want to
198 read the file called C<"etc/passwd"> then you could do:
200 char *data = guestfs_cat (g, "/etc/passwd");
202 This would return C<data> as a newly allocated buffer containing the
203 full content of that file (with some conditions: see also
204 L</DOWNLOADING> below), or C<NULL> if there was an error.
206 As another example, to create a top-level directory on that filesystem
207 called C<"var"> you would do:
209 guestfs_mkdir (g, "/var");
211 To create a symlink you could do:
213 guestfs_ln_s (g, "/etc/init.d/portmap",
214 "/etc/rc3.d/S30portmap");
216 Libguestfs will reject attempts to use relative paths and there is no
217 concept of a current working directory.
219 Libguestfs can return errors in many situations: for example if the
220 filesystem isn't writable, or if a file or directory that you
221 requested doesn't exist. If you are using the C API (documented here)
222 you have to check for those error conditions after each call. (Other
223 language bindings turn these errors into exceptions).
225 File writes are affected by the per-handle umask, set by calling
226 L</guestfs_umask> and defaulting to 022. See L</UMASK>.
230 Libguestfs contains API calls to read, create and modify partition
231 tables on disk images.
233 In the common case where you want to create a single partition
234 covering the whole disk, you should use the L</guestfs_part_disk>
237 const char *parttype = "mbr";
238 if (disk_is_larger_than_2TB)
240 guestfs_part_disk (g, "/dev/sda", parttype);
242 Obviously this effectively wipes anything that was on that disk image
247 Libguestfs provides access to a large part of the LVM2 API, such as
248 L</guestfs_lvcreate> and L</guestfs_vgremove>. It won't make much sense
249 unless you familiarize yourself with the concepts of physical volumes,
250 volume groups and logical volumes.
252 This author strongly recommends reading the LVM HOWTO, online at
253 L<http://tldp.org/HOWTO/LVM-HOWTO/>.
257 Use L</guestfs_cat> to download small, text only files. This call
258 is limited to files which are less than 2 MB and which cannot contain
259 any ASCII NUL (C<\0>) characters. However it has a very simple
262 L</guestfs_read_file> can be used to read files which contain
263 arbitrary 8 bit data, since it returns a (pointer, size) pair.
264 However it is still limited to "small" files, less than 2 MB.
266 L</guestfs_download> can be used to download any file, with no
267 limits on content or size (even files larger than 4 GB).
269 To download multiple files, see L</guestfs_tar_out> and
274 It's often the case that you want to write a file or files to the disk
277 To write a small file with fixed content, use L</guestfs_write>. To
278 create a file of all zeroes, use L</guestfs_truncate_size> (sparse) or
279 L</guestfs_fallocate64> (with all disk blocks allocated). There are a
280 variety of other functions for creating test files, for example
281 L</guestfs_fill> and L</guestfs_fill_pattern>.
283 To upload a single file, use L</guestfs_upload>. This call has no
284 limits on file content or size (even files larger than 4 GB).
286 To upload multiple files, see L</guestfs_tar_in> and L</guestfs_tgz_in>.
288 However the fastest way to upload I<large numbers of arbitrary files>
289 is to turn them into a squashfs or CD ISO (see L<mksquashfs(8)> and
290 L<mkisofs(8)>), then attach this using L</guestfs_add_drive_ro>. If
291 you add the drive in a predictable way (eg. adding it last after all
292 other drives) then you can get the device name from
293 L</guestfs_list_devices> and mount it directly using
294 L</guestfs_mount_ro>. Note that squashfs images are sometimes
295 non-portable between kernel versions, and they don't support labels or
296 UUIDs. If you want to pre-build an image or you need to mount it
297 using a label or UUID, use an ISO image instead.
301 There are various different commands for copying between files and
302 devices and in and out of the guest filesystem. These are summarised
307 =item B<file> to B<file>
309 Use L</guestfs_cp> to copy a single file, or
310 L</guestfs_cp_a> to copy directories recursively.
312 =item B<file or device> to B<file or device>
314 Use L</guestfs_dd> which efficiently uses L<dd(1)>
315 to copy between files and devices in the guest.
317 Example: duplicate the contents of an LV:
319 guestfs_dd (g, "/dev/VG/Original", "/dev/VG/Copy");
321 The destination (C</dev/VG/Copy>) must be at least as large as the
322 source (C</dev/VG/Original>). To copy less than the whole
323 source device, use L</guestfs_copy_size>.
325 =item B<file on the host> to B<file or device>
327 Use L</guestfs_upload>. See L</UPLOADING> above.
329 =item B<file or device> to B<file on the host>
331 Use L</guestfs_download>. See L</DOWNLOADING> above.
337 L</guestfs_ll> is just designed for humans to read (mainly when using
338 the L<guestfish(1)>-equivalent command C<ll>).
340 L</guestfs_ls> is a quick way to get a list of files in a directory
341 from programs, as a flat list of strings.
343 L</guestfs_readdir> is a programmatic way to get a list of files in a
344 directory, plus additional information about each one. It is more
345 equivalent to using the L<readdir(3)> call on a local filesystem.
347 L</guestfs_find> and L</guestfs_find0> can be used to recursively list
350 =head2 RUNNING COMMANDS
352 Although libguestfs is primarily an API for manipulating files
353 inside guest images, we also provide some limited facilities for
354 running commands inside guests.
356 There are many limitations to this:
362 The kernel version that the command runs under will be different
363 from what it expects.
367 If the command needs to communicate with daemons, then most likely
368 they won't be running.
372 The command will be running in limited memory.
376 The network may not be available unless you enable it
377 (see L</guestfs_set_network>).
381 Only supports Linux guests (not Windows, BSD, etc).
385 Architecture limitations (eg. won't work for a PPC guest on
390 For SELinux guests, you may need to enable SELinux and load policy
391 first. See L</SELINUX> in this manpage.
395 I<Security:> It is not safe to run commands from untrusted, possibly
396 malicious guests. These commands may attempt to exploit your program
397 by sending unexpected output. They could also try to exploit the
398 Linux kernel or qemu provided by the libguestfs appliance. They could
399 use the network provided by the libguestfs appliance to bypass
400 ordinary network partitions and firewalls. They could use the
401 elevated privileges or different SELinux context of your program
404 A secure alternative is to use libguestfs to install a "firstboot"
405 script (a script which runs when the guest next boots normally), and
406 to have this script run the commands you want in the normal context of
407 the running guest, network security and so on.
411 The two main API calls to run commands are L</guestfs_command> and
412 L</guestfs_sh> (there are also variations).
414 The difference is that L</guestfs_sh> runs commands using the shell, so
415 any shell globs, redirections, etc will work.
417 =head2 CONFIGURATION FILES
419 To read and write configuration files in Linux guest filesystems, we
420 strongly recommend using Augeas. For example, Augeas understands how
421 to read and write, say, a Linux shadow password file or X.org
422 configuration file, and so avoids you having to write that code.
424 The main Augeas calls are bound through the C<guestfs_aug_*> APIs. We
425 don't document Augeas itself here because there is excellent
426 documentation on the L<http://augeas.net/> website.
428 If you don't want to use Augeas (you fool!) then try calling
429 L</guestfs_read_lines> to get the file as a list of lines which
430 you can iterate over.
434 We support SELinux guests. To ensure that labeling happens correctly
435 in SELinux guests, you need to enable SELinux and load the guest's
442 Before launching, do:
444 guestfs_set_selinux (g, 1);
448 After mounting the guest's filesystem(s), load the policy. This
449 is best done by running the L<load_policy(8)> command in the
452 guestfs_sh (g, "/usr/sbin/load_policy");
454 (Older versions of C<load_policy> require you to specify the
455 name of the policy file).
459 Optionally, set the security context for the API. The correct
460 security context to use can only be known by inspecting the
461 guest. As an example:
463 guestfs_setcon (g, "unconfined_u:unconfined_r:unconfined_t:s0");
467 This will work for running commands and editing existing files.
469 When new files are created, you may need to label them explicitly,
470 for example by running the external command
471 C<restorecon pathname>.
475 Certain calls are affected by the current file mode creation mask (the
476 "umask"). In particular ones which create files or directories, such
477 as L</guestfs_touch>, L</guestfs_mknod> or L</guestfs_mkdir>. This
478 affects either the default mode that the file is created with or
479 modifies the mode that you supply.
481 The default umask is C<022>, so files are created with modes such as
482 C<0644> and directories with C<0755>.
484 There are two ways to avoid being affected by umask. Either set umask
485 to 0 (call C<guestfs_umask (g, 0)> early after launching). Or call
486 L</guestfs_chmod> after creating each file or directory.
488 For more information about umask, see L<umask(2)>.
490 =head2 ENCRYPTED DISKS
492 Libguestfs allows you to access Linux guests which have been
493 encrypted using whole disk encryption that conforms to the
494 Linux Unified Key Setup (LUKS) standard. This includes
495 nearly all whole disk encryption systems used by modern
498 Use L</guestfs_vfs_type> to identify LUKS-encrypted block
499 devices (it returns the string C<crypto_LUKS>).
501 Then open these devices by calling L</guestfs_luks_open>.
502 Obviously you will require the passphrase!
504 Opening a LUKS device creates a new device mapper device
505 called C</dev/mapper/mapname> (where C<mapname> is the
506 string you supply to L</guestfs_luks_open>).
507 Reads and writes to this mapper device are decrypted from and
508 encrypted to the underlying block device respectively.
510 LVM volume groups on the device can be made visible by calling
511 L</guestfs_vgscan> followed by L</guestfs_vg_activate_all>.
512 The logical volume(s) can now be mounted in the usual way.
514 Use the reverse process to close a LUKS device. Unmount
515 any logical volumes on it, deactivate the volume groups
516 by caling C<guestfs_vg_activate (g, 0, ["/dev/VG"])>.
517 Then close the mapper device by calling
518 L</guestfs_luks_close> on the C</dev/mapper/mapname>
519 device (I<not> the underlying encrypted block device).
523 Libguestfs has APIs for inspecting an unknown disk image to find out
524 if it contains operating systems. (These APIs used to be in a
525 separate Perl-only library called L<Sys::Guestfs::Lib(3)> but since
526 version 1.5.3 the most frequently used part of this library has been
527 rewritten in C and moved into the core code).
529 Add all disks belonging to the unknown virtual machine and call
530 L</guestfs_launch> in the usual way.
532 Then call L</guestfs_inspect_os>. This function uses other libguestfs
533 calls and certain heuristics, and returns a list of operating systems
534 that were found. An empty list means none were found. A single
535 element is the root filesystem of the operating system. For dual- or
536 multi-boot guests, multiple roots can be returned, each one
537 corresponding to a separate operating system. (Multi-boot virtual
538 machines are extremely rare in the world of virtualization, but since
539 this scenario can happen, we have built libguestfs to deal with it.)
541 For each root, you can then call various C<guestfs_inspect_get_*>
542 functions to get additional details about that operating system. For
543 example, call L</guestfs_inspect_get_type> to return the string
544 C<windows> or C<linux> for Windows and Linux-based operating systems
547 Un*x-like and Linux-based operating systems usually consist of several
548 filesystems which are mounted at boot time (for example, a separate
549 boot partition mounted on C</boot>). The inspection rules are able to
550 detect how filesystems correspond to mount points. Call
551 C<guestfs_inspect_get_mountpoints> to get this mapping. It might
552 return a hash table like this example:
555 / => /dev/vg_guest/lv_root
556 /usr => /dev/vg_guest/lv_usr
558 The caller can then make calls to L</guestfs_mount_options> to
559 mount the filesystems as suggested.
561 Be careful to mount filesystems in the right order (eg. C</> before
562 C</usr>). Sorting the keys of the hash by length, shortest first,
565 Inspection currently only works for some common operating systems.
566 Contributors are welcome to send patches for other operating systems
567 that we currently cannot detect.
569 Encrypted disks must be opened before inspection. See
570 L</ENCRYPTED DISKS> for more details. The L</guestfs_inspect_os>
571 function just ignores any encrypted devices.
573 A note on the implementation: The call L</guestfs_inspect_os> performs
574 inspection and caches the results in the guest handle. Subsequent
575 calls to C<guestfs_inspect_get_*> return this cached information, but
576 I<do not> re-read the disks. If you change the content of the guest
577 disks, you can redo inspection by calling L</guestfs_inspect_os>
580 =head2 SPECIAL CONSIDERATIONS FOR WINDOWS GUESTS
582 Libguestfs can mount NTFS partitions. It does this using the
583 L<http://www.ntfs-3g.org/> driver.
585 DOS and Windows still use drive letters, and the filesystems are
586 always treated as case insensitive by Windows itself, and therefore
587 you might find a Windows configuration file referring to a path like
588 C<c:\windows\system32>. When the filesystem is mounted in libguestfs,
589 that directory might be referred to as C</WINDOWS/System32>.
591 Drive letter mappings are outside the scope of libguestfs. You have
592 to use libguestfs to read the appropriate Windows Registry and
593 configuration files, to determine yourself how drives are mapped (see
594 also L<hivex(3)> and L<virt-inspector(1)>).
596 Replacing backslash characters with forward slash characters is also
597 outside the scope of libguestfs, but something that you can easily do.
599 Where we can help is in resolving the case insensitivity of paths.
600 For this, call L</guestfs_case_sensitive_path>.
602 Libguestfs also provides some help for decoding Windows Registry
603 "hive" files, through the library C<hivex> which is part of the
604 libguestfs project although ships as a separate tarball. You have to
605 locate and download the hive file(s) yourself, and then pass them to
606 C<hivex> functions. See also the programs L<hivexml(1)>,
607 L<hivexsh(1)>, L<hivexregedit(1)> and L<virt-win-reg(1)> for more help
610 =head2 USING LIBGUESTFS WITH OTHER PROGRAMMING LANGUAGES
612 Although we don't want to discourage you from using the C API, we will
613 mention here that the same API is also available in other languages.
615 The API is broadly identical in all supported languages. This means
616 that the C call C<guestfs_mount(g,path)> is
617 C<$g-E<gt>mount($path)> in Perl, C<g.mount(path)> in Python,
618 and C<Guestfs.mount g path> in OCaml. In other words, a
619 straightforward, predictable isomorphism between each language.
621 Error messages are automatically transformed
622 into exceptions if the language supports it.
624 We don't try to "object orientify" parts of the API in OO languages,
625 although contributors are welcome to write higher level APIs above
626 what we provide in their favourite languages if they wish.
632 You can use the I<guestfs.h> header file from C++ programs. The C++
633 API is identical to the C API. C++ classes and exceptions are not
638 The C# bindings are highly experimental. Please read the warnings
639 at the top of C<csharp/Libguestfs.cs>.
643 This is the only language binding that is working but incomplete.
644 Only calls which return simple integers have been bound in Haskell,
645 and we are looking for help to complete this binding.
649 Full documentation is contained in the Javadoc which is distributed
654 For documentation see the file C<guestfs.mli>.
658 For documentation see L<Sys::Guestfs(3)>.
662 For documentation see C<README-PHP> supplied with libguestfs
663 sources or in the php-libguestfs package for your distribution.
665 The PHP binding only works correctly on 64 bit machines.
669 For documentation do:
677 Use the Guestfs module. There is no Ruby-specific documentation, but
678 you can find examples written in Ruby in the libguestfs source.
680 =item B<shell scripts>
682 For documentation see L<guestfish(1)>.
686 =head2 LIBGUESTFS GOTCHAS
688 L<http://en.wikipedia.org/wiki/Gotcha_(programming)>: "A feature of a
689 system [...] that works in the way it is documented but is
690 counterintuitive and almost invites mistakes."
692 Since we developed libguestfs and the associated tools, there are
693 several things we would have designed differently, but are now stuck
694 with for backwards compatibility or other reasons. If there is ever a
695 libguestfs 2.0 release, you can expect these to change. Beware of
700 =item Autosync / forgetting to sync.
702 When modifying a filesystem from C or another language, you B<must>
703 unmount all filesystems and call L</guestfs_sync> explicitly before
704 you close the libguestfs handle. You can also call:
706 guestfs_set_autosync (g, 1);
708 to have the unmount/sync done automatically for you when the handle 'g'
709 is closed. (This feature is called "autosync", L</guestfs_set_autosync>
712 If you forget to do this, then it is entirely possible that your
713 changes won't be written out, or will be partially written, or (very
714 rarely) that you'll get disk corruption.
716 Note that in L<guestfish(3)> autosync is the default. So quick and
717 dirty guestfish scripts that forget to sync will work just fine, which
718 can make this very puzzling if you are trying to debug a problem.
720 Update: Autosync is enabled by default for all API users starting from
723 =item Mount option C<-o sync> should not be the default.
725 If you use L</guestfs_mount>, then C<-o sync,noatime> are added
726 implicitly. However C<-o sync> does not add any reliability benefit,
727 but does have a very large performance impact.
729 The work around is to use L</guestfs_mount_options> and set the mount
730 options that you actually want to use.
732 =item Read-only should be the default.
734 In L<guestfish(3)>, I<--ro> should be the default, and you should
735 have to specify I<--rw> if you want to make changes to the image.
737 This would reduce the potential to corrupt live VM images.
739 Note that many filesystems change the disk when you just mount and
740 unmount, even if you didn't perform any writes. You need to use
741 L</guestfs_add_drive_ro> to guarantee that the disk is not changed.
743 =item guestfish command line is hard to use.
745 C<guestfish disk.img> doesn't do what people expect (open C<disk.img>
746 for examination). It tries to run a guestfish command C<disk.img>
747 which doesn't exist, so it fails. In earlier versions of guestfish
748 the error message was also unintuitive, but we have corrected this
749 since. Like the Bourne shell, we should have used C<guestfish -c
750 command> to run commands.
752 =item guestfish megabyte modifiers don't work right on all commands
754 In recent guestfish you can use C<1M> to mean 1 megabyte (and
755 similarly for other modifiers). What guestfish actually does is to
756 multiply the number part by the modifier part and pass the result to
757 the C API. However this doesn't work for a few APIs which aren't
758 expecting bytes, but are already expecting some other unit
761 The most common is L</guestfs_lvcreate>. The guestfish command:
765 does not do what you might expect. Instead because
766 L</guestfs_lvcreate> is already expecting megabytes, this tries to
767 create a 100 I<terabyte> (100 megabytes * megabytes) logical volume.
768 The error message you get from this is also a little obscure.
770 This could be fixed in the generator by specially marking parameters
771 and return values which take bytes or other units.
773 =item Ambiguity between devices and paths
775 There is a subtle ambiguity in the API between a device name
776 (eg. C</dev/sdb2>) and a similar pathname. A file might just happen
777 to be called C<sdb2> in the directory C</dev> (consider some non-Unix
780 In the current API we usually resolve this ambiguity by having two
781 separate calls, for example L</guestfs_checksum> and
782 L</guestfs_checksum_device>. Some API calls are ambiguous and
783 (incorrectly) resolve the problem by detecting if the path supplied
784 begins with C</dev/>.
786 To avoid both the ambiguity and the need to duplicate some calls, we
787 could make paths/devices into structured names. One way to do this
788 would be to use a notation like grub (C<hd(0,0)>), although nobody
789 really likes this aspect of grub. Another way would be to use a
790 structured type, equivalent to this OCaml type:
792 type path = Path of string | Device of int | Partition of int * int
794 which would allow you to pass arguments like:
797 Device 1 (* /dev/sdb, or perhaps /dev/sda *)
798 Partition (1, 2) (* /dev/sdb2 (or is it /dev/sda2 or /dev/sdb3?) *)
799 Path "/dev/sdb2" (* not a device *)
801 As you can see there are still problems to resolve even with this
802 representation. Also consider how it might work in guestfish.
806 =head2 PROTOCOL LIMITS
808 Internally libguestfs uses a message-based protocol to pass API calls
809 and their responses to and from a small "appliance" (see L</INTERNALS>
810 for plenty more detail about this). The maximum message size used by
811 the protocol is slightly less than 4 MB. For some API calls you may
812 need to be aware of this limit. The API calls which may be affected
813 are individually documented, with a link back to this section of the
816 A simple call such as L</guestfs_cat> returns its result (the file
817 data) in a simple string. Because this string is at some point
818 internally encoded as a message, the maximum size that it can return
819 is slightly under 4 MB. If the requested file is larger than this
820 then you will get an error.
822 In order to transfer large files into and out of the guest filesystem,
823 you need to use particular calls that support this. The sections
824 L</UPLOADING> and L</DOWNLOADING> document how to do this.
826 You might also consider mounting the disk image using our FUSE
827 filesystem support (L<guestmount(1)>).
829 =head2 KEYS AND PASSPHRASES
831 Certain libguestfs calls take a parameter that contains sensitive key
832 material, passed in as a C string.
834 In the future we would hope to change the libguestfs implementation so
835 that keys are L<mlock(2)>-ed into physical RAM, and thus can never end
836 up in swap. However this is I<not> done at the moment, because of the
837 complexity of such an implementation.
839 Therefore you should be aware that any key parameter you pass to
840 libguestfs might end up being written out to the swap partition. If
841 this is a concern, scrub the swap partition or don't use libguestfs on
844 =head1 CONNECTION MANAGEMENT
848 C<guestfs_h> is the opaque type representing a connection handle.
849 Create a handle by calling L</guestfs_create>. Call L</guestfs_close>
850 to free the handle and release all resources used.
852 For information on using multiple handles and threads, see the section
853 L</MULTIPLE HANDLES AND MULTIPLE THREADS> below.
855 =head2 guestfs_create
857 guestfs_h *guestfs_create (void);
859 Create a connection handle.
861 You have to call L</guestfs_add_drive_opts> (or one of the equivalent
862 calls) on the handle at least once.
864 This function returns a non-NULL pointer to a handle on success or
867 After configuring the handle, you have to call L</guestfs_launch>.
869 You may also want to configure error handling for the handle. See
870 L</ERROR HANDLING> section below.
874 void guestfs_close (guestfs_h *g);
876 This closes the connection handle and frees up all resources used.
878 =head1 ERROR HANDLING
880 API functions can return errors. For example, almost all functions
881 that return C<int> will return C<-1> to indicate an error.
883 Additional information is available for errors: an error message
884 string and optionally an error number (errno) if the thing that failed
887 You can get at the additional information about the last error on the
888 handle by calling L</guestfs_last_error>, L</guestfs_last_errno>,
889 and/or by setting up an error handler with
890 L</guestfs_set_error_handler>.
892 When the handle is created, a default error handler is installed which
893 prints the error message string to C<stderr>. For small short-running
894 command line programs it is sufficient to do:
896 if (guestfs_launch (g) == -1)
899 since the default error handler will ensure that an error message has
900 been printed to C<stderr> before the program exits.
902 For other programs the caller will almost certainly want to install an
903 alternate error handler or do error handling in-line like this:
905 g = guestfs_create ();
907 /* This disables the default behaviour of printing errors
909 guestfs_set_error_handler (g, NULL, NULL);
911 if (guestfs_launch (g) == -1) {
912 /* Examine the error message and print it etc. */
913 char *msg = guestfs_last_error (g);
914 int errnum = guestfs_last_errno (g);
915 fprintf (stderr, "%s\n", msg);
919 Out of memory errors are handled differently. The default action is
920 to call L<abort(3)>. If this is undesirable, then you can set a
921 handler using L</guestfs_set_out_of_memory_handler>.
923 =head2 guestfs_last_error
925 const char *guestfs_last_error (guestfs_h *g);
927 This returns the last error message that happened on C<g>. If
928 there has not been an error since the handle was created, then this
931 The lifetime of the returned string is until the next error occurs, or
932 L</guestfs_close> is called.
934 =head2 guestfs_last_errno
936 int guestfs_last_errno (guestfs_h *g);
938 This returns the last error number (errno) that happened on C<g>.
940 If successful, an errno integer not equal to zero is returned.
942 If no error, this returns 0. This call can return 0 in three
949 There has not been any error on the handle.
953 There has been an error but the errno was meaningless. This
954 corresponds to the case where the error did not come from a
955 failed system call, but for some other reason.
959 There was an error from a failed system call, but for some
960 reason the errno was not captured and returned. This usually
961 indicates a bug in libguestfs.
965 Libguestfs tries to convert the errno from inside the applicance into
966 a corresponding errno for the caller (not entirely trivial: the
967 appliance might be running a completely different operating system
968 from the library and error numbers are not standardized across
969 Un*xen). If this could not be done, then the error is translated to
970 C<EINVAL>. In practice this should only happen in very rare
973 =head2 guestfs_set_error_handler
975 typedef void (*guestfs_error_handler_cb) (guestfs_h *g,
978 void guestfs_set_error_handler (guestfs_h *g,
979 guestfs_error_handler_cb cb,
982 The callback C<cb> will be called if there is an error. The
983 parameters passed to the callback are an opaque data pointer and the
984 error message string.
986 C<errno> is not passed to the callback. To get that the callback must
987 call L</guestfs_last_errno>.
989 Note that the message string C<msg> is freed as soon as the callback
990 function returns, so if you want to stash it somewhere you must make
993 The default handler prints messages on C<stderr>.
995 If you set C<cb> to C<NULL> then I<no> handler is called.
997 =head2 guestfs_get_error_handler
999 guestfs_error_handler_cb guestfs_get_error_handler (guestfs_h *g,
1002 Returns the current error handler callback.
1004 =head2 guestfs_set_out_of_memory_handler
1006 typedef void (*guestfs_abort_cb) (void);
1007 int guestfs_set_out_of_memory_handler (guestfs_h *g,
1010 The callback C<cb> will be called if there is an out of memory
1011 situation. I<Note this callback must not return>.
1013 The default is to call L<abort(3)>.
1015 You cannot set C<cb> to C<NULL>. You can't ignore out of memory
1018 =head2 guestfs_get_out_of_memory_handler
1020 guestfs_abort_fn guestfs_get_out_of_memory_handler (guestfs_h *g);
1022 This returns the current out of memory handler.
1026 Libguestfs needs a kernel and initrd.img, which it finds by looking
1027 along an internal path.
1029 By default it looks for these in the directory C<$libdir/guestfs>
1030 (eg. C</usr/local/lib/guestfs> or C</usr/lib64/guestfs>).
1032 Use L</guestfs_set_path> or set the environment variable
1033 L</LIBGUESTFS_PATH> to change the directories that libguestfs will
1034 search in. The value is a colon-separated list of paths. The current
1035 directory is I<not> searched unless the path contains an empty element
1036 or C<.>. For example C<LIBGUESTFS_PATH=:/usr/lib/guestfs> would
1037 search the current directory and then C</usr/lib/guestfs>.
1039 =head1 HIGH-LEVEL API ACTIONS
1041 =head2 ABI GUARANTEE
1043 We guarantee the libguestfs ABI (binary interface), for public,
1044 high-level actions as outlined in this section. Although we will
1045 deprecate some actions, for example if they get replaced by newer
1046 calls, we will keep the old actions forever. This allows you the
1047 developer to program in confidence against the libguestfs API.
1057 =head2 GROUPS OF FUNCTIONALITY IN THE APPLIANCE
1059 Using L</guestfs_available> you can test availability of
1060 the following groups of functions. This test queries the
1061 appliance to see if the appliance you are currently using
1062 supports the functionality.
1066 =head2 GUESTFISH supported COMMAND
1068 In L<guestfish(3)> there is a handy interactive command
1069 C<supported> which prints out the available groups and
1070 whether they are supported by this build of libguestfs.
1071 Note however that you have to do C<run> first.
1073 =head2 SINGLE CALLS AT COMPILE TIME
1075 Since version 1.5.8, C<E<lt>guestfs.hE<gt>> defines symbols
1076 for each C API function, such as:
1078 #define LIBGUESTFS_HAVE_DD 1
1080 if L</guestfs_dd> is available.
1082 Before version 1.5.8, if you needed to test whether a single
1083 libguestfs function is available at compile time, we recommended using
1084 build tools such as autoconf or cmake. For example in autotools you
1087 AC_CHECK_LIB([guestfs],[guestfs_create])
1088 AC_CHECK_FUNCS([guestfs_dd])
1090 which would result in C<HAVE_GUESTFS_DD> being either defined
1091 or not defined in your program.
1093 =head2 SINGLE CALLS AT RUN TIME
1095 Testing at compile time doesn't guarantee that a function really
1096 exists in the library. The reason is that you might be dynamically
1097 linked against a previous I<libguestfs.so> (dynamic library)
1098 which doesn't have the call. This situation unfortunately results
1099 in a segmentation fault, which is a shortcoming of the C dynamic
1100 linking system itself.
1102 You can use L<dlopen(3)> to test if a function is available
1103 at run time, as in this example program (note that you still
1104 need the compile time check as well):
1110 #include <guestfs.h>
1114 #ifdef LIBGUESTFS_HAVE_DD
1118 /* Test if the function guestfs_dd is really available. */
1119 dl = dlopen (NULL, RTLD_LAZY);
1121 fprintf (stderr, "dlopen: %s\n", dlerror ());
1122 exit (EXIT_FAILURE);
1124 has_function = dlsym (dl, "guestfs_dd") != NULL;
1128 printf ("this libguestfs.so does NOT have guestfs_dd function\n");
1130 printf ("this libguestfs.so has guestfs_dd function\n");
1131 /* Now it's safe to call
1132 guestfs_dd (g, "foo", "bar");
1136 printf ("guestfs_dd function was not found at compile time\n");
1140 You may think the above is an awful lot of hassle, and it is.
1141 There are other ways outside of the C linking system to ensure
1142 that this kind of incompatibility never arises, such as using
1145 Requires: libguestfs >= 1.0.80
1147 =head1 CALLS WITH OPTIONAL ARGUMENTS
1149 A recent feature of the API is the introduction of calls which take
1150 optional arguments. In C these are declared 3 ways. The main way is
1151 as a call which takes variable arguments (ie. C<...>), as in this
1154 int guestfs_add_drive_opts (guestfs_h *g, const char *filename, ...);
1156 Call this with a list of optional arguments, terminated by C<-1>.
1157 So to call with no optional arguments specified:
1159 guestfs_add_drive_opts (g, filename, -1);
1161 With a single optional argument:
1163 guestfs_add_drive_opts (g, filename,
1164 GUESTFS_ADD_DRIVE_OPTS_FORMAT, "qcow2",
1169 guestfs_add_drive_opts (g, filename,
1170 GUESTFS_ADD_DRIVE_OPTS_FORMAT, "qcow2",
1171 GUESTFS_ADD_DRIVE_OPTS_READONLY, 1,
1174 and so forth. Don't forget the terminating C<-1> otherwise
1175 Bad Things will happen!
1177 =head2 USING va_list FOR OPTIONAL ARGUMENTS
1179 The second variant has the same name with the suffix C<_va>, which
1180 works the same way but takes a C<va_list>. See the C manual for
1181 details. For the example function, this is declared:
1183 int guestfs_add_drive_opts_va (guestfs_h *g, const char *filename,
1186 =head2 CONSTRUCTING OPTIONAL ARGUMENTS
1188 The third variant is useful where you need to construct these
1189 calls. You pass in a structure where you fill in the optional
1190 fields. The structure has a bitmask as the first element which
1191 you must set to indicate which fields you have filled in. For
1192 our example function the structure and call are declared:
1194 struct guestfs_add_drive_opts_argv {
1200 int guestfs_add_drive_opts_argv (guestfs_h *g, const char *filename,
1201 const struct guestfs_add_drive_opts_argv *optargs);
1203 You could call it like this:
1205 struct guestfs_add_drive_opts_argv optargs = {
1206 .bitmask = GUESTFS_ADD_DRIVE_OPTS_READONLY_BITMASK |
1207 GUESTFS_ADD_DRIVE_OPTS_FORMAT_BITMASK,
1212 guestfs_add_drive_opts_argv (g, filename, &optargs);
1220 The C<_BITMASK> suffix on each option name when specifying the
1225 You do not need to fill in all fields of the structure.
1229 There must be a one-to-one correspondence between fields of the
1230 structure that are filled in, and bits set in the bitmask.
1234 =head2 OPTIONAL ARGUMENTS IN OTHER LANGUAGES
1236 In other languages, optional arguments are expressed in the
1237 way that is natural for that language. We refer you to the
1238 language-specific documentation for more details on that.
1240 For guestfish, see L<guestfish(1)/OPTIONAL ARGUMENTS>.
1244 <!-- old anchor for the next section -->
1245 <a name="state_machine_and_low_level_event_api"/>
1251 Internally, libguestfs is implemented by running an appliance (a
1252 special type of small virtual machine) using L<qemu(1)>. Qemu runs as
1253 a child process of the main program.
1259 | | child process / appliance
1260 | | __________________________
1262 +-------------------+ RPC | +-----------------+ |
1263 | libguestfs <--------------------> guestfsd | |
1264 | | | +-----------------+ |
1265 \___________________/ | | Linux kernel | |
1266 | +--^--------------+ |
1267 \_________|________________/
1275 The library, linked to the main program, creates the child process and
1276 hence the appliance in the L</guestfs_launch> function.
1278 Inside the appliance is a Linux kernel and a complete stack of
1279 userspace tools (such as LVM and ext2 programs) and a small
1280 controlling daemon called L</guestfsd>. The library talks to
1281 L</guestfsd> using remote procedure calls (RPC). There is a mostly
1282 one-to-one correspondence between libguestfs API calls and RPC calls
1283 to the daemon. Lastly the disk image(s) are attached to the qemu
1284 process which translates device access by the appliance's Linux kernel
1285 into accesses to the image.
1287 A common misunderstanding is that the appliance "is" the virtual
1288 machine. Although the disk image you are attached to might also be
1289 used by some virtual machine, libguestfs doesn't know or care about
1290 this. (But you will care if both libguestfs's qemu process and your
1291 virtual machine are trying to update the disk image at the same time,
1292 since these usually results in massive disk corruption).
1294 =head1 STATE MACHINE
1296 libguestfs uses a state machine to model the child process:
1307 / | \ \ guestfs_launch
1318 \______/ <------ \________/
1320 The normal transitions are (1) CONFIG (when the handle is created, but
1321 there is no child process), (2) LAUNCHING (when the child process is
1322 booting up), (3) alternating between READY and BUSY as commands are
1323 issued to, and carried out by, the child process.
1325 The guest may be killed by L</guestfs_kill_subprocess>, or may die
1326 asynchronously at any time (eg. due to some internal error), and that
1327 causes the state to transition back to CONFIG.
1329 Configuration commands for qemu such as L</guestfs_add_drive> can only
1330 be issued when in the CONFIG state.
1332 The API offers one call that goes from CONFIG through LAUNCHING to
1333 READY. L</guestfs_launch> blocks until the child process is READY to
1334 accept commands (or until some failure or timeout).
1335 L</guestfs_launch> internally moves the state from CONFIG to LAUNCHING
1336 while it is running.
1338 API actions such as L</guestfs_mount> can only be issued when in the
1339 READY state. These API calls block waiting for the command to be
1340 carried out (ie. the state to transition to BUSY and then back to
1341 READY). There are no non-blocking versions, and no way to issue more
1342 than one command per handle at the same time.
1344 Finally, the child process sends asynchronous messages back to the
1345 main program, such as kernel log messages. You can register a
1346 callback to receive these messages.
1348 =head2 SETTING CALLBACKS TO HANDLE EVENTS
1350 The child process generates events in some situations. Current events
1351 include: receiving a log message, the child process exits.
1353 Use the C<guestfs_set_*_callback> functions to set a callback for
1354 different types of events.
1356 Only I<one callback of each type> can be registered for each handle.
1357 Calling C<guestfs_set_*_callback> again overwrites the previous
1358 callback of that type. Cancel all callbacks of this type by calling
1359 this function with C<cb> set to C<NULL>.
1361 =head2 guestfs_set_log_message_callback
1363 typedef void (*guestfs_log_message_cb) (guestfs_h *g, void *opaque,
1364 char *buf, int len);
1365 void guestfs_set_log_message_callback (guestfs_h *g,
1366 guestfs_log_message_cb cb,
1369 The callback function C<cb> will be called whenever qemu or the guest
1370 writes anything to the console.
1372 Use this function to capture kernel messages and similar.
1374 Normally there is no log message handler, and log messages are just
1377 =head2 guestfs_set_subprocess_quit_callback
1379 typedef void (*guestfs_subprocess_quit_cb) (guestfs_h *g, void *opaque);
1380 void guestfs_set_subprocess_quit_callback (guestfs_h *g,
1381 guestfs_subprocess_quit_cb cb,
1384 The callback function C<cb> will be called when the child process
1385 quits, either asynchronously or if killed by
1386 L</guestfs_kill_subprocess>. (This corresponds to a transition from
1387 any state to the CONFIG state).
1389 =head2 guestfs_set_launch_done_callback
1391 typedef void (*guestfs_launch_done_cb) (guestfs_h *g, void *opaque);
1392 void guestfs_set_launch_done_callback (guestfs_h *g,
1393 guestfs_launch_done_cb cb,
1396 The callback function C<cb> will be called when the child process
1397 becomes ready first time after it has been launched. (This
1398 corresponds to a transition from LAUNCHING to the READY state).
1400 =head2 guestfs_set_close_callback
1402 typedef void (*guestfs_close_cb) (guestfs_h *g, void *opaque);
1403 void guestfs_set_close_callback (guestfs_h *g,
1404 guestfs_close_cb cb,
1407 The callback function C<cb> will be called while the handle
1408 is being closed (synchronously from L</guestfs_close>).
1410 Note that libguestfs installs an L<atexit(3)> handler to try to
1411 clean up handles that are open when the program exits. This
1412 means that this callback might be called indirectly from
1413 L<exit(3)>, which can cause unexpected problems in higher-level
1414 languages (eg. if your HLL interpreter has already been cleaned
1415 up by the time this is called, and if your callback then jumps
1416 into some HLL function).
1418 =head2 guestfs_set_progress_callback
1420 typedef void (*guestfs_progress_cb) (guestfs_h *g, void *opaque,
1421 int proc_nr, int serial,
1422 uint64_t position, uint64_t total);
1423 void guestfs_set_progress_callback (guestfs_h *g,
1424 guestfs_progress_cb cb,
1427 Some long-running operations can generate progress messages. If
1428 this callback is registered, then it will be called each time a
1429 progress message is generated (usually two seconds after the
1430 operation started, and three times per second thereafter until
1431 it completes, although the frequency may change in future versions).
1433 The callback receives two numbers: C<position> and C<total>.
1434 The units of C<total> are not defined, although for some
1435 operations C<total> may relate in some way to the amount of
1436 data to be transferred (eg. in bytes or megabytes), and
1437 C<position> may be the portion which has been transferred.
1439 The only defined and stable parts of the API are:
1445 The callback can display to the user some type of progress bar or
1446 indicator which shows the ratio of C<position>:C<total>.
1450 0 E<lt>= C<position> E<lt>= C<total>
1454 If any progress notification is sent during a call, then a final
1455 progress notification is always sent when C<position> = C<total>.
1457 This is to simplify caller code, so callers can easily set the
1458 progress indicator to "100%" at the end of the operation, without
1459 requiring special code to detect this case.
1463 The callback also receives the procedure number and serial number of
1464 the call. These are only useful for debugging protocol issues, and
1465 the callback can normally ignore them. The callback may want to
1466 print these numbers in error messages or debugging messages.
1468 =head1 PRIVATE DATA AREA
1470 You can attach named pieces of private data to the libguestfs handle,
1471 and fetch them by name for the lifetime of the handle. This is called
1472 the private data area and is only available from the C API.
1474 To attach a named piece of data, use the following call:
1476 void guestfs_set_private (guestfs_h *g, const char *key, void *data);
1478 C<key> is the name to associate with this data, and C<data> is an
1479 arbitrary pointer (which can be C<NULL>). Any previous item with the
1480 same name is overwritten.
1482 You can use any C<key> you want, but names beginning with an
1483 underscore character are reserved for internal libguestfs purposes
1484 (for implementing language bindings). It is recommended to prefix the
1485 name with some unique string to avoid collisions with other users.
1487 To retrieve the pointer, use:
1489 void *guestfs_get_private (guestfs_h *g, const char *key);
1491 This function returns C<NULL> if either no data is found associated
1492 with C<key>, or if the user previously set the C<key>'s C<data>
1495 Libguestfs does not try to look at or interpret the C<data> pointer in
1496 any way. As far as libguestfs is concerned, it need not be a valid
1497 pointer at all. In particular, libguestfs does I<not> try to free the
1498 data when the handle is closed. If the data must be freed, then the
1499 caller must either free it before calling L</guestfs_close> or must
1500 set up a close callback to do it (see L</guestfs_set_close_callback>,
1501 and note that only one callback can be registered for a handle).
1503 The private data area is implemented using a hash table, and should be
1504 reasonably efficient for moderate numbers of keys.
1506 =head1 BLOCK DEVICE NAMING
1508 In the kernel there is now quite a profusion of schemata for naming
1509 block devices (in this context, by I<block device> I mean a physical
1510 or virtual hard drive). The original Linux IDE driver used names
1511 starting with C</dev/hd*>. SCSI devices have historically used a
1512 different naming scheme, C</dev/sd*>. When the Linux kernel I<libata>
1513 driver became a popular replacement for the old IDE driver
1514 (particularly for SATA devices) those devices also used the
1515 C</dev/sd*> scheme. Additionally we now have virtual machines with
1516 paravirtualized drivers. This has created several different naming
1517 systems, such as C</dev/vd*> for virtio disks and C</dev/xvd*> for Xen
1520 As discussed above, libguestfs uses a qemu appliance running an
1521 embedded Linux kernel to access block devices. We can run a variety
1522 of appliances based on a variety of Linux kernels.
1524 This causes a problem for libguestfs because many API calls use device
1525 or partition names. Working scripts and the recipe (example) scripts
1526 that we make available over the internet could fail if the naming
1529 Therefore libguestfs defines C</dev/sd*> as the I<standard naming
1530 scheme>. Internally C</dev/sd*> names are translated, if necessary,
1531 to other names as required. For example, under RHEL 5 which uses the
1532 C</dev/hd*> scheme, any device parameter C</dev/sda2> is translated to
1533 C</dev/hda2> transparently.
1535 Note that this I<only> applies to parameters. The
1536 L</guestfs_list_devices>, L</guestfs_list_partitions> and similar calls
1537 return the true names of the devices and partitions as known to the
1540 =head2 ALGORITHM FOR BLOCK DEVICE NAME TRANSLATION
1542 Usually this translation is transparent. However in some (very rare)
1543 cases you may need to know the exact algorithm. Such cases include
1544 where you use L</guestfs_config> to add a mixture of virtio and IDE
1545 devices to the qemu-based appliance, so have a mixture of C</dev/sd*>
1546 and C</dev/vd*> devices.
1548 The algorithm is applied only to I<parameters> which are known to be
1549 either device or partition names. Return values from functions such
1550 as L</guestfs_list_devices> are never changed.
1556 Is the string a parameter which is a device or partition name?
1560 Does the string begin with C</dev/sd>?
1564 Does the named device exist? If so, we use that device.
1565 However if I<not> then we continue with this algorithm.
1569 Replace initial C</dev/sd> string with C</dev/hd>.
1571 For example, change C</dev/sda2> to C</dev/hda2>.
1573 If that named device exists, use it. If not, continue.
1577 Replace initial C</dev/sd> string with C</dev/vd>.
1579 If that named device exists, use it. If not, return an error.
1583 =head2 PORTABILITY CONCERNS
1585 Although the standard naming scheme and automatic translation is
1586 useful for simple programs and guestfish scripts, for larger programs
1587 it is best not to rely on this mechanism.
1589 Where possible for maximum future portability programs using
1590 libguestfs should use these future-proof techniques:
1596 Use L</guestfs_list_devices> or L</guestfs_list_partitions> to list
1597 actual device names, and then use those names directly.
1599 Since those device names exist by definition, they will never be
1604 Use higher level ways to identify filesystems, such as LVM names,
1605 UUIDs and filesystem labels.
1611 =head2 COMMUNICATION PROTOCOL
1613 Don't rely on using this protocol directly. This section documents
1614 how it currently works, but it may change at any time.
1616 The protocol used to talk between the library and the daemon running
1617 inside the qemu virtual machine is a simple RPC mechanism built on top
1618 of XDR (RFC 1014, RFC 1832, RFC 4506).
1620 The detailed format of structures is in C<src/guestfs_protocol.x>
1621 (note: this file is automatically generated).
1623 There are two broad cases, ordinary functions that don't have any
1624 C<FileIn> and C<FileOut> parameters, which are handled with very
1625 simple request/reply messages. Then there are functions that have any
1626 C<FileIn> or C<FileOut> parameters, which use the same request and
1627 reply messages, but they may also be followed by files sent using a
1630 =head3 ORDINARY FUNCTIONS (NO FILEIN/FILEOUT PARAMS)
1632 For ordinary functions, the request message is:
1634 total length (header + arguments,
1635 but not including the length word itself)
1636 struct guestfs_message_header (encoded as XDR)
1637 struct guestfs_<foo>_args (encoded as XDR)
1639 The total length field allows the daemon to allocate a fixed size
1640 buffer into which it slurps the rest of the message. As a result, the
1641 total length is limited to C<GUESTFS_MESSAGE_MAX> bytes (currently
1642 4MB), which means the effective size of any request is limited to
1643 somewhere under this size.
1645 Note also that many functions don't take any arguments, in which case
1646 the C<guestfs_I<foo>_args> is completely omitted.
1648 The header contains the procedure number (C<guestfs_proc>) which is
1649 how the receiver knows what type of args structure to expect, or none
1652 The reply message for ordinary functions is:
1654 total length (header + ret,
1655 but not including the length word itself)
1656 struct guestfs_message_header (encoded as XDR)
1657 struct guestfs_<foo>_ret (encoded as XDR)
1659 As above the C<guestfs_I<foo>_ret> structure may be completely omitted
1660 for functions that return no formal return values.
1662 As above the total length of the reply is limited to
1663 C<GUESTFS_MESSAGE_MAX>.
1665 In the case of an error, a flag is set in the header, and the reply
1666 message is slightly changed:
1668 total length (header + error,
1669 but not including the length word itself)
1670 struct guestfs_message_header (encoded as XDR)
1671 struct guestfs_message_error (encoded as XDR)
1673 The C<guestfs_message_error> structure contains the error message as a
1676 =head3 FUNCTIONS THAT HAVE FILEIN PARAMETERS
1678 A C<FileIn> parameter indicates that we transfer a file I<into> the
1679 guest. The normal request message is sent (see above). However this
1680 is followed by a sequence of file chunks.
1682 total length (header + arguments,
1683 but not including the length word itself,
1684 and not including the chunks)
1685 struct guestfs_message_header (encoded as XDR)
1686 struct guestfs_<foo>_args (encoded as XDR)
1687 sequence of chunks for FileIn param #0
1688 sequence of chunks for FileIn param #1 etc.
1690 The "sequence of chunks" is:
1692 length of chunk (not including length word itself)
1693 struct guestfs_chunk (encoded as XDR)
1695 struct guestfs_chunk (encoded as XDR)
1698 struct guestfs_chunk (with data.data_len == 0)
1700 The final chunk has the C<data_len> field set to zero. Additionally a
1701 flag is set in the final chunk to indicate either successful
1702 completion or early cancellation.
1704 At time of writing there are no functions that have more than one
1705 FileIn parameter. However this is (theoretically) supported, by
1706 sending the sequence of chunks for each FileIn parameter one after
1707 another (from left to right).
1709 Both the library (sender) I<and> the daemon (receiver) may cancel the
1710 transfer. The library does this by sending a chunk with a special
1711 flag set to indicate cancellation. When the daemon sees this, it
1712 cancels the whole RPC, does I<not> send any reply, and goes back to
1713 reading the next request.
1715 The daemon may also cancel. It does this by writing a special word
1716 C<GUESTFS_CANCEL_FLAG> to the socket. The library listens for this
1717 during the transfer, and if it gets it, it will cancel the transfer
1718 (it sends a cancel chunk). The special word is chosen so that even if
1719 cancellation happens right at the end of the transfer (after the
1720 library has finished writing and has started listening for the reply),
1721 the "spurious" cancel flag will not be confused with the reply
1724 This protocol allows the transfer of arbitrary sized files (no 32 bit
1725 limit), and also files where the size is not known in advance
1726 (eg. from pipes or sockets). However the chunks are rather small
1727 (C<GUESTFS_MAX_CHUNK_SIZE>), so that neither the library nor the
1728 daemon need to keep much in memory.
1730 =head3 FUNCTIONS THAT HAVE FILEOUT PARAMETERS
1732 The protocol for FileOut parameters is exactly the same as for FileIn
1733 parameters, but with the roles of daemon and library reversed.
1735 total length (header + ret,
1736 but not including the length word itself,
1737 and not including the chunks)
1738 struct guestfs_message_header (encoded as XDR)
1739 struct guestfs_<foo>_ret (encoded as XDR)
1740 sequence of chunks for FileOut param #0
1741 sequence of chunks for FileOut param #1 etc.
1743 =head3 INITIAL MESSAGE
1745 When the daemon launches it sends an initial word
1746 (C<GUESTFS_LAUNCH_FLAG>) which indicates that the guest and daemon is
1747 alive. This is what L</guestfs_launch> waits for.
1749 =head3 PROGRESS NOTIFICATION MESSAGES
1751 The daemon may send progress notification messages at any time. These
1752 are distinguished by the normal length word being replaced by
1753 C<GUESTFS_PROGRESS_FLAG>, followed by a fixed size progress message.
1755 The library turns them into progress callbacks (see
1756 C<guestfs_set_progress_callback>) if there is a callback registered,
1757 or discards them if not.
1759 The daemon self-limits the frequency of progress messages it sends
1760 (see C<daemon/proto.c:notify_progress>). Not all calls generate
1763 =head1 MULTIPLE HANDLES AND MULTIPLE THREADS
1765 All high-level libguestfs actions are synchronous. If you want
1766 to use libguestfs asynchronously then you must create a thread.
1768 Only use the handle from a single thread. Either use the handle
1769 exclusively from one thread, or provide your own mutex so that two
1770 threads cannot issue calls on the same handle at the same time.
1772 See the graphical program guestfs-browser for one possible
1773 architecture for multithreaded programs using libvirt and libguestfs.
1775 =head1 QEMU WRAPPERS
1777 If you want to compile your own qemu, run qemu from a non-standard
1778 location, or pass extra arguments to qemu, then you can write a
1779 shell-script wrapper around qemu.
1781 There is one important rule to remember: you I<must C<exec qemu>> as
1782 the last command in the shell script (so that qemu replaces the shell
1783 and becomes the direct child of the libguestfs-using program). If you
1784 don't do this, then the qemu process won't be cleaned up correctly.
1786 Here is an example of a wrapper, where I have built my own copy of
1790 qemudir=/home/rjones/d/qemu
1791 exec $qemudir/x86_64-softmmu/qemu-system-x86_64 -L $qemudir/pc-bios "$@"
1793 Save this script as C</tmp/qemu.wrapper> (or wherever), C<chmod +x>,
1794 and then use it by setting the LIBGUESTFS_QEMU environment variable.
1797 LIBGUESTFS_QEMU=/tmp/qemu.wrapper guestfish
1799 Note that libguestfs also calls qemu with the -help and -version
1800 options in order to determine features.
1802 =head1 LIBGUESTFS VERSION NUMBERS
1804 Since April 2010, libguestfs has started to make separate development
1805 and stable releases, along with corresponding branches in our git
1806 repository. These separate releases can be identified by version
1809 even numbers for stable: 1.2.x, 1.4.x, ...
1810 .-------- odd numbers for development: 1.3.x, 1.5.x, ...
1816 | `-------- sub-version
1818 `------ always '1' because we don't change the ABI
1820 Thus "1.3.5" is the 5th update to the development branch "1.3".
1822 As time passes we cherry pick fixes from the development branch and
1823 backport those into the stable branch, the effect being that the
1824 stable branch should get more stable and less buggy over time. So the
1825 stable releases are ideal for people who don't need new features but
1826 would just like the software to work.
1828 Our criteria for backporting changes are:
1834 Documentation changes which don't affect any code are
1835 backported unless the documentation refers to a future feature
1836 which is not in stable.
1840 Bug fixes which are not controversial, fix obvious problems, and
1841 have been well tested are backported.
1845 Simple rearrangements of code which shouldn't affect how it works get
1846 backported. This is so that the code in the two branches doesn't get
1847 too far out of step, allowing us to backport future fixes more easily.
1851 We I<don't> backport new features, new APIs, new tools etc, except in
1852 one exceptional case: the new feature is required in order to
1853 implement an important bug fix.
1857 A new stable branch starts when we think the new features in
1858 development are substantial and compelling enough over the current
1859 stable branch to warrant it. When that happens we create new stable
1860 and development versions 1.N.0 and 1.(N+1).0 [N is even]. The new
1861 dot-oh release won't necessarily be so stable at this point, but by
1862 backporting fixes from development, that branch will stabilize over
1865 =head1 ENVIRONMENT VARIABLES
1869 =item LIBGUESTFS_APPEND
1871 Pass additional options to the guest kernel.
1873 =item LIBGUESTFS_DEBUG
1875 Set C<LIBGUESTFS_DEBUG=1> to enable verbose messages. This
1876 has the same effect as calling C<guestfs_set_verbose (g, 1)>.
1878 =item LIBGUESTFS_MEMSIZE
1880 Set the memory allocated to the qemu process, in megabytes. For
1883 LIBGUESTFS_MEMSIZE=700
1885 =item LIBGUESTFS_PATH
1887 Set the path that libguestfs uses to search for kernel and initrd.img.
1888 See the discussion of paths in section PATH above.
1890 =item LIBGUESTFS_QEMU
1892 Set the default qemu binary that libguestfs uses. If not set, then
1893 the qemu which was found at compile time by the configure script is
1896 See also L</QEMU WRAPPERS> above.
1898 =item LIBGUESTFS_TRACE
1900 Set C<LIBGUESTFS_TRACE=1> to enable command traces. This
1901 has the same effect as calling C<guestfs_set_trace (g, 1)>.
1905 Location of temporary directory, defaults to C</tmp>.
1907 If libguestfs was compiled to use the supermin appliance then the
1908 real appliance is cached in this directory, shared between all
1909 handles belonging to the same EUID. You can use C<$TMPDIR> to
1910 configure another directory to use in case C</tmp> is not large
1922 L<virt-inspector(1)>,
1923 L<virt-list-filesystems(1)>,
1924 L<virt-list-partitions(1)>,
1933 L<http://libguestfs.org/>.
1935 Tools with a similar purpose:
1944 To get a list of bugs against libguestfs use this link:
1946 L<https://bugzilla.redhat.com/buglist.cgi?component=libguestfs&product=Virtualization+Tools>
1948 To report a new bug against libguestfs use this link:
1950 L<https://bugzilla.redhat.com/enter_bug.cgi?component=libguestfs&product=Virtualization+Tools>
1952 When reporting a bug, please check:
1958 That the bug hasn't been reported already.
1962 That you are testing a recent version.
1966 Describe the bug accurately, and give a way to reproduce it.
1970 Run libguestfs-test-tool and paste the B<complete, unedited>
1971 output into the bug report.
1977 Richard W.M. Jones (C<rjones at redhat dot com>)
1981 Copyright (C) 2009-2010 Red Hat Inc.
1982 L<http://libguestfs.org/>
1984 This library is free software; you can redistribute it and/or
1985 modify it under the terms of the GNU Lesser General Public
1986 License as published by the Free Software Foundation; either
1987 version 2 of the License, or (at your option) any later version.
1989 This library is distributed in the hope that it will be useful,
1990 but WITHOUT ANY WARRANTY; without even the implied warranty of
1991 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
1992 Lesser General Public License for more details.
1994 You should have received a copy of the GNU Lesser General Public
1995 License along with this library; if not, write to the Free Software
1996 Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA