Gjsify LogoGjsify Logo

A libguestfs session, encapsulating a single libguestfs handle.

Hierarchy

Index

Constructors

Properties

Methods

Constructors

Properties

gTypeInstance: TypeInstance
parent: GObject.Object
name: string

Methods

  • aclDeleteDefFile(dir: string): boolean
  • delete the default POSIX ACL of a directory

    This function deletes the default POSIX Access Control List (ACL) attached to directory dir.

    This function depends on the feature "acl". See also guestfs_session_feature_available().

    Parameters

    • dir: string

    Returns boolean

  • aclGetFile(path: string, acltype: string): string
  • get the POSIX ACL attached to a file

    This function returns the POSIX Access Control List (ACL) attached to path. The ACL is returned in "long text form" (see acl(5)).

    The acltype parameter may be:

    access Return the ordinary (access) ACL for any file, directory or other filesystem object.

    default Return the default ACL. Normally this only makes sense if path is a directory.

    This function depends on the feature "acl". See also guestfs_session_feature_available().

    Parameters

    • path: string
    • acltype: string

    Returns string

  • aclSetFile(path: string, acltype: string, acl: string): boolean
  • set the POSIX ACL attached to a file

    This function sets the POSIX Access Control List (ACL) attached to path.

    The acltype parameter may be:

    access Set the ordinary (access) ACL for any file, directory or other filesystem object.

    default Set the default ACL. Normally this only makes sense if path is a directory.

    The acl parameter is the new ACL in either "long text form" or "short text form" (see acl(5)). The new ACL completely replaces any previous ACL on the file. The ACL must contain the full Unix permissions (eg. "u::rwx,g::rx,o::rx").

    If you are specifying individual users or groups, then the mask field is also required (eg. "m::rwx"), followed by the "u:ID:..." and/or "g:ID:..." field(s). A full ACL string might therefore look like this:

    You should use numeric UIDs and GIDs. To map usernames and groupnames to the correct numeric ID in the context of the guest, use the Augeas functions (see guestfs_session_aug_init()).

    This function depends on the feature "acl". See also guestfs_session_feature_available().

    Parameters

    • path: string
    • acltype: string
    • acl: string

    Returns boolean

  • addCdrom(filename: string): boolean
  • add a CD-ROM disk image to examine

    This function adds a virtual CD-ROM disk image to the guest.

    The image is added as read-only drive, so this function is equivalent of guestfs_session_add_drive_ro().

    Parameters

    • filename: string

    Returns boolean

  • addDomain(dom: string, optargs: AddDomain): number
  • add the disk(s) from a named libvirt domain

    This function adds the disk(s) attached to the named libvirt domain dom. It works by connecting to libvirt, requesting the domain and domain XML from libvirt, parsing it for disks, and calling guestfs_session_add_drive_opts() on each one.

    The number of disks added is returned. This operation is atomic: if an error is returned, then no disks are added.

    This function does some minimal checks to make sure the libvirt domain is not running (unless readonly is true). In a future version we will try to acquire the libvirt lock on each disk.

    Disks must be accessible locally. This often means that adding disks from a remote libvirt connection (see http://libvirt.org/remote.html ) will fail unless those disks are accessible via the same device path locally too.

    The optional libvirturi parameter sets the libvirt URI (see http://libvirt.org/uri.html ). If this is not set then we connect to the default libvirt URI (or one set through an environment variable, see the libvirt documentation for full details).

    The optional live flag controls whether this call will try to connect to a running virtual machine guestfsd process if it sees a suitable <channel> element in the libvirt XML definition. The default (if the flag is omitted) is never to try. See "ATTACHING TO RUNNING DAEMONS" in guestfs(3) for more information.

    If the allowuuid flag is true (default is false) then a UUID may be passed instead of the domain name. The dom string is treated as a UUID first and looked up, and if that lookup fails then we treat dom as a name as usual.

    The optional readonlydisk parameter controls what we do for disks which are marked <readonly/> in the libvirt XML. Possible values are:

    readonlydisk = "error" If readonly is false:

    The whole call is aborted with an error if any disk with the <readonly/> flag is found.

    If readonly is true:

    Disks with the <readonly/> flag are added read-only.

    readonlydisk = "read" If readonly is false:

    Disks with the <readonly/> flag are added read-only. Other disks are added read/write.

    If readonly is true:

    Disks with the <readonly/> flag are added read-only.

    readonlydisk = "write" (default) If readonly is false:

    Disks with the <readonly/> flag are added read/write.

    If readonly is true:

    Disks with the <readonly/> flag are added read-only.

    readonlydisk = "ignore" If readonly is true or false:

    Disks with the <readonly/> flag are skipped.

    The other optional parameters are passed directly through to guestfs_session_add_drive_opts().

    Parameters

    • dom: string
    • optargs: AddDomain

      a GuestfsAddDomain containing optional arguments

    Returns number

  • addDrive(filename: string, optargs: AddDrive): boolean
  • add an image to examine or modify

    This function adds a disk image called filename to the handle. filename may be a regular host file or a host device.

    When this function is called before guestfs_session_launch() (the usual case) then the first time you call this function, the disk appears in the API as /dev/sda, the second time as /dev/sdb, and so on.

    In libguestfs ≥ 1.20 you can also call this function after launch (with some restrictions). This is called "hotplugging". When hotplugging, you must specify a label so that the new disk gets a predictable name. For more information see "HOTPLUGGING" in guestfs(3).

    You don't necessarily need to be root when using libguestfs. However you obviously do need sufficient permissions to access the filename for whatever operations you want to perform (ie. read access if you just want to read the image or write access if you want to modify the image).

    This call checks that filename exists.

    filename may be the special string "/dev/null". See "NULL DISKS" in guestfs(3).

    The optional arguments are:

    readonly If true then the image is treated as read-only. Writes are still allowed, but they are stored in a temporary snapshot overlay which is discarded at the end. The disk that you add is not modified.

    format This forces the image format. If you omit this (or use guestfs_session_add_drive() or guestfs_session_add_drive_ro()) then the format is automatically detected. Possible formats include raw and qcow2.

    Automatic detection of the format opens you up to a potential security hole when dealing with untrusted raw-format images. See CVE-2010-3851 and RHBZ#642934 . Specifying the format closes this security hole.

    iface This rarely-used option lets you emulate the behaviour of the deprecated guestfs_session_add_drive_with_if() call (q.v.)

    name The name the drive had in the original guest, e.g. /dev/sdb. This is used as a hint to the guest inspection process if it is available.

    label Give the disk a label. The label should be a unique, short string using only ASCII characters "[a-zA-Z]". As well as its usual name in the API (such as /dev/sda), the drive will also be named /dev/disk/guestfs/label.

    See "DISK LABELS" in guestfs(3).

    protocol The optional protocol argument can be used to select an alternate source protocol.

    See also: "REMOTE STORAGE" in guestfs(3).

    "protocol = "file"" filename is interpreted as a local file or device. This is the default if the optional protocol parameter is omitted.

    "protocol = "ftp"|"ftps"|"http"|"https"|"tftp"" Connect to a remote FTP, HTTP or TFTP server. The server parameter must also be supplied - see below.

    See also: "FTP, HTTP AND TFTP" in guestfs(3)

    "protocol = "gluster"" Connect to the GlusterFS server. The server parameter must also be supplied - see below.

    See also: "GLUSTER" in guestfs(3)

    "protocol = "iscsi"" Connect to the iSCSI server. The server parameter must also be supplied - see below. The username parameter may be supplied. See below. The secret parameter may be supplied. See below.

    See also: "ISCSI" in guestfs(3).

    "protocol = "nbd"" Connect to the Network Block Device server. The server parameter must also be supplied - see below.

    See also: "NETWORK BLOCK DEVICE" in guestfs(3).

    "protocol = "rbd"" Connect to the Ceph (librbd/RBD) server. The server parameter must also be supplied - see below. The username parameter may be supplied. See below. The secret parameter may be supplied. See below.

    See also: "CEPH" in guestfs(3).

    "protocol = "sheepdog"" Connect to the Sheepdog server. The server parameter may also be supplied - see below.

    See also: "SHEEPDOG" in guestfs(3).

    "protocol = "ssh"" Connect to the Secure Shell (ssh) server.

    The server parameter must be supplied. The username parameter may be supplied. See below.

    See also: "SSH" in guestfs(3).

    server For protocols which require access to a remote server, this is a list of server(s).

    Each list element is a string specifying a server. The string must be in one of the following formats:

    If the port number is omitted, then the standard port number for the protocol is used (see /etc/services).

    username For the ftp, ftps, http, https, iscsi, rbd, ssh and tftp protocols, this specifies the remote username.

    If not given, then the local username is used for ssh, and no authentication is attempted for ceph. But note this sometimes may give unexpected results, for example if using the libvirt backend and if the libvirt backend is configured to start the qemu appliance as a special user such as "qemu.qemu". If in doubt, specify the remote username you want.

    secret For the rbd protocol only, this specifies the ‘secret’ to use when connecting to the remote device. It must be base64 encoded.

    If not given, then a secret matching the given username will be looked up in the default keychain locations, or if no username is given, then no authentication will be used.

    cachemode Choose whether or not libguestfs will obey sync operations (safe but slow) or not (unsafe but fast). The possible values for this string are:

    "cachemode = "writeback"" This is the default.

    Write operations in the API do not return until a write(2) call has completed in the host [but note this does not imply that anything gets written to disk].

    Sync operations in the API, including implicit syncs caused by filesystem journalling, will not return until an fdatasync(2) call has completed in the host, indicating that data has been committed to disk.

    "cachemode = "unsafe"" In this mode, there are no guarantees. Libguestfs may cache anything and ignore sync requests. This is suitable only for scratch or temporary disks.

    discard Enable or disable discard (a.k.a. trim or unmap) support on this drive. If enabled, operations such as guestfs_session_fstrim() will be able to discard / make thin / punch holes in the underlying host file or device.

    Possible discard settings are:

    "discard = "disable"" Disable discard support. This is the default.

    "discard = "enable"" Enable discard support. Fail if discard is not possible.

    "discard = "besteffort"" Enable discard support if possible, but don't fail if it is not supported.

    Since not all backends and not all underlying systems support discard, this is a good choice if you want to use discard if possible, but don't mind if it doesn't work.

    copyonread The boolean parameter copyonread enables copy-on-read support. This only affects disk formats which have backing files, and causes reads to be stored in the overlay layer, speeding up multiple reads of the same area of disk.

    The default is false.

    Parameters

    • filename: string
    • optargs: AddDrive

      a GuestfsAddDrive containing optional arguments

    Returns boolean

  • addDriveRo(filename: string): boolean
  • add a drive in snapshot mode (read-only)

    This function is the equivalent of calling guestfs_session_add_drive_opts() with the optional parameter GUESTFS_ADD_DRIVE_OPTS_READONLY set to 1, so the disk is added read-only, with the format being detected automatically.

    Parameters

    • filename: string

    Returns boolean

  • addDriveRoWithIf(filename: string, iface: string): boolean
  • add a drive read-only specifying the QEMU block emulation to use

    This is the same as guestfs_session_add_drive_ro() but it allows you to specify the QEMU interface emulation to use at run time.

    Parameters

    • filename: string
    • iface: string

    Returns boolean

  • add a temporary scratch drive

    This command adds a temporary scratch drive to the handle. The size parameter is the virtual size (in bytes). The scratch drive is blank initially (all reads return zeroes until you start writing to it). The drive is deleted when the handle is closed.

    The optional arguments name and label are passed through to guestfs_session_add_drive().

    Parameters

    • size: number
    • optargs: AddDriveScratch

      a GuestfsAddDriveScratch containing optional arguments

    Returns boolean

  • addDriveWithIf(filename: string, iface: string): boolean
  • add a drive specifying the QEMU block emulation to use

    This is the same as guestfs_session_add_drive() but it allows you to specify the QEMU interface emulation to use at run time.

    Parameters

    • filename: string
    • iface: string

    Returns boolean

  • add the disk(s) from a libvirt domain

    This function adds the disk(s) attached to the libvirt domain dom. It works by requesting the domain XML from libvirt, parsing it for disks, and calling guestfs_session_add_drive_opts() on each one.

    In the C API we declare "void *dom", but really it has type "virDomainPtr dom". This is so we don't need <libvirt.h>.

    The number of disks added is returned. This operation is atomic: if an error is returned, then no disks are added.

    This function does some minimal checks to make sure the libvirt domain is not running (unless readonly is true). In a future version we will try to acquire the libvirt lock on each disk.

    Disks must be accessible locally. This often means that adding disks from a remote libvirt connection (see http://libvirt.org/remote.html ) will fail unless those disks are accessible via the same device path locally too.

    The optional live flag controls whether this call will try to connect to a running virtual machine guestfsd process if it sees a suitable <channel> element in the libvirt XML definition. The default (if the flag is omitted) is never to try. See "ATTACHING TO RUNNING DAEMONS" in guestfs(3) for more information.

    The optional readonlydisk parameter controls what we do for disks which are marked <readonly/> in the libvirt XML. See guestfs_session_add_domain() for possible values.

    The other optional parameters are passed directly through to guestfs_session_add_drive_opts().

    Parameters

    • dom: object

      pointer (not implemented in gobject bindings)

    • optargs: AddLibvirtDom

      a GuestfsAddLibvirtDom containing optional arguments

    Returns number

  • augClear(augpath: string): boolean
  • clear Augeas path

    Set the value associated with path to NULL. This is the same as the augtool(1) clear command.

    Parameters

    • augpath: string

    Returns boolean

  • augClose(): boolean
  • close the current Augeas handle

    Close the current Augeas handle and free up any resources used by it. After calling this, you have to call guestfs_session_aug_init() again before you can use any other Augeas functions.

    Returns boolean

  • augDefnode(name: string, expr: string, val: string): IntBool
  • define an Augeas node

    Defines a variable name whose value is the result of evaluating expr.

    If expr evaluates to an empty nodeset, a node is created, equivalent to calling guestfs_session_aug_set() expr, value. name will be the nodeset containing that single node.

    On success this returns a pair containing the number of nodes in the nodeset, and a boolean flag if a node was created.

    Parameters

    • name: string
    • expr: string
    • val: string

    Returns IntBool

  • augDefvar(name: string, expr: string): number
  • define an Augeas variable

    Defines an Augeas variable name whose value is the result of evaluating expr. If expr is NULL, then name is undefined.

    On success this returns the number of nodes in expr, or 0 if expr evaluates to something which is not a nodeset.

    Parameters

    • name: string
    • expr: string

    Returns number

  • augGet(augpath: string): string
  • look up the value of an Augeas path

    Look up the value associated with path. If path matches exactly one node, the value is returned.

    Parameters

    • augpath: string

    Returns string

  • augInit(root: string, flags: number): boolean
  • create a new Augeas handle

    Create a new Augeas handle for editing configuration files. If there was any previous Augeas handle associated with this guestfs session, then it is closed.

    You must call this before using any other "guestfs_aug_*" commands.

    root is the filesystem root. root must not be NULL, use / instead.

    The flags are the same as the flags defined in <augeas.h>, the logical or of the following integers:

    AUG_SAVE_BACKUP = 1 Keep the original file with a ".augsave" extension.

    AUG_SAVE_NEWFILE = 2 Save changes into a file with extension ".augnew", and do not overwrite original. Overrides AUG_SAVE_BACKUP.

    AUG_TYPE_CHECK = 4 Typecheck lenses.

    This option is only useful when debugging Augeas lenses. Use of this option may require additional memory for the libguestfs appliance. You may need to set the LIBGUESTFS_MEMSIZE environment variable or call guestfs_session_set_memsize().

    AUG_NO_STDINC = 8 Do not use standard load path for modules.

    AUG_SAVE_NOOP = 16 Make save a no-op, just record what would have been changed.

    AUG_NO_LOAD = 32 Do not load the tree in guestfs_session_aug_init().

    To close the handle, you can call guestfs_session_aug_close().

    To find out more about Augeas, see http://augeas.net/ .

    Parameters

    • root: string
    • flags: number

    Returns boolean

  • augInsert(augpath: string, label: string, before: boolean): boolean
  • insert a sibling Augeas node

    Create a new sibling label for path, inserting it into the tree before or after path (depending on the boolean flag before).

    path must match exactly one existing node in the tree, and label must be a label, ie. not contain /, "*" or end with a bracketed index "[N]".

    Parameters

    • augpath: string
    • label: string
    • before: boolean

    Returns boolean

  • augLabel(augpath: string): string
  • return the label from an Augeas path expression

    The label (name of the last element) of the Augeas path expression augpath is returned. augpath must match exactly one node, else this function returns an error.

    Parameters

    • augpath: string

    Returns string

  • augLoad(): boolean
  • load files into the tree

    Load files into the tree.

    See aug_load in the Augeas documentation for the full gory details.

    Returns boolean

  • augLs(augpath: string): string[]
  • list Augeas nodes under augpath

    This is just a shortcut for listing guestfs_session_aug_match() "path/*" and sorting the resulting nodes into alphabetical order.

    Parameters

    • augpath: string

    Returns string[]

  • augMatch(augpath: string): string[]
  • return Augeas nodes which match augpath

    Returns a list of paths which match the path expression path. The returned paths are sufficiently qualified so that they match exactly one node in the current tree.

    Parameters

    • augpath: string

    Returns string[]

  • augMv(src: string, dest: string): boolean
  • move Augeas node

    Move the node src to dest. src must match exactly one node. dest is overwritten if it exists.

    Parameters

    • src: string
    • dest: string

    Returns boolean

  • augRm(augpath: string): number
  • remove an Augeas path

    Remove path and all of its children.

    On success this returns the number of entries which were removed.

    Parameters

    • augpath: string

    Returns number

  • augSave(): boolean
  • write all pending Augeas changes to disk

    This writes all pending changes to disk.

    The flags which were passed to guestfs_session_aug_init() affect exactly how files are saved.

    Returns boolean

  • augSet(augpath: string, val: string): boolean
  • set Augeas path to value

    Set the value associated with path to val.

    In the Augeas API, it is possible to clear a node by setting the value to NULL. Due to an oversight in the libguestfs API you cannot do that with this call. Instead you must use the guestfs_session_aug_clear() call.

    Parameters

    • augpath: string
    • val: string

    Returns boolean

  • augSetm(base: string, sub: string, val: string): number
  • set multiple Augeas nodes

    Change multiple Augeas nodes in a single operation. base is an expression matching multiple nodes. sub is a path expression relative to base. All nodes matching base are found, and then for each node, sub is changed to val. sub may also be NULL in which case the base nodes are modified.

    This returns the number of nodes modified.

    Parameters

    • base: string
    • sub: string
    • val: string

    Returns number

  • augTransform(lens: string, file: string, optargs: AugTransform): boolean
  • add/remove an Augeas lens transformation

    Add an Augeas transformation for the specified lens so it can handle file.

    If remove is true (false by default), then the transformation is removed.

    Parameters

    • lens: string
    • file: string
    • optargs: AugTransform

      a GuestfsAugTransform containing optional arguments

    Returns boolean

  • available(groups: string[]): boolean
  • test availability of some parts of the API

    This command is used to check the availability of some groups of functionality in the appliance, which not all builds of the libguestfs appliance will be able to provide.

    The libguestfs groups, and the functions that those groups correspond to, are listed in "AVAILABILITY" in guestfs(3). You can also fetch this list at runtime by calling guestfs_session_available_all_groups().

    The argument groups is a list of group names, eg: "["inotify", "augeas"]" would check for the availability of the Linux inotify functions and Augeas (configuration file editing) functions.

    The command returns no error if all requested groups are available.

    It fails with an error if one or more of the requested groups is unavailable in the appliance.

    If an unknown group name is included in the list of groups then an error is always returned.

    Notes:

    • guestfs_session_feature_available() is the same as this call, but with a slightly simpler to use API: that call returns a boolean true/false instead of throwing an error.

    • You must call guestfs_session_launch() before calling this function.

    The reason is because we don't know what groups are supported by the appliance/daemon until it is running and can be queried.

    • If a group of functions is available, this does not necessarily mean that they will work. You still have to check for errors when calling individual API functions even if they are available.

    • It is usually the job of distro packagers to build complete functionality into the libguestfs appliance. Upstream libguestfs, if built from source with all requirements satisfied, will support everything.

    • This call was added in version 1.0.80. In previous versions of libguestfs all you could do would be to speculatively execute a command to find out if the daemon implemented it. See also guestfs_session_version().

    See also guestfs_session_filesystem_available().

    Parameters

    • groups: string[]

      an array of strings

    Returns boolean

  • availableAllGroups(): string[]
  • return a list of all optional groups

    This command returns a list of all optional groups that this daemon knows about. Note this returns both supported and unsupported groups. To find out which ones the daemon can actually support you have to call guestfs_session_available() / guestfs_session_feature_available() on each member of the returned list.

    See also guestfs_session_available(), guestfs_session_feature_available() and "AVAILABILITY" in guestfs(3).

    Returns string[]

  • base64In(base64file: string, filename: string, cancellable: Gio.Cancellable): boolean
  • upload base64-encoded data to file

    This command uploads base64-encoded data from base64file to filename.

    Parameters

    • base64file: string
    • filename: string
    • cancellable: Gio.Cancellable

      A GCancellable object

    Returns boolean

  • base64Out(filename: string, base64file: string, cancellable: Gio.Cancellable): boolean
  • download file and encode as base64

    This command downloads the contents of filename, writing it out to local file base64file encoded as base64.

    Parameters

    • filename: string
    • base64file: string
    • cancellable: Gio.Cancellable

      A GCancellable object

    Returns boolean

  • Creates a binding between source_property on source and target_property on target.

    Whenever the source_property is changed the target_property is updated using the same value. For instance:

      g_object_bind_property (action, "active", widget, "sensitive", 0);
    

    Will result in the "sensitive" property of the widget #GObject instance to be updated with the same value of the "active" property of the action #GObject instance.

    If flags contains %G_BINDING_BIDIRECTIONAL then the binding will be mutual: if target_property on target changes then the source_property on source will be updated as well.

    The binding will automatically be removed when either the source or the target instances are finalized. To remove the binding without affecting the source and the target you can just call g_object_unref() on the returned #GBinding instance.

    Removing the binding by calling g_object_unref() on it must only be done if the binding, source and target are only used from a single thread and it is clear that both source and target outlive the binding. Especially it is not safe to rely on this if the binding, source or target can be finalized from different threads. Keep another reference to the binding and use g_binding_unbind() instead to be on the safe side.

    A #GObject can have multiple bindings.

    Parameters

    • sourceProperty: string

      the property on source to bind

    • target: GObject.Object

      the target #GObject

    • targetProperty: string

      the property on target to bind

    • flags: BindingFlags

      flags to pass to #GBinding

    Returns Binding

  • Creates a binding between source_property on source and target_property on target, allowing you to set the transformation functions to be used by the binding.

    This function is the language bindings friendly version of g_object_bind_property_full(), using #GClosures instead of function pointers.

    Parameters

    • sourceProperty: string

      the property on source to bind

    • target: GObject.Object

      the target #GObject

    • targetProperty: string

      the property on target to bind

    • flags: BindingFlags

      flags to pass to #GBinding

    • transformTo: TClosure<any, any>

      a #GClosure wrapping the transformation function from the source to the target, or %NULL to use the default

    • transformFrom: TClosure<any, any>

      a #GClosure wrapping the transformation function from the target to the source, or %NULL to use the default

    Returns Binding

  • blkdiscard(device: string): boolean
  • discard all blocks on a device

    This discards all blocks on the block device device, giving the free space back to the host.

    This operation requires support in libguestfs, the host filesystem, qemu and the host kernel. If this support isn't present it may give an error or even appear to run but do nothing. You must also set the discard attribute on the underlying drive (see guestfs_session_add_drive_opts()).

    This function depends on the feature "blkdiscard". See also guestfs_session_feature_available().

    Parameters

    • device: string

    Returns boolean

  • blkdiscardzeroes(device: string): number
  • return true if discarded blocks are read as zeroes

    This call returns true if blocks on device that have been discarded by a call to guestfs_session_blkdiscard() are returned as blocks of zero bytes when read the next time.

    If it returns false, then it may be that discarded blocks are read as stale or random data.

    This function depends on the feature "blkdiscardzeroes". See also guestfs_session_feature_available().

    Parameters

    • device: string

    Returns number

  • blkid(device: string): HashTable<string | number | symbol, string | number | boolean>
  • print block device attributes

    This command returns block device attributes for device. The following fields are usually present in the returned hash. Other fields may also be present.

    UUID The uuid of this device.

    LABEL The label of this device.

    VERSION The version of blkid command.

    TYPE The filesystem type or RAID of this device.

    USAGE The usage of this device, for example filesystem or raid.

    Parameters

    • device: string

    Returns HashTable<string | number | symbol, string | number | boolean>

  • blockdevFlushbufs(device: string): boolean
  • flush device buffers

    This tells the kernel to flush internal buffers associated with device.

    This uses the blockdev(8) command.

    Parameters

    • device: string

    Returns boolean

  • blockdevGetbsz(device: string): number
  • get blocksize of block device

    This returns the block size of a device.

    Note: this is different from both size in blocks and filesystem block size. Also this setting is not really used by anything. You should probably not use it for anything. Filesystems have their own idea about what block size to choose.

    This uses the blockdev(8) command.

    Parameters

    • device: string

    Returns number

  • blockdevGetro(device: string): number
  • is block device set to read-only

    Returns a boolean indicating if the block device is read-only (true if read-only, false if not).

    This uses the blockdev(8) command.

    Parameters

    • device: string

    Returns number

  • blockdevGetsize64(device: string): number
  • get total size of device in bytes

    This returns the size of the device in bytes.

    See also guestfs_session_blockdev_getsz().

    This uses the blockdev(8) command.

    Parameters

    • device: string

    Returns number

  • blockdevGetss(device: string): number
  • get sectorsize of block device

    This returns the size of sectors on a block device. Usually 512, but can be larger for modern devices.

    (Note, this is not the size in sectors, use guestfs_session_blockdev_getsz() for that).

    This uses the blockdev(8) command.

    Parameters

    • device: string

    Returns number

  • blockdevGetsz(device: string): number
  • get total size of device in 512-byte sectors

    This returns the size of the device in units of 512-byte sectors (even if the sectorsize isn't 512 bytes ... weird).

    See also guestfs_session_blockdev_getss() for the real sector size of the device, and guestfs_session_blockdev_getsize64() for the more useful size in bytes.

    This uses the blockdev(8) command.

    Parameters

    • device: string

    Returns number

  • blockdevRereadpt(device: string): boolean
  • reread partition table

    Reread the partition table on device.

    This uses the blockdev(8) command.

    Parameters

    • device: string

    Returns boolean

  • blockdevSetbsz(device: string, blocksize: number): boolean
  • set blocksize of block device

    This call does nothing and has never done anything because of a bug in blockdev. Do not use it.

    If you need to set the filesystem block size, use the blocksize option of guestfs_session_mkfs().

    Parameters

    • device: string
    • blocksize: number

    Returns boolean

  • blockdevSetra(device: string, sectors: number): boolean
  • set readahead

    Set readahead (in 512-byte sectors) for the device.

    This uses the blockdev(8) command.

    Parameters

    • device: string
    • sectors: number

    Returns boolean

  • blockdevSetro(device: string): boolean
  • set block device to read-only

    Sets the block device named device to read-only.

    This uses the blockdev(8) command.

    Parameters

    • device: string

    Returns boolean

  • blockdevSetrw(device: string): boolean
  • set block device to read-write

    Sets the block device named device to read-write.

    This uses the blockdev(8) command.

    Parameters

    • device: string

    Returns boolean

  • btrfsBalanceCancel(path: string): boolean
  • cancel a running or paused balance

    Cancel a running balance on a btrfs filesystem.

    This function depends on the feature "btrfs". See also guestfs_session_feature_available().

    Parameters

    • path: string

    Returns boolean

  • btrfsBalancePause(path: string): boolean
  • pause a running balance

    Pause a running balance on a btrfs filesystem.

    This function depends on the feature "btrfs". See also guestfs_session_feature_available().

    Parameters

    • path: string

    Returns boolean

  • btrfsBalanceResume(path: string): boolean
  • resume a paused balance

    Resume a paused balance on a btrfs filesystem.

    This function depends on the feature "btrfs". See also guestfs_session_feature_available().

    Parameters

    • path: string

    Returns boolean

  • show the status of a running or paused balance

    Show the status of a running or paused balance on a btrfs filesystem.

    This function depends on the feature "btrfs". See also guestfs_session_feature_available().

    Parameters

    • path: string

    Returns BTRFSBalance

  • btrfsDeviceAdd(devices: string[], fs: string): boolean
  • add devices to a btrfs filesystem

    Add the list of device(s) in devices to the btrfs filesystem mounted at fs. If devices is an empty list, this does nothing.

    This function depends on the feature "btrfs". See also guestfs_session_feature_available().

    Parameters

    • devices: string[]

      an array of strings

    • fs: string

    Returns boolean

  • btrfsDeviceDelete(devices: string[], fs: string): boolean
  • remove devices from a btrfs filesystem

    Remove the devices from the btrfs filesystem mounted at fs. If devices is an empty list, this does nothing.

    This function depends on the feature "btrfs". See also guestfs_session_feature_available().

    Parameters

    • devices: string[]

      an array of strings

    • fs: string

    Returns boolean

  • btrfsFilesystemBalance(fs: string): boolean
  • balance a btrfs filesystem

    Balance the chunks in the btrfs filesystem mounted at fs across the underlying devices.

    This function depends on the feature "btrfs". See also guestfs_session_feature_available().

    Parameters

    • fs: string

    Returns boolean

  • defragment a file or directory

    Defragment a file or directory on a btrfs filesystem. compress is one of zlib or lzo.

    This function depends on the feature "btrfs". See also guestfs_session_feature_available().

    Parameters

    Returns boolean

  • resize a btrfs filesystem

    This command resizes a btrfs filesystem.

    Note that unlike other resize calls, the filesystem has to be mounted and the parameter is the mountpoint not the device (this is a requirement of btrfs itself).

    The optional parameters are:

    size The new size (in bytes) of the filesystem. If omitted, the filesystem is resized to the maximum size.

    See also btrfs(8).

    This function depends on the feature "btrfs". See also guestfs_session_feature_available().

    Parameters

    • mountpoint: string
    • optargs: BTRFSFilesystemResize

      a GuestfsBTRFSFilesystemResize containing optional arguments

    Returns boolean

  • btrfsFilesystemShow(device: string): string[]
  • list devices for btrfs filesystem

    Show all the devices where the filesystems in device is spanned over.

    If not all the devices for the filesystems are present, then this function fails and the errno is set to ENODEV.

    This function depends on the feature "btrfs". See also guestfs_session_feature_available().

    Parameters

    • device: string

    Returns string[]

  • btrfsFilesystemSync(fs: string): boolean
  • sync a btrfs filesystem

    Force sync on the btrfs filesystem mounted at fs.

    This function depends on the feature "btrfs". See also guestfs_session_feature_available().

    Parameters

    • fs: string

    Returns boolean

  • btrfsFsck(device: string, optargs: BtrfsFsck): boolean
  • check a btrfs filesystem

    Used to check a btrfs filesystem, device is the device file where the filesystem is stored.

    This function depends on the feature "btrfs". See also guestfs_session_feature_available().

    Parameters

    • device: string
    • optargs: BtrfsFsck

      a GuestfsBtrfsFsck containing optional arguments

    Returns boolean

  • btrfsImage(source: string[], image: string, optargs: BTRFSImage): boolean
  • create an image of a btrfs filesystem

    This is used to create an image of a btrfs filesystem. All data will be zeroed, but metadata and the like is preserved.

    This function depends on the feature "btrfs". See also guestfs_session_feature_available().

    Parameters

    • source: string[]

      an array of strings

    • image: string
    • optargs: BTRFSImage

      a GuestfsBTRFSImage containing optional arguments

    Returns boolean

  • btrfsQgroupAssign(src: string, dst: string, path: string): boolean
  • add a qgroup to a parent qgroup

    Add qgroup src to parent qgroup dst. This command can group several qgroups into a parent qgroup to share common limit.

    This function depends on the feature "btrfs". See also guestfs_session_feature_available().

    Parameters

    • src: string
    • dst: string
    • path: string

    Returns boolean

  • btrfsQgroupCreate(qgroupid: string, subvolume: string): boolean
  • create a subvolume quota group

    Create a quota group (qgroup) for subvolume at subvolume.

    This function depends on the feature "btrfs". See also guestfs_session_feature_available().

    Parameters

    • qgroupid: string
    • subvolume: string

    Returns boolean

  • btrfsQgroupDestroy(qgroupid: string, subvolume: string): boolean
  • destroy a subvolume quota group

    Destroy a quota group.

    This function depends on the feature "btrfs". See also guestfs_session_feature_available().

    Parameters

    • qgroupid: string
    • subvolume: string

    Returns boolean

  • btrfsQgroupLimit(subvolume: string, size: number): boolean
  • limit the size of a subvolume

    Limit the size of the subvolume with path subvolume.

    This function depends on the feature "btrfs". See also guestfs_session_feature_available().

    Parameters

    • subvolume: string
    • size: number

    Returns boolean

  • btrfsQgroupRemove(src: string, dst: string, path: string): boolean
  • remove a qgroup from its parent qgroup

    Remove qgroup src from the parent qgroup dst.

    This function depends on the feature "btrfs". See also guestfs_session_feature_available().

    Parameters

    • src: string
    • dst: string
    • path: string

    Returns boolean

  • show subvolume quota groups

    Show all subvolume quota groups in a btrfs filesystem, including their usages.

    This function depends on the feature "btrfs". See also guestfs_session_feature_available().

    Parameters

    • path: string

    Returns BTRFSQgroup[]

  • btrfsQuotaEnable(fs: string, enable: boolean): boolean
  • enable or disable subvolume quota support

    Enable or disable subvolume quota support for filesystem which contains path.

    This function depends on the feature "btrfs". See also guestfs_session_feature_available().

    Parameters

    • fs: string
    • enable: boolean

    Returns boolean

  • btrfsQuotaRescan(fs: string): boolean
  • trash all qgroup numbers and scan the metadata again with the current config

    Trash all qgroup numbers and scan the metadata again with the current config.

    This function depends on the feature "btrfs". See also guestfs_session_feature_available().

    Parameters

    • fs: string

    Returns boolean

  • btrfsReplace(srcdev: string, targetdev: string, mntpoint: string): boolean
  • replace a btrfs managed device with another device

    Replace device of a btrfs filesystem. On a live filesystem, duplicate the data to the target device which is currently stored on the source device. After completion of the operation, the source device is wiped out and removed from the filesystem.

    The targetdev needs to be same size or larger than the srcdev. Devices which are currently mounted are never allowed to be used as the targetdev.

    This function depends on the feature "btrfs". See also guestfs_session_feature_available().

    Parameters

    • srcdev: string
    • targetdev: string
    • mntpoint: string

    Returns boolean

  • btrfsRescueChunkRecover(device: string): boolean
  • recover the chunk tree of btrfs filesystem

    Recover the chunk tree of btrfs filesystem by scanning the devices one by one.

    This function depends on the feature "btrfs". See also guestfs_session_feature_available().

    Parameters

    • device: string

    Returns boolean

  • btrfsRescueSuperRecover(device: string): boolean
  • recover bad superblocks from good copies

    Recover bad superblocks from good copies.

    This function depends on the feature "btrfs". See also guestfs_session_feature_available().

    Parameters

    • device: string

    Returns boolean

  • btrfsScrubCancel(path: string): boolean
  • cancel a running scrub

    Cancel a running scrub on a btrfs filesystem.

    This function depends on the feature "btrfs". See also guestfs_session_feature_available().

    Parameters

    • path: string

    Returns boolean

  • btrfsScrubResume(path: string): boolean
  • resume a previously canceled or interrupted scrub

    Resume a previously canceled or interrupted scrub on a btrfs filesystem.

    This function depends on the feature "btrfs". See also guestfs_session_feature_available().

    Parameters

    • path: string

    Returns boolean

  • btrfsScrubStart(path: string): boolean
  • read all data from all disks and verify checksums

    Reads all the data and metadata on the filesystem, and uses checksums and the duplicate copies from RAID storage to identify and repair any corrupt data.

    This function depends on the feature "btrfs". See also guestfs_session_feature_available().

    Parameters

    • path: string

    Returns boolean

  • show status of running or finished scrub

    Show status of running or finished scrub on a btrfs filesystem.

    This function depends on the feature "btrfs". See also guestfs_session_feature_available().

    Parameters

    • path: string

    Returns BTRFSScrub

  • btrfsSetSeeding(device: string, seeding: boolean): boolean
  • enable or disable the seeding feature of device

    Enable or disable the seeding feature of a device that contains a btrfs filesystem.

    This function depends on the feature "btrfs". See also guestfs_session_feature_available().

    Parameters

    • device: string
    • seeding: boolean

    Returns boolean

  • create a btrfs subvolume

    Create a btrfs subvolume. The dest argument is the destination directory and the name of the subvolume, in the form /path/to/dest/name. The optional parameter qgroupid represents the qgroup which the newly created subvolume will be added to.

    This function depends on the feature "btrfs". See also guestfs_session_feature_available().

    Parameters

    • dest: string
    • optargs: BTRFSSubvolumeCreate

      a GuestfsBTRFSSubvolumeCreate containing optional arguments

    Returns boolean

  • btrfsSubvolumeDelete(subvolume: string): boolean
  • delete a btrfs subvolume or snapshot

    Delete the named btrfs subvolume or snapshot.

    This function depends on the feature "btrfs". See also guestfs_session_feature_available().

    Parameters

    • subvolume: string

    Returns boolean

  • btrfsSubvolumeGetDefault(fs: string): number
  • get the default subvolume or snapshot of a filesystem

    Get the default subvolume or snapshot of a filesystem mounted at mountpoint.

    This function depends on the feature "btrfs". See also guestfs_session_feature_available().

    Parameters

    • fs: string

    Returns number

  • list btrfs snapshots and subvolumes

    List the btrfs snapshots and subvolumes of the btrfs filesystem which is mounted at fs.

    This function depends on the feature "btrfs". See also guestfs_session_feature_available().

    Parameters

    • fs: string

    Returns BTRFSSubvolume[]

  • btrfsSubvolumeSetDefault(id: number, fs: string): boolean
  • set default btrfs subvolume

    Set the subvolume of the btrfs filesystem fs which will be mounted by default. See guestfs_session_btrfs_subvolume_list() to get a list of subvolumes.

    This function depends on the feature "btrfs". See also guestfs_session_feature_available().

    Parameters

    • id: number
    • fs: string

    Returns boolean

  • btrfsSubvolumeShow(subvolume: string): HashTable<string | number | symbol, string | number | boolean>
  • return detailed information of the subvolume

    Return detailed information of the subvolume.

    This function depends on the feature "btrfs". See also guestfs_session_feature_available().

    Parameters

    • subvolume: string

    Returns HashTable<string | number | symbol, string | number | boolean>

  • create a btrfs snapshot

    Create a snapshot of the btrfs subvolume source. The dest argument is the destination directory and the name of the snapshot, in the form /path/to/dest/name. By default the newly created snapshot is writable, if the value of optional parameter ro is true, then a readonly snapshot is created. The optional parameter qgroupid represents the qgroup which the newly created snapshot will be added to.

    This function depends on the feature "btrfs". See also guestfs_session_feature_available().

    Parameters

    • source: string
    • dest: string
    • optargs: BTRFSSubvolumeSnapshot

      a GuestfsBTRFSSubvolumeSnapshot containing optional arguments

    Returns boolean

  • btrfstuneEnableExtendedInodeRefs(device: string): boolean
  • enable extended inode refs

    This will Enable extended inode refs.

    This function depends on the feature "btrfs". See also guestfs_session_feature_available().

    Parameters

    • device: string

    Returns boolean

  • btrfstuneEnableSkinnyMetadataExtentRefs(device: string): boolean
  • enable skinny metadata extent refs

    This enable skinny metadata extent refs.

    This function depends on the feature "btrfs". See also guestfs_session_feature_available().

    Parameters

    • device: string

    Returns boolean

  • btrfstuneSeeding(device: string, seeding: boolean): boolean
  • enable or disable seeding of a btrfs device

    Enable seeding of a btrfs device, this will force a fs readonly so that you can use it to build other filesystems.

    This function depends on the feature "btrfs". See also guestfs_session_feature_available().

    Parameters

    • device: string
    • seeding: boolean

    Returns boolean

  • cPointer(): number
  • return the C pointer to the guestfs_h handle

    In non-C language bindings, this allows you to retrieve the underlying C pointer to the handle (ie. "guestfs_h *"). The purpose of this is to allow other libraries to interwork with libguestfs.

    Returns number

  • canonicalDeviceName(device: string): string
  • return canonical device name

    This utility function is useful when displaying device names to the user. It takes a number of irregular device names and returns them in a consistent format:

    /dev/hdX /dev/vdX These are returned as /dev/sdX. Note this works for device names and partition names. This is approximately the reverse of the algorithm described in "BLOCK DEVICE NAMING" in guestfs(3).

    /dev/mapper/VG-LV /dev/dm-N Converted to /dev/VG/LV form using guestfs_session_lvm_canonical_lv_name().

    Other strings are returned unmodified.

    Parameters

    • device: string

    Returns string

  • capGetFile(path: string): string
  • get the Linux capabilities attached to a file

    This function returns the Linux capabilities attached to path. The capabilities set is returned in text form (see cap_to_text(3)).

    If no capabilities are attached to a file, an empty string is returned.

    This function depends on the feature "linuxcaps". See also guestfs_session_feature_available().

    Parameters

    • path: string

    Returns string

  • capSetFile(path: string, cap: string): boolean
  • set the Linux capabilities attached to a file

    This function sets the Linux capabilities attached to path. The capabilities set cap should be passed in text form (see cap_from_text(3)).

    This function depends on the feature "linuxcaps". See also guestfs_session_feature_available().

    Parameters

    • path: string
    • cap: string

    Returns boolean

  • caseSensitivePath(path: string): string
  • return true path on case-insensitive filesystem

    This can be used to resolve case insensitive paths on a filesystem which is case sensitive. The use case is to resolve paths which you have read from Windows configuration files or the Windows Registry, to the true path.

    The command handles a peculiarity of the Linux ntfs-3g filesystem driver (and probably others), which is that although the underlying filesystem is case-insensitive, the driver exports the filesystem to Linux as case-sensitive.

    One consequence of this is that special directories such as C:\windows may appear as /WINDOWS or /windows (or other things) depending on the precise details of how they were created. In Windows itself this would not be a problem.

    Bug or feature? You decide: http://www.tuxera.com/community/ntfs-3g-faq/#posixfilenames1

    guestfs_session_case_sensitive_path() attempts to resolve the true case of each element in the path. It will return a resolved path if either the full path or its parent directory exists. If the parent directory exists but the full path does not, the case of the parent directory will be correctly resolved, and the remainder appended unmodified. For example, if the file "/Windows/System32/netkvm.sys" exists:

    guestfs_session_case_sensitive_path() ("/windows/system32/netkvm.sys") "Windows/System32/netkvm.sys"

    guestfs_session_case_sensitive_path() ("/windows/system32/NoSuchFile") "Windows/System32/NoSuchFile"

    guestfs_session_case_sensitive_path() ("/windows/system33/netkvm.sys") ERROR

    Note: Because of the above behaviour, guestfs_session_case_sensitive_path() cannot be used to check for the existence of a file.

    Note: This function does not handle drive names, backslashes etc.

    See also guestfs_session_realpath().

    Parameters

    • path: string

    Returns string

  • cat(path: string): string
  • list the contents of a file

    Return the contents of the file named path.

    Because, in C, this function returns a "char *", there is no way to differentiate between a "\0" character in a file and end of string. To handle binary files, use the guestfs_session_read_file() or guestfs_session_download() functions.

    Parameters

    • path: string

    Returns string

  • checksum(csumtype: string, path: string): string
  • compute MD5, SHAx or CRC checksum of file

    This call computes the MD5, SHAx or CRC checksum of the file named path.

    The type of checksum to compute is given by the csumtype parameter which must have one of the following values:

    crc Compute the cyclic redundancy check (CRC) specified by POSIX for the cksum command.

    md5 Compute the MD5 hash (using the md5sum program).

    sha1 Compute the SHA1 hash (using the sha1sum program).

    sha224 Compute the SHA224 hash (using the sha224sum program).

    sha256 Compute the SHA256 hash (using the sha256sum program).

    sha384 Compute the SHA384 hash (using the sha384sum program).

    sha512 Compute the SHA512 hash (using the sha512sum program).

    The checksum is returned as a printable string.

    To get the checksum for a device, use guestfs_session_checksum_device().

    To get the checksums for many files, use guestfs_session_checksums_out().

    Parameters

    • csumtype: string
    • path: string

    Returns string

  • checksumDevice(csumtype: string, device: string): string
  • compute MD5, SHAx or CRC checksum of the contents of a device

    This call computes the MD5, SHAx or CRC checksum of the contents of the device named device. For the types of checksums supported see the guestfs_session_checksum() command.

    Parameters

    • csumtype: string
    • device: string

    Returns string

  • checksumsOut(csumtype: string, directory: string, sumsfile: string, cancellable: Gio.Cancellable): boolean
  • compute MD5, SHAx or CRC checksum of files in a directory

    This command computes the checksums of all regular files in directory and then emits a list of those checksums to the local output file sumsfile.

    This can be used for verifying the integrity of a virtual machine. However to be properly secure you should pay attention to the output of the checksum command (it uses the ones from GNU coreutils). In particular when the filename is not printable, coreutils uses a special backslash syntax. For more information, see the GNU coreutils info file.

    Parameters

    • csumtype: string
    • directory: string
    • sumsfile: string
    • cancellable: Gio.Cancellable

      A GCancellable object

    Returns boolean

  • chmod(mode: number, path: string): boolean
  • change file mode

    Change the mode (permissions) of path to mode. Only numeric modes are supported.

    Note: When using this command from guestfish, mode by default would be decimal, unless you prefix it with 0 to get octal, ie. use 0700 not 700.

    The mode actually set is affected by the umask.

    Parameters

    • mode: number
    • path: string

    Returns boolean

  • chown(owner: number, group: number, path: string): boolean
  • change file owner and group

    Change the file owner to owner and group to group.

    Only numeric uid and gid are supported. If you want to use names, you will need to locate and parse the password file yourself (Augeas support makes this relatively easy).

    Parameters

    • owner: number
    • group: number
    • path: string

    Returns boolean

  • clearBackendSetting(name: string): number
  • remove a single per-backend settings string

    If there is a backend setting string matching "name" or beginning with "name=", then that string is removed from the backend settings.

    This call returns the number of strings which were removed (which may be 0, 1 or greater than 1).

    See "BACKEND" in guestfs(3), "BACKEND SETTINGS" in guestfs(3).

    Parameters

    • name: string

    Returns number

  • close(): boolean
  • command(arguments_: string[]): string
  • run a command from the guest filesystem

    This call runs a command from the guest filesystem. The filesystem must be mounted, and must contain a compatible operating system (ie. something Linux, with the same or compatible processor architecture).

    The single parameter is an argv-style list of arguments. The first element is the name of the program to run. Subsequent elements are parameters. The list must be non-empty (ie. must contain a program name). Note that the command runs directly, and is not invoked via the shell (see guestfs_session_sh()).

    The return value is anything printed to stdout by the command.

    If the command returns a non-zero exit status, then this function returns an error message. The error message string is the content of stderr from the command.

    The $PATH environment variable will contain at least /usr/bin and /bin. If you require a program from another location, you should provide the full path in the first parameter.

    Shared libraries and data files required by the program must be available on filesystems which are mounted in the correct places. It is the caller’s responsibility to ensure all filesystems that are needed are mounted at the right locations.

    Parameters

    • arguments_: string[]

      an array of strings

    Returns string

  • commandLines(arguments_: string[]): string[]
  • run a command, returning lines

    This is the same as guestfs_session_command(), but splits the result into a list of lines.

    See also: guestfs_session_sh_lines()

    Parameters

    • arguments_: string[]

      an array of strings

    Returns string[]

  • output compressed device

    This command compresses device and writes it out to the local file zdevice.

    The ctype and optional level parameters have the same meaning as in guestfs_session_compress_out().

    Parameters

    • ctype: string
    • device: string
    • zdevice: string
    • optargs: CompressDeviceOut

      a GuestfsCompressDeviceOut containing optional arguments

    • cancellable: Gio.Cancellable

      A GCancellable object

    Returns boolean

  • output compressed file

    This command compresses file and writes it out to the local file zfile.

    The compression program used is controlled by the ctype parameter. Currently this includes: compress, gzip, bzip2, xz or lzop. Some compression types may not be supported by particular builds of libguestfs, in which case you will get an error containing the substring "not supported".

    The optional level parameter controls compression level. The meaning and default for this parameter depends on the compression program being used.

    Parameters

    • ctype: string
    • file: string
    • zfile: string
    • optargs: CompressOut

      a GuestfsCompressOut containing optional arguments

    • cancellable: Gio.Cancellable

      A GCancellable object

    Returns boolean

  • config(hvparam: string, hvvalue: string): boolean
  • add hypervisor parameters

    This can be used to add arbitrary hypervisor parameters of the form -param value. Actually it’s not quite arbitrary - we prevent you from setting some parameters which would interfere with parameters that we use.

    The first character of hvparam string must be a - (dash).

    hvvalue can be NULL.

    Parameters

    • hvparam: string
    • hvvalue: string

    Returns boolean

  • copyAttributes(src: string, dest: string, optargs: CopyAttributes): boolean
  • copy the attributes of a path (file/directory) to another

    Copy the attributes of a path (which can be a file or a directory) to another path.

    By default no attribute is copied, so make sure to specify any (or all to copy everything).

    The optional arguments specify which attributes can be copied:

    mode Copy part of the file mode from source to destination. Only the UNIX permissions and the sticky/setuid/setgid bits can be copied.

    xattributes Copy the Linux extended attributes (xattrs) from source to destination. This flag does nothing if the linuxxattrs feature is not available (see guestfs_session_feature_available()).

    ownership Copy the owner uid and the group gid of source to destination.

    all Copy all the attributes from source to destination. Enabling it enables all the other flags, if they are not specified already.

    Parameters

    • src: string
    • dest: string
    • optargs: CopyAttributes

      a GuestfsCopyAttributes containing optional arguments

    Returns boolean

  • copy from source device to destination device

    The four calls guestfs_session_copy_device_to_device(), guestfs_session_copy_device_to_file(), guestfs_session_copy_file_to_device(), and guestfs_session_copy_file_to_file() let you copy from a source (device|file) to a destination (device|file).

    Partial copies can be made since you can specify optionally the source offset, destination offset and size to copy. These values are all specified in bytes. If not given, the offsets both default to zero, and the size defaults to copying as much as possible until we hit the end of the source.

    The source and destination may be the same object. However overlapping regions may not be copied correctly.

    If the destination is a file, it is created if required. If the destination file is not large enough, it is extended.

    If the destination is a file and the append flag is not set, then the destination file is truncated. If the append flag is set, then the copy appends to the destination file. The append flag currently cannot be set for devices.

    If the sparse flag is true then the call avoids writing blocks that contain only zeroes, which can help in some situations where the backing disk is thin-provisioned. Note that unless the target is already zeroed, using this option will result in incorrect copying.

    Parameters

    • src: string
    • dest: string
    • optargs: CopyDeviceToDevice

      a GuestfsCopyDeviceToDevice containing optional arguments

    Returns boolean

  • copy from source device to destination file

    See guestfs_session_copy_device_to_device() for a general overview of this call.

    Parameters

    • src: string
    • dest: string
    • optargs: CopyDeviceToFile

      a GuestfsCopyDeviceToFile containing optional arguments

    Returns boolean

  • copy from source file to destination device

    See guestfs_session_copy_device_to_device() for a general overview of this call.

    Parameters

    • src: string
    • dest: string
    • optargs: CopyFileToDevice

      a GuestfsCopyFileToDevice containing optional arguments

    Returns boolean

  • copyFileToFile(src: string, dest: string, optargs: CopyFileToFile): boolean
  • copy from source file to destination file

    See guestfs_session_copy_device_to_device() for a general overview of this call.

    This is not the function you want for copying files. This is for copying blocks within existing files. See guestfs_session_cp(), guestfs_session_cp_a() and guestfs_session_mv() for general file copying and moving functions.

    Parameters

    • src: string
    • dest: string
    • optargs: CopyFileToFile

      a GuestfsCopyFileToFile containing optional arguments

    Returns boolean

  • copyIn(localpath: string, remotedir: string): boolean
  • copy local files or directories into an image

    guestfs_session_copy_in() copies local files or directories recursively into the disk image, placing them in the directory called remotedir (which must exist).

    Wildcards cannot be used.

    Parameters

    • localpath: string
    • remotedir: string

    Returns boolean

  • copyOut(remotepath: string, localdir: string): boolean
  • copy remote files or directories out of an image

    guestfs_session_copy_out() copies remote files or directories recursively out of the disk image, placing them on the host disk in a local directory called localdir (which must exist).

    To download to the current directory, use "." as in:

    Wildcards cannot be used.

    Parameters

    • remotepath: string
    • localdir: string

    Returns boolean

  • copySize(src: string, dest: string, size: number): boolean
  • copy size bytes from source to destination using dd

    This command copies exactly size bytes from one source device or file src to another destination device or file dest.

    Note this will fail if the source is too short or if the destination is not large enough.

    Parameters

    • src: string
    • dest: string
    • size: number

    Returns boolean

  • cp(src: string, dest: string): boolean
  • copy a file

    This copies a file from src to dest where dest is either a destination filename or destination directory.

    Parameters

    • src: string
    • dest: string

    Returns boolean

  • cpA(src: string, dest: string): boolean
  • copy a file or directory recursively

    This copies a file or directory from src to dest recursively using the "cp -a" command.

    Parameters

    • src: string
    • dest: string

    Returns boolean

  • cpR(src: string, dest: string): boolean
  • copy a file or directory recursively

    This copies a file or directory from src to dest recursively using the "cp -rP" command.

    Most users should use guestfs_session_cp_a() instead. This command is useful when you don't want to preserve permissions, because the target filesystem does not support it (primarily when writing to DOS FAT filesystems).

    Parameters

    • src: string
    • dest: string

    Returns boolean

  • pack directory into cpio file

    This command packs the contents of directory and downloads it to local file cpiofile.

    The optional format parameter can be used to select the format. Only the following formats are currently permitted:

    newc New (SVR4) portable format. This format happens to be compatible with the cpio-like format used by the Linux kernel for initramfs.

    This is the default format.

    crc New (SVR4) portable format with a checksum.

    Parameters

    • directory: string
    • cpiofile: string
    • optargs: CpioOut

      a GuestfsCpioOut containing optional arguments

    • cancellable: Gio.Cancellable

      A GCancellable object

    Returns boolean

  • dd(src: string, dest: string): boolean
  • copy from source to destination using dd

    This command copies from one source device or file src to another destination device or file dest. Normally you would use this to copy to or from a device or partition, for example to duplicate a filesystem.

    If the destination is a device, it must be as large or larger than the source file or device, otherwise the copy will fail. This command cannot do partial copies (see guestfs_session_copy_device_to_device()).

    Parameters

    • src: string
    • dest: string

    Returns boolean

  • debug(subcmd: string, extraargs: string[]): string
  • debugging and internals

    The guestfs_session_debug() command exposes some internals of guestfsd (the guestfs daemon) that runs inside the hypervisor.

    There is no comprehensive help for this command. You have to look at the file daemon/debug.c in the libguestfs source to find out what you can do.

    Parameters

    • subcmd: string
    • extraargs: string[]

      an array of strings

    Returns string

  • debugDrives(): string[]
  • debug the drives (internal use only)

    This returns the internal list of drives. ‘debug’ commands are not part of the formal API and can be removed or changed at any time.

    Returns string[]

  • debugUpload(filename: string, tmpname: string, mode: number, cancellable: Gio.Cancellable): boolean
  • upload a file to the appliance (internal use only)

    The guestfs_session_debug_upload() command uploads a file to the libguestfs appliance.

    There is no comprehensive help for this command. You have to look at the file daemon/debug.c in the libguestfs source to find out what it is for.

    Parameters

    • filename: string
    • tmpname: string
    • mode: number
    • cancellable: Gio.Cancellable

      A GCancellable object

    Returns boolean

  • deviceIndex(device: string): number
  • convert device to index

    This function takes a device name (eg. "/dev/sdb") and returns the index of the device in the list of devices.

    Index numbers start from 0. The named device must exist, for example as a string returned from guestfs_session_list_devices().

    See also guestfs_session_list_devices(), guestfs_session_part_to_dev().

    Parameters

    • device: string

    Returns number

  • df(): string
  • report file system disk space usage

    This command runs the df command to report disk space used.

    This command is mostly useful for interactive sessions. It is not intended that you try to parse the output string. Use guestfs_session_statvfs() from programs.

    Returns string

  • dfH(): string
  • report file system disk space usage (human readable)

    This command runs the "df -h" command to report disk space used in human-readable format.

    This command is mostly useful for interactive sessions. It is not intended that you try to parse the output string. Use guestfs_session_statvfs() from programs.

    Returns string

  • diskCreate(filename: string, format: string, size: number, optargs: DiskCreate): boolean
  • create a blank disk image

    Create a blank disk image called filename (a host file) with format format (usually raw or qcow2). The size is size bytes.

    If used with the optional backingfile parameter, then a snapshot is created on top of the backing file. In this case, size must be passed as -1. The size of the snapshot is the same as the size of the backing file, which is discovered automatically. You are encouraged to also pass backingformat to describe the format of backingfile.

    If filename refers to a block device, then the device is formatted. The size is ignored since block devices have an intrinsic size.

    The other optional parameters are:

    preallocation If format is raw, then this can be either off (or sparse) or full to create a sparse or fully allocated file respectively. The default is off.

    If format is qcow2, then this can be off (or sparse), metadata or full. Preallocating metadata can be faster when doing lots of writes, but uses more space. The default is off.

    compat qcow2 only: Pass the string 1.1 to use the advanced qcow2 format supported by qemu ≥ 1.1.

    clustersize qcow2 only: Change the qcow2 cluster size. The default is 65536 (bytes) and this setting may be any power of two between 512 and 2097152.

    Note that this call does not add the new disk to the handle. You may need to call guestfs_session_add_drive_opts() separately.

    Parameters

    • filename: string
    • format: string
    • size: number
    • optargs: DiskCreate

      a GuestfsDiskCreate containing optional arguments

    Returns boolean

  • diskFormat(filename: string): string
  • detect the disk format of a disk image

    Detect and return the format of the disk image called filename. filename can also be a host device, etc. If the format of the image could not be detected, then "unknown" is returned.

    Note that detecting the disk format can be insecure under some circumstances. See "CVE-2010-3851" in guestfs(3).

    See also: "DISK IMAGE FORMATS" in guestfs(3)

    Parameters

    • filename: string

    Returns string

  • diskHasBackingFile(filename: string): number
  • return whether disk has a backing file

    Detect and return whether the disk image filename has a backing file.

    Note that detecting disk features can be insecure under some circumstances. See "CVE-2010-3851" in guestfs(3).

    Parameters

    • filename: string

    Returns number

  • diskVirtualSize(filename: string): number
  • return virtual size of a disk

    Detect and return the virtual size in bytes of the disk image called filename.

    Note that detecting disk features can be insecure under some circumstances. See "CVE-2010-3851" in guestfs(3).

    Parameters

    • filename: string

    Returns number

  • dmesg(): string
  • return kernel messages

    This returns the kernel messages (dmesg output) from the guest kernel. This is sometimes useful for extended debugging of problems.

    Another way to get the same information is to enable verbose messages with guestfs_session_set_verbose() or by setting the environment variable "LIBGUESTFS_DEBUG=1" before running the program.

    Returns string

  • download(remotefilename: string, filename: string, cancellable: Gio.Cancellable): boolean
  • download a file to the local machine

    Download file remotefilename and save it as filename on the local machine.

    filename can also be a named pipe.

    See also guestfs_session_upload(), guestfs_session_cat().

    Parameters

    • remotefilename: string
    • filename: string
    • cancellable: Gio.Cancellable

      A GCancellable object

    Returns boolean

  • downloadBlocks(device: string, start: number, stop: number, filename: string, optargs: DownloadBlocks, cancellable: Gio.Cancellable): boolean
  • download the given data units from the disk

    Download the data units from start address to stop from the disk partition (eg. /dev/sda1) and save them as filename on the local machine.

    The use of this API on sparse disk image formats such as QCOW, may result in large zero-filled files downloaded on the host.

    The size of a data unit varies across filesystem implementations. On NTFS filesystems data units are referred as clusters while on ExtX ones they are referred as fragments.

    If the optional unallocated flag is true (default is false), only the unallocated blocks will be extracted. This is useful to detect hidden data or to retrieve deleted files which data units have not been overwritten yet.

    This function depends on the feature "sleuthkit". See also guestfs_session_feature_available().

    Parameters

    • device: string
    • start: number
    • stop: number
    • filename: string
    • optargs: DownloadBlocks

      a GuestfsDownloadBlocks containing optional arguments

    • cancellable: Gio.Cancellable

      A GCancellable object

    Returns boolean

  • downloadInode(device: string, inode: number, filename: string, cancellable: Gio.Cancellable): boolean
  • download a file to the local machine given its inode

    Download a file given its inode from the disk partition (eg. /dev/sda1) and save it as filename on the local machine.

    It is not required to mount the disk to run this command.

    The command is capable of downloading deleted or inaccessible files.

    This function depends on the feature "sleuthkit". See also guestfs_session_feature_available().

    Parameters

    • device: string
    • inode: number
    • filename: string
    • cancellable: Gio.Cancellable

      A GCancellable object

    Returns boolean

  • downloadOffset(remotefilename: string, filename: string, offset: number, size: number, cancellable: Gio.Cancellable): boolean
  • download a file to the local machine with offset and size

    Download file remotefilename and save it as filename on the local machine.

    remotefilename is read for size bytes starting at offset (this region must be within the file or device).

    Note that there is no limit on the amount of data that can be downloaded with this call, unlike with guestfs_session_pread(), and this call always reads the full amount unless an error occurs.

    See also guestfs_session_download(), guestfs_session_pread().

    Parameters

    • remotefilename: string
    • filename: string
    • offset: number
    • size: number
    • cancellable: Gio.Cancellable

      A GCancellable object

    Returns boolean

  • dropCaches(whattodrop: number): boolean
  • drop kernel page cache, dentries and inodes

    This instructs the guest kernel to drop its page cache, and/or dentries and inode caches. The parameter whattodrop tells the kernel what precisely to drop, see http://linux-mm.org/Drop_Caches

    Setting whattodrop to 3 should drop everything.

    This automatically calls sync(2) before the operation, so that the maximum guest memory is freed.

    Parameters

    • whattodrop: number

    Returns boolean

  • du(path: string): number
  • estimate file space usage

    This command runs the "du -s" command to estimate file space usage for path.

    path can be a file or a directory. If path is a directory then the estimate includes the contents of the directory and all subdirectories (recursively).

    The result is the estimated size in kilobytes (ie. units of 1024 bytes).

    Parameters

    • path: string

    Returns number

  • e2fsck(device: string, optargs: E2fsck): boolean
  • check an ext2/ext3 filesystem

    This runs the ext2/ext3 filesystem checker on device. It can take the following optional arguments:

    correct Automatically repair the file system. This option will cause e2fsck to automatically fix any filesystem problems that can be safely fixed without human intervention.

    This option may not be specified at the same time as the forceall option.

    forceall Assume an answer of ‘yes’ to all questions; allows e2fsck to be used non-interactively.

    This option may not be specified at the same time as the correct option.

    Parameters

    • device: string
    • optargs: E2fsck

      a GuestfsE2fsck containing optional arguments

    Returns boolean

  • e2fsckF(device: string): boolean
  • check an ext2/ext3 filesystem

    This runs "e2fsck -p -f device", ie. runs the ext2/ext3 filesystem checker on device, noninteractively (-p), even if the filesystem appears to be clean (-f).

    Parameters

    • device: string

    Returns boolean

  • echoDaemon(words: string[]): string
  • echo arguments back to the client

    This command concatenates the list of words passed with single spaces between them and returns the resulting string.

    You can use this command to test the connection through to the daemon.

    See also guestfs_session_ping_daemon().

    Parameters

    • words: string[]

      an array of strings

    Returns string

  • egrep(regex: string, path: string): string[]
  • return lines matching a pattern

    This calls the external egrep program and returns the matching lines.

    Parameters

    • regex: string
    • path: string

    Returns string[]

  • egrepi(regex: string, path: string): string[]
  • return lines matching a pattern

    This calls the external "egrep -i" program and returns the matching lines.

    Parameters

    • regex: string
    • path: string

    Returns string[]

  • emit(sigName: "appliance", ...args: any[]): void
  • emit(sigName: "close", ...args: any[]): void
  • emit(sigName: "enter", ...args: any[]): void
  • emit(sigName: "launch-done", ...args: any[]): void
  • emit(sigName: "library", ...args: any[]): void
  • emit(sigName: "libvirt-auth", ...args: any[]): void
  • emit(sigName: "progress", ...args: any[]): void
  • emit(sigName: "subprocess-quit", ...args: any[]): void
  • emit(sigName: "trace", ...args: any[]): void
  • emit(sigName: "warning", ...args: any[]): void
  • emit(sigName: string, ...args: any[]): void
  • equal(file1: string, file2: string): number
  • test if two files have equal contents

    This compares the two files file1 and file2 and returns true if their content is exactly equal, or false otherwise.

    The external cmp(1) program is used for the comparison.

    Parameters

    • file1: string
    • file2: string

    Returns number

  • exists(path: string): number
  • test if file or directory exists

    This returns true if and only if there is a file, directory (or anything) with the given path name.

    See also guestfs_session_is_file(), guestfs_session_is_dir(), guestfs_session_stat().

    Parameters

    • path: string

    Returns number

  • extlinux(directory: string): boolean
  • install the SYSLINUX bootloader on an ext2/3/4 or btrfs filesystem

    Install the SYSLINUX bootloader on the device mounted at directory. Unlike guestfs_session_syslinux() which requires a FAT filesystem, this can be used on an ext2/3/4 or btrfs filesystem.

    The directory parameter can be either a mountpoint, or a directory within the mountpoint.

    You also have to mark the partition as "active" (guestfs_session_part_set_bootable()) and a Master Boot Record must be installed (eg. using guestfs_session_pwrite_device()) on the first sector of the whole disk. The SYSLINUX package comes with some suitable Master Boot Records. See the extlinux(1) man page for further information.

    Additional configuration can be supplied to SYSLINUX by placing a file called extlinux.conf on the filesystem under directory. For further information about the contents of this file, see extlinux(1).

    See also guestfs_session_syslinux().

    This function depends on the feature "extlinux". See also guestfs_session_feature_available().

    Parameters

    • directory: string

    Returns boolean

  • f2fsExpand(device: string): boolean
  • expand a f2fs filesystem

    This expands a f2fs filesystem to match the size of the underlying device.

    This function depends on the feature "f2fs". See also guestfs_session_feature_available().

    Parameters

    • device: string

    Returns boolean

  • fallocate(path: string, len: number): boolean
  • preallocate a file in the guest filesystem

    This command preallocates a file (containing zero bytes) named path of size len bytes. If the file exists already, it is overwritten.

    Do not confuse this with the guestfish-specific alloc command which allocates a file in the host and attaches it as a device.

    Parameters

    • path: string
    • len: number

    Returns boolean

  • fallocate64(path: string, len: number): boolean
  • preallocate a file in the guest filesystem

    This command preallocates a file (containing zero bytes) named path of size len bytes. If the file exists already, it is overwritten.

    Note that this call allocates disk blocks for the file. To create a sparse file use guestfs_session_truncate_size() instead.

    The deprecated call guestfs_session_fallocate() does the same, but owing to an oversight it only allowed 30 bit lengths to be specified, effectively limiting the maximum size of files created through that call to 1GB.

    Do not confuse this with the guestfish-specific alloc and sparse commands which create a file in the host and attach it as a device.

    Parameters

    • path: string
    • len: number

    Returns boolean

  • featureAvailable(groups: string[]): number
  • test availability of some parts of the API

    This is the same as guestfs_session_available(), but unlike that call it returns a simple true/false boolean result, instead of throwing an exception if a feature is not found. For other documentation see guestfs_session_available().

    Parameters

    • groups: string[]

      an array of strings

    Returns number

  • fgrep(pattern: string, path: string): string[]
  • return lines matching a pattern

    This calls the external fgrep program and returns the matching lines.

    Parameters

    • pattern: string
    • path: string

    Returns string[]

  • fgrepi(pattern: string, path: string): string[]
  • return lines matching a pattern

    This calls the external "fgrep -i" program and returns the matching lines.

    Parameters

    • pattern: string
    • path: string

    Returns string[]

  • file(path: string): string
  • determine file type

    This call uses the standard file(1) command to determine the type or contents of the file.

    This call will also transparently look inside various types of compressed file.

    The exact command which runs is "file -zb path". Note in particular that the filename is not prepended to the output (the -b option).

    The output depends on the output of the underlying file(1) command and it can change in future in ways beyond our control. In other words, the output is not guaranteed by the ABI.

    See also: file(1), guestfs_session_vfs_type(), guestfs_session_lstat(), guestfs_session_is_file(), guestfs_session_is_blockdev() (etc), guestfs_session_is_zero().

    Parameters

    • path: string

    Returns string

  • fileArchitecture(filename: string): string
  • detect the architecture of a binary file

    This detects the architecture of the binary filename, and returns it if known.

    Currently defined architectures are:

    "aarch64" 64 bit ARM.

    "arm" 32 bit ARM.

    "i386" This string is returned for all 32 bit i386, i486, i586, i686 binaries irrespective of the precise processor requirements of the binary.

    "ia64" Intel Itanium.

    "ppc" 32 bit Power PC.

    "ppc64" 64 bit Power PC (big endian).

    "ppc64le" 64 bit Power PC (little endian).

    "riscv32" "riscv64" "riscv128" RISC-V 32-, 64- or 128-bit variants.

    "s390" 31 bit IBM S/390.

    "s390x" 64 bit IBM S/390.

    "sparc" 32 bit SPARC.

    "sparc64" 64 bit SPARC V9 and above.

    "x86_64" 64 bit x86-64.

    Libguestfs may return other architecture strings in future.

    The function works on at least the following types of files:

    • many types of Un*x and Linux binary

    • many types of Un*x and Linux shared library

    • Windows Win32 and Win64 binaries

    • Windows Win32 and Win64 DLLs

    Win32 binaries and DLLs return i386.

    Win64 binaries and DLLs return x86_64.

    • Linux kernel modules

    • Linux new-style initrd images

    • some non-x86 Linux vmlinuz kernels

    What it can't do currently:

    • static libraries (libfoo.a)

    • Linux old-style initrd as compressed ext2 filesystem (RHEL 3)

    • x86 Linux vmlinuz kernels

    x86 vmlinuz images (bzImage format) consist of a mix of 16-, 32- and compressed code, and are horribly hard to unpack. If you want to find the architecture of a kernel, use the architecture of the associated initrd or kernel module(s) instead.

    Parameters

    • filename: string

    Returns string

  • filesize(file: string): number
  • return the size of the file in bytes

    This command returns the size of file in bytes.

    To get other stats about a file, use guestfs_session_stat(), guestfs_session_lstat(), guestfs_session_is_dir(), guestfs_session_is_file() etc. To get the size of block devices, use guestfs_session_blockdev_getsize64().

    Parameters

    • file: string

    Returns number

  • filesystemAvailable(filesystem: string): number
  • check if filesystem is available

    Check whether libguestfs supports the named filesystem. The argument filesystem is a filesystem name, such as ext3.

    You must call guestfs_session_launch() before using this command.

    This is mainly useful as a negative test. If this returns true, it doesn't mean that a particular filesystem can be created or mounted, since filesystems can fail for other reasons such as it being a later version of the filesystem, or having incompatible features, or lacking the right mkfs.<fs> tool.

    See also guestfs_session_available(), guestfs_session_feature_available(), "AVAILABILITY" in guestfs(3).

    Parameters

    • filesystem: string

    Returns number

  • walk through the filesystem content

    Walk through the internal structures of a disk partition (eg. /dev/sda1) in order to return a list of all the files and directories stored within.

    It is not necessary to mount the disk partition to run this command.

    All entries in the filesystem are returned. This function can list deleted or unaccessible files. The entries are not sorted.

    The tsk_dirent structure contains the following fields.

    tsk_inode Filesystem reference number of the node. It might be 0 if the node has been deleted.

    tsk_type Basic file type information. See below for a detailed list of values.

    tsk_size File size in bytes. It might be -1 if the node has been deleted.

    tsk_name The file path relative to its directory.

    tsk_flags Bitfield containing extra information regarding the entry. It contains the logical OR of the following values:

    0x0001 If set to 1, the file is allocated and visible within the filesystem. Otherwise, the file has been deleted. Under certain circumstances, the function download_inode can be used to recover deleted files.

    0x0002 Filesystem such as NTFS and Ext2 or greater, separate the file name from the metadata structure. The bit is set to 1 when the file name is in an unallocated state and the metadata structure is in an allocated one. This generally implies the metadata has been reallocated to a new file. Therefore, information such as file type, file size, timestamps, number of links and symlink target might not correspond with the ones of the original deleted entry.

    0x0004 The bit is set to 1 when the file is compressed using filesystem native compression support (NTFS). The API is not able to detect application level compression.

    tsk_atime_sec tsk_atime_nsec tsk_mtime_sec tsk_mtime_nsec tsk_ctime_sec tsk_ctime_nsec tsk_crtime_sec tsk_crtime_nsec Respectively, access, modification, last status change and creation time in Unix format in seconds and nanoseconds.

    tsk_nlink Number of file names pointing to this entry.

    tsk_link If the entry is a symbolic link, this field will contain the path to the target file.

    The tsk_type field will contain one of the following characters:

    'b' Block special

    'c' Char special

    'd' Directory

    'f' FIFO (named pipe)

    'l' Symbolic link

    'r' Regular file

    's' Socket

    'h' Shadow inode (Solaris)

    'w' Whiteout inode (BSD)

    'u' Unknown file type

    This function depends on the feature "libtsk". See also guestfs_session_feature_available().

    Parameters

    Returns TSKDirent[]

  • fill(c: number, len: number, path: string): boolean
  • fill a file with octets

    This command creates a new file called path. The initial content of the file is len octets of c, where c must be a number in the range "[0..255]".

    To fill a file with zero bytes (sparsely), it is much more efficient to use guestfs_session_truncate_size(). To create a file with a pattern of repeating bytes use guestfs_session_fill_pattern().

    Parameters

    • c: number
    • len: number
    • path: string

    Returns boolean

  • fillDir(dir: string, nr: number): boolean
  • fill a directory with empty files

    This function, useful for testing filesystems, creates nr empty files in the directory dir with names 00000000 through nr-1 (ie. each file name is 8 digits long padded with zeroes).

    Parameters

    • dir: string
    • nr: number

    Returns boolean

  • fillPattern(pattern: string, len: number, path: string): boolean
  • fill a file with a repeating pattern of bytes

    This function is like guestfs_session_fill() except that it creates a new file of length len containing the repeating pattern of bytes in pattern. The pattern is truncated if necessary to ensure the length of the file is exactly len bytes.

    Parameters

    • pattern: string
    • len: number
    • path: string

    Returns boolean

  • find(directory: string): string[]
  • find all files and directories

    This command lists out all files and directories, recursively, starting at directory. It is essentially equivalent to running the shell command "find directory -print" but some post-processing happens on the output, described below.

    This returns a list of strings without any prefix. Thus if the directory structure was:

    then the returned list from guestfs_session_find() /tmp would be 4 elements:

    If directory is not a directory, then this command returns an error.

    The returned list is sorted.

    Parameters

    • directory: string

    Returns string[]

  • find0(directory: string, files: string, cancellable: Gio.Cancellable): boolean
  • find all files and directories, returning NUL-separated list

    This command lists out all files and directories, recursively, starting at directory, placing the resulting list in the external file called files.

    This command works the same way as guestfs_session_find() with the following exceptions:

    • The resulting list is written to an external file.

    • Items (filenames) in the result are separated by "\0" characters. See find(1) option -print0.

    • The result list is not sorted.

    Parameters

    • directory: string
    • files: string
    • cancellable: Gio.Cancellable

      A GCancellable object

    Returns boolean

  • search the entries associated to the given inode

    Searches all the entries associated with the given inode.

    For each entry, a tsk_dirent structure is returned. See filesystem_walk for more information about tsk_dirent structures.

    This function depends on the feature "libtsk". See also guestfs_session_feature_available().

    Parameters

    • device: string
    • inode: number
    • cancellable: Gio.Cancellable

      A GCancellable object

    Returns TSKDirent[]

  • findfsLabel(label: string): string
  • find a filesystem by label

    This command searches the filesystems and returns the one which has the given label. An error is returned if no such filesystem can be found.

    To find the label of a filesystem, use guestfs_session_vfs_label().

    Parameters

    • label: string

    Returns string

  • findfsUuid(uuid: string): string
  • find a filesystem by UUID

    This command searches the filesystems and returns the one which has the given UUID. An error is returned if no such filesystem can be found.

    To find the UUID of a filesystem, use guestfs_session_vfs_uuid().

    Parameters

    • uuid: string

    Returns string

  • forceFloating(): void
  • This function is intended for #GObject implementations to re-enforce a [floating][floating-ref] object reference. Doing this is seldom required: all #GInitiallyUnowneds are created with a floating reference which usually just needs to be sunken by calling g_object_ref_sink().

    Returns void

  • freezeNotify(): void
  • Increases the freeze count on object. If the freeze count is non-zero, the emission of "notify" signals on object is stopped. The signals are queued until the freeze count is decreased to zero. Duplicate notifications are squashed so that at most one #GObject::notify signal is emitted for each property modified while the object is frozen.

    This is necessary for accessors that modify multiple properties to prevent premature notification while the object is still being modified.

    Returns void

  • fsck(fstype: string, device: string): number
  • run the filesystem checker

    This runs the filesystem checker (fsck) on device which should have filesystem type fstype.

    The returned integer is the status. See fsck(8) for the list of status codes from fsck.

    Notes:

    • Multiple status codes can be summed together.

    • A non-zero return code can mean "success", for example if errors have been corrected on the filesystem.

    • Checking or repairing NTFS volumes is not supported (by linux-ntfs).

    This command is entirely equivalent to running "fsck -a -t fstype device".

    Parameters

    • fstype: string
    • device: string

    Returns number

  • fstrim(mountpoint: string, optargs: Fstrim): boolean
  • trim free space in a filesystem

    Trim the free space in the filesystem mounted on mountpoint. The filesystem must be mounted read-write.

    The filesystem contents are not affected, but any free space in the filesystem is "trimmed", that is, given back to the host device, thus making disk images more sparse, allowing unused space in qcow2 files to be reused, etc.

    This operation requires support in libguestfs, the mounted filesystem, the host filesystem, qemu and the host kernel. If this support isn't present it may give an error or even appear to run but do nothing.

    In the case where the kernel vfs driver does not support trimming, this call will fail with errno set to ENOTSUP. Currently this happens when trying to trim FAT filesystems.

    See also guestfs_session_zero_free_space(). That is a slightly different operation that turns free space in the filesystem into zeroes. It is valid to call guestfs_session_fstrim() either instead of, or after calling guestfs_session_zero_free_space().

    This function depends on the feature "fstrim". See also guestfs_session_feature_available().

    Parameters

    • mountpoint: string
    • optargs: Fstrim

      a GuestfsFstrim containing optional arguments

    Returns boolean

  • getAppend(): string
  • get the additional kernel options

    Return the additional kernel options which are added to the libguestfs appliance kernel command line.

    If NULL then no options are added.

    Returns string

  • getAttachMethod(): string
  • get the backend

    Return the current backend.

    See guestfs_session_set_backend() and "BACKEND" in guestfs(3).

    Returns string

  • getAutosync(): number
  • getBackend(): string
  • get the backend

    Return the current backend.

    This handle property was previously called the "attach method".

    See guestfs_session_set_backend() and "BACKEND" in guestfs(3).

    Returns string

  • getBackendSetting(name: string): string
  • get a single per-backend settings string

    Find a backend setting string which is either "name" or begins with "name=". If "name", this returns the string "1". If "name=", this returns the part after the equals sign (which may be an empty string).

    If no such setting is found, this function throws an error. The errno (see guestfs_session_last_errno()) will be ESRCH in this case.

    See "BACKEND" in guestfs(3), "BACKEND SETTINGS" in guestfs(3).

    Parameters

    • name: string

    Returns string

  • getBackendSettings(): string[]
  • get per-backend settings

    Return the current backend settings.

    This call returns all backend settings strings. If you want to find a single backend setting, see guestfs_session_get_backend_setting().

    See "BACKEND" in guestfs(3), "BACKEND SETTINGS" in guestfs(3).

    Returns string[]

  • getCachedir(): string
  • get the appliance cache directory

    Get the directory used by the handle to store the appliance cache.

    Returns string

  • getData(key?: string): object
  • Gets a named field from the objects table of associations (see g_object_set_data()).

    Parameters

    • Optional key: string

      name of the key for that association

    Returns object

  • getDirect(): number
  • get direct appliance mode flag

    Return the direct appliance mode flag.

    Returns number

  • getE2attrs(file: string): string
  • get ext2 file attributes of a file

    This returns the file attributes associated with file.

    The attributes are a set of bits associated with each inode which affect the behaviour of the file. The attributes are returned as a string of letters (described below). The string may be empty, indicating that no file attributes are set for this file.

    These attributes are only present when the file is located on an ext2/3/4 filesystem. Using this call on other filesystem types will result in an error.

    The characters (file attributes) in the returned string are currently:

    'A' When the file is accessed, its atime is not modified.

    'a' The file is append-only.

    'c' The file is compressed on-disk.

    'D' (Directories only.) Changes to this directory are written synchronously to disk.

    'd' The file is not a candidate for backup (see dump(8)).

    'E' The file has compression errors.

    'e' The file is using extents.

    'h' The file is storing its blocks in units of the filesystem blocksize instead of sectors.

    'I' (Directories only.) The directory is using hashed trees.

    'i' The file is immutable. It cannot be modified, deleted or renamed. No link can be created to this file.

    'j' The file is data-journaled.

    's' When the file is deleted, all its blocks will be zeroed.

    'S' Changes to this file are written synchronously to disk.

    'T' (Directories only.) This is a hint to the block allocator that subdirectories contained in this directory should be spread across blocks. If not present, the block allocator will try to group subdirectories together.

    't' For a file, this disables tail-merging. (Not used by upstream implementations of ext2.)

    'u' When the file is deleted, its blocks will be saved, allowing the file to be undeleted.

    'X' The raw contents of the compressed file may be accessed.

    'Z' The compressed file is dirty.

    More file attributes may be added to this list later. Not all file attributes may be set for all kinds of files. For detailed information, consult the chattr(1) man page.

    See also guestfs_session_set_e2attrs().

    Don't confuse these attributes with extended attributes (see guestfs_session_getxattr()).

    Parameters

    • file: string

    Returns string

  • getE2generation(file: string): number
  • get ext2 file generation of a file

    This returns the ext2 file generation of a file. The generation (which used to be called the "version") is a number associated with an inode. This is most commonly used by NFS servers.

    The generation is only present when the file is located on an ext2/3/4 filesystem. Using this call on other filesystem types will result in an error.

    See guestfs_session_set_e2generation().

    Parameters

    • file: string

    Returns number

  • getE2label(device: string): string
  • get the ext2/3/4 filesystem label

    This returns the ext2/3/4 filesystem label of the filesystem on device.

    Parameters

    • device: string

    Returns string

  • getE2uuid(device: string): string
  • get the ext2/3/4 filesystem UUID

    This returns the ext2/3/4 filesystem UUID of the filesystem on device.

    Parameters

    • device: string

    Returns string

  • getHv(): string
  • get the hypervisor binary

    Return the current hypervisor binary.

    This is always non-NULL. If it wasn't set already, then this will return the default qemu binary name.

    Returns string

  • getIdentifier(): string
  • get the handle identifier

    Get the handle identifier. See guestfs_session_set_identifier().

    Returns string

  • getLibvirtRequestedCredentialChallenge(index: number): string
  • challenge of i'th requested credential

    Get the challenge (provided by libvirt) for the index'th requested credential. If libvirt did not provide a challenge, this returns the empty string "".

    See "LIBVIRT AUTHENTICATION" in guestfs(3) for documentation and example code.

    Parameters

    • index: number

    Returns string

  • getLibvirtRequestedCredentialDefresult(index: number): string
  • default result of i'th requested credential

    Get the default result (provided by libvirt) for the index'th requested credential. If libvirt did not provide a default result, this returns the empty string "".

    See "LIBVIRT AUTHENTICATION" in guestfs(3) for documentation and example code.

    Parameters

    • index: number

    Returns string

  • getLibvirtRequestedCredentialPrompt(index: number): string
  • prompt of i'th requested credential

    Get the prompt (provided by libvirt) for the index'th requested credential. If libvirt did not provide a prompt, this returns the empty string "".

    See "LIBVIRT AUTHENTICATION" in guestfs(3) for documentation and example code.

    Parameters

    • index: number

    Returns string

  • getLibvirtRequestedCredentials(): string[]
  • get list of credentials requested by libvirt

    This should only be called during the event callback for events of type GUESTFS_EVENT_LIBVIRT_AUTH.

    Return the list of credentials requested by libvirt. Possible values are a subset of the strings provided when you called guestfs_session_set_libvirt_supported_credentials().

    See "LIBVIRT AUTHENTICATION" in guestfs(3) for documentation and example code.

    Returns string[]

  • getMemsize(): number
  • get memory allocated to the hypervisor

    This gets the memory size in megabytes allocated to the hypervisor.

    If guestfs_session_set_memsize() was not called on this handle, and if LIBGUESTFS_MEMSIZE was not set, then this returns the compiled-in default value for memsize.

    For more information on the architecture of libguestfs, see guestfs(3).

    Returns number

  • getNetwork(): number
  • get enable network flag

    This returns the enable network flag.

    Returns number

  • getPath(): string
  • get the search path

    Return the current search path.

    This is always non-NULL. If it wasn't set already, then this will return the default path.

    Returns string

  • getPgroup(): number
  • get process group flag

    This returns the process group flag.

    Returns number

  • getPid(): number
  • get PID of hypervisor

    Return the process ID of the hypervisor. If there is no hypervisor running, then this will return an error.

    This is an internal call used for debugging and testing.

    Returns number

  • getProgram(): string
  • get the program name

    Get the program name. See guestfs_session_set_program().

    Returns string

  • getProperty(propertyName?: string, value?: any): void
  • Gets a property of an object.

    The value can be:

    • an empty #GValue initialized by %G_VALUE_INIT, which will be automatically initialized with the expected type of the property (since GLib 2.60)
    • a #GValue initialized with the expected type of the property
    • a #GValue initialized with a type to which the expected type of the property can be transformed

    In general, a copy is made of the property contents and the caller is responsible for freeing the memory by calling g_value_unset().

    Note that g_object_get_property() is really intended for language bindings, g_object_get() is much more convenient for C programming.

    Parameters

    • Optional propertyName: string

      the name of the property to get

    • Optional value: any

      return location for the property value

    Returns void

  • getQdata(quark: number): object
  • This function gets back user data pointers stored via g_object_set_qdata().

    Parameters

    • quark: number

      A #GQuark, naming the user data pointer

    Returns object

  • getQemu(): string
  • get the hypervisor binary (usually qemu)

    Return the current hypervisor binary (usually qemu).

    This is always non-NULL. If it wasn't set already, then this will return the default qemu binary name.

    Returns string

  • getRecoveryProc(): number
  • get recovery process enabled flag

    Return the recovery process enabled flag.

    Returns number

  • getSelinux(): number
  • get SELinux enabled flag

    This returns the current setting of the selinux flag which is passed to the appliance at boot time. See guestfs_session_set_selinux().

    For more information on the architecture of libguestfs, see guestfs(3).

    Returns number

  • getSmp(): number
  • get number of virtual CPUs in appliance

    This returns the number of virtual CPUs assigned to the appliance.

    Returns number

  • getSockdir(): string
  • get the temporary directory for sockets

    Get the directory used by the handle to store temporary socket files.

    This is different from guestfs_session_tmpdir(), as we need shorter paths for sockets (due to the limited buffers of filenames for UNIX sockets), and guestfs_session_tmpdir() may be too long for them.

    The environment variable XDG_RUNTIME_DIR controls the default value: If XDG_RUNTIME_DIR is set, then that is the default. Else /tmp is the default.

    Returns string

  • getState(): number
  • get the current state

    This returns the current state as an opaque integer. This is only useful for printing debug and internal error messages.

    For more information on states, see guestfs(3).

    Returns number

  • getTmpdir(): string
  • get the temporary directory

    Get the directory used by the handle to store temporary files.

    Returns string

  • getTrace(): number
  • get command trace enabled flag

    Return the command trace flag.

    Returns number

  • getUmask(): number
  • get the current umask

    Return the current umask. By default the umask is 022 unless it has been set by calling guestfs_session_umask().

    Returns number

  • getVerbose(): number
  • getcon(): string
  • get SELinux security context

    This gets the SELinux security context of the daemon.

    See the documentation about SELINUX in guestfs(3), and guestfs_session_setcon()

    This function depends on the feature "selinux". See also guestfs_session_feature_available().

    Returns string

  • getv(names: string[], values: any[]): void
  • Gets n_properties properties for an object. Obtained properties will be set to values. All properties must be valid. Warnings will be emitted and undefined behaviour may result if invalid properties are passed in.

    Parameters

    • names: string[]

      the names of each property to get

    • values: any[]

      the values of each property to get

    Returns void

  • getxattr(path: string, name: string): Uint8Array
  • get a single extended attribute

    Get a single extended attribute from file path named name. This call follows symlinks. If you want to lookup an extended attribute for the symlink itself, use guestfs_session_lgetxattr().

    Normally it is better to get all extended attributes from a file in one go by calling guestfs_session_getxattrs(). However some Linux filesystem implementations are buggy and do not provide a way to list out attributes. For these filesystems (notably ntfs-3g) you have to know the names of the extended attributes you want in advance and call this function.

    Extended attribute values are blobs of binary data. If there is no extended attribute named name, this returns an error.

    See also: guestfs_session_getxattrs(), guestfs_session_lgetxattr(), attr(5).

    This function depends on the feature "linuxxattrs". See also guestfs_session_feature_available().

    Parameters

    • path: string
    • name: string

    Returns Uint8Array

  • getxattrs(path: string): XAttr[]
  • list extended attributes of a file or directory

    This call lists the extended attributes of the file or directory path.

    At the system call level, this is a combination of the listxattr(2) and getxattr(2) calls.

    See also: guestfs_session_lgetxattrs(), attr(5).

    This function depends on the feature "linuxxattrs". See also guestfs_session_feature_available().

    Parameters

    • path: string

    Returns XAttr[]

  • globExpand(pattern: string, optargs: GlobExpand): string[]
  • expand a wildcard path

    This command searches for all the pathnames matching pattern according to the wildcard expansion rules used by the shell.

    If no paths match, then this returns an empty list (note: not an error).

    It is just a wrapper around the C glob(3) function with flags "GLOB_MARK|GLOB_BRACE". See that manual page for more details.

    directoryslash controls whether use the GLOB_MARK flag for glob(3), and it defaults to true. It can be explicitly set as off to return no trailing slashes in filenames of directories.

    Notice that there is no equivalent command for expanding a device name (eg. /dev/sd*). Use guestfs_session_list_devices(), guestfs_session_list_partitions() etc functions instead.

    Parameters

    • pattern: string
    • optargs: GlobExpand

      a GuestfsGlobExpand containing optional arguments

    Returns string[]

  • grep(regex: string, path: string, optargs: Grep): string[]
  • return lines matching a pattern

    This calls the external grep program and returns the matching lines.

    The optional flags are:

    extended Use extended regular expressions. This is the same as using the -E flag.

    fixed Match fixed (don't use regular expressions). This is the same as using the -F flag.

    insensitive Match case-insensitive. This is the same as using the -i flag.

    compressed Use zgrep instead of grep. This allows the input to be compress- or gzip-compressed.

    Parameters

    • regex: string
    • path: string
    • optargs: Grep

      a GuestfsGrep containing optional arguments

    Returns string[]

  • grepi(regex: string, path: string): string[]
  • return lines matching a pattern

    This calls the external "grep -i" program and returns the matching lines.

    Parameters

    • regex: string
    • path: string

    Returns string[]

  • grubInstall(root: string, device: string): boolean
  • install GRUB 1

    This command installs GRUB 1 (the Grand Unified Bootloader) on device, with the root directory being root.

    Notes:

    • There is currently no way in the API to install grub2, which is used by most modern Linux guests. It is possible to run the grub2 command from the guest, although see the caveats in "RUNNING COMMANDS" in guestfs(3).

    • This uses grub-install from the host. Unfortunately grub is not always compatible with itself, so this only works in rather narrow circumstances. Careful testing with each guest version is advisable.

    • If grub-install reports the error "No suitable drive was found in the generated device map." it may be that you need to create a /boot/grub/device.map file first that contains the mapping between grub device names and Linux device names. It is usually sufficient to create a file containing:

    replacing /dev/vda with the name of the installation device.

    This function depends on the feature "grub". See also guestfs_session_feature_available().

    Parameters

    • root: string
    • device: string

    Returns boolean

  • head(path: string): string[]
  • return first 10 lines of a file

    This command returns up to the first 10 lines of a file as a list of strings.

    Parameters

    • path: string

    Returns string[]

  • headN(nrlines: number, path: string): string[]
  • return first N lines of a file

    If the parameter nrlines is a positive number, this returns the first nrlines lines of the file path.

    If the parameter nrlines is a negative number, this returns lines from the file path, excluding the last nrlines lines.

    If the parameter nrlines is zero, this returns an empty list.

    Parameters

    • nrlines: number
    • path: string

    Returns string[]

  • hexdump(path: string): string
  • dump a file in hexadecimal

    This runs "hexdump -C" on the given path. The result is the human-readable, canonical hex dump of the file.

    Parameters

    • path: string

    Returns string

  • hivexClose(): boolean
  • close the current hivex handle

    Close the current hivex handle.

    This is a wrapper around the hivex(3) call of the same name.

    This function depends on the feature "hivex". See also guestfs_session_feature_available().

    Returns boolean

  • hivexCommit(filename: string): boolean
  • commit (write) changes back to the hive

    Commit (write) changes to the hive.

    If the optional filename parameter is null, then the changes are written back to the same hive that was opened. If this is not null then they are written to the alternate filename given and the original hive is left untouched.

    This is a wrapper around the hivex(3) call of the same name.

    This function depends on the feature "hivex". See also guestfs_session_feature_available().

    Parameters

    • filename: string

    Returns boolean

  • hivexNodeAddChild(parent: number, name: string): number
  • add a child node

    Add a child node to parent named name.

    This is a wrapper around the hivex(3) call of the same name.

    This function depends on the feature "hivex". See also guestfs_session_feature_available().

    Parameters

    • parent: number
    • name: string

    Returns number

  • hivexNodeChildren(nodeh: number): HivexNode[]
  • return list of nodes which are subkeys of node

    Return the list of nodes which are subkeys of nodeh.

    This is a wrapper around the hivex(3) call of the same name.

    This function depends on the feature "hivex". See also guestfs_session_feature_available().

    Parameters

    • nodeh: number

    Returns HivexNode[]

  • hivexNodeDeleteChild(nodeh: number): boolean
  • delete a node (recursively)

    Delete nodeh, recursively if necessary.

    This is a wrapper around the hivex(3) call of the same name.

    This function depends on the feature "hivex". See also guestfs_session_feature_available().

    Parameters

    • nodeh: number

    Returns boolean

  • hivexNodeGetChild(nodeh: number, name: string): number
  • return the named child of node

    Return the child of nodeh with the name name, if it exists. This can return 0 meaning the name was not found.

    This is a wrapper around the hivex(3) call of the same name.

    This function depends on the feature "hivex". See also guestfs_session_feature_available().

    Parameters

    • nodeh: number
    • name: string

    Returns number

  • hivexNodeGetValue(nodeh: number, key: string): number
  • return the named value

    Return the value attached to nodeh which has the name key, if it exists. This can return 0 meaning the key was not found.

    This is a wrapper around the hivex(3) call of the same name.

    This function depends on the feature "hivex". See also guestfs_session_feature_available().

    Parameters

    • nodeh: number
    • key: string

    Returns number

  • hivexNodeName(nodeh: number): string
  • return the name of the node

    Return the name of nodeh.

    This is a wrapper around the hivex(3) call of the same name.

    This function depends on the feature "hivex". See also guestfs_session_feature_available().

    Parameters

    • nodeh: number

    Returns string

  • hivexNodeParent(nodeh: number): number
  • return the parent of node

    Return the parent node of nodeh.

    This is a wrapper around the hivex(3) call of the same name.

    This function depends on the feature "hivex". See also guestfs_session_feature_available().

    Parameters

    • nodeh: number

    Returns number

  • hivexNodeSetValue(nodeh: number, key: string, t: number, val: Uint8Array): boolean
  • set or replace a single value in a node

    Set or replace a single value under the node nodeh. The key is the name, t is the type, and val is the data.

    This is a wrapper around the hivex(3) call of the same name.

    This function depends on the feature "hivex". See also guestfs_session_feature_available().

    Parameters

    • nodeh: number
    • key: string
    • t: number
    • val: Uint8Array

      an array of binary data

    Returns boolean

  • return list of values attached to node

    Return the array of (key, datatype, data) tuples attached to nodeh.

    This is a wrapper around the hivex(3) call of the same name.

    This function depends on the feature "hivex". See also guestfs_session_feature_available().

    Parameters

    • nodeh: number

    Returns HivexValue[]

  • hivexOpen(filename: string, optargs: HivexOpen): boolean
  • open a Windows Registry hive file

    Open the Windows Registry hive file named filename. If there was any previous hivex handle associated with this guestfs session, then it is closed.

    This is a wrapper around the hivex(3) call of the same name.

    This function depends on the feature "hivex". See also guestfs_session_feature_available().

    Parameters

    • filename: string
    • optargs: HivexOpen

      a GuestfsHivexOpen containing optional arguments

    Returns boolean

  • hivexRoot(): number
  • return the root node of the hive

    Return the root node of the hive.

    This is a wrapper around the hivex(3) call of the same name.

    This function depends on the feature "hivex". See also guestfs_session_feature_available().

    Returns number

  • hivexValueKey(valueh: number): string
  • return the key field from the (key, datatype, data) tuple

    Return the key (name) field of a (key, datatype, data) tuple.

    This is a wrapper around the hivex(3) call of the same name.

    This function depends on the feature "hivex". See also guestfs_session_feature_available().

    Parameters

    • valueh: number

    Returns string

  • hivexValueString(valueh: number): string
  • return the data field as a UTF-8 string

    This calls guestfs_session_hivex_value_value() (which returns the data field from a hivex value tuple). It then assumes that the field is a UTF-16LE string and converts the result to UTF-8 (or if this is not possible, it returns an error).

    This is useful for reading strings out of the Windows registry. However it is not foolproof because the registry is not strongly-typed and fields can contain arbitrary or unexpected data.

    This function depends on the feature "hivex". See also guestfs_session_feature_available().

    Parameters

    • valueh: number

    Returns string

  • hivexValueType(valueh: number): number
  • return the data type from the (key, datatype, data) tuple

    Return the data type field from a (key, datatype, data) tuple.

    This is a wrapper around the hivex(3) call of the same name.

    This function depends on the feature "hivex". See also guestfs_session_feature_available().

    Parameters

    • valueh: number

    Returns number

  • hivexValueUtf8(valueh: number): string
  • return the data field as a UTF-8 string

    This calls guestfs_session_hivex_value_value() (which returns the data field from a hivex value tuple). It then assumes that the field is a UTF-16LE string and converts the result to UTF-8 (or if this is not possible, it returns an error).

    This is useful for reading strings out of the Windows registry. However it is not foolproof because the registry is not strongly-typed and fields can contain arbitrary or unexpected data.

    This function depends on the feature "hivex". See also guestfs_session_feature_available().

    Parameters

    • valueh: number

    Returns string

  • hivexValueValue(valueh: number): Uint8Array
  • return the data field from the (key, datatype, data) tuple

    Return the data field of a (key, datatype, data) tuple.

    This is a wrapper around the hivex(3) call of the same name.

    See also: guestfs_session_hivex_value_utf8().

    This function depends on the feature "hivex". See also guestfs_session_feature_available().

    Parameters

    • valueh: number

    Returns Uint8Array

  • initrdCat(initrdpath: string, filename: string): Uint8Array
  • list the contents of a single file in an initrd

    This command unpacks the file filename from the initrd file called initrdpath. The filename must be given without the initial / character.

    For example, in guestfish you could use the following command to examine the boot script (usually called /init) contained in a Linux initrd or initramfs image:

    .img init]]>

    See also guestfs_session_initrd_list().

    Parameters

    • initrdpath: string
    • filename: string

    Returns Uint8Array

  • initrdList(path: string): string[]
  • list files in an initrd

    This command lists out files contained in an initrd.

    The files are listed without any initial / character. The files are listed in the order they appear (not necessarily alphabetical). Directory names are listed as separate items.

    Old Linux kernels (2.4 and earlier) used a compressed ext2 filesystem as initrd. We only support the newer initramfs format (compressed cpio files).

    Parameters

    • path: string

    Returns string[]

  • inotifyAddWatch(path: string, mask: number): number
  • add an inotify watch

    Watch path for the events listed in mask.

    Note that if path is a directory then events within that directory are watched, but this does not happen recursively (in subdirectories).

    Note for non-C or non-Linux callers: the inotify events are defined by the Linux kernel ABI and are listed in /usr/include/sys/inotify.h.

    This function depends on the feature "inotify". See also guestfs_session_feature_available().

    Parameters

    • path: string
    • mask: number

    Returns number

  • inotifyClose(): boolean
  • close the inotify handle

    This closes the inotify handle which was previously opened by inotify_init. It removes all watches, throws away any pending events, and deallocates all resources.

    This function depends on the feature "inotify". See also guestfs_session_feature_available().

    Returns boolean

  • inotifyFiles(): string[]
  • return list of watched files that had events

    This function is a helpful wrapper around guestfs_session_inotify_read() which just returns a list of pathnames of objects that were touched. The returned pathnames are sorted and deduplicated.

    This function depends on the feature "inotify". See also guestfs_session_feature_available().

    Returns string[]

  • inotifyInit(maxevents: number): boolean
  • create an inotify handle

    This command creates a new inotify handle. The inotify subsystem can be used to notify events which happen to objects in the guest filesystem.

    maxevents is the maximum number of events which will be queued up between calls to guestfs_session_inotify_read() or guestfs_session_inotify_files(). If this is passed as 0, then the kernel (or previously set) default is used. For Linux 2.6.29 the default was 16384 events. Beyond this limit, the kernel throws away events, but records the fact that it threw them away by setting a flag IN_Q_OVERFLOW in the returned structure list (see guestfs_session_inotify_read()).

    Before any events are generated, you have to add some watches to the internal watch list. See: guestfs_session_inotify_add_watch() and guestfs_session_inotify_rm_watch().

    Queued up events should be read periodically by calling guestfs_session_inotify_read() (or guestfs_session_inotify_files() which is just a helpful wrapper around guestfs_session_inotify_read()). If you don't read the events out often enough then you risk the internal queue overflowing.

    The handle should be closed after use by calling guestfs_session_inotify_close(). This also removes any watches automatically.

    See also inotify(7) for an overview of the inotify interface as exposed by the Linux kernel, which is roughly what we expose via libguestfs. Note that there is one global inotify handle per libguestfs instance.

    This function depends on the feature "inotify". See also guestfs_session_feature_available().

    Parameters

    • maxevents: number

    Returns boolean

  • return list of inotify events

    Return the complete queue of events that have happened since the previous read call.

    If no events have happened, this returns an empty list.

    Note: In order to make sure that all events have been read, you must call this function repeatedly until it returns an empty list. The reason is that the call will read events up to the maximum appliance-to-host message size and leave remaining events in the queue.

    This function depends on the feature "inotify". See also guestfs_session_feature_available().

    Returns INotifyEvent[]

  • inotifyRmWatch(wd: number): boolean
  • remove an inotify watch

    Remove a previously defined inotify watch. See guestfs_session_inotify_add_watch().

    This function depends on the feature "inotify". See also guestfs_session_feature_available().

    Parameters

    • wd: number

    Returns boolean

  • inspectGetArch(root: string): string
  • get architecture of inspected operating system

    This returns the architecture of the inspected operating system. The possible return values are listed under guestfs_session_file_architecture().

    If the architecture could not be determined, then the string unknown is returned.

    Please read "INSPECTION" in guestfs(3) for more details.

    Parameters

    • root: string

    Returns string

  • inspectGetDistro(root: string): string
  • get distro of inspected operating system

    This returns the distro (distribution) of the inspected operating system.

    Currently defined distros are:

    "alpinelinux" Alpine Linux.

    "altlinux" ALT Linux.

    "archlinux" Arch Linux.

    "buildroot" Buildroot-derived distro, but not one we specifically recognize.

    "centos" CentOS.

    "cirros" Cirros.

    "coreos" CoreOS.

    "debian" Debian.

    "fedora" Fedora.

    "freebsd" FreeBSD.

    "freedos" FreeDOS.

    "frugalware" Frugalware.

    "gentoo" Gentoo.

    "kalilinux" Kali Linux.

    "linuxmint" Linux Mint.

    "mageia" Mageia.

    "mandriva" Mandriva.

    "meego" MeeGo.

    "msdos" Microsoft DOS.

    "neokylin" NeoKylin.

    "netbsd" NetBSD.

    "openbsd" OpenBSD.

    "opensuse" OpenSUSE.

    "oraclelinux" Oracle Linux.

    "pardus" Pardus.

    "pldlinux" PLD Linux.

    "redhat-based" Some Red Hat-derived distro.

    "rhel" Red Hat Enterprise Linux.

    "scientificlinux" Scientific Linux.

    "slackware" Slackware.

    "sles" SuSE Linux Enterprise Server or Desktop.

    "suse-based" Some openSuSE-derived distro.

    "ttylinux" ttylinux.

    "ubuntu" Ubuntu.

    "unknown" The distro could not be determined.

    "voidlinux" Void Linux.

    "windows" Windows does not have distributions. This string is returned if the OS type is Windows.

    Future versions of libguestfs may return other strings here. The caller should be prepared to handle any string.

    Please read "INSPECTION" in guestfs(3) for more details.

    Parameters

    • root: string

    Returns string

  • inspectGetDriveMappings(root: string): HashTable<string | number | symbol, string | number | boolean>
  • get drive letter mappings

    This call is useful for Windows which uses a primitive system of assigning drive letters (like C:) to partitions. This inspection API examines the Windows Registry to find out how disks/partitions are mapped to drive letters, and returns a hash table as in the example below:

    /dev/vda2]]> /dev/vdb1]]> /dev/vdc1]]>

    Note that keys are drive letters. For Windows, the key is case insensitive and just contains the drive letter, without the customary colon separator character.

    In future we may support other operating systems that also used drive letters, but the keys for those might not be case insensitive and might be longer than 1 character. For example in OS-9, hard drives were named h0, h1 etc.

    For Windows guests, currently only hard drive mappings are returned. Removable disks (eg. DVD-ROMs) are ignored.

    For guests that do not use drive mappings, or if the drive mappings could not be determined, this returns an empty hash table.

    Please read "INSPECTION" in guestfs(3) for more details. See also guestfs_session_inspect_get_mountpoints(), guestfs_session_inspect_get_filesystems().

    Parameters

    • root: string

    Returns HashTable<string | number | symbol, string | number | boolean>

  • inspectGetFilesystems(root: string): string[]
  • get filesystems associated with inspected operating system

    This returns a list of all the filesystems that we think are associated with this operating system. This includes the root filesystem, other ordinary filesystems, and non-mounted devices like swap partitions.

    In the case of a multi-boot virtual machine, it is possible for a filesystem to be shared between operating systems.

    Please read "INSPECTION" in guestfs(3) for more details. See also guestfs_session_inspect_get_mountpoints().

    Parameters

    • root: string

    Returns string[]

  • inspectGetFormat(root: string): string
  • get format of inspected operating system

    Before libguestfs 1.38, there was some unreliable support for detecting installer CDs. This API would return:

    "installed" This is an installed operating system.

    "installer" The disk image being inspected is not an installed operating system, but a bootable install disk, live CD, or similar.

    "unknown" The format of this disk image is not known.

    In libguestfs ≥ 1.38, this only returns installed. Use libosinfo directly to detect installer CDs.

    Please read "INSPECTION" in guestfs(3) for more details.

    Parameters

    • root: string

    Returns string

  • inspectGetHostname(root: string): string
  • get hostname of the operating system

    This function returns the hostname of the operating system as found by inspection of the guest’s configuration files.

    If the hostname could not be determined, then the string unknown is returned.

    Please read "INSPECTION" in guestfs(3) for more details.

    Parameters

    • root: string

    Returns string

  • get the icon corresponding to this operating system

    This function returns an icon corresponding to the inspected operating system. The icon is returned as a buffer containing a PNG image (re-encoded to PNG if necessary).

    If it was not possible to get an icon this function returns a zero-length (non-NULL) buffer. Callers must check for this case.

    Libguestfs will start by looking for a file called /etc/favicon.png or C:\etc\favicon.png and if it has the correct format, the contents of this file will be returned. You can disable favicons by passing the optional favicon boolean as false (default is true).

    If finding the favicon fails, then we look in other places in the guest for a suitable icon.

    If the optional highquality boolean is true then only high quality icons are returned, which means only icons of high resolution with an alpha channel. The default (false) is to return any icon we can, even if it is of substandard quality.

    Notes:

    • Unlike most other inspection API calls, the guest’s disks must be mounted up before you call this, since it needs to read information from the guest filesystem during the call.

    • Security: The icon data comes from the untrusted guest, and should be treated with caution. PNG files have been known to contain exploits. Ensure that libpng (or other relevant libraries) are fully up to date before trying to process or display the icon.

    • The PNG image returned can be any size. It might not be square. Libguestfs tries to return the largest, highest quality icon available. The application must scale the icon to the required size.

    • Extracting icons from Windows guests requires the external wrestool program from the icoutils package, and several programs (bmptopnm, pnmtopng, pamcut) from the netpbm package. These must be installed separately.

    • Operating system icons are usually trademarks. Seek legal advice before using trademarks in applications.

    Parameters

    • root: string
    • optargs: InspectGetIcon

      a GuestfsInspectGetIcon containing optional arguments

    Returns Uint8Array

  • inspectGetMajorVersion(root: string): number
  • get major version of inspected operating system

    This returns the major version number of the inspected operating system.

    Windows uses a consistent versioning scheme which is not reflected in the popular public names used by the operating system. Notably the operating system known as "Windows 7" is really version 6.1 (ie. major = 6, minor = 1). You can find out the real versions corresponding to releases of Windows by consulting Wikipedia or MSDN.

    If the version could not be determined, then 0 is returned.

    Please read "INSPECTION" in guestfs(3) for more details.

    Parameters

    • root: string

    Returns number

  • inspectGetMinorVersion(root: string): number
  • get minor version of inspected operating system

    This returns the minor version number of the inspected operating system.

    If the version could not be determined, then 0 is returned.

    Please read "INSPECTION" in guestfs(3) for more details. See also guestfs_session_inspect_get_major_version().

    Parameters

    • root: string

    Returns number

  • inspectGetMountpoints(root: string): HashTable<string | number | symbol, string | number | boolean>
  • get mountpoints of inspected operating system

    This returns a hash of where we think the filesystems associated with this operating system should be mounted. Callers should note that this is at best an educated guess made by reading configuration files such as /etc/fstab. In particular note that this may return filesystems which are non-existent or not mountable and callers should be prepared to handle or ignore failures if they try to mount them.

    Each element in the returned hashtable has a key which is the path of the mountpoint (eg. /boot) and a value which is the filesystem that would be mounted there (eg. /dev/sda1).

    Non-mounted devices such as swap devices are not returned in this list.

    For operating systems like Windows which still use drive letters, this call will only return an entry for the first drive "mounted on" /. For information about the mapping of drive letters to partitions, see guestfs_session_inspect_get_drive_mappings().

    Please read "INSPECTION" in guestfs(3) for more details. See also guestfs_session_inspect_get_filesystems().

    Parameters

    • root: string

    Returns HashTable<string | number | symbol, string | number | boolean>

  • inspectGetOsinfo(root: string): string
  • get a possible osinfo short ID corresponding to this operating system

    This function returns a possible short ID for libosinfo corresponding to the guest.

    Note: The returned ID is only a guess by libguestfs, and nothing ensures that it actually exists in osinfo-db.

    If no ID could not be determined, then the string unknown is returned.

    Parameters

    • root: string

    Returns string

  • inspectGetPackageFormat(root: string): string
  • get package format used by the operating system

    This function and guestfs_session_inspect_get_package_management() return the package format and package management tool used by the inspected operating system. For example for Fedora these functions would return rpm (package format), and yum or dnf (package management).

    This returns the string unknown if we could not determine the package format or if the operating system does not have a real packaging system (eg. Windows).

    Possible strings include: rpm, deb, ebuild, pisi, pacman, pkgsrc, apk, xbps. Future versions of libguestfs may return other strings.

    Please read "INSPECTION" in guestfs(3) for more details.

    Parameters

    • root: string

    Returns string

  • inspectGetPackageManagement(root: string): string
  • get package management tool used by the operating system

    guestfs_session_inspect_get_package_format() and this function return the package format and package management tool used by the inspected operating system. For example for Fedora these functions would return rpm (package format), and yum or dnf (package management).

    This returns the string unknown if we could not determine the package management tool or if the operating system does not have a real packaging system (eg. Windows).

    Possible strings include: yum, dnf, up2date, apt (for all Debian derivatives), portage, pisi, pacman, urpmi, zypper, apk, xbps. Future versions of libguestfs may return other strings.

    Please read "INSPECTION" in guestfs(3) for more details.

    Parameters

    • root: string

    Returns string

  • inspectGetProductName(root: string): string
  • get product name of inspected operating system

    This returns the product name of the inspected operating system. The product name is generally some freeform string which can be displayed to the user, but should not be parsed by programs.

    If the product name could not be determined, then the string unknown is returned.

    Please read "INSPECTION" in guestfs(3) for more details.

    Parameters

    • root: string

    Returns string

  • inspectGetProductVariant(root: string): string
  • get product variant of inspected operating system

    This returns the product variant of the inspected operating system.

    For Windows guests, this returns the contents of the Registry key "HKLM\Software\Microsoft\Windows NT\CurrentVersion" InstallationType which is usually a string such as Client or Server (other values are possible). This can be used to distinguish consumer and enterprise versions of Windows that have the same version number (for example, Windows 7 and Windows 2008 Server are both version 6.1, but the former is Client and the latter is Server).

    For enterprise Linux guests, in future we intend this to return the product variant such as Desktop, Server and so on. But this is not implemented at present.

    If the product variant could not be determined, then the string unknown is returned.

    Please read "INSPECTION" in guestfs(3) for more details. See also guestfs_session_inspect_get_product_name(), guestfs_session_inspect_get_major_version().

    Parameters

    • root: string

    Returns string

  • inspectGetRoots(): string[]
  • return list of operating systems found by last inspection

    This function is a convenient way to get the list of root devices, as returned from a previous call to guestfs_session_inspect_os(), but without redoing the whole inspection process.

    This returns an empty list if either no root devices were found or the caller has not called guestfs_session_inspect_os().

    Please read "INSPECTION" in guestfs(3) for more details.

    Returns string[]

  • inspectGetType(root: string): string
  • get type of inspected operating system

    This returns the type of the inspected operating system. Currently defined types are:

    "linux" Any Linux-based operating system.

    "windows" Any Microsoft Windows operating system.

    "freebsd" FreeBSD.

    "netbsd" NetBSD.

    "openbsd" OpenBSD.

    "hurd" GNU/Hurd.

    "dos" MS-DOS, FreeDOS and others.

    "minix" MINIX.

    "unknown" The operating system type could not be determined.

    Future versions of libguestfs may return other strings here. The caller should be prepared to handle any string.

    Please read "INSPECTION" in guestfs(3) for more details.

    Parameters

    • root: string

    Returns string

  • inspectGetWindowsCurrentControlSet(root: string): string
  • get Windows CurrentControlSet of inspected operating system

    This returns the Windows CurrentControlSet of the inspected guest. The CurrentControlSet is a registry key name such as ControlSet001.

    This call assumes that the guest is Windows and that the Registry could be examined by inspection. If this is not the case then an error is returned.

    Please read "INSPECTION" in guestfs(3) for more details.

    Parameters

    • root: string

    Returns string

  • inspectGetWindowsSoftwareHive(root: string): string
  • get the path of the Windows software hive

    This returns the path to the hive (binary Windows Registry file) corresponding to HKLM\SOFTWARE.

    This call assumes that the guest is Windows and that the guest has a software hive file with the right name. If this is not the case then an error is returned. This call does not check that the hive is a valid Windows Registry hive.

    You can use guestfs_session_hivex_open() to read or write to the hive.

    Please read "INSPECTION" in guestfs(3) for more details.

    Parameters

    • root: string

    Returns string

  • inspectGetWindowsSystemHive(root: string): string
  • get the path of the Windows system hive

    This returns the path to the hive (binary Windows Registry file) corresponding to HKLM\SYSTEM.

    This call assumes that the guest is Windows and that the guest has a system hive file with the right name. If this is not the case then an error is returned. This call does not check that the hive is a valid Windows Registry hive.

    You can use guestfs_session_hivex_open() to read or write to the hive.

    Please read "INSPECTION" in guestfs(3) for more details.

    Parameters

    • root: string

    Returns string

  • inspectGetWindowsSystemroot(root: string): string
  • get Windows systemroot of inspected operating system

    This returns the Windows systemroot of the inspected guest. The systemroot is a directory path such as /WINDOWS.

    This call assumes that the guest is Windows and that the systemroot could be determined by inspection. If this is not the case then an error is returned.

    Please read "INSPECTION" in guestfs(3) for more details.

    Parameters

    • root: string

    Returns string

  • inspectIsLive(root: string): number
  • get live flag for install disk

    This is deprecated and always returns false.

    Please read "INSPECTION" in guestfs(3) for more details.

    Parameters

    • root: string

    Returns number

  • inspectIsMultipart(root: string): number
  • get multipart flag for install disk

    This is deprecated and always returns false.

    Please read "INSPECTION" in guestfs(3) for more details.

    Parameters

    • root: string

    Returns number

  • inspectIsNetinst(root: string): number
  • get netinst (network installer) flag for install disk

    This is deprecated and always returns false.

    Please read "INSPECTION" in guestfs(3) for more details.

    Parameters

    • root: string

    Returns number

  • get list of applications installed in the operating system

    Return the list of applications installed in the operating system.

    Note: This call works differently from other parts of the inspection API. You have to call guestfs_session_inspect_os(), then guestfs_session_inspect_get_mountpoints(), then mount up the disks, before calling this. Listing applications is a significantly more difficult operation which requires access to the full filesystem. Also note that unlike the other "guestfs_inspect_get_*" calls which are just returning data cached in the libguestfs handle, this call actually reads parts of the mounted filesystems during the call.

    This returns an empty list if the inspection code was not able to determine the list of applications.

    The application structure contains the following fields:

    app_name The name of the application. For Red Hat-derived and Debian-derived Linux guests, this is the package name.

    app_display_name The display name of the application, sometimes localized to the install language of the guest operating system.

    If unavailable this is returned as an empty string "". Callers needing to display something can use app_name instead.

    app_epoch For package managers which use epochs, this contains the epoch of the package (an integer). If unavailable, this is returned as 0.

    app_version The version string of the application or package. If unavailable this is returned as an empty string "".

    app_release The release string of the application or package, for package managers that use this. If unavailable this is returned as an empty string "".

    app_install_path The installation path of the application (on operating systems such as Windows which use installation paths). This path is in the format used by the guest operating system, it is not a libguestfs path.

    If unavailable this is returned as an empty string "".

    app_trans_path The install path translated into a libguestfs path. If unavailable this is returned as an empty string "".

    app_publisher The name of the publisher of the application, for package managers that use this. If unavailable this is returned as an empty string "".

    app_url The URL (eg. upstream URL) of the application. If unavailable this is returned as an empty string "".

    app_source_package For packaging systems which support this, the name of the source package. If unavailable this is returned as an empty string "".

    app_summary A short (usually one line) description of the application or package. If unavailable this is returned as an empty string "".

    app_description A longer description of the application or package. If unavailable this is returned as an empty string "".

    Please read "INSPECTION" in guestfs(3) for more details.

    Parameters

    • root: string

    Returns Guestfs.Application[]

  • get list of applications installed in the operating system

    Return the list of applications installed in the operating system.

    Note: This call works differently from other parts of the inspection API. You have to call guestfs_session_inspect_os(), then guestfs_session_inspect_get_mountpoints(), then mount up the disks, before calling this. Listing applications is a significantly more difficult operation which requires access to the full filesystem. Also note that unlike the other "guestfs_inspect_get_*" calls which are just returning data cached in the libguestfs handle, this call actually reads parts of the mounted filesystems during the call.

    This returns an empty list if the inspection code was not able to determine the list of applications.

    The application structure contains the following fields:

    app2_name The name of the application. For Red Hat-derived and Debian-derived Linux guests, this is the package name.

    app2_display_name The display name of the application, sometimes localized to the install language of the guest operating system.

    If unavailable this is returned as an empty string "". Callers needing to display something can use app2_name instead.

    app2_epoch For package managers which use epochs, this contains the epoch of the package (an integer). If unavailable, this is returned as 0.

    app2_version The version string of the application or package. If unavailable this is returned as an empty string "".

    app2_release The release string of the application or package, for package managers that use this. If unavailable this is returned as an empty string "".

    app2_arch The architecture string of the application or package, for package managers that use this. If unavailable this is returned as an empty string "".

    app2_install_path The installation path of the application (on operating systems such as Windows which use installation paths). This path is in the format used by the guest operating system, it is not a libguestfs path.

    If unavailable this is returned as an empty string "".

    app2_trans_path The install path translated into a libguestfs path. If unavailable this is returned as an empty string "".

    app2_publisher The name of the publisher of the application, for package managers that use this. If unavailable this is returned as an empty string "".

    app2_url The URL (eg. upstream URL) of the application. If unavailable this is returned as an empty string "".

    app2_source_package For packaging systems which support this, the name of the source package. If unavailable this is returned as an empty string "".

    app2_summary A short (usually one line) description of the application or package. If unavailable this is returned as an empty string "".

    app2_description A longer description of the application or package. If unavailable this is returned as an empty string "".

    Please read "INSPECTION" in guestfs(3) for more details.

    Parameters

    • root: string

    Returns Application2[]

  • inspectOs(): string[]
  • inspect disk and return list of operating systems found

    This function uses other libguestfs functions and certain heuristics to inspect the disk(s) (usually disks belonging to a virtual machine), looking for operating systems.

    The list returned is empty if no operating systems were found.

    If one operating system was found, then this returns a list with a single element, which is the name of the root filesystem of this operating system. It is also possible for this function to return a list containing more than one element, indicating a dual-boot or multi-boot virtual machine, with each element being the root filesystem of one of the operating systems.

    You can pass the root string(s) returned to other "guestfs_inspect_get_*" functions in order to query further information about each operating system, such as the name and version.

    This function uses other libguestfs features such as guestfs_session_mount_ro() and guestfs_session_umount_all() in order to mount and unmount filesystems and look at the contents. This should be called with no disks currently mounted. The function may also use Augeas, so any existing Augeas handle will be closed.

    This function cannot decrypt encrypted disks. The caller must do that first (supplying the necessary keys) if the disk is encrypted.

    Please read "INSPECTION" in guestfs(3) for more details.

    See also guestfs_session_list_filesystems().

    Returns string[]

  • cause the daemon to exit (internal use only)

    This function is used internally when testing the appliance.

    Parameters

    Returns boolean

  • internalTest(str: string, optstr: string, strlist: string[], b: boolean, integer: number, integer64: number, filein: string, fileout: string, bufferin: Uint8Array, optargs: InternalTest, cancellable: Gio.Cancellable): boolean
  • internal test function - do not use

    This is an internal test function which is used to test whether the automatically generated bindings can handle every possible parameter type correctly.

    It echos the contents of each parameter to stdout (by default) or to a file (if guestfs_session_internal_test_set_output() was called).

    You probably don't want to call this function.

    Parameters

    • str: string
    • optstr: string
    • strlist: string[]

      an array of strings

    • b: boolean
    • integer: number
    • integer64: number
    • filein: string
    • fileout: string
    • bufferin: Uint8Array

      an array of binary data

    • optargs: InternalTest

      a GuestfsInternalTest containing optional arguments

    • cancellable: Gio.Cancellable

      A GCancellable object

    Returns boolean

  • internal test function - do not use

    This is an internal test function which is used to test whether the automatically generated bindings can handle the full range of 63 optargs correctly. (Note that 63 is not an absolute limit and it could be raised by changing the XDR protocol).

    It echos the contents of each parameter to stdout (by default) or to a file (if guestfs_session_internal_test_set_output() was called).

    You probably don't want to call this function.

    Parameters

    Returns boolean

  • internalTestCloseOutput(): boolean
  • internal test function - do not use

    This is an internal test function which is used to test whether the automatically generated bindings can handle every possible parameter type correctly.

    It closes the output file previously opened by guestfs_session_internal_test_set_output().

    You probably don't want to call this function.

    Returns boolean

  • internal test function - do not use

    This is an internal test function which is used to test whether the automatically generated bindings can handle no args, some optargs correctly.

    It echos the contents of each parameter to stdout (by default) or to a file (if guestfs_session_internal_test_set_output() was called).

    You probably don't want to call this function.

    Parameters

    Returns boolean

  • internalTestRbool(val: string): number
  • internal test function - do not use

    This is an internal test function which is used to test whether the automatically generated bindings can handle every possible return type correctly.

    It converts string val to the return type.

    You probably don't want to call this function.

    Parameters

    • val: string

    Returns number

  • internalTestRboolerr(): number
  • internal test function - do not use

    This is an internal test function which is used to test whether the automatically generated bindings can handle every possible return type correctly.

    This function always returns an error.

    You probably don't want to call this function.

    Returns number

  • internalTestRbufferout(val: string): Uint8Array
  • internal test function - do not use

    This is an internal test function which is used to test whether the automatically generated bindings can handle every possible return type correctly.

    It converts string val to the return type.

    You probably don't want to call this function.

    Parameters

    • val: string

    Returns Uint8Array

  • internalTestRbufferouterr(): Uint8Array
  • internal test function - do not use

    This is an internal test function which is used to test whether the automatically generated bindings can handle every possible return type correctly.

    This function always returns an error.

    You probably don't want to call this function.

    Returns Uint8Array

  • internalTestRconstoptstring(val: string): string
  • internal test function - do not use

    This is an internal test function which is used to test whether the automatically generated bindings can handle every possible return type correctly.

    It converts string val to the return type.

    You probably don't want to call this function.

    Parameters

    • val: string

    Returns string

  • internalTestRconstoptstringerr(): string
  • internal test function - do not use

    This is an internal test function which is used to test whether the automatically generated bindings can handle every possible return type correctly.

    This function always returns an error.

    You probably don't want to call this function.

    Returns string

  • internalTestRconststring(val: string): string
  • internal test function - do not use

    This is an internal test function which is used to test whether the automatically generated bindings can handle every possible return type correctly.

    It converts string val to the return type.

    You probably don't want to call this function.

    Parameters

    • val: string

    Returns string

  • internalTestRconststringerr(): string
  • internal test function - do not use

    This is an internal test function which is used to test whether the automatically generated bindings can handle every possible return type correctly.

    This function always returns an error.

    You probably don't want to call this function.

    Returns string

  • internalTestRhashtable(val: string): HashTable<string | number | symbol, string | number | boolean>
  • internal test function - do not use

    This is an internal test function which is used to test whether the automatically generated bindings can handle every possible return type correctly.

    It converts string val to the return type.

    You probably don't want to call this function.

    Parameters

    • val: string

    Returns HashTable<string | number | symbol, string | number | boolean>

  • internalTestRhashtableerr(): HashTable<string | number | symbol, string | number | boolean>
  • internal test function - do not use

    This is an internal test function which is used to test whether the automatically generated bindings can handle every possible return type correctly.

    This function always returns an error.

    You probably don't want to call this function.

    Returns HashTable<string | number | symbol, string | number | boolean>

  • internalTestRint(val: string): number
  • internal test function - do not use

    This is an internal test function which is used to test whether the automatically generated bindings can handle every possible return type correctly.

    It converts string val to the return type.

    You probably don't want to call this function.

    Parameters

    • val: string

    Returns number

  • internalTestRint64(val: string): number
  • internal test function - do not use

    This is an internal test function which is used to test whether the automatically generated bindings can handle every possible return type correctly.

    It converts string val to the return type.

    You probably don't want to call this function.

    Parameters

    • val: string

    Returns number

  • internalTestRint64err(): number
  • internal test function - do not use

    This is an internal test function which is used to test whether the automatically generated bindings can handle every possible return type correctly.

    This function always returns an error.

    You probably don't want to call this function.

    Returns number

  • internalTestRinterr(): number
  • internal test function - do not use

    This is an internal test function which is used to test whether the automatically generated bindings can handle every possible return type correctly.

    This function always returns an error.

    You probably don't want to call this function.

    Returns number

  • internalTestRstring(val: string): string
  • internal test function - do not use

    This is an internal test function which is used to test whether the automatically generated bindings can handle every possible return type correctly.

    It converts string val to the return type.

    You probably don't want to call this function.

    Parameters

    • val: string

    Returns string

  • internalTestRstringerr(): string
  • internal test function - do not use

    This is an internal test function which is used to test whether the automatically generated bindings can handle every possible return type correctly.

    This function always returns an error.

    You probably don't want to call this function.

    Returns string

  • internalTestRstringlist(val: string): string[]
  • internal test function - do not use

    This is an internal test function which is used to test whether the automatically generated bindings can handle every possible return type correctly.

    It converts string val to the return type.

    You probably don't want to call this function.

    Parameters

    • val: string

    Returns string[]

  • internalTestRstringlisterr(): string[]
  • internal test function - do not use

    This is an internal test function which is used to test whether the automatically generated bindings can handle every possible return type correctly.

    This function always returns an error.

    You probably don't want to call this function.

    Returns string[]

  • internalTestRstruct(val: string): PV
  • internal test function - do not use

    This is an internal test function which is used to test whether the automatically generated bindings can handle every possible return type correctly.

    It converts string val to the return type.

    You probably don't want to call this function.

    Parameters

    • val: string

    Returns PV

  • internalTestRstructerr(): PV
  • internal test function - do not use

    This is an internal test function which is used to test whether the automatically generated bindings can handle every possible return type correctly.

    This function always returns an error.

    You probably don't want to call this function.

    Returns PV

  • internalTestRstructlist(val: string): PV[]
  • internal test function - do not use

    This is an internal test function which is used to test whether the automatically generated bindings can handle every possible return type correctly.

    It converts string val to the return type.

    You probably don't want to call this function.

    Parameters

    • val: string

    Returns PV[]

  • internalTestRstructlisterr(): PV[]
  • internal test function - do not use

    This is an internal test function which is used to test whether the automatically generated bindings can handle every possible return type correctly.

    This function always returns an error.

    You probably don't want to call this function.

    Returns PV[]

  • internalTestSetOutput(filename: string): boolean
  • internal test function - do not use

    This is an internal test function which is used to test whether the automatically generated bindings can handle every possible parameter type correctly.

    It sets the output file used by guestfs_session_internal_test().

    You probably don't want to call this function.

    Parameters

    • filename: string

    Returns boolean

  • isBlockdev(path: string, optargs: IsBlockdev): number
  • test if block device

    This returns true if and only if there is a block device with the given path name.

    If the optional flag followsymlinks is true, then a symlink (or chain of symlinks) that ends with a block device also causes the function to return true.

    This call only looks at files within the guest filesystem. Libguestfs partitions and block devices (eg. /dev/sda) cannot be used as the path parameter of this call.

    See also guestfs_session_stat().

    Parameters

    • path: string
    • optargs: IsBlockdev

      a GuestfsIsBlockdev containing optional arguments

    Returns number

  • isBusy(): number
  • is busy processing a command

    This always returns false. This function is deprecated with no replacement. Do not use this function.

    For more information on states, see guestfs(3).

    Returns number

  • isChardev(path: string, optargs: IsChardev): number
  • test if character device

    This returns true if and only if there is a character device with the given path name.

    If the optional flag followsymlinks is true, then a symlink (or chain of symlinks) that ends with a chardev also causes the function to return true.

    See also guestfs_session_stat().

    Parameters

    • path: string
    • optargs: IsChardev

      a GuestfsIsChardev containing optional arguments

    Returns number

  • isConfig(): number
  • is in configuration state

    This returns true iff this handle is being configured (in the CONFIG state).

    For more information on states, see guestfs(3).

    Returns number

  • isDir(path: string, optargs: IsDir): number
  • test if a directory

    This returns true if and only if there is a directory with the given path name. Note that it returns false for other objects like files.

    If the optional flag followsymlinks is true, then a symlink (or chain of symlinks) that ends with a directory also causes the function to return true.

    See also guestfs_session_stat().

    Parameters

    • path: string
    • optargs: IsDir

      a GuestfsIsDir containing optional arguments

    Returns number

  • isFifo(path: string, optargs: IsFifo): number
  • test if FIFO (named pipe)

    This returns true if and only if there is a FIFO (named pipe) with the given path name.

    If the optional flag followsymlinks is true, then a symlink (or chain of symlinks) that ends with a FIFO also causes the function to return true.

    See also guestfs_session_stat().

    Parameters

    • path: string
    • optargs: IsFifo

      a GuestfsIsFifo containing optional arguments

    Returns number

  • isFile(path: string, optargs: IsFile): number
  • test if a regular file

    This returns true if and only if there is a regular file with the given path name. Note that it returns false for other objects like directories.

    If the optional flag followsymlinks is true, then a symlink (or chain of symlinks) that ends with a file also causes the function to return true.

    See also guestfs_session_stat().

    Parameters

    • path: string
    • optargs: IsFile

      a GuestfsIsFile containing optional arguments

    Returns number

  • isFloating(): boolean
  • isLaunching(): number
  • is launching subprocess

    This returns true iff this handle is launching the subprocess (in the LAUNCHING state).

    For more information on states, see guestfs(3).

    Returns number

  • isLv(mountable: string): number
  • test if mountable is a logical volume

    This command tests whether mountable is a logical volume, and returns true iff this is the case.

    Parameters

    • mountable: string

    Returns number

  • isReady(): number
  • is ready to accept commands

    This returns true iff this handle is ready to accept commands (in the READY state).

    For more information on states, see guestfs(3).

    Returns number

  • isSocket(path: string, optargs: IsSocket): number
  • test if socket

    This returns true if and only if there is a Unix domain socket with the given path name.

    If the optional flag followsymlinks is true, then a symlink (or chain of symlinks) that ends with a socket also causes the function to return true.

    See also guestfs_session_stat().

    Parameters

    • path: string
    • optargs: IsSocket

      a GuestfsIsSocket containing optional arguments

    Returns number

  • isSymlink(path: string): number
  • test if symbolic link

    This returns true if and only if there is a symbolic link with the given path name.

    See also guestfs_session_stat().

    Parameters

    • path: string

    Returns number

  • isWholeDevice(device: string): number
  • test if a device is a whole device

    This returns true if and only if device refers to a whole block device. That is, not a partition or a logical device.

    Parameters

    • device: string

    Returns number

  • isZero(path: string): number
  • test if a file contains all zero bytes

    This returns true iff the file exists and the file is empty or it contains all zero bytes.

    Parameters

    • path: string

    Returns number

  • isZeroDevice(device: string): number
  • test if a device contains all zero bytes

    This returns true iff the device exists and contains all zero bytes.

    Note that for large devices this can take a long time to run.

    Parameters

    • device: string

    Returns number

  • get ISO information from primary volume descriptor of ISO file

    This is the same as guestfs_session_isoinfo_device() except that it works for an ISO file located inside some other mounted filesystem. Note that in the common case where you have added an ISO file as a libguestfs device, you would not call this. Instead you would call guestfs_session_isoinfo_device().

    Parameters

    • isofile: string

    Returns ISOInfo

  • isoinfoDevice(device: string): ISOInfo
  • get ISO information from primary volume descriptor of device

    device is an ISO device. This returns a struct of information read from the primary volume descriptor (the ISO equivalent of the superblock) of the device.

    Usually it is more efficient to use the isoinfo(1) command with the -d option on the host to analyze ISO files, instead of going through libguestfs.

    For information on the primary volume descriptor fields, see http://wiki.osdev.org/ISO_9660#The_Primary_Volume_Descriptor

    Parameters

    • device: string

    Returns ISOInfo

  • journalClose(): boolean
  • close the systemd journal

    Close the journal handle.

    This function depends on the feature "journal". See also guestfs_session_feature_available().

    Returns boolean

  • read the current journal entry

    Read the current journal entry. This returns all the fields in the journal as a set of "(attrname, attrval)" pairs. The attrname is the field name (a string).

    The attrval is the field value (a binary blob, often but not always a string). Please note that attrval is a byte array, not a \0-terminated C string.

    The length of data may be truncated to the data threshold (see: guestfs_session_journal_set_data_threshold(), guestfs_session_journal_get_data_threshold()).

    If you set the data threshold to unlimited (0) then this call can read a journal entry of any size, ie. it is not limited by the libguestfs protocol.

    This function depends on the feature "journal". See also guestfs_session_feature_available().

    Returns XAttr[]

  • journalGetDataThreshold(): number
  • get the data threshold for reading journal entries

    Get the current data threshold for reading journal entries. This is a hint to the journal that it may truncate data fields to this size when reading them (note also that it may not truncate them). If this returns 0, then the threshold is unlimited.

    See also guestfs_session_journal_set_data_threshold().

    This function depends on the feature "journal". See also guestfs_session_feature_available().

    Returns number

  • journalGetRealtimeUsec(): number
  • get the timestamp of the current journal entry

    Get the realtime (wallclock) timestamp of the current journal entry.

    This function depends on the feature "journal". See also guestfs_session_feature_available().

    Returns number

  • journalNext(): number
  • move to the next journal entry

    Move to the next journal entry. You have to call this at least once after opening the handle before you are able to read data.

    The returned boolean tells you if there are any more journal records to read. true means you can read the next record (eg. using guestfs_session_journal_get()), and false means you have reached the end of the journal.

    This function depends on the feature "journal". See also guestfs_session_feature_available().

    Returns number

  • journalOpen(directory: string): boolean
  • open the systemd journal

    Open the systemd journal located in directory. Any previously opened journal handle is closed.

    The contents of the journal can be read using guestfs_session_journal_next() and guestfs_session_journal_get().

    After you have finished using the journal, you should close the handle by calling guestfs_session_journal_close().

    This function depends on the feature "journal". See also guestfs_session_feature_available().

    Parameters

    • directory: string

    Returns boolean

  • journalSetDataThreshold(threshold: number): boolean
  • set the data threshold for reading journal entries

    Set the data threshold for reading journal entries. This is a hint to the journal that it may truncate data fields to this size when reading them (note also that it may not truncate them). If you set this to 0, then the threshold is unlimited.

    See also guestfs_session_journal_get_data_threshold().

    This function depends on the feature "journal". See also guestfs_session_feature_available().

    Parameters

    • threshold: number

    Returns boolean

  • journalSkip(skip: number): number
  • skip forwards or backwards in the journal

    Skip forwards ("skip ≥ 0") or backwards ("skip < 0") in the journal.

    The number of entries actually skipped is returned (note "rskip ≥ 0"). If this is not the same as the absolute value of the skip parameter ("|skip|") you passed in then it means you have reached the end or the start of the journal.

    This function depends on the feature "journal". See also guestfs_session_feature_available().

    Parameters

    • skip: number

    Returns number

  • killSubprocess(): boolean
  • kill the hypervisor

    This kills the hypervisor.

    Do not call this. See: guestfs_session_shutdown() instead.

    Returns boolean

  • launch(): boolean
  • launch the backend

    You should call this after configuring the handle (eg. adding drives) but before performing any actions.

    Do not call guestfs_session_launch() twice on the same handle. Although it will not give an error (for historical reasons), the precise behaviour when you do this is not well defined. Handles are very cheap to create, so create a new one for each launch.

    Returns boolean

  • lchown(owner: number, group: number, path: string): boolean
  • change file owner and group

    Change the file owner to owner and group to group. This is like guestfs_session_chown() but if path is a symlink then the link itself is changed, not the target.

    Only numeric uid and gid are supported. If you want to use names, you will need to locate and parse the password file yourself (Augeas support makes this relatively easy).

    Parameters

    • owner: number
    • group: number
    • path: string

    Returns boolean

  • ldmtoolCreateAll(): boolean
  • scan and create Windows dynamic disk volumes

    This function scans all block devices looking for Windows dynamic disk volumes and partitions, and creates devices for any that were found.

    Call guestfs_session_list_ldm_volumes() and guestfs_session_list_ldm_partitions() to return all devices.

    Note that you don't normally need to call this explicitly, since it is done automatically at guestfs_session_launch() time. However you might want to call this function if you have hotplugged disks or have just created a Windows dynamic disk.

    This function depends on the feature "ldm". See also guestfs_session_feature_available().

    Returns boolean

  • ldmtoolDiskgroupDisks(diskgroup: string): string[]
  • return the disks in a Windows dynamic disk group

    Return the disks in a Windows dynamic disk group. The diskgroup parameter should be the GUID of a disk group, one element from the list returned by guestfs_session_ldmtool_scan().

    This function depends on the feature "ldm". See also guestfs_session_feature_available().

    Parameters

    • diskgroup: string

    Returns string[]

  • ldmtoolDiskgroupName(diskgroup: string): string
  • return the name of a Windows dynamic disk group

    Return the name of a Windows dynamic disk group. The diskgroup parameter should be the GUID of a disk group, one element from the list returned by guestfs_session_ldmtool_scan().

    This function depends on the feature "ldm". See also guestfs_session_feature_available().

    Parameters

    • diskgroup: string

    Returns string

  • ldmtoolDiskgroupVolumes(diskgroup: string): string[]
  • return the volumes in a Windows dynamic disk group

    Return the volumes in a Windows dynamic disk group. The diskgroup parameter should be the GUID of a disk group, one element from the list returned by guestfs_session_ldmtool_scan().

    This function depends on the feature "ldm". See also guestfs_session_feature_available().

    Parameters

    • diskgroup: string

    Returns string[]

  • ldmtoolRemoveAll(): boolean
  • remove all Windows dynamic disk volumes

    This is essentially the opposite of guestfs_session_ldmtool_create_all(). It removes the device mapper mappings for all Windows dynamic disk volumes

    This function depends on the feature "ldm". See also guestfs_session_feature_available().

    Returns boolean

  • ldmtoolScan(): string[]
  • scan for Windows dynamic disks

    This function scans for Windows dynamic disks. It returns a list of identifiers (GUIDs) for all disk groups that were found. These identifiers can be passed to other "guestfs_ldmtool_*" functions.

    This function scans all block devices. To scan a subset of block devices, call guestfs_session_ldmtool_scan_devices() instead.

    This function depends on the feature "ldm". See also guestfs_session_feature_available().

    Returns string[]

  • ldmtoolScanDevices(devices: string[]): string[]
  • scan for Windows dynamic disks

    This function scans for Windows dynamic disks. It returns a list of identifiers (GUIDs) for all disk groups that were found. These identifiers can be passed to other "guestfs_ldmtool_*" functions.

    The parameter devices is a list of block devices which are scanned. If this list is empty, all block devices are scanned.

    This function depends on the feature "ldm". See also guestfs_session_feature_available().

    Parameters

    • devices: string[]

      an array of strings

    Returns string[]

  • ldmtoolVolumeHint(diskgroup: string, volume: string): string
  • return the hint field of a Windows dynamic disk volume

    Return the hint field of the volume named volume in the disk group with GUID diskgroup. This may not be defined, in which case the empty string is returned. The hint field is often, though not always, the name of a Windows drive, eg. "E:".

    This function depends on the feature "ldm". See also guestfs_session_feature_available().

    Parameters

    • diskgroup: string
    • volume: string

    Returns string

  • ldmtoolVolumePartitions(diskgroup: string, volume: string): string[]
  • return the partitions in a Windows dynamic disk volume

    Return the list of partitions in the volume named volume in the disk group with GUID diskgroup.

    This function depends on the feature "ldm". See also guestfs_session_feature_available().

    Parameters

    • diskgroup: string
    • volume: string

    Returns string[]

  • ldmtoolVolumeType(diskgroup: string, volume: string): string
  • return the type of a Windows dynamic disk volume

    Return the type of the volume named volume in the disk group with GUID diskgroup.

    Possible volume types that can be returned here include: simple, spanned, striped, mirrored, raid5. Other types may also be returned.

    This function depends on the feature "ldm". See also guestfs_session_feature_available().

    Parameters

    • diskgroup: string
    • volume: string

    Returns string

  • lgetxattr(path: string, name: string): Uint8Array
  • get a single extended attribute

    Get a single extended attribute from file path named name. If path is a symlink, then this call returns an extended attribute from the symlink.

    Normally it is better to get all extended attributes from a file in one go by calling guestfs_session_getxattrs(). However some Linux filesystem implementations are buggy and do not provide a way to list out attributes. For these filesystems (notably ntfs-3g) you have to know the names of the extended attributes you want in advance and call this function.

    Extended attribute values are blobs of binary data. If there is no extended attribute named name, this returns an error.

    See also: guestfs_session_lgetxattrs(), guestfs_session_getxattr(), attr(5).

    This function depends on the feature "linuxxattrs". See also guestfs_session_feature_available().

    Parameters

    • path: string
    • name: string

    Returns Uint8Array

  • lgetxattrs(path: string): XAttr[]
  • list extended attributes of a file or directory

    This is the same as guestfs_session_getxattrs(), but if path is a symbolic link, then it returns the extended attributes of the link itself.

    This function depends on the feature "linuxxattrs". See also guestfs_session_feature_available().

    Parameters

    • path: string

    Returns XAttr[]

  • list9p(): string[]
  • list 9p filesystems

    List all 9p filesystems attached to the guest. A list of mount tags is returned.

    Returns string[]

  • listDevices(): string[]
  • list the block devices

    List all the block devices.

    The full block device names are returned, eg. /dev/sda.

    See also guestfs_session_list_filesystems().

    Returns string[]

  • listDiskLabels(): HashTable<string | number | symbol, string | number | boolean>
  • mapping of disk labels to devices

    If you add drives using the optional label parameter of guestfs_session_add_drive_opts(), you can use this call to map between disk labels, and raw block device and partition names (like /dev/sda and /dev/sda1).

    This returns a hashtable, where keys are the disk labels (without the /dev/disk/guestfs prefix), and the values are the full raw block device and partition names (eg. /dev/sda and /dev/sda1).

    Returns HashTable<string | number | symbol, string | number | boolean>

  • listDmDevices(): string[]
  • list device mapper devices

    List all device mapper devices.

    The returned list contains /dev/mapper/* devices, eg. ones created by a previous call to guestfs_session_luks_open().

    Device mapper devices which correspond to logical volumes are not returned in this list. Call guestfs_session_lvs() if you want to list logical volumes.

    Returns string[]

  • listFilesystems(): HashTable<string | number | symbol, string | number | boolean>
  • list filesystems

    This inspection command looks for filesystems on partitions, block devices and logical volumes, returning a list of mountables containing filesystems and their type.

    The return value is a hash, where the keys are the devices containing filesystems, and the values are the filesystem types. For example:

    "ntfs"]]> "ext2"]]> "ext4"]]> "swap"]]>

    The key is not necessarily a block device. It may also be an opaque ‘mountable’ string which can be passed to guestfs_session_mount().

    The value can have the special value "unknown", meaning the content of the device is undetermined or empty. "swap" means a Linux swap partition.

    In libguestfs ≤ 1.36 this command ran other libguestfs commands, which might have included guestfs_session_mount() and guestfs_session_umount(), and therefore you had to use this soon after launch and only when nothing else was mounted. This restriction is removed in libguestfs ≥ 1.38.

    Not all of the filesystems returned will be mountable. In particular, swap partitions are returned in the list. Also this command does not check that each filesystem found is valid and mountable, and some filesystems might be mountable but require special options. Filesystems may not all belong to a single logical operating system (use guestfs_session_inspect_os() to look for OSes).

    Returns HashTable<string | number | symbol, string | number | boolean>

  • listLdmPartitions(): string[]
  • list all Windows dynamic disk partitions

    This function returns all Windows dynamic disk partitions that were found at launch time. It returns a list of device names.

    This function depends on the feature "ldm". See also guestfs_session_feature_available().

    Returns string[]

  • listLdmVolumes(): string[]
  • list all Windows dynamic disk volumes

    This function returns all Windows dynamic disk volumes that were found at launch time. It returns a list of device names.

    This function depends on the feature "ldm". See also guestfs_session_feature_available().

    Returns string[]

  • listMdDevices(): string[]
  • listPartitions(): string[]
  • list the partitions

    List all the partitions detected on all block devices.

    The full partition device names are returned, eg. /dev/sda1

    This does not return logical volumes. For that you will need to call guestfs_session_lvs().

    See also guestfs_session_list_filesystems().

    Returns string[]

  • ll(directory: string): string
  • list the files in a directory (long format)

    List the files in directory (relative to the root directory, there is no cwd) in the format of 'ls -la'.

    This command is mostly useful for interactive sessions. It is not intended that you try to parse the output string.

    Parameters

    • directory: string

    Returns string

  • llz(directory: string): string
  • list the files in a directory (long format with SELinux contexts)

    List the files in directory in the format of 'ls -laZ'.

    This command is mostly useful for interactive sessions. It is not intended that you try to parse the output string.

    Parameters

    • directory: string

    Returns string

  • ln(target: string, linkname: string): boolean
  • create a hard link

    This command creates a hard link using the ln command.

    Parameters

    • target: string
    • linkname: string

    Returns boolean

  • lnF(target: string, linkname: string): boolean
  • create a hard link

    This command creates a hard link using the "ln -f" command. The -f option removes the link (linkname) if it exists already.

    Parameters

    • target: string
    • linkname: string

    Returns boolean

  • lnS(target: string, linkname: string): boolean
  • create a symbolic link

    This command creates a symbolic link using the "ln -s" command.

    Parameters

    • target: string
    • linkname: string

    Returns boolean

  • lnSf(target: string, linkname: string): boolean
  • create a symbolic link

    This command creates a symbolic link using the "ln -sf" command, The -f option removes the link (linkname) if it exists already.

    Parameters

    • target: string
    • linkname: string

    Returns boolean

  • lremovexattr(xattr: string, path: string): boolean
  • remove extended attribute of a file or directory

    This is the same as guestfs_session_removexattr(), but if path is a symbolic link, then it removes an extended attribute of the link itself.

    This function depends on the feature "linuxxattrs". See also guestfs_session_feature_available().

    Parameters

    • xattr: string
    • path: string

    Returns boolean

  • ls(directory: string): string[]
  • list the files in a directory

    List the files in directory (relative to the root directory, there is no cwd). The '.' and '..' entries are not returned, but hidden files are shown.

    Parameters

    • directory: string

    Returns string[]

  • ls0(dir: string, filenames: string): boolean
  • get list of files in a directory

    This specialized command is used to get a listing of the filenames in the directory dir. The list of filenames is written to the local file filenames (on the host).

    In the output file, the filenames are separated by "\0" characters.

    "." and ".." are not returned. The filenames are not sorted.

    Parameters

    • dir: string
    • filenames: string

    Returns boolean

  • lsetxattr(xattr: string, val: string, vallen: number, path: string): boolean
  • set extended attribute of a file or directory

    This is the same as guestfs_session_setxattr(), but if path is a symbolic link, then it sets an extended attribute of the link itself.

    This function depends on the feature "linuxxattrs". See also guestfs_session_feature_available().

    Parameters

    • xattr: string
    • val: string
    • vallen: number
    • path: string

    Returns boolean

  • lstat(path: string): Stat
  • get file information for a symbolic link

    Returns file information for the given path.

    This is the same as guestfs_session_stat() except that if path is a symbolic link, then the link is stat-ed, not the file it refers to.

    This is the same as the lstat(2) system call.

    Parameters

    • path: string

    Returns Stat

  • lstatlist(path: string, names: string[]): Stat[]
  • lstat on multiple files

    This call allows you to perform the guestfs_session_lstat() operation on multiple files, where all files are in the directory path. names is the list of files from this directory.

    On return you get a list of stat structs, with a one-to-one correspondence to the names list. If any name did not exist or could not be lstat'd, then the st_ino field of that structure is set to -1.

    This call is intended for programs that want to efficiently list a directory contents without making many round-trips. See also guestfs_session_lxattrlist() for a similarly efficient call for getting extended attributes.

    Parameters

    • path: string
    • names: string[]

      an array of strings

    Returns Stat[]

  • get file information for a symbolic link

    Returns file information for the given path.

    This is the same as guestfs_session_statns() except that if path is a symbolic link, then the link is stat-ed, not the file it refers to.

    This is the same as the lstat(2) system call.

    Parameters

    • path: string

    Returns StatNS

  • lstatnslist(path: string, names: string[]): StatNS[]
  • lstat on multiple files

    This call allows you to perform the guestfs_session_lstatns() operation on multiple files, where all files are in the directory path. names is the list of files from this directory.

    On return you get a list of stat structs, with a one-to-one correspondence to the names list. If any name did not exist or could not be lstat'd, then the st_ino field of that structure is set to -1.

    This call is intended for programs that want to efficiently list a directory contents without making many round-trips. See also guestfs_session_lxattrlist() for a similarly efficient call for getting extended attributes.

    Parameters

    • path: string
    • names: string[]

      an array of strings

    Returns StatNS[]

  • luksAddKey(device: string, key: string, newkey: string, keyslot: number): boolean
  • add a key on a LUKS encrypted device

    This command adds a new key on LUKS device device. key is any existing key, and is used to access the device. newkey is the new key to add. keyslot is the key slot that will be replaced.

    Note that if keyslot already contains a key, then this command will fail. You have to use guestfs_session_luks_kill_slot() first to remove that key.

    This function depends on the feature "luks". See also guestfs_session_feature_available().

    Parameters

    • device: string
    • key: string
    • newkey: string
    • keyslot: number

    Returns boolean

  • luksClose(device: string): boolean
  • close a LUKS device

    This closes a LUKS device that was created earlier by guestfs_session_luks_open() or guestfs_session_luks_open_ro(). The device parameter must be the name of the LUKS mapping device (ie. /dev/mapper/mapname) and not the name of the underlying block device.

    This function depends on the feature "luks". See also guestfs_session_feature_available().

    Parameters

    • device: string

    Returns boolean

  • luksFormat(device: string, key: string, keyslot: number): boolean
  • format a block device as a LUKS encrypted device

    This command erases existing data on device and formats the device as a LUKS encrypted device. key is the initial key, which is added to key slot slot. (LUKS supports 8 key slots, numbered 0-7).

    This function depends on the feature "luks". See also guestfs_session_feature_available().

    Parameters

    • device: string
    • key: string
    • keyslot: number

    Returns boolean

  • luksFormatCipher(device: string, key: string, keyslot: number, cipher: string): boolean
  • format a block device as a LUKS encrypted device

    This command is the same as guestfs_session_luks_format() but it also allows you to set the cipher used.

    This function depends on the feature "luks". See also guestfs_session_feature_available().

    Parameters

    • device: string
    • key: string
    • keyslot: number
    • cipher: string

    Returns boolean

  • luksKillSlot(device: string, key: string, keyslot: number): boolean
  • remove a key from a LUKS encrypted device

    This command deletes the key in key slot keyslot from the encrypted LUKS device device. key must be one of the other keys.

    This function depends on the feature "luks". See also guestfs_session_feature_available().

    Parameters

    • device: string
    • key: string
    • keyslot: number

    Returns boolean

  • luksOpen(device: string, key: string, mapname: string): boolean
  • open a LUKS-encrypted block device

    This command opens a block device which has been encrypted according to the Linux Unified Key Setup (LUKS) standard.

    device is the encrypted block device or partition.

    The caller must supply one of the keys associated with the LUKS block device, in the key parameter.

    This creates a new block device called /dev/mapper/mapname. Reads and writes to this block device are decrypted from and encrypted to the underlying device respectively.

    If this block device contains LVM volume groups, then calling guestfs_session_lvm_scan() with the activate parameter true will make them visible.

    Use guestfs_session_list_dm_devices() to list all device mapper devices.

    This function depends on the feature "luks". See also guestfs_session_feature_available().

    Parameters

    • device: string
    • key: string
    • mapname: string

    Returns boolean

  • luksOpenRo(device: string, key: string, mapname: string): boolean
  • open a LUKS-encrypted block device read-only

    This is the same as guestfs_session_luks_open() except that a read-only mapping is created.

    This function depends on the feature "luks". See also guestfs_session_feature_available().

    Parameters

    • device: string
    • key: string
    • mapname: string

    Returns boolean

  • lvcreate(logvol: string, volgroup: string, mbytes: number): boolean
  • create an LVM logical volume

    This creates an LVM logical volume called logvol on the volume group volgroup, with size megabytes.

    This function depends on the feature "lvm2". See also guestfs_session_feature_available().

    Parameters

    • logvol: string
    • volgroup: string
    • mbytes: number

    Returns boolean

  • lvcreateFree(logvol: string, volgroup: string, percent: number): boolean
  • create an LVM logical volume in % remaining free space

    Create an LVM logical volume called /dev/volgroup/logvol, using approximately percent % of the free space remaining in the volume group. Most usefully, when percent is 100 this will create the largest possible LV.

    This function depends on the feature "lvm2". See also guestfs_session_feature_available().

    Parameters

    • logvol: string
    • volgroup: string
    • percent: number

    Returns boolean

  • lvmCanonicalLvName(lvname: string): string
  • get canonical name of an LV

    This converts alternative naming schemes for LVs that you might find to the canonical name. For example, /dev/mapper/VG-LV is converted to /dev/VG/LV.

    This command returns an error if the lvname parameter does not refer to a logical volume.

    See also guestfs_session_is_lv(), guestfs_session_canonical_device_name().

    Parameters

    • lvname: string

    Returns string

  • lvmClearFilter(): boolean
  • clear LVM device filter

    This undoes the effect of guestfs_session_lvm_set_filter(). LVM will be able to see every block device.

    This command also clears the LVM cache and performs a volume group scan.

    Returns boolean

  • lvmRemoveAll(): boolean
  • remove all LVM LVs, VGs and PVs

    This command removes all LVM logical volumes, volume groups and physical volumes.

    This function depends on the feature "lvm2". See also guestfs_session_feature_available().

    Returns boolean

  • lvmScan(activate: boolean): boolean
  • scan for LVM physical volumes, volume groups and logical volumes

    This scans all block devices and rebuilds the list of LVM physical volumes, volume groups and logical volumes.

    If the activate parameter is true then newly found volume groups and logical volumes are activated, meaning the LV /dev/VG/LV devices become visible.

    When a libguestfs handle is launched it scans for existing devices, so you do not normally need to use this API. However it is useful when you have added a new device or deleted an existing device (such as when the guestfs_session_luks_open() API is used).

    Parameters

    • activate: boolean

    Returns boolean

  • lvmSetFilter(devices: string[]): boolean
  • set LVM device filter

    This sets the LVM device filter so that LVM will only be able to "see" the block devices in the list devices, and will ignore all other attached block devices.

    Where disk image(s) contain duplicate PVs or VGs, this command is useful to get LVM to ignore the duplicates, otherwise LVM can get confused. Note also there are two types of duplication possible: either cloned PVs/VGs which have identical UUIDs; or VGs that are not cloned but just happen to have the same name. In normal operation you cannot create this situation, but you can do it outside LVM, eg. by cloning disk images or by bit twiddling inside the LVM metadata.

    This command also clears the LVM cache and performs a volume group scan.

    You can filter whole block devices or individual partitions.

    You cannot use this if any VG is currently in use (eg. contains a mounted filesystem), even if you are not filtering out that VG.

    This function depends on the feature "lvm2". See also guestfs_session_feature_available().

    Parameters

    • devices: string[]

      an array of strings

    Returns boolean

  • lvremove(device: string): boolean
  • remove an LVM logical volume

    Remove an LVM logical volume device, where device is the path to the LV, such as /dev/VG/LV.

    You can also remove all LVs in a volume group by specifying the VG name, /dev/VG.

    This function depends on the feature "lvm2". See also guestfs_session_feature_available().

    Parameters

    • device: string

    Returns boolean

  • lvrename(logvol: string, newlogvol: string): boolean
  • rename an LVM logical volume

    Rename a logical volume logvol with the new name newlogvol.

    Parameters

    • logvol: string
    • newlogvol: string

    Returns boolean

  • lvresize(device: string, mbytes: number): boolean
  • resize an LVM logical volume

    This resizes (expands or shrinks) an existing LVM logical volume to mbytes. When reducing, data in the reduced part is lost.

    This function depends on the feature "lvm2". See also guestfs_session_feature_available().

    Parameters

    • device: string
    • mbytes: number

    Returns boolean

  • lvresizeFree(lv: string, percent: number): boolean
  • expand an LV to fill free space

    This expands an existing logical volume lv so that it fills pc% of the remaining free space in the volume group. Commonly you would call this with pc = 100 which expands the logical volume as much as possible, using all remaining free space in the volume group.

    This function depends on the feature "lvm2". See also guestfs_session_feature_available().

    Parameters

    • lv: string
    • percent: number

    Returns boolean

  • lvs(): string[]
  • list the LVM logical volumes (LVs)

    List all the logical volumes detected. This is the equivalent of the lvs(8) command.

    This returns a list of the logical volume device names (eg. /dev/VolGroup00/LogVol00).

    See also guestfs_session_lvs_full(), guestfs_session_list_filesystems().

    This function depends on the feature "lvm2". See also guestfs_session_feature_available().

    Returns string[]

  • lvsFull(): LV[]
  • list the LVM logical volumes (LVs)

    List all the logical volumes detected. This is the equivalent of the lvs(8) command. The "full" version includes all fields.

    This function depends on the feature "lvm2". See also guestfs_session_feature_available().

    Returns LV[]

  • lvuuid(device: string): string
  • get the UUID of a logical volume

    This command returns the UUID of the LVM LV device.

    Parameters

    • device: string

    Returns string

  • lxattrlist(path: string, names: string[]): XAttr[]
  • lgetxattr on multiple files

    This call allows you to get the extended attributes of multiple files, where all files are in the directory path. names is the list of files from this directory.

    On return you get a flat list of xattr structs which must be interpreted sequentially. The first xattr struct always has a zero-length attrname. attrval in this struct is zero-length to indicate there was an error doing lgetxattr for this file, or is a C string which is a decimal number (the number of following attributes for this file, which could be "0"). Then after the first xattr struct are the zero or more attributes for the first named file. This repeats for the second and subsequent files.

    This call is intended for programs that want to efficiently list a directory contents without making many round-trips. See also guestfs_session_lstatlist() for a similarly efficient call for getting standard stats.

    This function depends on the feature "linuxxattrs". See also guestfs_session_feature_available().

    Parameters

    • path: string
    • names: string[]

      an array of strings

    Returns XAttr[]

  • maxDisks(): number
  • maximum number of disks that may be added

    Return the maximum number of disks that may be added to a handle (eg. by guestfs_session_add_drive_opts() and similar calls).

    This function was added in libguestfs 1.19.7. In previous versions of libguestfs the limit was 25.

    See "MAXIMUM NUMBER OF DISKS" in guestfs(3) for additional information on this topic.

    Returns number

  • mdCreate(name: string, devices: string[], optargs: MDCreate): boolean
  • create a Linux md (RAID) device

    Create a Linux md (RAID) device named name on the devices in the list devices.

    The optional parameters are:

    missingbitmap A bitmap of missing devices. If a bit is set it means that a missing device is added to the array. The least significant bit corresponds to the first device in the array.

    As examples:

    If "devices = ["/dev/sda"]" and "missingbitmap = 0x1" then the resulting array would be "[<missing>, "/dev/sda"]".

    If "devices = ["/dev/sda"]" and "missingbitmap = 0x2" then the resulting array would be "["/dev/sda", <missing>]".

    This defaults to 0 (no missing devices).

    The length of devices + the number of bits set in missingbitmap must equal nrdevices + spare.

    nrdevices The number of active RAID devices.

    If not set, this defaults to the length of devices plus the number of bits set in missingbitmap.

    spare The number of spare devices.

    If not set, this defaults to 0.

    chunk The chunk size in bytes.

    level The RAID level, which can be one of: linear, raid0, 0, stripe, raid1, 1, mirror, raid4, 4, raid5, 5, raid6, 6, raid10, 10. Some of these are synonymous, and more levels may be added in future.

    If not set, this defaults to raid1.

    This function depends on the feature "mdadm". See also guestfs_session_feature_available().

    Parameters

    • name: string
    • devices: string[]

      an array of strings

    • optargs: MDCreate

      a GuestfsMDCreate containing optional arguments

    Returns boolean

  • mdDetail(md: string): HashTable<string | number | symbol, string | number | boolean>
  • obtain metadata for an MD device

    This command exposes the output of 'mdadm -DY <md>'. The following fields are usually present in the returned hash. Other fields may also be present.

    level The raid level of the MD device.

    devices The number of underlying devices in the MD device.

    metadata The metadata version used.

    uuid The UUID of the MD device.

    name The name of the MD device.

    This function depends on the feature "mdadm". See also guestfs_session_feature_available().

    Parameters

    • md: string

    Returns HashTable<string | number | symbol, string | number | boolean>

  • get underlying devices from an MD device

    This call returns a list of the underlying devices which make up the single software RAID array device md.

    To get a list of software RAID devices, call guestfs_session_list_md_devices().

    Each structure returned corresponds to one device along with additional status information:

    mdstat_device The name of the underlying device.

    mdstat_index The index of this device within the array.

    mdstat_flags Flags associated with this device. This is a string containing (in no specific order) zero or more of the following flags:

    W write-mostly

    F device is faulty

    S device is a RAID spare

    R replacement

    This function depends on the feature "mdadm". See also guestfs_session_feature_available().

    Parameters

    • md: string

    Returns MDStat[]

  • mdStop(md: string): boolean
  • stop a Linux md (RAID) device

    This command deactivates the MD array named md. The device is stopped, but it is not destroyed or zeroed.

    This function depends on the feature "mdadm". See also guestfs_session_feature_available().

    Parameters

    • md: string

    Returns boolean

  • mkdir(path: string): boolean
  • create a directory

    Create a directory named path.

    Parameters

    • path: string

    Returns boolean

  • mkdirMode(path: string, mode: number): boolean
  • create a directory with a particular mode

    This command creates a directory, setting the initial permissions of the directory to mode.

    For common Linux filesystems, the actual mode which is set will be "mode & ~umask & 01777". Non-native-Linux filesystems may interpret the mode in other ways.

    See also guestfs_session_mkdir(), guestfs_session_umask()

    Parameters

    • path: string
    • mode: number

    Returns boolean

  • mkdirP(path: string): boolean
  • create a directory and parents

    Create a directory named path, creating any parent directories as necessary. This is like the "mkdir -p" shell command.

    Parameters

    • path: string

    Returns boolean

  • mkdtemp(tmpl: string): string
  • create a temporary directory

    This command creates a temporary directory. The tmpl parameter should be a full pathname for the temporary directory name with the final six characters being "XXXXXX".

    For example: "/tmp/myprogXXXXXX" or "/Temp/myprogXXXXXX", the second one being suitable for Windows filesystems.

    The name of the temporary directory that was created is returned.

    The temporary directory is created with mode 0700 and is owned by root.

    The caller is responsible for deleting the temporary directory and its contents after use.

    See also: mkdtemp(3)

    Parameters

    • tmpl: string

    Returns string

  • mke2fs(device: string, optargs: Mke2fs): boolean
  • create an ext2/ext3/ext4 filesystem on device

    mke2fs is used to create an ext2, ext3, or ext4 filesystem on device.

    The optional blockscount is the size of the filesystem in blocks. If omitted it defaults to the size of device. Note if the filesystem is too small to contain a journal, mke2fs will silently create an ext2 filesystem instead.

    Parameters

    • device: string
    • optargs: Mke2fs

      a GuestfsMke2fs containing optional arguments

    Returns boolean

  • mke2fsJ(fstype: string, blocksize: number, device: string, journal: string): boolean
  • make ext2/3/4 filesystem with external journal

    This creates an ext2/3/4 filesystem on device with an external journal on journal. It is equivalent to the command:

    ]]>

    See also guestfs_session_mke2journal().

    Parameters

    • fstype: string
    • blocksize: number
    • device: string
    • journal: string

    Returns boolean

  • mke2fsJL(fstype: string, blocksize: number, device: string, label: string): boolean
  • make ext2/3/4 filesystem with external journal

    This creates an ext2/3/4 filesystem on device with an external journal on the journal labeled label.

    See also guestfs_session_mke2journal_L().

    Parameters

    • fstype: string
    • blocksize: number
    • device: string
    • label: string

    Returns boolean

  • mke2fsJU(fstype: string, blocksize: number, device: string, uuid: string): boolean
  • make ext2/3/4 filesystem with external journal

    This creates an ext2/3/4 filesystem on device with an external journal on the journal with UUID uuid.

    See also guestfs_session_mke2journal_U().

    This function depends on the feature "linuxfsuuid". See also guestfs_session_feature_available().

    Parameters

    • fstype: string
    • blocksize: number
    • device: string
    • uuid: string

    Returns boolean

  • mke2journal(blocksize: number, device: string): boolean
  • make ext2/3/4 external journal

    This creates an ext2 external journal on device. It is equivalent to the command:

    Parameters

    • blocksize: number
    • device: string

    Returns boolean

  • mke2journalL(blocksize: number, label: string, device: string): boolean
  • make ext2/3/4 external journal with label

    This creates an ext2 external journal on device with label label.

    Parameters

    • blocksize: number
    • label: string
    • device: string

    Returns boolean

  • mke2journalU(blocksize: number, uuid: string, device: string): boolean
  • make ext2/3/4 external journal with UUID

    This creates an ext2 external journal on device with UUID uuid.

    This function depends on the feature "linuxfsuuid". See also guestfs_session_feature_available().

    Parameters

    • blocksize: number
    • uuid: string
    • device: string

    Returns boolean

  • mkfifo(mode: number, path: string): boolean
  • make FIFO (named pipe)

    This call creates a FIFO (named pipe) called path with mode mode. It is just a convenient wrapper around guestfs_session_mknod().

    Unlike with guestfs_session_mknod(), mode must contain only permissions bits.

    The mode actually set is affected by the umask.

    This function depends on the feature "mknod". See also guestfs_session_feature_available().

    Parameters

    • mode: number
    • path: string

    Returns boolean

  • mkfs(fstype: string, device: string, optargs: Mkfs): boolean
  • make a filesystem

    This function creates a filesystem on device. The filesystem type is fstype, for example ext3.

    The optional arguments are:

    blocksize The filesystem block size. Supported block sizes depend on the filesystem type, but typically they are 1024, 2048 or 4096 for Linux ext2/3 filesystems.

    For VFAT and NTFS the blocksize parameter is treated as the requested cluster size.

    For UFS block sizes, please see mkfs.ufs(8).

    features This passes the -O parameter to the external mkfs program.

    For certain filesystem types, this allows extra filesystem features to be selected. See mke2fs(8) and mkfs.ufs(8) for more details.

    You cannot use this optional parameter with the gfs or gfs2 filesystem type.

    inode This passes the -I parameter to the external mke2fs(8) program which sets the inode size (only for ext2/3/4 filesystems at present).

    sectorsize This passes the -S parameter to external mkfs.ufs(8) program, which sets sector size for ufs filesystem.

    Parameters

    • fstype: string
    • device: string
    • optargs: Mkfs

      a GuestfsMkfs containing optional arguments

    Returns boolean

  • mkfsB(fstype: string, blocksize: number, device: string): boolean
  • make a filesystem with block size

    This call is similar to guestfs_session_mkfs(), but it allows you to control the block size of the resulting filesystem. Supported block sizes depend on the filesystem type, but typically they are 1024, 2048 or 4096 only.

    For VFAT and NTFS the blocksize parameter is treated as the requested cluster size.

    Parameters

    • fstype: string
    • blocksize: number
    • device: string

    Returns boolean

  • mkfsBtrfs(devices: string[], optargs: MkfsBtrfs): boolean
  • create a btrfs filesystem

    Create a btrfs filesystem, allowing all configurables to be set. For more information on the optional arguments, see mkfs.btrfs(8).

    Since btrfs filesystems can span multiple devices, this takes a non-empty list of devices.

    To create general filesystems, use guestfs_session_mkfs().

    This function depends on the feature "btrfs". See also guestfs_session_feature_available().

    Parameters

    • devices: string[]

      an array of strings

    • optargs: MkfsBtrfs

      a GuestfsMkfsBtrfs containing optional arguments

    Returns boolean

  • mklostAndFound(mountpoint: string): boolean
  • make lost+found directory on an ext2/3/4 filesystem

    Make the "lost+found" directory, normally in the root directory of an ext2/3/4 filesystem. mountpoint is the directory under which we try to create the "lost+found" directory.

    Parameters

    • mountpoint: string

    Returns boolean

  • mkmountpoint(exemptpath: string): boolean
  • create a mountpoint

    guestfs_session_mkmountpoint() and guestfs_session_rmmountpoint() are specialized calls that can be used to create extra mountpoints before mounting the first filesystem.

    These calls are only necessary in some very limited circumstances, mainly the case where you want to mount a mix of unrelated and/or read-only filesystems together.

    For example, live CDs often contain a "Russian doll" nest of filesystems, an ISO outer layer, with a squashfs image inside, with an ext2/3 image inside that. You can unpack this as follows in guestfish:

    The inner filesystem is now unpacked under the /ext3fs mountpoint.

    guestfs_session_mkmountpoint() is not compatible with guestfs_session_umount_all(). You may get unexpected errors if you try to mix these calls. It is safest to manually unmount filesystems and remove mountpoints after use.

    guestfs_session_umount_all() unmounts filesystems by sorting the paths longest first, so for this to work for manual mountpoints, you must ensure that the innermost mountpoints have the longest pathnames, as in the example code above.

    For more details see http://bugzilla.redhat.com/show_bug.cgi?id=599503

    Autosync [see guestfs_session_set_autosync(), this is set by default on handles] can cause guestfs_session_umount_all() to be called when the handle is closed which can also trigger these issues.

    Parameters

    • exemptpath: string

    Returns boolean

  • mknod(mode: number, devmajor: number, devminor: number, path: string): boolean
  • make block, character or FIFO devices

    This call creates block or character special devices, or named pipes (FIFOs).

    The mode parameter should be the mode, using the standard constants. devmajor and devminor are the device major and minor numbers, only used when creating block and character special devices.

    Note that, just like mknod(2), the mode must be bitwise OR'd with S_IFBLK, S_IFCHR, S_IFIFO or S_IFSOCK (otherwise this call just creates a regular file). These constants are available in the standard Linux header files, or you can use guestfs_session_mknod_b(), guestfs_session_mknod_c() or guestfs_session_mkfifo() which are wrappers around this command which bitwise OR in the appropriate constant for you.

    The mode actually set is affected by the umask.

    This function depends on the feature "mknod". See also guestfs_session_feature_available().

    Parameters

    • mode: number
    • devmajor: number
    • devminor: number
    • path: string

    Returns boolean

  • mknodB(mode: number, devmajor: number, devminor: number, path: string): boolean
  • make block device node

    This call creates a block device node called path with mode mode and device major/minor devmajor and devminor. It is just a convenient wrapper around guestfs_session_mknod().

    Unlike with guestfs_session_mknod(), mode must contain only permissions bits.

    The mode actually set is affected by the umask.

    This function depends on the feature "mknod". See also guestfs_session_feature_available().

    Parameters

    • mode: number
    • devmajor: number
    • devminor: number
    • path: string

    Returns boolean

  • mknodC(mode: number, devmajor: number, devminor: number, path: string): boolean
  • make char device node

    This call creates a char device node called path with mode mode and device major/minor devmajor and devminor. It is just a convenient wrapper around guestfs_session_mknod().

    Unlike with guestfs_session_mknod(), mode must contain only permissions bits.

    The mode actually set is affected by the umask.

    This function depends on the feature "mknod". See also guestfs_session_feature_available().

    Parameters

    • mode: number
    • devmajor: number
    • devminor: number
    • path: string

    Returns boolean

  • create a squashfs filesystem

    Create a squashfs filesystem for the specified path.

    The optional compress flag controls compression. If not given, then the output compressed using gzip. Otherwise one of the following strings may be given to select the compression type of the squashfs: gzip, lzma, lzo, lz4, xz.

    The other optional arguments are:

    excludes A list of wildcards. Files are excluded if they match any of the wildcards.

    Please note that this API may fail when used to compress directories with large files, such as the resulting squashfs will be over 3GB big.

    This function depends on the feature "squashfs". See also guestfs_session_feature_available().

    Parameters

    • path: string
    • filename: string
    • optargs: Mksquashfs

      a GuestfsMksquashfs containing optional arguments

    • cancellable: Gio.Cancellable

      A GCancellable object

    Returns boolean

  • mkswap(device: string, optargs: Mkswap): boolean
  • create a swap partition

    Create a Linux swap partition on device.

    The option arguments label and uuid allow you to set the label and/or UUID of the new swap partition.

    Parameters

    • device: string
    • optargs: Mkswap

      a GuestfsMkswap containing optional arguments

    Returns boolean

  • mkswapFile(path: string): boolean
  • create a swap file

    Create a swap file.

    This command just writes a swap file signature to an existing file. To create the file itself, use something like guestfs_session_fallocate().

    Parameters

    • path: string

    Returns boolean

  • mkswapL(label: string, device: string): boolean
  • create a swap partition with a label

    Create a swap partition on device with label label.

    Note that you cannot attach a swap label to a block device (eg. /dev/sda), just to a partition. This appears to be a limitation of the kernel or swap tools.

    Parameters

    • label: string
    • device: string

    Returns boolean

  • mkswapU(uuid: string, device: string): boolean
  • create a swap partition with an explicit UUID

    Create a swap partition on device with UUID uuid.

    This function depends on the feature "linuxfsuuid". See also guestfs_session_feature_available().

    Parameters

    • uuid: string
    • device: string

    Returns boolean

  • mktemp(tmpl: string, optargs: Mktemp): string
  • create a temporary file

    This command creates a temporary file. The tmpl parameter should be a full pathname for the temporary directory name with the final six characters being "XXXXXX".

    For example: "/tmp/myprogXXXXXX" or "/Temp/myprogXXXXXX", the second one being suitable for Windows filesystems.

    The name of the temporary file that was created is returned.

    The temporary file is created with mode 0600 and is owned by root.

    The caller is responsible for deleting the temporary file after use.

    If the optional suffix parameter is given, then the suffix (eg. ".txt") is appended to the temporary name.

    See also: guestfs_session_mkdtemp().

    Parameters

    • tmpl: string
    • optargs: Mktemp

      a GuestfsMktemp containing optional arguments

    Returns string

  • modprobe(modulename: string): boolean
  • load a kernel module

    This loads a kernel module in the appliance.

    This function depends on the feature "linuxmodules". See also guestfs_session_feature_available().

    Parameters

    • modulename: string

    Returns boolean

  • mount(mountable: string, mountpoint: string): boolean
  • mount a guest disk at a position in the filesystem

    Mount a guest disk at a position in the filesystem. Block devices are named /dev/sda, /dev/sdb and so on, as they were added to the guest. If those block devices contain partitions, they will have the usual names (eg. /dev/sda1). Also LVM /dev/VG/LV-style names can be used, or ‘mountable’ strings returned by guestfs_session_list_filesystems() or guestfs_session_inspect_get_mountpoints().

    The rules are the same as for mount(2): A filesystem must first be mounted on / before others can be mounted. Other filesystems can only be mounted on directories which already exist.

    The mounted filesystem is writable, if we have sufficient permissions on the underlying device.

    Before libguestfs 1.13.16, this call implicitly added the options sync and noatime. The sync option greatly slowed writes and caused many problems for users. If your program might need to work with older versions of libguestfs, use guestfs_session_mount_options() instead (using an empty string for the first parameter if you don't want any options).

    Parameters

    • mountable: string
    • mountpoint: string

    Returns boolean

  • mount9p(mounttag: string, mountpoint: string, optargs: Mount9P): boolean
  • mount 9p filesystem

    Mount the virtio-9p filesystem with the tag mounttag on the directory mountpoint.

    If required, "trans=virtio" will be automatically added to the options. Any other options required can be passed in the optional options parameter.

    Parameters

    • mounttag: string
    • mountpoint: string
    • optargs: Mount9P

      a GuestfsMount9P containing optional arguments

    Returns boolean

  • mountLocal(localmountpoint: string, optargs: MountLocal): boolean
  • mount on the local filesystem

    This call exports the libguestfs-accessible filesystem to a local mountpoint (directory) called localmountpoint. Ordinary reads and writes to files and directories under localmountpoint are redirected through libguestfs.

    If the optional readonly flag is set to true, then writes to the filesystem return error EROFS.

    options is a comma-separated list of mount options. See guestmount(1) for some useful options.

    cachetimeout sets the timeout (in seconds) for cached directory entries. The default is 60 seconds. See guestmount(1) for further information.

    If debugcalls is set to true, then additional debugging information is generated for every FUSE call.

    When guestfs_session_mount_local() returns, the filesystem is ready, but is not processing requests (access to it will block). You have to call guestfs_session_mount_local_run() to run the main loop.

    See "MOUNT LOCAL" in guestfs(3) for full documentation.

    Parameters

    • localmountpoint: string
    • optargs: MountLocal

      a GuestfsMountLocal containing optional arguments

    Returns boolean

  • run main loop of mount on the local filesystem

    Run the main loop which translates kernel calls to libguestfs calls.

    This should only be called after guestfs_session_mount_local() returns successfully. The call will not return until the filesystem is unmounted.

    Note you must not make concurrent libguestfs calls on the same handle from another thread.

    You may call this from a different thread than the one which called guestfs_session_mount_local(), subject to the usual rules for threads and libguestfs (see "MULTIPLE HANDLES AND MULTIPLE THREADS" in guestfs(3)).

    See "MOUNT LOCAL" in guestfs(3) for full documentation.

    Parameters

    Returns boolean

  • mountLoop(file: string, mountpoint: string): boolean
  • mount a file using the loop device

    This command lets you mount file (a filesystem image in a file) on a mount point. It is entirely equivalent to the command "mount -o loop file mountpoint".

    Parameters

    • file: string
    • mountpoint: string

    Returns boolean

  • mountOptions(options: string, mountable: string, mountpoint: string): boolean
  • mount a guest disk with mount options

    This is the same as the guestfs_session_mount() command, but it allows you to set the mount options as for the mount(8) -o flag.

    If the options parameter is an empty string, then no options are passed (all options default to whatever the filesystem uses).

    Parameters

    • options: string
    • mountable: string
    • mountpoint: string

    Returns boolean

  • mountRo(mountable: string, mountpoint: string): boolean
  • mount a guest disk, read-only

    This is the same as the guestfs_session_mount() command, but it mounts the filesystem with the read-only (-o ro) flag.

    Parameters

    • mountable: string
    • mountpoint: string

    Returns boolean

  • mountVfs(options: string, vfstype: string, mountable: string, mountpoint: string): boolean
  • mount a guest disk with mount options and vfstype

    This is the same as the guestfs_session_mount() command, but it allows you to set both the mount options and the vfstype as for the mount(8) -o and -t flags.

    Parameters

    • options: string
    • vfstype: string
    • mountable: string
    • mountpoint: string

    Returns boolean

  • mountableDevice(mountable: string): string
  • extract the device part of a mountable

    Returns the device name of a mountable. In quite a lot of cases, the mountable is the device name.

    However this doesn't apply for btrfs subvolumes, where the mountable is a combination of both the device name and the subvolume path (see also guestfs_session_mountable_subvolume() to extract the subvolume path of the mountable if any).

    Parameters

    • mountable: string

    Returns string

  • mountableSubvolume(mountable: string): string
  • extract the subvolume part of a mountable

    Returns the subvolume path of a mountable. Btrfs subvolumes mountables are a combination of both the device name and the subvolume path (see also guestfs_session_mountable_device() to extract the device of the mountable).

    If the mountable does not represent a btrfs subvolume, then this function fails and the errno is set to EINVAL.

    Parameters

    • mountable: string

    Returns string

  • mountpoints(): HashTable<string | number | symbol, string | number | boolean>
  • show mountpoints

    This call is similar to guestfs_session_mounts(). That call returns a list of devices. This one returns a hash table (map) of device name to directory where the device is mounted.

    Returns HashTable<string | number | symbol, string | number | boolean>

  • mounts(): string[]
  • show mounted filesystems

    This returns the list of currently mounted filesystems. It returns the list of devices (eg. /dev/sda1, /dev/VG/LV).

    Some internal mounts are not shown.

    See also: guestfs_session_mountpoints()

    Returns string[]

  • mv(src: string, dest: string): boolean
  • move a file

    This moves a file from src to dest where dest is either a destination filename or destination directory.

    See also: guestfs_session_rename().

    Parameters

    • src: string
    • dest: string

    Returns boolean

  • notify(propertyName: string): void
  • Emits a "notify" signal for the property property_name on object.

    When possible, eg. when signaling a property change from within the class that registered the property, you should use g_object_notify_by_pspec() instead.

    Note that emission of the notify signal may be blocked with g_object_freeze_notify(). In this case, the signal emissions are queued and will be emitted (in reverse order) when g_object_thaw_notify() is called.

    Parameters

    • propertyName: string

      the name of a property installed on the class of object.

    Returns void

  • Emits a "notify" signal for the property specified by pspec on object.

    This function omits the property name lookup, hence it is faster than g_object_notify().

    One way to avoid using g_object_notify() from within the class that registered the properties, and using g_object_notify_by_pspec() instead, is to store the GParamSpec used with g_object_class_install_property() inside a static array, e.g.:

      enum
    {
    PROP_0,
    PROP_FOO,
    PROP_LAST
    };

    static GParamSpec *properties[PROP_LAST];

    static void
    my_object_class_init (MyObjectClass *klass)
    {
    properties[PROP_FOO] = g_param_spec_int ("foo", "Foo", "The foo",
    0, 100,
    50,
    G_PARAM_READWRITE);
    g_object_class_install_property (gobject_class,
    PROP_FOO,
    properties[PROP_FOO]);
    }

    and then notify a change on the "foo" property with:

      g_object_notify_by_pspec (self, properties[PROP_FOO]);
    

    Parameters

    • pspec: ParamSpec

      the #GParamSpec of a property installed on the class of object.

    Returns void

  • nrDevices(): number
  • return number of whole block devices (disks) added

    This returns the number of whole block devices that were added. This is the same as the number of devices that would be returned if you called guestfs_session_list_devices().

    To find out the maximum number of devices that could be added, call guestfs_session_max_disks().

    Returns number

  • ntfs3gProbe(rw: boolean, device: string): number
  • probe NTFS volume

    This command runs the ntfs-3g.probe(8) command which probes an NTFS device for mountability. (Not all NTFS volumes can be mounted read-write, and some cannot be mounted at all).

    rw is a boolean flag. Set it to true if you want to test if the volume can be mounted read-write. Set it to false if you want to test if the volume can be mounted read-only.

    The return value is an integer which 0 if the operation would succeed, or some non-zero value documented in the ntfs-3g.probe(8) manual page.

    This function depends on the feature "ntfs3g". See also guestfs_session_feature_available().

    Parameters

    • rw: boolean
    • device: string

    Returns number

  • ntfscatI(device: string, inode: number, filename: string, cancellable: Gio.Cancellable): boolean
  • download a file to the local machine given its inode

    Download a file given its inode from a NTFS filesystem and save it as filename on the local machine.

    This allows to download some otherwise inaccessible files such as the ones within the $Extend folder.

    The filesystem from which to extract the file must be unmounted, otherwise the call will fail.

    Parameters

    • device: string
    • inode: number
    • filename: string
    • cancellable: Gio.Cancellable

      A GCancellable object

    Returns boolean

  • ntfscloneIn(backupfile: string, device: string, cancellable: Gio.Cancellable): boolean
  • restore NTFS from backup file

    Restore the backupfile (from a previous call to guestfs_session_ntfsclone_out()) to device, overwriting any existing contents of this device.

    This function depends on the feature "ntfs3g". See also guestfs_session_feature_available().

    Parameters

    • backupfile: string
    • device: string
    • cancellable: Gio.Cancellable

      A GCancellable object

    Returns boolean

  • save NTFS to backup file

    Stream the NTFS filesystem device to the local file backupfile. The format used for the backup file is a special format used by the ntfsclone(8) tool.

    If the optional metadataonly flag is true, then only the metadata is saved, losing all the user data (this is useful for diagnosing some filesystem problems).

    The optional rescue, ignorefscheck, preservetimestamps and force flags have precise meanings detailed in the ntfsclone(8) man page.

    Use guestfs_session_ntfsclone_in() to restore the file back to a libguestfs device.

    This function depends on the feature "ntfs3g". See also guestfs_session_feature_available().

    Parameters

    • device: string
    • backupfile: string
    • optargs: NtfscloneOut

      a GuestfsNtfscloneOut containing optional arguments

    • cancellable: Gio.Cancellable

      A GCancellable object

    Returns boolean

  • ntfsfix(device: string, optargs: Ntfsfix): boolean
  • fix common errors and force Windows to check NTFS

    This command repairs some fundamental NTFS inconsistencies, resets the NTFS journal file, and schedules an NTFS consistency check for the first boot into Windows.

    This is not an equivalent of Windows chkdsk. It does not scan the filesystem for inconsistencies.

    The optional clearbadsectors flag clears the list of bad sectors. This is useful after cloning a disk with bad sectors to a new disk.

    This function depends on the feature "ntfs3g". See also guestfs_session_feature_available().

    Parameters

    • device: string
    • optargs: Ntfsfix

      a GuestfsNtfsfix containing optional arguments

    Returns boolean

  • resize an NTFS filesystem

    This command resizes an NTFS filesystem, expanding or shrinking it to the size of the underlying device.

    The optional parameters are:

    size The new size (in bytes) of the filesystem. If omitted, the filesystem is resized to fit the container (eg. partition).

    force If this option is true, then force the resize of the filesystem even if the filesystem is marked as requiring a consistency check.

    After the resize operation, the filesystem is always marked as requiring a consistency check (for safety). You have to boot into Windows to perform this check and clear this condition. If you don't set the force option then it is not possible to call guestfs_session_ntfsresize() multiple times on a single filesystem without booting into Windows between each resize.

    See also ntfsresize(8).

    This function depends on the feature "ntfsprogs". See also guestfs_session_feature_available().

    Parameters

    • device: string
    • optargs: NTFSResizeOpts

      a GuestfsNTFSResizeOpts containing optional arguments

    Returns boolean

  • ntfsresizeSize(device: string, size: number): boolean
  • resize an NTFS filesystem (with size)

    This command is the same as guestfs_session_ntfsresize() except that it allows you to specify the new size (in bytes) explicitly.

    This function depends on the feature "ntfsprogs". See also guestfs_session_feature_available().

    Parameters

    • device: string
    • size: number

    Returns boolean

  • parseEnvironment(): boolean
  • parse the environment and set handle flags accordingly

    Parse the program’s environment and set flags in the handle accordingly. For example if "LIBGUESTFS_DEBUG=1" then the ‘verbose’ flag is set in the handle.

    Most programs do not need to call this. It is done implicitly when you call guestfs_session_create().

    See "ENVIRONMENT VARIABLES" in guestfs(3) for a list of environment variables that can affect libguestfs handles. See also "guestfs_create_flags" in guestfs(3), and guestfs_session_parse_environment_list().

    Returns boolean

  • parseEnvironmentList(environment: string[]): boolean
  • parse the environment and set handle flags accordingly

    Parse the list of strings in the argument environment and set flags in the handle accordingly. For example if "LIBGUESTFS_DEBUG=1" is a string in the list, then the ‘verbose’ flag is set in the handle.

    This is the same as guestfs_session_parse_environment() except that it parses an explicit list of strings instead of the program's environment.

    Parameters

    • environment: string[]

      an array of strings

    Returns boolean

  • partAdd(device: string, prlogex: string, startsect: number, endsect: number): boolean
  • add a partition to the device

    This command adds a partition to device. If there is no partition table on the device, call guestfs_session_part_init() first.

    The prlogex parameter is the type of partition. Normally you should pass p or primary here, but MBR partition tables also support l (or logical) and e (or extended) partition types.

    startsect and endsect are the start and end of the partition in sectors. endsect may be negative, which means it counts backwards from the end of the disk (-1 is the last sector).

    Creating a partition which covers the whole disk is not so easy. Use guestfs_session_part_disk() to do that.

    Parameters

    • device: string
    • prlogex: string
    • startsect: number
    • endsect: number

    Returns boolean

  • partDel(device: string, partnum: number): boolean
  • delete a partition

    This command deletes the partition numbered partnum on device.

    Note that in the case of MBR partitioning, deleting an extended partition also deletes any logical partitions it contains.

    Parameters

    • device: string
    • partnum: number

    Returns boolean

  • partDisk(device: string, parttype: string): boolean
  • partition whole disk with a single primary partition

    This command is simply a combination of guestfs_session_part_init() followed by guestfs_session_part_add() to create a single primary partition covering the whole disk.

    parttype is the partition table type, usually mbr or gpt, but other possible values are described in guestfs_session_part_init().

    Parameters

    • device: string
    • parttype: string

    Returns boolean

  • partExpandGpt(device: string): boolean
  • move backup GPT header to the end of the disk

    Move backup GPT data structures to the end of the disk. This is useful in case of in-place image expand since disk space after backup GPT header is not usable. This is equivalent to "sgdisk -e".

    See also sgdisk(8).

    This function depends on the feature "gdisk". See also guestfs_session_feature_available().

    Parameters

    • device: string

    Returns boolean

  • partGetBootable(device: string, partnum: number): number
  • return true if a partition is bootable

    This command returns true if the partition partnum on device has the bootable flag set.

    See also guestfs_session_part_set_bootable().

    Parameters

    • device: string
    • partnum: number

    Returns number

  • partGetDiskGuid(device: string): string
  • get the GUID of a GPT-partitioned disk

    Return the disk identifier (GUID) of a GPT-partitioned device. Behaviour is undefined for other partition types.

    This function depends on the feature "gdisk". See also guestfs_session_feature_available().

    Parameters

    • device: string

    Returns string

  • partGetGptAttributes(device: string, partnum: number): number
  • get the attribute flags of a GPT partition

    Return the attribute flags of numbered GPT partition partnum. An error is returned for MBR partitions.

    This function depends on the feature "gdisk". See also guestfs_session_feature_available().

    Parameters

    • device: string
    • partnum: number

    Returns number

  • partGetGptGuid(device: string, partnum: number): string
  • get the GUID of a GPT partition

    Return the GUID of numbered GPT partition partnum.

    This function depends on the feature "gdisk". See also guestfs_session_feature_available().

    Parameters

    • device: string
    • partnum: number

    Returns string

  • partGetGptType(device: string, partnum: number): string
  • get the type GUID of a GPT partition

    Return the type GUID of numbered GPT partition partnum. For MBR partitions, return an appropriate GUID corresponding to the MBR type. Behaviour is undefined for other partition types.

    This function depends on the feature "gdisk". See also guestfs_session_feature_available().

    Parameters

    • device: string
    • partnum: number

    Returns string

  • partGetMbrId(device: string, partnum: number): number
  • get the MBR type byte (ID byte) from a partition

    Returns the MBR type byte (also known as the ID byte) from the numbered partition partnum.

    Note that only MBR (old DOS-style) partitions have type bytes. You will get undefined results for other partition table types (see guestfs_session_part_get_parttype()).

    Parameters

    • device: string
    • partnum: number

    Returns number

  • partGetMbrPartType(device: string, partnum: number): string
  • get the MBR partition type

    This returns the partition type of an MBR partition numbered partnum on device device.

    It returns primary, logical, or extended.

    Parameters

    • device: string
    • partnum: number

    Returns string

  • partGetName(device: string, partnum: number): string
  • get partition name

    This gets the partition name on partition numbered partnum on device device. Note that partitions are numbered from 1.

    The partition name can only be read on certain types of partition table. This works on gpt but not on mbr partitions.

    Parameters

    • device: string
    • partnum: number

    Returns string

  • partGetParttype(device: string): string
  • get the partition table type

    This command examines the partition table on device and returns the partition table type (format) being used.

    Common return values include: msdos (a DOS/Windows style MBR partition table), gpt (a GPT/EFI-style partition table). Other values are possible, although unusual. See guestfs_session_part_init() for a full list.

    Parameters

    • device: string

    Returns string

  • partInit(device: string, parttype: string): boolean
  • create an empty partition table

    This creates an empty partition table on device of one of the partition types listed below. Usually parttype should be either msdos or gpt (for large disks).

    Initially there are no partitions. Following this, you should call guestfs_session_part_add() for each partition required.

    Possible values for parttype are:

    efi gpt Intel EFI / GPT partition table.

    This is recommended for >= 2 TB partitions that will be accessed from Linux and Intel-based Mac OS X. It also has limited backwards compatibility with the mbr format.

    mbr msdos The standard PC "Master Boot Record" (MBR) format used by MS-DOS and Windows. This partition type will only work for device sizes up to 2 TB. For large disks we recommend using gpt.

    Other partition table types that may work but are not supported include:

    aix AIX disk labels.

    amiga rdb Amiga "Rigid Disk Block" format.

    bsd BSD disk labels.

    dasd DASD, used on IBM mainframes.

    dvh MIPS/SGI volumes.

    mac Old Mac partition format. Modern Macs use gpt.

    pc98 NEC PC-98 format, common in Japan apparently.

    sun Sun disk labels.

    Parameters

    • device: string
    • parttype: string

    Returns boolean

  • list partitions on a device

    This command parses the partition table on device and returns the list of partitions found.

    The fields in the returned structure are:

    part_num Partition number, counting from 1.

    part_start Start of the partition in bytes. To get sectors you have to divide by the device’s sector size, see guestfs_session_blockdev_getss().

    part_end End of the partition in bytes.

    part_size Size of the partition in bytes.

    Parameters

    • device: string

    Returns Guestfs.Partition[]

  • partResize(device: string, partnum: number, endsect: number): boolean
  • resize a partition

    This command resizes the partition numbered partnum on device by moving the end position.

    Note that this does not modify any filesystem present in the partition. If you wish to do this, you will need to use filesystem resizing commands like guestfs_session_resize2fs().

    When growing a partition you will want to grow the filesystem afterwards, but when shrinking, you need to shrink the filesystem before the partition.

    Parameters

    • device: string
    • partnum: number
    • endsect: number

    Returns boolean

  • partSetBootable(device: string, partnum: number, bootable: boolean): boolean
  • make a partition bootable

    This sets the bootable flag on partition numbered partnum on device device. Note that partitions are numbered from 1.

    The bootable flag is used by some operating systems (notably Windows) to determine which partition to boot from. It is by no means universally recognized.

    Parameters

    • device: string
    • partnum: number
    • bootable: boolean

    Returns boolean

  • partSetDiskGuid(device: string, guid: string): boolean
  • set the GUID of a GPT-partitioned disk

    Set the disk identifier (GUID) of a GPT-partitioned device to guid. Return an error if the partition table of device isn't GPT, or if guid is not a valid GUID.

    This function depends on the feature "gdisk". See also guestfs_session_feature_available().

    Parameters

    • device: string
    • guid: string

    Returns boolean

  • partSetDiskGuidRandom(device: string): boolean
  • set the GUID of a GPT-partitioned disk to random value

    Set the disk identifier (GUID) of a GPT-partitioned device to a randomly generated value. Return an error if the partition table of device isn't GPT.

    This function depends on the feature "gdisk". See also guestfs_session_feature_available().

    Parameters

    • device: string

    Returns boolean

  • partSetGptAttributes(device: string, partnum: number, attributes: number): boolean
  • set the attribute flags of a GPT partition

    Set the attribute flags of numbered GPT partition partnum to attributes. Return an error if the partition table of device isn't GPT.

    See http://en.wikipedia.org/wiki/GUID_Partition_Table#Partition_entries for a useful list of partition attributes.

    This function depends on the feature "gdisk". See also guestfs_session_feature_available().

    Parameters

    • device: string
    • partnum: number
    • attributes: number

    Returns boolean

  • partSetGptGuid(device: string, partnum: number, guid: string): boolean
  • set the GUID of a GPT partition

    Set the GUID of numbered GPT partition partnum to guid. Return an error if the partition table of device isn't GPT, or if guid is not a valid GUID.

    This function depends on the feature "gdisk". See also guestfs_session_feature_available().

    Parameters

    • device: string
    • partnum: number
    • guid: string

    Returns boolean

  • partSetGptType(device: string, partnum: number, guid: string): boolean
  • set the type GUID of a GPT partition

    Set the type GUID of numbered GPT partition partnum to guid. Return an error if the partition table of device isn't GPT, or if guid is not a valid GUID.

    See http://en.wikipedia.org/wiki/GUID_Partition_Table#Partition_type_GUIDs for a useful list of type GUIDs.

    This function depends on the feature "gdisk". See also guestfs_session_feature_available().

    Parameters

    • device: string
    • partnum: number
    • guid: string

    Returns boolean

  • partSetMbrId(device: string, partnum: number, idbyte: number): boolean
  • set the MBR type byte (ID byte) of a partition

    Sets the MBR type byte (also known as the ID byte) of the numbered partition partnum to idbyte. Note that the type bytes quoted in most documentation are in fact hexadecimal numbers, but usually documented without any leading "0x" which might be confusing.

    Note that only MBR (old DOS-style) partitions have type bytes. You will get undefined results for other partition table types (see guestfs_session_part_get_parttype()).

    Parameters

    • device: string
    • partnum: number
    • idbyte: number

    Returns boolean

  • partSetName(device: string, partnum: number, name: string): boolean
  • set partition name

    This sets the partition name on partition numbered partnum on device device. Note that partitions are numbered from 1.

    The partition name can only be set on certain types of partition table. This works on gpt but not on mbr partitions.

    Parameters

    • device: string
    • partnum: number
    • name: string

    Returns boolean

  • partToDev(partition: string): string
  • convert partition name to device name

    This function takes a partition name (eg. "/dev/sdb1") and removes the partition number, returning the device name (eg. "/dev/sdb").

    The named partition must exist, for example as a string returned from guestfs_session_list_partitions().

    See also guestfs_session_part_to_partnum(), guestfs_session_device_index().

    Parameters

    • partition: string

    Returns string

  • partToPartnum(partition: string): number
  • convert partition name to partition number

    This function takes a partition name (eg. "/dev/sdb1") and returns the partition number (eg. 1).

    The named partition must exist, for example as a string returned from guestfs_session_list_partitions().

    See also guestfs_session_part_to_dev().

    Parameters

    • partition: string

    Returns number

  • pingDaemon(): boolean
  • ping the guest daemon

    This is a test probe into the guestfs daemon running inside the libguestfs appliance. Calling this function checks that the daemon responds to the ping message, without affecting the daemon or attached block device(s) in any other way.

    Returns boolean

  • pread(path: string, count: number, offset: number): Uint8Array
  • read part of a file

    This command lets you read part of a file. It reads count bytes of the file, starting at offset, from file path.

    This may read fewer bytes than requested. For further details see the pread(2) system call.

    See also guestfs_session_pwrite(), guestfs_session_pread_device().

    Parameters

    • path: string
    • count: number
    • offset: number

    Returns Uint8Array

  • preadDevice(device: string, count: number, offset: number): Uint8Array
  • read part of a device

    This command lets you read part of a block device. It reads count bytes of device, starting at offset.

    This may read fewer bytes than requested. For further details see the pread(2) system call.

    See also guestfs_session_pread().

    Parameters

    • device: string
    • count: number
    • offset: number

    Returns Uint8Array

  • pvchangeUuid(device: string): boolean
  • generate a new random UUID for a physical volume

    Generate a new random UUID for the physical volume device.

    This function depends on the feature "lvm2". See also guestfs_session_feature_available().

    Parameters

    • device: string

    Returns boolean

  • pvchangeUuidAll(): boolean
  • generate new random UUIDs for all physical volumes

    Generate new random UUIDs for all physical volumes.

    This function depends on the feature "lvm2". See also guestfs_session_feature_available().

    Returns boolean

  • pvcreate(device: string): boolean
  • create an LVM physical volume

    This creates an LVM physical volume on the named device, where device should usually be a partition name such as /dev/sda1.

    This function depends on the feature "lvm2". See also guestfs_session_feature_available().

    Parameters

    • device: string

    Returns boolean

  • pvremove(device: string): boolean
  • remove an LVM physical volume

    This wipes a physical volume device so that LVM will no longer recognise it.

    The implementation uses the pvremove command which refuses to wipe physical volumes that contain any volume groups, so you have to remove those first.

    This function depends on the feature "lvm2". See also guestfs_session_feature_available().

    Parameters

    • device: string

    Returns boolean

  • pvresize(device: string): boolean
  • resize an LVM physical volume

    This resizes (expands or shrinks) an existing LVM physical volume to match the new size of the underlying device.

    This function depends on the feature "lvm2". See also guestfs_session_feature_available().

    Parameters

    • device: string

    Returns boolean

  • pvresizeSize(device: string, size: number): boolean
  • resize an LVM physical volume (with size)

    This command is the same as guestfs_session_pvresize() except that it allows you to specify the new size (in bytes) explicitly.

    This function depends on the feature "lvm2". See also guestfs_session_feature_available().

    Parameters

    • device: string
    • size: number

    Returns boolean

  • pvs(): string[]
  • list the LVM physical volumes (PVs)

    List all the physical volumes detected. This is the equivalent of the pvs(8) command.

    This returns a list of just the device names that contain PVs (eg. /dev/sda2).

    See also guestfs_session_pvs_full().

    This function depends on the feature "lvm2". See also guestfs_session_feature_available().

    Returns string[]

  • pvsFull(): PV[]
  • list the LVM physical volumes (PVs)

    List all the physical volumes detected. This is the equivalent of the pvs(8) command. The "full" version includes all fields.

    This function depends on the feature "lvm2". See also guestfs_session_feature_available().

    Returns PV[]

  • pvuuid(device: string): string
  • get the UUID of a physical volume

    This command returns the UUID of the LVM PV device.

    Parameters

    • device: string

    Returns string

  • pwrite(path: string, content: Uint8Array, offset: number): number
  • write to part of a file

    This command writes to part of a file. It writes the data buffer content to the file path starting at offset offset.

    This command implements the pwrite(2) system call, and like that system call it may not write the full data requested. The return value is the number of bytes that were actually written to the file. This could even be 0, although short writes are unlikely for regular files in ordinary circumstances.

    See also guestfs_session_pread(), guestfs_session_pwrite_device().

    Parameters

    • path: string
    • content: Uint8Array

      an array of binary data

    • offset: number

    Returns number

  • pwriteDevice(device: string, content: Uint8Array, offset: number): number
  • write to part of a device

    This command writes to part of a device. It writes the data buffer content to device starting at offset offset.

    This command implements the pwrite(2) system call, and like that system call it may not write the full data requested (although short writes to disk devices and partitions are probably impossible with standard Linux kernels).

    See also guestfs_session_pwrite().

    Parameters

    • device: string
    • content: Uint8Array

      an array of binary data

    • offset: number

    Returns number

  • readFile(path: string): Uint8Array
  • read a file

    This calls returns the contents of the file path as a buffer.

    Unlike guestfs_session_cat(), this function can correctly handle files that contain embedded ASCII NUL characters.

    Parameters

    • path: string

    Returns Uint8Array

  • readLines(path: string): string[]
  • read file as lines

    Return the contents of the file named path.

    The file contents are returned as a list of lines. Trailing LF and CRLF character sequences are not returned.

    Note that this function cannot correctly handle binary files (specifically, files containing "\0" character which is treated as end of string). For those you need to use the guestfs_session_read_file() function and split the buffer into lines yourself.

    Parameters

    • path: string

    Returns string[]

  • readdir(dir: string): Dirent[]
  • read directories entries

    This returns the list of directory entries in directory dir.

    All entries in the directory are returned, including "." and "..". The entries are not sorted, but returned in the same order as the underlying filesystem.

    Also this call returns basic file type information about each file. The ftyp field will contain one of the following characters:

    'b' Block special

    'c' Char special

    'd' Directory

    'f' FIFO (named pipe)

    'l' Symbolic link

    'r' Regular file

    's' Socket

    'u' Unknown file type

    '?' The readdir(3) call returned a d_type field with an unexpected value

    This function is primarily intended for use by programs. To get a simple list of names, use guestfs_session_ls(). To get a printable directory for human consumption, use guestfs_session_ll().

    Parameters

    • dir: string

    Returns Dirent[]

  • readlink(path: string): string
  • read the target of a symbolic link

    This command reads the target of a symbolic link.

    Parameters

    • path: string

    Returns string

  • readlinklist(path: string, names: string[]): string[]
  • readlink on multiple files

    This call allows you to do a readlink operation on multiple files, where all files are in the directory path. names is the list of files from this directory.

    On return you get a list of strings, with a one-to-one correspondence to the names list. Each string is the value of the symbolic link.

    If the readlink(2) operation fails on any name, then the corresponding result string is the empty string "". However the whole operation is completed even if there were readlink(2) errors, and so you can call this function with names where you don't know if they are symbolic links already (albeit slightly less efficient).

    This call is intended for programs that want to efficiently list a directory contents without making many round-trips.

    Parameters

    • path: string
    • names: string[]

      an array of strings

    Returns string[]

  • realpath(path: string): string
  • canonicalized absolute pathname

    Return the canonicalized absolute pathname of path. The returned path has no ".", ".." or symbolic link path elements.

    Parameters

    • path: string

    Returns string

  • Increases the reference count of object.

    Since GLib 2.56, if GLIB_VERSION_MAX_ALLOWED is 2.56 or greater, the type of object will be propagated to the return type (using the GCC typeof() extension), so any casting the caller needs to do on the return type must be explicit.

    Returns GObject.Object

  • Increase the reference count of object, and possibly remove the [floating][floating-ref] reference, if object has a floating reference.

    In other words, if the object is floating, then this call "assumes ownership" of the floating reference, converting it to a normal reference by clearing the floating flag while leaving the reference count unchanged. If the object is not floating, then this call adds a new normal reference increasing the reference count by one.

    Since GLib 2.56, the type of object will be propagated to the return type under the same conditions as for g_object_ref().

    Returns GObject.Object

  • remount(mountpoint: string, optargs: Remount): boolean
  • remount a filesystem with different options

    This call allows you to change the rw (readonly/read-write) flag on an already mounted filesystem at mountpoint, converting a readonly filesystem to be read-write, or vice-versa.

    Note that at the moment you must supply the "optional" rw parameter. In future we may allow other flags to be adjusted.

    Parameters

    • mountpoint: string
    • optargs: Remount

      a GuestfsRemount containing optional arguments

    Returns boolean

  • removeDrive(label: string): boolean
  • remove a disk image

    This function is conceptually the opposite of guestfs_session_add_drive_opts(). It removes the drive that was previously added with label label.

    Note that in order to remove drives, you have to add them with labels (see the optional label argument to guestfs_session_add_drive_opts()). If you didn't use a label, then they cannot be removed.

    You can call this function before or after launching the handle. If called after launch, if the backend supports it, we try to hot unplug the drive: see "HOTPLUGGING" in guestfs(3). The disk must not be in use (eg. mounted) when you do this. We try to detect if the disk is in use and stop you from doing this.

    Parameters

    • label: string

    Returns boolean

  • removexattr(xattr: string, path: string): boolean
  • remove extended attribute of a file or directory

    This call removes the extended attribute named xattr of the file path.

    See also: guestfs_session_lremovexattr(), attr(5).

    This function depends on the feature "linuxxattrs". See also guestfs_session_feature_available().

    Parameters

    • xattr: string
    • path: string

    Returns boolean

  • rename(oldpath: string, newpath: string): boolean
  • rename a file on the same filesystem

    Rename a file to a new place on the same filesystem. This is the same as the Linux rename(2) system call. In most cases you are better to use guestfs_session_mv() instead.

    Parameters

    • oldpath: string
    • newpath: string

    Returns boolean

  • resize2fs(device: string): boolean
  • resize an ext2, ext3 or ext4 filesystem

    This resizes an ext2, ext3 or ext4 filesystem to match the size of the underlying device.

    See also "RESIZE2FS ERRORS" in guestfs(3).

    Parameters

    • device: string

    Returns boolean

  • resize2fsM(device: string): boolean
  • resize an ext2, ext3 or ext4 filesystem to the minimum size

    This command is the same as guestfs_session_resize2fs(), but the filesystem is resized to its minimum size. This works like the -M option to the resize2fs command.

    To get the resulting size of the filesystem you should call guestfs_session_tune2fs_l() and read the "Block size" and "Block count" values. These two numbers, multiplied together, give the resulting size of the minimal filesystem in bytes.

    See also "RESIZE2FS ERRORS" in guestfs(3).

    Parameters

    • device: string

    Returns boolean

  • resize2fsSize(device: string, size: number): boolean
  • resize an ext2, ext3 or ext4 filesystem (with size)

    This command is the same as guestfs_session_resize2fs() except that it allows you to specify the new size (in bytes) explicitly.

    See also "RESIZE2FS ERRORS" in guestfs(3).

    Parameters

    • device: string
    • size: number

    Returns boolean

  • rm(path: string): boolean
  • remove a file

    Remove the single file path.

    Parameters

    • path: string

    Returns boolean

  • rmF(path: string): boolean
  • remove a file ignoring errors

    Remove the file path.

    If the file doesn't exist, that error is ignored. (Other errors, eg. I/O errors or bad paths, are not ignored)

    This call cannot remove directories. Use guestfs_session_rmdir() to remove an empty directory, or guestfs_session_rm_rf() to remove directories recursively.

    Parameters

    • path: string

    Returns boolean

  • rmRf(path: string): boolean
  • remove a file or directory recursively

    Remove the file or directory path, recursively removing the contents if its a directory. This is like the "rm -rf" shell command.

    Parameters

    • path: string

    Returns boolean

  • rmdir(path: string): boolean
  • remove a directory

    Remove the single directory path.

    Parameters

    • path: string

    Returns boolean

  • rmmountpoint(exemptpath: string): boolean
  • remove a mountpoint

    This call removes a mountpoint that was previously created with guestfs_session_mkmountpoint(). See guestfs_session_mkmountpoint() for full details.

    Parameters

    • exemptpath: string

    Returns boolean

  • rsync(src: string, dest: string, optargs: Rsync): boolean
  • synchronize the contents of two directories

    This call may be used to copy or synchronize two directories under the same libguestfs handle. This uses the rsync(1) program which uses a fast algorithm that avoids copying files unnecessarily.

    src and dest are the source and destination directories. Files are copied from src to dest.

    The optional arguments are:

    archive Turns on archive mode. This is the same as passing the --archive flag to rsync.

    deletedest Delete files at the destination that do not exist at the source.

    This function depends on the feature "rsync". See also guestfs_session_feature_available().

    Parameters

    • src: string
    • dest: string
    • optargs: Rsync

      a GuestfsRsync containing optional arguments

    Returns boolean

  • rsyncIn(remote: string, dest: string, optargs: RsyncIn): boolean
  • synchronize host or remote filesystem with filesystem

    This call may be used to copy or synchronize the filesystem on the host or on a remote computer with the filesystem within libguestfs. This uses the rsync(1) program which uses a fast algorithm that avoids copying files unnecessarily.

    This call only works if the network is enabled. See guestfs_session_set_network() or the --network option to various tools like guestfish(1).

    Files are copied from the remote server and directory specified by remote to the destination directory dest.

    The format of the remote server string is defined by rsync(1). Note that there is no way to supply a password or passphrase so the target must be set up not to require one.

    The optional arguments are the same as those of guestfs_session_rsync().

    This function depends on the feature "rsync". See also guestfs_session_feature_available().

    Parameters

    • remote: string
    • dest: string
    • optargs: RsyncIn

      a GuestfsRsyncIn containing optional arguments

    Returns boolean

  • rsyncOut(src: string, remote: string, optargs: RsyncOut): boolean
  • synchronize filesystem with host or remote filesystem

    This call may be used to copy or synchronize the filesystem within libguestfs with a filesystem on the host or on a remote computer. This uses the rsync(1) program which uses a fast algorithm that avoids copying files unnecessarily.

    This call only works if the network is enabled. See guestfs_session_set_network() or the --network option to various tools like guestfish(1).

    Files are copied from the source directory src to the remote server and directory specified by remote.

    The format of the remote server string is defined by rsync(1). Note that there is no way to supply a password or passphrase so the target must be set up not to require one.

    The optional arguments are the same as those of guestfs_session_rsync().

    Globbing does not happen on the src parameter. In programs which use the API directly you have to expand wildcards yourself (see guestfs_session_glob_expand()). In guestfish you can use the glob command (see "glob" in guestfish(1)), for example:

    glob rsync-out /* rsync://remote/]]>

    This function depends on the feature "rsync". See also guestfs_session_feature_available().

    Parameters

    • src: string
    • remote: string
    • optargs: RsyncOut

      a GuestfsRsyncOut containing optional arguments

    Returns boolean

  • runDispose(): void
  • Releases all references to other objects. This can be used to break reference cycles.

    This function should only be called from object system implementations.

    Returns void

  • scrubDevice(device: string): boolean
  • scrub (securely wipe) a device

    This command writes patterns over device to make data retrieval more difficult.

    It is an interface to the scrub(1) program. See that manual page for more details.

    This function depends on the feature "scrub". See also guestfs_session_feature_available().

    Parameters

    • device: string

    Returns boolean

  • scrubFile(file: string): boolean
  • scrub (securely wipe) a file

    This command writes patterns over a file to make data retrieval more difficult.

    The file is removed after scrubbing.

    It is an interface to the scrub(1) program. See that manual page for more details.

    This function depends on the feature "scrub". See also guestfs_session_feature_available().

    Parameters

    • file: string

    Returns boolean

  • scrubFreespace(dir: string): boolean
  • scrub (securely wipe) free space

    This command creates the directory dir and then fills it with files until the filesystem is full, and scrubs the files as for guestfs_session_scrub_file(), and deletes them. The intention is to scrub any free space on the partition containing dir.

    It is an interface to the scrub(1) program. See that manual page for more details.

    This function depends on the feature "scrub". See also guestfs_session_feature_available().

    Parameters

    • dir: string

    Returns boolean

  • selinuxRelabel(specfile: string, path: string, optargs: SelinuxRelabel): boolean
  • relabel parts of the filesystem

    SELinux relabel parts of the filesystem.

    The specfile parameter controls the policy spec file used. You have to parse "/etc/selinux/config" to find the correct SELinux policy and then pass the spec file, usually: "/etc/selinux/" + selinuxtype + "/contexts/files/file_contexts".

    The required path parameter is the top level directory where relabelling starts. Normally you should pass path as "/" to relabel the whole guest filesystem.

    The optional force boolean controls whether the context is reset for customizable files, and also whether the user, role and range parts of the file context is changed.

    This function depends on the feature "selinuxrelabel". See also guestfs_session_feature_available().

    Parameters

    • specfile: string
    • path: string
    • optargs: SelinuxRelabel

      a GuestfsSelinuxRelabel containing optional arguments

    Returns boolean

  • setAppend(append: string): boolean
  • add options to kernel command line

    This function is used to add additional options to the libguestfs appliance kernel command line.

    The default is NULL unless overridden by setting LIBGUESTFS_APPEND environment variable.

    Setting append to NULL means no additional options are passed (libguestfs always adds a few of its own).

    Parameters

    • append: string

    Returns boolean

  • setAttachMethod(backend: string): boolean
  • set the backend

    Set the method that libguestfs uses to connect to the backend guestfsd daemon.

    See "BACKEND" in guestfs(3).

    Parameters

    • backend: string

    Returns boolean

  • setAutosync(autosync: boolean): boolean
  • set autosync mode

    If autosync is true, this enables autosync. Libguestfs will make a best effort attempt to make filesystems consistent and synchronized when the handle is closed (also if the program exits without closing handles).

    This is enabled by default (since libguestfs 1.5.24, previously it was disabled by default).

    Parameters

    • autosync: boolean

    Returns boolean

  • setBackend(backend: string): boolean
  • set the backend

    Set the method that libguestfs uses to connect to the backend guestfsd daemon.

    This handle property was previously called the "attach method".

    See "BACKEND" in guestfs(3).

    Parameters

    • backend: string

    Returns boolean

  • setBackendSetting(name: string, val: string): boolean
  • set a single per-backend settings string

    Append "name=value" to the backend settings string list. However if a string already exists matching "name" or beginning with "name=", then that setting is replaced.

    See "BACKEND" in guestfs(3), "BACKEND SETTINGS" in guestfs(3).

    Parameters

    • name: string
    • val: string

    Returns boolean

  • setBackendSettings(settings: string[]): boolean
  • replace per-backend settings strings

    Set a list of zero or more settings which are passed through to the current backend. Each setting is a string which is interpreted in a backend-specific way, or ignored if not understood by the backend.

    The default value is an empty list, unless the environment variable LIBGUESTFS_BACKEND_SETTINGS was set when the handle was created. This environment variable contains a colon-separated list of settings.

    This call replaces all backend settings. If you want to replace a single backend setting, see guestfs_session_set_backend_setting(). If you want to clear a single backend setting, see guestfs_session_clear_backend_setting().

    See "BACKEND" in guestfs(3), "BACKEND SETTINGS" in guestfs(3).

    Parameters

    • settings: string[]

      an array of strings

    Returns boolean

  • setCachedir(cachedir: string): boolean
  • set the appliance cache directory

    Set the directory used by the handle to store the appliance cache, when using a supermin appliance. The appliance is cached and shared between all handles which have the same effective user ID.

    The environment variables LIBGUESTFS_CACHEDIR and TMPDIR control the default value: If LIBGUESTFS_CACHEDIR is set, then that is the default. Else if TMPDIR is set, then that is the default. Else /var/tmp is the default.

    Parameters

    • cachedir: string

    Returns boolean

  • setData(key: string, data?: object): void
  • Each object carries around a table of associations from strings to pointers. This function lets you set an association.

    If the object already had an association with that name, the old association will be destroyed.

    Internally, the key is converted to a #GQuark using g_quark_from_string(). This means a copy of key is kept permanently (even after object has been finalized) — so it is recommended to only use a small, bounded set of values for key in your program, to avoid the #GQuark storage growing unbounded.

    Parameters

    • key: string

      name of the key

    • Optional data: object

      data to associate with that key

    Returns void

  • setDirect(direct: boolean): boolean
  • enable or disable direct appliance mode

    If the direct appliance mode flag is enabled, then stdin and stdout are passed directly through to the appliance once it is launched.

    One consequence of this is that log messages aren't caught by the library and handled by guestfs_session_set_log_message_callback(), but go straight to stdout.

    You probably don't want to use this unless you know what you are doing.

    The default is disabled.

    Parameters

    • direct: boolean

    Returns boolean

  • setE2attrs(file: string, attrs: string, optargs: SetE2attrs): boolean
  • set ext2 file attributes of a file

    This sets or clears the file attributes attrs associated with the inode file.

    attrs is a string of characters representing file attributes. See guestfs_session_get_e2attrs() for a list of possible attributes. Not all attributes can be changed.

    If optional boolean clear is not present or false, then the attrs listed are set in the inode.

    If clear is true, then the attrs listed are cleared in the inode.

    In both cases, other attributes not present in the attrs string are left unchanged.

    These attributes are only present when the file is located on an ext2/3/4 filesystem. Using this call on other filesystem types will result in an error.

    Parameters

    • file: string
    • attrs: string
    • optargs: SetE2attrs

      a GuestfsSetE2attrs containing optional arguments

    Returns boolean

  • setE2generation(file: string, generation: number): boolean
  • set ext2 file generation of a file

    This sets the ext2 file generation of a file.

    See guestfs_session_get_e2generation().

    Parameters

    • file: string
    • generation: number

    Returns boolean

  • setE2label(device: string, label: string): boolean
  • set the ext2/3/4 filesystem label

    This sets the ext2/3/4 filesystem label of the filesystem on device to label. Filesystem labels are limited to 16 characters.

    You can use either guestfs_session_tune2fs_l() or guestfs_session_get_e2label() to return the existing label on a filesystem.

    Parameters

    • device: string
    • label: string

    Returns boolean

  • setE2uuid(device: string, uuid: string): boolean
  • set the ext2/3/4 filesystem UUID

    This sets the ext2/3/4 filesystem UUID of the filesystem on device to uuid. The format of the UUID and alternatives such as clear, random and time are described in the tune2fs(8) manpage.

    You can use guestfs_session_vfs_uuid() to return the existing UUID of a filesystem.

    Parameters

    • device: string
    • uuid: string

    Returns boolean

  • setHv(hv: string): boolean
  • set the hypervisor binary

    Set the hypervisor binary that we will use. The hypervisor depends on the backend, but is usually the location of the qemu/KVM hypervisor. For the uml backend, it is the location of the linux or vmlinux binary.

    The default is chosen when the library was compiled by the configure script.

    You can also override this by setting the LIBGUESTFS_HV environment variable.

    Note that you should call this function as early as possible after creating the handle. This is because some pre-launch operations depend on testing qemu features (by running "qemu -help"). If the qemu binary changes, we don't retest features, and so you might see inconsistent results. Using the environment variable LIBGUESTFS_HV is safest of all since that picks the qemu binary at the same time as the handle is created.

    Parameters

    • hv: string

    Returns boolean

  • setIdentifier(identifier: string): boolean
  • set the handle identifier

    This is an informative string which the caller may optionally set in the handle. It is printed in various places, allowing the current handle to be identified in debugging output.

    One important place is when tracing is enabled. If the identifier string is not an empty string, then trace messages change from this:

    to this:

    where ID is the identifier string set by this call.

    The identifier must only contain alphanumeric ASCII characters, underscore and minus sign. The default is the empty string.

    See also guestfs_session_set_program(), guestfs_session_set_trace(), guestfs_session_get_identifier().

    Parameters

    • identifier: string

    Returns boolean

  • setLabel(mountable: string, label: string): boolean
  • set filesystem label

    Set the filesystem label on mountable to label.

    Only some filesystem types support labels, and libguestfs supports setting labels on only a subset of these.

    ext2, ext3, ext4 Labels are limited to 16 bytes.

    NTFS Labels are limited to 128 unicode characters.

    XFS The label is limited to 12 bytes. The filesystem must not be mounted when trying to set the label.

    btrfs The label is limited to 255 bytes and some characters are not allowed. Setting the label on a btrfs subvolume will set the label on its parent filesystem. The filesystem must not be mounted when trying to set the label.

    fat The label is limited to 11 bytes.

    swap The label is limited to 16 bytes.

    If there is no support for changing the label for the type of the specified filesystem, set_label will fail and set errno as ENOTSUP.

    To read the label on a filesystem, call guestfs_session_vfs_label().

    Parameters

    • mountable: string
    • label: string

    Returns boolean

  • setLibvirtRequestedCredential(index: number, cred: Uint8Array): boolean
  • pass requested credential back to libvirt

    After requesting the index'th credential from the user, call this function to pass the answer back to libvirt.

    See "LIBVIRT AUTHENTICATION" in guestfs(3) for documentation and example code.

    Parameters

    • index: number
    • cred: Uint8Array

      an array of binary data

    Returns boolean

  • setLibvirtSupportedCredentials(creds: string[]): boolean
  • set libvirt credentials supported by calling program

    Call this function before setting an event handler for GUESTFS_EVENT_LIBVIRT_AUTH, to supply the list of credential types that the program knows how to process.

    The creds list must be a non-empty list of strings. Possible strings are:

    username authname language cnonce passphrase echoprompt noechoprompt realm external

    See libvirt documentation for the meaning of these credential types.

    See "LIBVIRT AUTHENTICATION" in guestfs(3) for documentation and example code.

    Parameters

    • creds: string[]

      an array of strings

    Returns boolean

  • setMemsize(memsize: number): boolean
  • set memory allocated to the hypervisor

    This sets the memory size in megabytes allocated to the hypervisor. This only has any effect if called before guestfs_session_launch().

    You can also change this by setting the environment variable LIBGUESTFS_MEMSIZE before the handle is created.

    For more information on the architecture of libguestfs, see guestfs(3).

    Parameters

    • memsize: number

    Returns boolean

  • setNetwork(network: boolean): boolean
  • set enable network flag

    If network is true, then the network is enabled in the libguestfs appliance. The default is false.

    This affects whether commands are able to access the network (see "RUNNING COMMANDS" in guestfs(3)).

    You must call this before calling guestfs_session_launch(), otherwise it has no effect.

    Parameters

    • network: boolean

    Returns boolean

  • setPath(searchpath: string): boolean
  • set the search path

    Set the path that libguestfs searches for kernel and initrd.img.

    The default is "$libdir/guestfs" unless overridden by setting LIBGUESTFS_PATH environment variable.

    Setting path to NULL restores the default path.

    Parameters

    • searchpath: string

    Returns boolean

  • setPgroup(pgroup: boolean): boolean
  • set process group flag

    If pgroup is true, child processes are placed into their own process group.

    The practical upshot of this is that signals like SIGINT (from users pressing "^C") won't be received by the child process.

    The default for this flag is false, because usually you want "^C" to kill the subprocess. Guestfish sets this flag to true when used interactively, so that "^C" can cancel long-running commands gracefully (see guestfs_session_user_cancel()).

    Parameters

    • pgroup: boolean

    Returns boolean

  • setProgram(program: string): boolean
  • set the program name

    Set the program name. This is an informative string which the main program may optionally set in the handle.

    When the handle is created, the program name in the handle is set to the basename from "argv[0]". The program name can never be NULL.

    Parameters

    • program: string

    Returns boolean

  • setProperty(propertyName: string, value?: any): void
  • Sets a property on an object.

    Parameters

    • propertyName: string

      the name of the property to set

    • Optional value: any

      the value

    Returns void

  • setQemu(hv: string): boolean
  • set the hypervisor binary (usually qemu)

    Set the hypervisor binary (usually qemu) that we will use.

    The default is chosen when the library was compiled by the configure script.

    You can also override this by setting the LIBGUESTFS_HV environment variable.

    Setting hv to NULL restores the default qemu binary.

    Note that you should call this function as early as possible after creating the handle. This is because some pre-launch operations depend on testing qemu features (by running "qemu -help"). If the qemu binary changes, we don't retest features, and so you might see inconsistent results. Using the environment variable LIBGUESTFS_HV is safest of all since that picks the qemu binary at the same time as the handle is created.

    Parameters

    • hv: string

    Returns boolean

  • setRecoveryProc(recoveryproc: boolean): boolean
  • enable or disable the recovery process

    If this is called with the parameter false then guestfs_session_launch() does not create a recovery process. The purpose of the recovery process is to stop runaway hypervisor processes in the case where the main program aborts abruptly.

    This only has any effect if called before guestfs_session_launch(), and the default is true.

    About the only time when you would want to disable this is if the main process will fork itself into the background ("daemonize" itself). In this case the recovery process thinks that the main program has disappeared and so kills the hypervisor, which is not very helpful.

    Parameters

    • recoveryproc: boolean

    Returns boolean

  • setSelinux(selinux: boolean): boolean
  • set SELinux enabled or disabled at appliance boot

    This sets the selinux flag that is passed to the appliance at boot time. The default is "selinux=0" (disabled).

    Note that if SELinux is enabled, it is always in Permissive mode ("enforcing=0").

    For more information on the architecture of libguestfs, see guestfs(3).

    Parameters

    • selinux: boolean

    Returns boolean

  • setSmp(smp: number): boolean
  • set number of virtual CPUs in appliance

    Change the number of virtual CPUs assigned to the appliance. The default is 1. Increasing this may improve performance, though often it has no effect.

    This function must be called before guestfs_session_launch().

    Parameters

    • smp: number

    Returns boolean

  • setTmpdir(tmpdir: string): boolean
  • set the temporary directory

    Set the directory used by the handle to store temporary files.

    The environment variables LIBGUESTFS_TMPDIR and TMPDIR control the default value: If LIBGUESTFS_TMPDIR is set, then that is the default. Else if TMPDIR is set, then that is the default. Else /tmp is the default.

    Parameters

    • tmpdir: string

    Returns boolean

  • setTrace(trace: boolean): boolean
  • enable or disable command traces

    If the command trace flag is set to 1, then libguestfs calls, parameters and return values are traced.

    If you want to trace C API calls into libguestfs (and other libraries) then possibly a better way is to use the external ltrace(1) command.

    Command traces are disabled unless the environment variable LIBGUESTFS_TRACE is defined and set to 1.

    Trace messages are normally sent to stderr, unless you register a callback to send them somewhere else (see guestfs_session_set_event_callback()).

    Parameters

    • trace: boolean

    Returns boolean

  • setUuid(device: string, uuid: string): boolean
  • set the filesystem UUID

    Set the filesystem UUID on device to uuid. If this fails and the errno is ENOTSUP, means that there is no support for changing the UUID for the type of the specified filesystem.

    Only some filesystem types support setting UUIDs.

    To read the UUID on a filesystem, call guestfs_session_vfs_uuid().

    Parameters

    • device: string
    • uuid: string

    Returns boolean

  • setUuidRandom(device: string): boolean
  • set a random UUID for the filesystem

    Set the filesystem UUID on device to a random UUID. If this fails and the errno is ENOTSUP, means that there is no support for changing the UUID for the type of the specified filesystem.

    Only some filesystem types support setting UUIDs.

    To read the UUID on a filesystem, call guestfs_session_vfs_uuid().

    Parameters

    • device: string

    Returns boolean

  • setVerbose(verbose: boolean): boolean
  • set verbose mode

    If verbose is true, this turns on verbose messages.

    Verbose messages are disabled unless the environment variable LIBGUESTFS_DEBUG is defined and set to 1.

    Verbose messages are normally sent to stderr, unless you register a callback to send them somewhere else (see guestfs_session_set_event_callback()).

    Parameters

    • verbose: boolean

    Returns boolean

  • setcon(context: string): boolean
  • set SELinux security context

    This sets the SELinux security context of the daemon to the string context.

    See the documentation about SELINUX in guestfs(3).

    This function depends on the feature "selinux". See also guestfs_session_feature_available().

    Parameters

    • context: string

    Returns boolean

  • setxattr(xattr: string, val: string, vallen: number, path: string): boolean
  • set extended attribute of a file or directory

    This call sets the extended attribute named xattr of the file path to the value val (of length vallen). The value is arbitrary 8 bit data.

    See also: guestfs_session_lsetxattr(), attr(5).

    This function depends on the feature "linuxxattrs". See also guestfs_session_feature_available().

    Parameters

    • xattr: string
    • val: string
    • vallen: number
    • path: string

    Returns boolean

  • sfdisk(device: string, cyls: number, heads: number, sectors: number, lines: string[]): boolean
  • create partitions on a block device

    This is a direct interface to the sfdisk(8) program for creating partitions on block devices.

    device should be a block device, for example /dev/sda.

    cyls, heads and sectors are the number of cylinders, heads and sectors on the device, which are passed directly to sfdisk as the -C, -H and -S parameters. If you pass 0 for any of these, then the corresponding parameter is omitted. Usually for ‘large’ disks, you can just pass 0 for these, but for small (floppy-sized) disks, sfdisk (or rather, the kernel) cannot work out the right geometry and you will need to tell it.

    lines is a list of lines that we feed to sfdisk. For more information refer to the sfdisk(8) manpage.

    To create a single partition occupying the whole disk, you would pass lines as a single element list, when the single element being the string "," (comma).

    See also: guestfs_session_sfdisk_l(), guestfs_session_sfdisk_N(), guestfs_session_part_init()

    Parameters

    • device: string
    • cyls: number
    • heads: number
    • sectors: number
    • lines: string[]

      an array of strings

    Returns boolean

  • sfdiskDiskGeometry(device: string): string
  • display the disk geometry from the partition table

    This displays the disk geometry of device read from the partition table. Especially in the case where the underlying block device has been resized, this can be different from the kernel’s idea of the geometry (see guestfs_session_sfdisk_kernel_geometry()).

    The result is in human-readable format, and not designed to be parsed.

    Parameters

    • device: string

    Returns string

  • sfdiskKernelGeometry(device: string): string
  • display the kernel geometry

    This displays the kernel’s idea of the geometry of device.

    The result is in human-readable format, and not designed to be parsed.

    Parameters

    • device: string

    Returns string

  • sfdiskL(device: string): string
  • display the partition table

    This displays the partition table on device, in the human-readable output of the sfdisk(8) command. It is not intended to be parsed.

    See also: guestfs_session_part_list()

    Parameters

    • device: string

    Returns string

  • sfdiskM(device: string, lines: string[]): boolean
  • create partitions on a block device

    This is a simplified interface to the guestfs_session_sfdisk() command, where partition sizes are specified in megabytes only (rounded to the nearest cylinder) and you don't need to specify the cyls, heads and sectors parameters which were rarely if ever used anyway.

    See also: guestfs_session_sfdisk(), the sfdisk(8) manpage and guestfs_session_part_disk()

    Parameters

    • device: string
    • lines: string[]

      an array of strings

    Returns boolean

  • sfdiskN(device: string, partnum: number, cyls: number, heads: number, sectors: number, line: string): boolean
  • modify a single partition on a block device

    This runs sfdisk(8) option to modify just the single partition n (note: n counts from 1).

    For other parameters, see guestfs_session_sfdisk(). You should usually pass 0 for the cyls/heads/sectors parameters.

    See also: guestfs_session_part_add()

    Parameters

    • device: string
    • partnum: number
    • cyls: number
    • heads: number
    • sectors: number
    • line: string

    Returns boolean

  • sh(command: string): string
  • run a command via the shell

    This call runs a command from the guest filesystem via the guest’s /bin/sh.

    This is like guestfs_session_command(), but passes the command to:

    Depending on the guest’s shell, this usually results in wildcards being expanded, shell expressions being interpolated and so on.

    All the provisos about guestfs_session_command() apply to this call.

    Parameters

    • command: string

    Returns string

  • shLines(command: string): string[]
  • run a command via the shell returning lines

    This is the same as guestfs_session_sh(), but splits the result into a list of lines.

    See also: guestfs_session_command_lines()

    Parameters

    • command: string

    Returns string[]

  • shutdown(): boolean
  • shutdown the hypervisor

    This is the opposite of guestfs_session_launch(). It performs an orderly shutdown of the backend process(es). If the autosync flag is set (which is the default) then the disk image is synchronized.

    If the subprocess exits with an error then this function will return an error, which should not be ignored (it may indicate that the disk image could not be written out properly).

    It is safe to call this multiple times. Extra calls are ignored.

    This call does not close or free up the handle. You still need to call guestfs_session_close() afterwards.

    guestfs_session_close() will call this if you don't do it explicitly, but note that any errors are ignored in that case.

    Returns boolean

  • sleep(secs: number): boolean
  • sleep for some seconds

    Sleep for secs seconds.

    Parameters

    • secs: number

    Returns boolean

  • stat(path: string): Stat
  • get file information

    Returns file information for the given path.

    This is the same as the stat(2) system call.

    Parameters

    • path: string

    Returns Stat

  • get file information

    Returns file information for the given path.

    This is the same as the stat(2) system call.

    Parameters

    • path: string

    Returns StatNS

  • get file system statistics

    Returns file system statistics for any mounted file system. path should be a file or directory in the mounted file system (typically it is the mount point itself, but it doesn't need to be).

    This is the same as the statvfs(2) system call.

    Parameters

    • path: string

    Returns StatVFS

  • stealData(key?: string): object
  • Remove a specified datum from the object's data associations, without invoking the association's destroy handler.

    Parameters

    • Optional key: string

      name of the key

    Returns object

  • stealQdata(quark: number): object
  • This function gets back user data pointers stored via g_object_set_qdata() and removes the data from object without invoking its destroy() function (if any was set). Usually, calling this function is only required to update user data pointers with a destroy notifier, for example:

    void
    object_add_to_user_list (GObject *object,
    const gchar *new_string)
    {
    // the quark, naming the object data
    GQuark quark_string_list = g_quark_from_static_string ("my-string-list");
    // retrieve the old string list
    GList *list = g_object_steal_qdata (object, quark_string_list);

    // prepend new string
    list = g_list_prepend (list, g_strdup (new_string));
    // this changed 'list', so we need to set it again
    g_object_set_qdata_full (object, quark_string_list, list, free_string_list);
    }
    static void
    free_string_list (gpointer data)
    {
    GList *node, *list = data;

    for (node = list; node; node = node->next)
    g_free (node->data);
    g_list_free (list);
    }

    Using g_object_get_qdata() in the above example, instead of g_object_steal_qdata() would have left the destroy function set, and thus the partial string list would have been freed upon g_object_set_qdata_full().

    Parameters

    • quark: number

      A #GQuark, naming the user data pointer

    Returns object

  • strings(path: string): string[]
  • print the printable strings in a file

    This runs the strings(1) command on a file and returns the list of printable strings found.

    The strings command has, in the past, had problems with parsing untrusted files. These are mitigated in the current version of libguestfs, but see "CVE-2014-8484" in guestfs(3).

    Parameters

    • path: string

    Returns string[]

  • stringsE(encoding: string, path: string): string[]
  • print the printable strings in a file

    This is like the guestfs_session_strings() command, but allows you to specify the encoding of strings that are looked for in the source file path.

    Allowed encodings are:

    s Single 7-bit-byte characters like ASCII and the ASCII-compatible parts of ISO-8859-X (this is what guestfs_session_strings() uses).

    S Single 8-bit-byte characters.

    b 16-bit big endian strings such as those encoded in UTF-16BE or UCS-2BE.

    l (lower case letter L) 16-bit little endian such as UTF-16LE and UCS-2LE. This is useful for examining binaries in Windows guests.

    B 32-bit big endian such as UCS-4BE.

    L 32-bit little endian such as UCS-4LE.

    The returned strings are transcoded to UTF-8.

    The strings command has, in the past, had problems with parsing untrusted files. These are mitigated in the current version of libguestfs, but see "CVE-2014-8484" in guestfs(3).

    Parameters

    • encoding: string
    • path: string

    Returns string[]

  • swapoffDevice(device: string): boolean
  • disable swap on device

    This command disables the libguestfs appliance swap device or partition named device. See guestfs_session_swapon_device().

    Parameters

    • device: string

    Returns boolean

  • swapoffFile(file: string): boolean
  • disable swap on file

    This command disables the libguestfs appliance swap on file.

    Parameters

    • file: string

    Returns boolean

  • swapoffLabel(label: string): boolean
  • disable swap on labeled swap partition

    This command disables the libguestfs appliance swap on labeled swap partition.

    Parameters

    • label: string

    Returns boolean

  • swapoffUuid(uuid: string): boolean
  • disable swap on swap partition by UUID

    This command disables the libguestfs appliance swap partition with the given UUID.

    This function depends on the feature "linuxfsuuid". See also guestfs_session_feature_available().

    Parameters

    • uuid: string

    Returns boolean

  • swaponDevice(device: string): boolean
  • enable swap on device

    This command enables the libguestfs appliance to use the swap device or partition named device. The increased memory is made available for all commands, for example those run using guestfs_session_command() or guestfs_session_sh().

    Note that you should not swap to existing guest swap partitions unless you know what you are doing. They may contain hibernation information, or other information that the guest doesn't want you to trash. You also risk leaking information about the host to the guest this way. Instead, attach a new host device to the guest and swap on that.

    Parameters

    • device: string

    Returns boolean

  • swaponFile(file: string): boolean
  • enable swap on file

    This command enables swap to a file. See guestfs_session_swapon_device() for other notes.

    Parameters

    • file: string

    Returns boolean

  • swaponLabel(label: string): boolean
  • enable swap on labeled swap partition

    This command enables swap to a labeled swap partition. See guestfs_session_swapon_device() for other notes.

    Parameters

    • label: string

    Returns boolean

  • swaponUuid(uuid: string): boolean
  • enable swap on swap partition by UUID

    This command enables swap to a swap partition with the given UUID. See guestfs_session_swapon_device() for other notes.

    This function depends on the feature "linuxfsuuid". See also guestfs_session_feature_available().

    Parameters

    • uuid: string

    Returns boolean

  • sync(): boolean
  • sync disks, writes are flushed through to the disk image

    This syncs the disk, so that any writes are flushed through to the underlying disk image.

    You should always call this if you have modified a disk image, before closing the handle.

    Returns boolean

  • syslinux(device: string, optargs: Syslinux): boolean
  • install the SYSLINUX bootloader

    Install the SYSLINUX bootloader on device.

    The device parameter must be either a whole disk formatted as a FAT filesystem, or a partition formatted as a FAT filesystem. In the latter case, the partition should be marked as "active" (guestfs_session_part_set_bootable()) and a Master Boot Record must be installed (eg. using guestfs_session_pwrite_device()) on the first sector of the whole disk. The SYSLINUX package comes with some suitable Master Boot Records. See the syslinux(1) man page for further information.

    The optional arguments are:

    directory Install SYSLINUX in the named subdirectory, instead of in the root directory of the FAT filesystem.

    Additional configuration can be supplied to SYSLINUX by placing a file called syslinux.cfg on the FAT filesystem, either in the root directory, or under directory if that optional argument is being used. For further information about the contents of this file, see syslinux(1).

    See also guestfs_session_extlinux().

    This function depends on the feature "syslinux". See also guestfs_session_feature_available().

    Parameters

    • device: string
    • optargs: Syslinux

      a GuestfsSyslinux containing optional arguments

    Returns boolean

  • tail(path: string): string[]
  • return last 10 lines of a file

    This command returns up to the last 10 lines of a file as a list of strings.

    Parameters

    • path: string

    Returns string[]

  • tailN(nrlines: number, path: string): string[]
  • return last N lines of a file

    If the parameter nrlines is a positive number, this returns the last nrlines lines of the file path.

    If the parameter nrlines is a negative number, this returns lines from the file path, starting with the -nrlinesth line.

    If the parameter nrlines is zero, this returns an empty list.

    Parameters

    • nrlines: number
    • path: string

    Returns string[]

  • tarIn(tarfile: string, directory: string, optargs: TarIn, cancellable: Gio.Cancellable): boolean
  • unpack tarfile to directory

    This command uploads and unpacks local file tarfile into directory.

    The optional compress flag controls compression. If not given, then the input should be an uncompressed tar file. Otherwise one of the following strings may be given to select the compression type of the input file: compress, gzip, bzip2, xz, lzop. (Note that not all builds of libguestfs will support all of these compression types).

    The other optional arguments are:

    xattrs If set to true, extended attributes are restored from the tar file.

    selinux If set to true, SELinux contexts are restored from the tar file.

    acls If set to true, POSIX ACLs are restored from the tar file.

    Parameters

    • tarfile: string
    • directory: string
    • optargs: TarIn

      a GuestfsTarIn containing optional arguments

    • cancellable: Gio.Cancellable

      A GCancellable object

    Returns boolean

  • pack directory into tarfile

    This command packs the contents of directory and downloads it to local file tarfile.

    The optional compress flag controls compression. If not given, then the output will be an uncompressed tar file. Otherwise one of the following strings may be given to select the compression type of the output file: compress, gzip, bzip2, xz, lzop. (Note that not all builds of libguestfs will support all of these compression types).

    The other optional arguments are:

    excludes A list of wildcards. Files are excluded if they match any of the wildcards.

    numericowner If set to true, the output tar file will contain UID/GID numbers instead of user/group names.

    xattrs If set to true, extended attributes are saved in the output tar.

    selinux If set to true, SELinux contexts are saved in the output tar.

    acls If set to true, POSIX ACLs are saved in the output tar.

    Parameters

    • directory: string
    • tarfile: string
    • optargs: TarOut

      a GuestfsTarOut containing optional arguments

    • cancellable: Gio.Cancellable

      A GCancellable object

    Returns boolean

  • tgzIn(tarball: string, directory: string, cancellable: Gio.Cancellable): boolean
  • unpack compressed tarball to directory

    This command uploads and unpacks local file tarball (a gzip compressed tar file) into directory.

    Parameters

    • tarball: string
    • directory: string
    • cancellable: Gio.Cancellable

      A GCancellable object

    Returns boolean

  • tgzOut(directory: string, tarball: string, cancellable: Gio.Cancellable): boolean
  • pack directory into compressed tarball

    This command packs the contents of directory and downloads it to local file tarball.

    Parameters

    • directory: string
    • tarball: string
    • cancellable: Gio.Cancellable

      A GCancellable object

    Returns boolean

  • thawNotify(): void
  • Reverts the effect of a previous call to g_object_freeze_notify(). The freeze count is decreased on object and when it reaches zero, queued "notify" signals are emitted.

    Duplicate notifications for each property are squashed so that at most one #GObject::notify signal is emitted for each property, in the reverse order in which they have been queued.

    It is an error to call this function when the freeze count is zero.

    Returns void

  • touch(path: string): boolean
  • update file timestamps or create a new file

    Touch acts like the touch(1) command. It can be used to update the timestamps on a file, or, if the file does not exist, to create a new zero-length file.

    This command only works on regular files, and will fail on other file types such as directories, symbolic links, block special etc.

    Parameters

    • path: string

    Returns boolean

  • truncate(path: string): boolean
  • truncate a file to zero size

    This command truncates path to a zero-length file. The file must exist already.

    Parameters

    • path: string

    Returns boolean

  • truncateSize(path: string, size: number): boolean
  • truncate a file to a particular size

    This command truncates path to size size bytes. The file must exist already.

    If the current file size is less than size then the file is extended to the required size with zero bytes. This creates a sparse file (ie. disk blocks are not allocated for the file until you write to it). To create a non-sparse file of zeroes, use guestfs_session_fallocate64() instead.

    Parameters

    • path: string
    • size: number

    Returns boolean

  • tune2fs(device: string, optargs: Tune2FS): boolean
  • adjust ext2/ext3/ext4 filesystem parameters

    This call allows you to adjust various filesystem parameters of an ext2/ext3/ext4 filesystem called device.

    The optional parameters are:

    force Force tune2fs to complete the operation even in the face of errors. This is the same as the tune2fs -f option.

    maxmountcount Set the number of mounts after which the filesystem is checked by e2fsck(8). If this is 0 then the number of mounts is disregarded. This is the same as the tune2fs -c option.

    mountcount Set the number of times the filesystem has been mounted. This is the same as the tune2fs -C option.

    errorbehavior Change the behavior of the kernel code when errors are detected. Possible values currently are: continue, remount-ro, panic. In practice these options don't really make any difference, particularly for write errors.

    This is the same as the tune2fs -e option.

    group Set the group which can use reserved filesystem blocks. This is the same as the tune2fs -g option except that it can only be specified as a number.

    intervalbetweenchecks Adjust the maximal time between two filesystem checks (in seconds). If the option is passed as 0 then time-dependent checking is disabled.

    This is the same as the tune2fs -i option.

    reservedblockspercentage Set the percentage of the filesystem which may only be allocated by privileged processes. This is the same as the tune2fs -m option.

    lastmounteddirectory Set the last mounted directory. This is the same as the tune2fs -M option.

    reservedblockscount Set the number of reserved filesystem blocks. This is the same as the tune2fs -r option. user Set the user who can use the reserved filesystem blocks. This is the same as the tune2fs -u option except that it can only be specified as a number.

    To get the current values of filesystem parameters, see guestfs_session_tune2fs_l(). For precise details of how tune2fs works, see the tune2fs(8) man page.

    Parameters

    • device: string
    • optargs: Tune2FS

      a GuestfsTune2FS containing optional arguments

    Returns boolean

  • tune2fsL(device: string): HashTable<string | number | symbol, string | number | boolean>
  • get ext2/ext3/ext4 superblock details

    This returns the contents of the ext2, ext3 or ext4 filesystem superblock on device.

    It is the same as running "tune2fs -l device". See tune2fs(8) manpage for more details. The list of fields returned isn't clearly defined, and depends on both the version of tune2fs that libguestfs was built against, and the filesystem itself.

    Parameters

    • device: string

    Returns HashTable<string | number | symbol, string | number | boolean>

  • txzIn(tarball: string, directory: string, cancellable: Gio.Cancellable): boolean
  • unpack compressed tarball to directory

    This command uploads and unpacks local file tarball (an xz compressed tar file) into directory.

    This function depends on the feature "xz". See also guestfs_session_feature_available().

    Parameters

    • tarball: string
    • directory: string
    • cancellable: Gio.Cancellable

      A GCancellable object

    Returns boolean

  • txzOut(directory: string, tarball: string, cancellable: Gio.Cancellable): boolean
  • pack directory into compressed tarball

    This command packs the contents of directory and downloads it to local file tarball (as an xz compressed tar archive).

    This function depends on the feature "xz". See also guestfs_session_feature_available().

    Parameters

    • directory: string
    • tarball: string
    • cancellable: Gio.Cancellable

      A GCancellable object

    Returns boolean

  • umask(mask: number): number
  • set file mode creation mask (umask)

    This function sets the mask used for creating new files and device nodes to "mask & 0777".

    Typical umask values would be 022 which creates new files with permissions like "-rw-r--r--" or "-rwxr-xr-x", and 002 which creates new files with permissions like "-rw-rw-r--" or "-rwxrwxr-x".

    The default umask is 022. This is important because it means that directories and device nodes will be created with 0644 or 0755 mode even if you specify 0777.

    See also guestfs_session_get_umask(), umask(2), guestfs_session_mknod(), guestfs_session_mkdir().

    This call returns the previous umask.

    Parameters

    • mask: number

    Returns number

  • umount(pathordevice: string, optargs: Umount): boolean
  • unmount a filesystem

    This unmounts the given filesystem. The filesystem may be specified either by its mountpoint (path) or the device which contains the filesystem.

    Parameters

    • pathordevice: string
    • optargs: Umount

      a GuestfsUmount containing optional arguments

    Returns boolean

  • umountAll(): boolean
  • unmount all filesystems

    This unmounts all mounted filesystems.

    Some internal mounts are not unmounted by this call.

    Returns boolean

  • unmount a locally mounted filesystem

    If libguestfs is exporting the filesystem on a local mountpoint, then this unmounts it.

    See "MOUNT LOCAL" in guestfs(3) for full documentation.

    Parameters

    • optargs: UmountLocal

      a GuestfsUmountLocal containing optional arguments

    Returns boolean

  • unref(): void
  • Decreases the reference count of object. When its reference count drops to 0, the object is finalized (i.e. its memory is freed).

    If the pointer to the #GObject may be reused in future (for example, if it is an instance variable of another object), it is recommended to clear the pointer to %NULL rather than retain a dangling pointer to a potentially invalid #GObject instance. Use g_clear_object() for this.

    Returns void

  • upload(filename: string, remotefilename: string, cancellable: Gio.Cancellable): boolean
  • upload a file from the local machine

    Upload local file filename to remotefilename on the filesystem.

    filename can also be a named pipe.

    See also guestfs_session_download().

    Parameters

    • filename: string
    • remotefilename: string
    • cancellable: Gio.Cancellable

      A GCancellable object

    Returns boolean

  • uploadOffset(filename: string, remotefilename: string, offset: number, cancellable: Gio.Cancellable): boolean
  • upload a file from the local machine with offset

    Upload local file filename to remotefilename on the filesystem.

    remotefilename is overwritten starting at the byte offset specified. The intention is to overwrite parts of existing files or devices, although if a non-existent file is specified then it is created with a "hole" before offset. The size of the data written is implicit in the size of the source filename.

    Note that there is no limit on the amount of data that can be uploaded with this call, unlike with guestfs_session_pwrite(), and this call always writes the full amount unless an error occurs.

    See also guestfs_session_upload(), guestfs_session_pwrite().

    Parameters

    • filename: string
    • remotefilename: string
    • offset: number
    • cancellable: Gio.Cancellable

      A GCancellable object

    Returns boolean

  • userCancel(): boolean
  • cancel the current upload or download operation

    This function cancels the current upload or download operation.

    Unlike most other libguestfs calls, this function is signal safe and thread safe. You can call it from a signal handler or from another thread, without needing to do any locking.

    The transfer that was in progress (if there is one) will stop shortly afterwards, and will return an error. The errno (see "guestfs_last_errno") is set to EINTR, so you can test for this to find out if the operation was cancelled or failed because of another error.

    No cleanup is performed: for example, if a file was being uploaded then after cancellation there may be a partially uploaded file. It is the caller’s responsibility to clean up if necessary.

    There are two common places that you might call guestfs_session_user_cancel():

    In an interactive text-based program, you might call it from a SIGINT signal handler so that pressing "^C" cancels the current operation. (You also need to call "guestfs_set_pgroup" so that child processes don't receive the "^C" signal).

    In a graphical program, when the main thread is displaying a progress bar with a cancel button, wire up the cancel button to call this function.

    Returns boolean

  • utimens(path: string, atsecs: number, atnsecs: number, mtsecs: number, mtnsecs: number): boolean
  • set timestamp of a file with nanosecond precision

    This command sets the timestamps of a file with nanosecond precision.

    "atsecs, atnsecs" are the last access time (atime) in secs and nanoseconds from the epoch.

    "mtsecs, mtnsecs" are the last modification time (mtime) in secs and nanoseconds from the epoch.

    If the *nsecs field contains the special value -1 then the corresponding timestamp is set to the current time. (The *secs field is ignored in this case).

    If the *nsecs field contains the special value -2 then the corresponding timestamp is left unchanged. (The *secs field is ignored in this case).

    Parameters

    • path: string
    • atsecs: number
    • atnsecs: number
    • mtsecs: number
    • mtnsecs: number

    Returns boolean

  • appliance kernel version

    This returns the kernel version of the appliance, where this is available. This information is only useful for debugging. Nothing in the returned structure is defined by the API.

    Returns UTSName

  • get the library version number

    Return the libguestfs version number that the program is linked against.

    Note that because of dynamic linking this is not necessarily the version of libguestfs that you compiled against. You can compile the program, and then at runtime dynamically link against a completely different libguestfs.so library.

    This call was added in version 1.0.58. In previous versions of libguestfs there was no way to get the version number. From C code you can use dynamic linker functions to find out if this symbol exists (if it doesn't, then it’s an earlier version).

    The call returns a structure with four elements. The first three (major, minor and release) are numbers and correspond to the usual version triplet. The fourth element (extra) is a string and is normally empty, but may be used for distro-specific information.

    To construct the original version string: "$major.$minor.$release$extra"

    See also: "LIBGUESTFS VERSION NUMBERS" in guestfs(3).

    Note: Don't use this call to test for availability of features. In enterprise distributions we backport features from later versions into earlier versions, making this an unreliable way to test for features. Use guestfs_session_available() or guestfs_session_feature_available() instead.

    Returns Version

  • vfsLabel(mountable: string): string
  • get the filesystem label

    This returns the label of the filesystem on mountable.

    If the filesystem is unlabeled, this returns the empty string.

    To find a filesystem from the label, use guestfs_session_findfs_label().

    Parameters

    • mountable: string

    Returns string

  • vfsMinimumSize(mountable: string): number
  • get minimum filesystem size

    Get the minimum size of filesystem in bytes. This is the minimum possible size for filesystem shrinking.

    If getting minimum size of specified filesystem is not supported, this will fail and set errno as ENOTSUP.

    See also ntfsresize(8), resize2fs(8), btrfs(8), xfs_info(8).

    Parameters

    • mountable: string

    Returns number

  • vfsType(mountable: string): string
  • get the Linux VFS type corresponding to a mounted device

    This command gets the filesystem type corresponding to the filesystem on mountable.

    For most filesystems, the result is the name of the Linux VFS module which would be used to mount this filesystem if you mounted it without specifying the filesystem type. For example a string such as ext3 or ntfs.

    Parameters

    • mountable: string

    Returns string

  • vfsUuid(mountable: string): string
  • get the filesystem UUID

    This returns the filesystem UUID of the filesystem on mountable.

    If the filesystem does not have a UUID, this returns the empty string.

    To find a filesystem from the UUID, use guestfs_session_findfs_uuid().

    Parameters

    • mountable: string

    Returns string

  • vgActivate(activate: boolean, volgroups: string[]): boolean
  • activate or deactivate some volume groups

    This command activates or (if activate is false) deactivates all logical volumes in the listed volume groups volgroups.

    This command is the same as running "vgchange -a y|n volgroups..."

    Note that if volgroups is an empty list then all volume groups are activated or deactivated.

    This function depends on the feature "lvm2". See also guestfs_session_feature_available().

    Parameters

    • activate: boolean
    • volgroups: string[]

      an array of strings

    Returns boolean

  • vgActivateAll(activate: boolean): boolean
  • activate or deactivate all volume groups

    This command activates or (if activate is false) deactivates all logical volumes in all volume groups.

    This command is the same as running "vgchange -a y|n"

    This function depends on the feature "lvm2". See also guestfs_session_feature_available().

    Parameters

    • activate: boolean

    Returns boolean

  • vgchangeUuid(vg: string): boolean
  • generate a new random UUID for a volume group

    Generate a new random UUID for the volume group vg.

    This function depends on the feature "lvm2". See also guestfs_session_feature_available().

    Parameters

    • vg: string

    Returns boolean

  • vgchangeUuidAll(): boolean
  • generate new random UUIDs for all volume groups

    Generate new random UUIDs for all volume groups.

    This function depends on the feature "lvm2". See also guestfs_session_feature_available().

    Returns boolean

  • vgcreate(volgroup: string, physvols: string[]): boolean
  • create an LVM volume group

    This creates an LVM volume group called volgroup from the non-empty list of physical volumes physvols.

    This function depends on the feature "lvm2". See also guestfs_session_feature_available().

    Parameters

    • volgroup: string
    • physvols: string[]

      an array of strings

    Returns boolean

  • vglvuuids(vgname: string): string[]
  • get the LV UUIDs of all LVs in the volume group

    Given a VG called vgname, this returns the UUIDs of all the logical volumes created in this volume group.

    You can use this along with guestfs_session_lvs() and guestfs_session_lvuuid() calls to associate logical volumes and volume groups.

    See also guestfs_session_vgpvuuids().

    Parameters

    • vgname: string

    Returns string[]

  • vgmeta(vgname: string): Uint8Array
  • get volume group metadata

    vgname is an LVM volume group. This command examines the volume group and returns its metadata.

    Note that the metadata is an internal structure used by LVM, subject to change at any time, and is provided for information only.

    This function depends on the feature "lvm2". See also guestfs_session_feature_available().

    Parameters

    • vgname: string

    Returns Uint8Array

  • vgpvuuids(vgname: string): string[]
  • get the PV UUIDs containing the volume group

    Given a VG called vgname, this returns the UUIDs of all the physical volumes that this volume group resides on.

    You can use this along with guestfs_session_pvs() and guestfs_session_pvuuid() calls to associate physical volumes and volume groups.

    See also guestfs_session_vglvuuids().

    Parameters

    • vgname: string

    Returns string[]

  • vgremove(vgname: string): boolean
  • remove an LVM volume group

    Remove an LVM volume group vgname, (for example VG).

    This also forcibly removes all logical volumes in the volume group (if any).

    This function depends on the feature "lvm2". See also guestfs_session_feature_available().

    Parameters

    • vgname: string

    Returns boolean

  • vgrename(volgroup: string, newvolgroup: string): boolean
  • rename an LVM volume group

    Rename a volume group volgroup with the new name newvolgroup.

    Parameters

    • volgroup: string
    • newvolgroup: string

    Returns boolean

  • vgs(): string[]
  • list the LVM volume groups (VGs)

    List all the volumes groups detected. This is the equivalent of the vgs(8) command.

    This returns a list of just the volume group names that were detected (eg. VolGroup00).

    See also guestfs_session_vgs_full().

    This function depends on the feature "lvm2". See also guestfs_session_feature_available().

    Returns string[]

  • vgsFull(): VG[]
  • list the LVM volume groups (VGs)

    List all the volumes groups detected. This is the equivalent of the vgs(8) command. The "full" version includes all fields.

    This function depends on the feature "lvm2". See also guestfs_session_feature_available().

    Returns VG[]

  • vgscan(): boolean
  • rescan for LVM physical volumes, volume groups and logical volumes

    This rescans all block devices and rebuilds the list of LVM physical volumes, volume groups and logical volumes.

    Returns boolean

  • vguuid(vgname: string): string
  • get the UUID of a volume group

    This command returns the UUID of the LVM VG named vgname.

    Parameters

    • vgname: string

    Returns string

  • waitReady(): boolean
  • wait until the hypervisor launches (no op)

    This function is a no op.

    In versions of the API < 1.0.71 you had to call this function just after calling guestfs_session_launch() to wait for the launch to complete. However this is no longer necessary because guestfs_session_launch() now does the waiting.

    If you see any calls to this function in code then you can just remove them, unless you want to retain compatibility with older versions of the API.

    Returns boolean

  • watchClosure(closure: TClosure<any, any>): void
  • This function essentially limits the life time of the closure to the life time of the object. That is, when the object is finalized, the closure is invalidated by calling g_closure_invalidate() on it, in order to prevent invocations of the closure with a finalized (nonexisting) object. Also, g_object_ref() and g_object_unref() are added as marshal guards to the closure, to ensure that an extra reference count is held on object during invocation of the closure. Usually, this function will be called on closures that use this object as closure data.

    Parameters

    • closure: TClosure<any, any>

      #GClosure to watch

    Returns void

  • wcC(path: string): number
  • count characters in a file

    This command counts the characters in a file, using the "wc -c" external command.

    Parameters

    • path: string

    Returns number

  • wcL(path: string): number
  • count lines in a file

    This command counts the lines in a file, using the "wc -l" external command.

    Parameters

    • path: string

    Returns number

  • wcW(path: string): number
  • count words in a file

    This command counts the words in a file, using the "wc -w" external command.

    Parameters

    • path: string

    Returns number

  • wipefs(device: string): boolean
  • wipe a filesystem signature from a device

    This command erases filesystem or RAID signatures from the specified device to make the filesystem invisible to libblkid.

    This does not erase the filesystem itself nor any other data from the device.

    Compare with guestfs_session_zero() which zeroes the first few blocks of a device.

    This function depends on the feature "wipefs". See also guestfs_session_feature_available().

    Parameters

    • device: string

    Returns boolean

  • write(path: string, content: Uint8Array): boolean
  • create a new file

    This call creates a file called path. The content of the file is the string content (which can contain any 8 bit data).

    See also guestfs_session_write_append().

    Parameters

    • path: string
    • content: Uint8Array

      an array of binary data

    Returns boolean

  • writeAppend(path: string, content: Uint8Array): boolean
  • append content to end of file

    This call appends content to the end of file path. If path does not exist, then a new file is created.

    See also guestfs_session_write().

    Parameters

    • path: string
    • content: Uint8Array

      an array of binary data

    Returns boolean

  • writeFile(path: string, content: string, size: number): boolean
  • create a file

    This call creates a file called path. The contents of the file is the string content (which can contain any 8 bit data), with length size.

    As a special case, if size is 0 then the length is calculated using strlen (so in this case the content cannot contain embedded ASCII NULs).

    NB. Owing to a bug, writing content containing ASCII NUL characters does not work, even if the length is specified.

    Parameters

    • path: string
    • content: string
    • size: number

    Returns boolean

  • xfsAdmin(device: string, optargs: XfsAdmin): boolean
  • change parameters of an XFS filesystem

    Change the parameters of the XFS filesystem on device.

    Devices that are mounted cannot be modified. Administrators must unmount filesystems before this call can modify parameters.

    Some of the parameters of a mounted filesystem can be examined and modified using the guestfs_session_xfs_info() and guestfs_session_xfs_growfs() calls.

    This function depends on the feature "xfs". See also guestfs_session_feature_available().

    Parameters

    • device: string
    • optargs: XfsAdmin

      a GuestfsXfsAdmin containing optional arguments

    Returns boolean

  • xfsGrowfs(path: string, optargs: XfsGrowfs): boolean
  • expand an existing XFS filesystem

    Grow the XFS filesystem mounted at path.

    The returned struct contains geometry information. Missing fields are returned as -1 (for numeric fields) or empty string.

    This function depends on the feature "xfs". See also guestfs_session_feature_available().

    Parameters

    • path: string
    • optargs: XfsGrowfs

      a GuestfsXfsGrowfs containing optional arguments

    Returns boolean

  • xfsInfo(pathordevice: string): XFSInfo
  • get geometry of XFS filesystem

    pathordevice is a mounted XFS filesystem or a device containing an XFS filesystem. This command returns the geometry of the filesystem.

    The returned struct contains geometry information. Missing fields are returned as -1 (for numeric fields) or empty string.

    This function depends on the feature "xfs". See also guestfs_session_feature_available().

    Parameters

    • pathordevice: string

    Returns XFSInfo

  • xfsRepair(device: string, optargs: XfsRepair): number
  • repair an XFS filesystem

    Repair corrupt or damaged XFS filesystem on device.

    The filesystem is specified using the device argument which should be the device name of the disk partition or volume containing the filesystem. If given the name of a block device, xfs_repair will attempt to find the raw device associated with the specified block device and will use the raw device instead.

    Regardless, the filesystem to be repaired must be unmounted, otherwise, the resulting filesystem may be inconsistent or corrupt.

    The returned status indicates whether filesystem corruption was detected (returns 1) or was not detected (returns 0).

    This function depends on the feature "xfs". See also guestfs_session_feature_available().

    Parameters

    • device: string
    • optargs: XfsRepair

      a GuestfsXfsRepair containing optional arguments

    Returns number

  • yaraDestroy(): boolean
  • destroy previously loaded yara rules

    Destroy previously loaded Yara rules in order to free libguestfs resources.

    This function depends on the feature "libyara". See also guestfs_session_feature_available().

    Returns boolean

  • load yara rules within libguestfs

    Upload a set of Yara rules from local file filename.

    Yara rules allow to categorize files based on textual or binary patterns within their content. See guestfs_session_yara_scan() to see how to scan files with the loaded rules.

    Rules can be in binary format, as when compiled with yarac command, or in source code format. In the latter case, the rules will be first compiled and then loaded.

    Rules in source code format cannot include external files. In such cases, it is recommended to compile them first.

    Previously loaded rules will be destroyed.

    This function depends on the feature "libyara". See also guestfs_session_feature_available().

    Parameters

    Returns boolean

  • scan a file with the loaded yara rules

    Scan a file with the previously loaded Yara rules.

    For each matching rule, a yara_detection structure is returned.

    The yara_detection structure contains the following fields.

    yara_name Path of the file matching a Yara rule.

    yara_rule Identifier of the Yara rule which matched against the given file.

    This function depends on the feature "libyara". See also guestfs_session_feature_available().

    Parameters

    Returns YaraDetection[]

  • zegrep(regex: string, path: string): string[]
  • return lines matching a pattern

    This calls the external zegrep program and returns the matching lines.

    Parameters

    • regex: string
    • path: string

    Returns string[]

  • zegrepi(regex: string, path: string): string[]
  • return lines matching a pattern

    This calls the external "zegrep -i" program and returns the matching lines.

    Parameters

    • regex: string
    • path: string

    Returns string[]

  • zero(device: string): boolean
  • write zeroes to the device

    This command writes zeroes over the first few blocks of device.

    How many blocks are zeroed isn't specified (but it’s not enough to securely wipe the device). It should be sufficient to remove any partition tables, filesystem superblocks and so on.

    If blocks are already zero, then this command avoids writing zeroes. This prevents the underlying device from becoming non-sparse or growing unnecessarily.

    See also: guestfs_session_zero_device(), guestfs_session_scrub_device(), guestfs_session_is_zero_device()

    Parameters

    • device: string

    Returns boolean

  • zeroDevice(device: string): boolean
  • write zeroes to an entire device

    This command writes zeroes over the entire device. Compare with guestfs_session_zero() which just zeroes the first few blocks of a device.

    If blocks are already zero, then this command avoids writing zeroes. This prevents the underlying device from becoming non-sparse or growing unnecessarily.

    Parameters

    • device: string

    Returns boolean

  • zeroFreeSpace(directory: string): boolean
  • zero free space in a filesystem

    Zero the free space in the filesystem mounted on directory. The filesystem must be mounted read-write.

    The filesystem contents are not affected, but any free space in the filesystem is freed.

    Free space is not "trimmed". You may want to call guestfs_session_fstrim() either as an alternative to this, or after calling this, depending on your requirements.

    Parameters

    • directory: string

    Returns boolean

  • zerofree(device: string): boolean
  • zero unused inodes and disk blocks on ext2/3 filesystem

    This runs the zerofree program on device. This program claims to zero unused inodes and disk blocks on an ext2/3 filesystem, thus making it possible to compress the filesystem more effectively.

    You should not run this program if the filesystem is mounted.

    It is possible that using this program can damage the filesystem or data on the filesystem.

    This function depends on the feature "zerofree". See also guestfs_session_feature_available().

    Parameters

    • device: string

    Returns boolean

  • zfgrep(pattern: string, path: string): string[]
  • return lines matching a pattern

    This calls the external zfgrep program and returns the matching lines.

    Parameters

    • pattern: string
    • path: string

    Returns string[]

  • zfgrepi(pattern: string, path: string): string[]
  • return lines matching a pattern

    This calls the external "zfgrep -i" program and returns the matching lines.

    Parameters

    • pattern: string
    • path: string

    Returns string[]

  • zfile(meth: string, path: string): string
  • determine file type inside a compressed file

    This command runs file after first decompressing path using method.

    method must be one of gzip, compress or bzip2.

    Since 1.0.63, use guestfs_session_file() instead which can now process compressed files.

    Parameters

    • meth: string
    • path: string

    Returns string

  • zgrep(regex: string, path: string): string[]
  • return lines matching a pattern

    This calls the external zgrep program and returns the matching lines.

    Parameters

    • regex: string
    • path: string

    Returns string[]

  • zgrepi(regex: string, path: string): string[]
  • return lines matching a pattern

    This calls the external "zgrep -i" program and returns the matching lines.

    Parameters

    • regex: string
    • path: string

    Returns string[]

  • compatControl(what: number, data: object): number
  • Find the #GParamSpec with the given name for an interface. Generally, the interface vtable passed in as g_iface will be the default vtable from g_type_default_interface_ref(), or, if you know the interface has already been loaded, g_type_default_interface_peek().

    Parameters

    • gIface: TypeInterface

      any interface vtable for the interface, or the default vtable for the interface

    • propertyName: string

      name of a property to look up.

    Returns ParamSpec

  • Add a property to an interface; this is only useful for interfaces that are added to GObject-derived types. Adding a property to an interface forces all objects classes with that interface to have a compatible property. The compatible property could be a newly created #GParamSpec, but normally g_object_class_override_property() will be used so that the object class only needs to provide an implementation and inherits the property description, default value, bounds, and so forth from the interface property.

    This function is meant to be called from the interface's default vtable initialization function (the class_init member of #GTypeInfo.) It must not be called after after class_init has been called for any object types implementing this interface.

    If pspec is a floating reference, it will be consumed.

    Parameters

    • gIface: TypeInterface

      any interface vtable for the interface, or the default vtable for the interface.

    • pspec: ParamSpec

      the #GParamSpec for the new property

    Returns void

  • Lists the properties of an interface.Generally, the interface vtable passed in as g_iface will be the default vtable from g_type_default_interface_ref(), or, if you know the interface has already been loaded, g_type_default_interface_peek().

    Parameters

    • gIface: TypeInterface

      any interface vtable for the interface, or the default vtable for the interface

    Returns ParamSpec[]

  • Creates a new instance of a #GObject subtype and sets its properties.

    Construction parameters (see %G_PARAM_CONSTRUCT, %G_PARAM_CONSTRUCT_ONLY) which are not explicitly specified are set to their default values.

    Parameters

    • objectType: GType<unknown>

      the type id of the #GObject subtype to instantiate

    • parameters: GObject.Parameter[]

      an array of #GParameter

    Returns GObject.Object

Legend

  • Module
  • Object literal
  • Variable
  • Function
  • Function with type parameter
  • Index signature
  • Type alias
  • Type alias with type parameter
  • Enumeration
  • Enumeration member
  • Property
  • Method
  • Interface
  • Interface with type parameter
  • Constructor
  • Property
  • Method
  • Index signature
  • Class
  • Class with type parameter
  • Constructor
  • Property
  • Method
  • Accessor
  • Index signature
  • Inherited constructor
  • Inherited property
  • Inherited method
  • Inherited accessor
  • Protected property
  • Protected method
  • Protected accessor
  • Private property
  • Private method
  • Private accessor
  • Static property
  • Static method