Provided by: libguestfs-tools_1.32.2-4ubuntu2_amd64 bug


       virt-tar - 仮想マシンへのファイルの展開またはアップロード


        virt-tar [--options] -x domname directory tarball

        virt-tar [--options] -u domname tarball directory

        virt-tar [--options] disk.img [disk.img ...] -x directory tarball

        virt-tar [--options] disk.img [disk.img ...] -u tarball directory


       このツールは推奨されません。  代わりに virt-copy-in(1), virt-copy-out(1), virt-tar-in(1),
       virt-tar-out(1) を使用してください。

       仮想マシンから "/home" をローカルの tar ファイルにダウンロードします:

        virt-tar -x domname /home home.tar

        virt-tar -zx domname /home home.tar.gz

       ローカルの tar ファイルをアップロードして、仮想マシンの "/tmp" に展開します:

        virt-tar -u domname uploadstuff.tar /tmp

        virt-tar -zu domname uploadstuff.tar.gz /tmp


       You must not use "virt-tar" with the -u option (upload) on live virtual machines.  If you
       do this, you risk disk corruption in the VM.  "virt-tar" tries to stop you from doing
       this, but doesn't catch all cases.

       You can use -x (extract) on live virtual machines, but you might get inconsistent results
       or errors if there is filesystem activity inside the VM.  If the live VM is synched and
       quiescent, then "virt-tar" will usually work, but the only way to guarantee consistent
       results is if the virtual machine is shut down.


       "virt-tar" is a general purpose archive tool for downloading and uploading parts of a
       guest filesystem.  There are many possibilities: making backups, uploading data files,
       snooping on guest activity, fixing or customizing guests, etc.

       If you want to just view a single file, use virt-cat(1).  If you just want to edit a
       single file, use virt-edit(1).  For more complex cases you should look at the guestfish(1)

       There are two modes of operation: -x (eXtract) downloads a directory and its contents
       (recursively) from the virtual machine into a local tarball.  -u uploads from a local
       tarball, unpacking it into a directory inside the virtual machine.  You cannot use these
       two options together.

       In addition, you may need to use the -z (gZip) option to enable compression.  When
       uploading, you have to specify -z if the upload file is compressed because virt-tar won't
       detect this on its own.

       "virt-tar" can only handle tar (optionally gzipped) format tarballs.  For example it
       cannot do PKZip files or bzip2 compression.  If you want that then you'll have to rebuild
       the tarballs yourself.  (This is a limitation of the libguestfs(3) API).




       -c URI
       --connect URI
           libvirt を使用していると、指定された URI に接続します。  省略すると、デフォルトの
           libvirt ハイパーバイザーに接続します。

           仮想マシンのブロックデバイスを直接指定すると、libvirt はまったく使用されません。

       --format raw
           Specify the format of disk images given on the command line.  If this is omitted then
           the format is autodetected from the content of the disk image.

           If disk images are requested from libvirt, then this program asks libvirt for this
           information.  In this case, the value of the format parameter is ignored.

           If working with untrusted raw-format guest disk images, you should ensure the format
           is always specified.

           仮想マシンからローカル tar ファイルにディレクトリを展開 (ダウンロード) するには -x を

           ローカル tar ファイルから仮想マシンの中にアップロードおよび展開するには -u を使用しま
           す。このオプションを使用する前に "警告" セクションを参照してください。


           入力または出力 tar ファイルを gzip 圧縮するよう指定します。


       guestfs(3), guestfish(1), virt-cat(1), virt-edit(1), virt-copy-in(1), virt-copy-out(1),
       virt-tar-in(1), virt-tar-out(1), Sys::Guestfs(3), Sys::Virt(3),


       Richard W.M. Jones


       Copyright (C) 2009 Red Hat Inc.



       To get a list of bugs against libguestfs, use this link:

       To report a new bug against libguestfs, use this link:

       When reporting a bug, please supply:

       •   The version of libguestfs.

       •   Where you got libguestfs (eg. which Linux distro, compiled from source, etc)

       •   Describe the bug accurately and give a way to reproduce it.

       •   Run libguestfs-test-tool(1) and paste the complete, unedited output into the bug