Re: [Libguestfs] Can I use virt-filesystem on a running VM?
by Richard W.M. Jones
On Mon, Jan 11, 2021 at 12:04:22PM -0300, Sergio Belkin wrote:
>
>
> El lun, 11 ene 2021 a las 6:41, Richard W.M. Jones (<rjones(a)redhat.com>)
> escribió:
>
> On Sat, Jan 09, 2021 at 05:23:13PM -0300, Sergio Belkin wrote:
> > So do you think that is a SELinux issue (I haven't found anything
> > related to this with ausearch or audit logs)? So, can
> > virt-filesystems crash the guest? (I had to reboot and repair the
> > xfs)
>
> It's not that virt-filesystems is affecting the guest, it's that
> libvirtd relabels the disks and as a result original qemu loses access
> to its disks.
>
> Try with LIBGUESTFS_BACKEND=direct which doesn't use libvirt or
> SELinux labelling.
>
> Rich.
>
> --
> Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/
> ~rjones
> Read my programming and virtualization blog: http://rwmj.wordpress.com
> libguestfs lets you edit virtual machines. Supports shell scripting,
> bindings from many languages. http://libguestfs.org
>
>
>
> Hi Richard, thanks for your kind explanation and help. It worked like a charm.
>
> In case it becomes useful to someone, I get:
>
> Name Type VFS Label MBR Size Parent UUID
> /dev/sda1 filesystem xfs - - 500M -
> 8746b377-7e21-4cb5-b269-c034720d65c1
> /dev/centos_lx0001/root filesystem xfs - - 48G -
> 3a3d6041-5f1c-479f-92cf-42a569d57bab
> /dev/centos_lx0001/swap filesystem swap - - 2,0G -
> 76addd8c-7aa1-4779-8a86-70ab6baca2b2
> /dev/centos_lx0001/root lv - - - 48G /dev/centos_lx0001
> 2d4fOO-fXZm-HDHi-CiTY-umH3-Icu9-peXjGZ
> /dev/centos_lx0001/swap lv - - - 2,0G /dev/centos_lx0001
> mbKcjk-YXVg-MjhS-L0IA-cNgg-KF0o-4uxvc5
> /dev/centos_lx0001 vg - - - 50G /dev/sda2
> 17HB8hKfxKZHis9Tcrq2XoFLldN0fAft
> /dev/sda2 pv - - - 50G -
> NZT8FHFBUed0PZyKsrXLWAnemghOO0J7
> /dev/sda1 partition - - 83 500M /dev/sda -
> /dev/sda2 partition - - 8e 50G /dev/sda -
> /dev/sda device - - - 50G - -
>
> Jut only a question about this output, just out of curiosity why does it print
> /dev/sda* instead /dev/vda* ?
We don't know what drivers are installed in the guest, or (in
virt-filesystems) even what the guest is. Maybe it's Linux with
virtio. Maybe it's Windows. So we use a canonical naming scheme for
devices and partitions:
https://libguestfs.org/guestfs.3.html#block-device-naming
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-top is 'top' for virtual machines. Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://people.redhat.com/~rjones/virt-top
3 years, 4 months
Nbdkit old test plugins link to selinux.so.1
by Thomas Weißschuh
Hi all,
the old 1.2.8 plugins checked into the source repo that are used for testing
the plugin are linking to libselinux.so.1.
This prevents these tests being run on distros without libselinux.
(Arch Linux in my case)
$ ldd tests/old-plugins/x86_64/Linux/v1.2.8/nbdkit-file-plugin.so
linux-vdso.so.1 (0x00007ffde31d6000)
libselinux.so.1 => not found
libc.so.6 => /usr/lib/libc.so.6 (0x00007f72139ed000)
The other old plugins don't require libselinux.
Could the 1.2.8 plugins be replaced with ones not linking to libselinux?
Thanks,
Thomas
3 years, 4 months
libnbd 1.6 build fails with Python code style error
by Thomas Weißschuh
Hi all,
the checks for libnbd 1.6 fail for me in python/pycodestyle.sh.
Log output below.
It seems the CI machine is missing the flake8 installation.
Making check in python
make[1]: Entering directory '.../python'
make check-am
make[2]: Entering directory '.../python'
make check-TESTS
make[3]: Entering directory '.../python'
make[4]: Entering directory '.../python'
FAIL: pycodestyle.sh
PASS: run-python-tests
============================================================================
Testsuite summary for libnbd 1.6.0
============================================================================
# TOTAL: 2
# PASS: 1
# SKIP: 0
# XFAIL: 0
# FAIL: 1
# XPASS: 0
# ERROR: 0
============================================================================
See python/test-suite.log
============================================================================
.../python/t/590-aio-copy.py:56:43: E211 whitespace before '('
.../t/590-aio-copy.py:57:11: E127 continuation line over-indented for visual
+indent
FAIL pycodestyle.sh (exit status: 1)
3 years, 4 months
Can I use virt-filesystem on a running VM?
by Sergio Belkin
Well, if I've run from kvm hypervisor this command with a live guest:
virt-filesystems --long -h --all -a /home/storage-plus/myvm.qcow2
It outputs:
`libguestfs: error: list_filesystems: parted exited with status 1: Error:
Can't have a partition outside the disk!`
But the very very sad of the story is that guest filesystem crashes:
ene 05 21:23:22 myvm.example.com kernel: blk_update_request: I/O error, dev
vda, sector 25652400
ene 05 21:23:22 myvm.example.com kernel: XFS (dm-0): writeback error on
sector 20430000
ene 05 21:23:22 myvm.example.com kernel: blk_update_request: I/O error, dev
vda, sector 25651200
ene 05 21:23:22 myvm.example.com kernel: XFS (dm-0): writeback error on
sector 20428800
ene 05 21:23:27 myvm.example.com kernel: blk_update_request: I/O error, dev
vda, sector 44519951
ene 05 21:23:27 myvm.example.com kernel: blk_update_request: I/O error, dev
vda, sector 44519951
ene 05 21:23:27 myvm.example.com kernel: blk_update_request: I/O error, dev
vda, sector 5222401
ene 05 21:23:27 myvm.example.com kernel: blk_update_request: I/O error, dev
vda, sector 5231568
ene 05 21:23:27 myvm.example.com kernel: blk_update_request: I/O error, dev
vda, sector 5232232
ene 05 21:23:27 myvm.example.com kernel: blk_update_request: I/O error, dev
vda, sector 5237584
ene 05 21:23:27 myvm.example.com kernel: blk_update_request: I/O error, dev
vda, sector 5262240
ene 05 21:23:27 myvm.example.com kernel: blk_update_request: I/O error, dev
vda, sector 5379440
ene 05 21:23:27 myvm.example.com kernel: XFS (dm-0): metadata I/O error in
"xlog_iodone" at daddr 0x257a20f len 64 error 5
ene 05 21:23:27 myvm.example.com kernel: XFS (dm-0):
xfs_do_force_shutdown(0x2) called from line 1238 of file fs/xfs/xfs_log.c.
Return address = ffffffffc028a840
ene 05 21:23:27 myvm.example.com kernel: XFS (dm-0): Log I/O Error
Detected. Shutting down filesystem
ene 05 21:23:27 myvm.example.com kernel: XFS (dm-0): Please umount the
filesystem and rectify the problem(s)
ene 05 21:23:27 myvm.example.com kernel: XFS (dm-0): xfs_imap_to_bp:
xfs_trans_read_buf() returned error -5.
ene 05 21:23:27 myvm.example.com kernel: XFS (dm-0): xfs_iunlink_remove:
xfs_imap_to_bp returned error -5.
ene 05 21:23:27 myvm.example.com auditd[633]: Audit daemon is suspending
logging due to previously mentioned write error
ene 05 21:23:27 myvm.example.com systemd[1]: rsyslog.service: main process
exited, code=killed, status=7/BUS
ene 05 21:23:27 myvm.example.com systemd[1]: Unit rsyslog.service entered
failed state.
ene 05 21:23:27 myvm.example.com systemd[1]: rsyslog.service failed.
ene 05 21:23:27 myvm.example.com systemd[1]: rsyslog.service holdoff time
over, scheduling restart
So did I miss something? Or is it a bug?
Software versions are:
Guest OS: CentOS Linux release 7.8.2003 (Core)
Hypervisor OS: CentOS Linux release 7.5.1804 (Core)
with:
- qemu-kvm-1.5.3-175.el7_9.1.x86_64
- libguestfs-tools-c-1.40.2-10.el7.x86_64
Thanks in advance!
--
--
Sergio Belkin
LPIC-2 Certified - http://www.lpi.org
3 years, 4 months
ANNOUNCE: libnbd 1.6 and nbdkit 1.24 released
by Richard W.M. Jones
I'm pleased to announce the release of nbdkit 1.24, a high performance
plugin-based Network Block Device (NBD) server, and libnbd 1.6, a high
performance client library.
https://en.wikipedia.org/wiki/Network_block_device
Key features of nbdkit:
* Multithreaded NBD server written in C with good performance.
* Minimal dependencies for the basic server.
* Liberal license (BSD) allows nbdkit to be linked to proprietary
libraries or included in proprietary code.
* Well-documented, simple plugin API with a stable ABI guarantee.
Lets you export “unconventional” block devices easily.
* You can write plugins in C, Go, Lua, Perl, Python, OCaml, Ruby,
Rust, shell script or Tcl.
* Filters can be stacked in front of plugins to transform the output.
Key features of libnbd:
* Synchronous API for ease of use.
* Asynchronous API for writing non-blocking, multithreaded clients.
You can mix both APIs freely.
* High performance.
* Minimal dependencies for the basic library.
* Well-documented, stable API.
* Bindings in several programming languages.
* Shell (nbdsh) for command line and scripting.
* nbdfuse, nbdinfo and nbdcopy tools
Release notes for both are attached below.
Rich.
-------
These are the release notes for nbdkit stable release 1.24. This
describes the major changes since 1.22.
nbdkit 1.24.0 was released on 7 January 2021.
Security
There were no security issues found. All past security issues and
information about how to report new ones can be found in
nbdkit-security(1).
Server
The server and a subset of the plugins and filters have been ported to
Windows using the Win32 API. Only the mingw-w64 toolchain is supported
for building nbdkit (not MSVC). You can also cross-compile from Linux
and test under Wine. Some features are missing although it is very
usable.
New -D nbdkit.tls.log and -D nbdkit.tls.session debug flags which
enable additional debugging for TLS sessions.
The server now responds to "NBD_INFO_NAME" (Eric Blake).
Options --run and --vsock may now be used together.
In --run, $nbd is now a synonym for $uri instead of having confusing
magical properties.
Plugins
New nbdkit-S3-plugin(1) to access disks stored on AWS S3 and Ceph.
New nbdkit-sparse-random-plugin(1) which generates large disks sparsely
filled with random blocks of data. These look like virtual disk images
and can be used to benchmark copying tools.
nbdkit-data-plugin(1) has been greatly enhanced. New features include:
"(...)[N:M]" (slice syntax), assignments, comments, variables,
"<(SCRIPT)" (inlined shell script). In addition a parse tree is built,
allowing optimizations and other enhancements. The plugin is now 64
bit clean allowing patterns larger than 2^32 bytes to work correctly.
nbdkit-random-plugin(1) can now be used to test copying tools.
nbdkit-vddk-plugin(1) supports enabling compression between VDDK and
the VMware server which in some situations can improve performance.
Filters
New nbdkit-exportname-filter(1) can be used to extend, mask and modify
the exports exposed by a plugin (Eric Blake).
New nbdkit-exitwhen-filter(1) allowing the server to gracefully exit on
various events including external scripts.
New nbdkit-checkwrite-filter(1) can be used to benchmark copying tools.
nbdkit-ip-filter(1) now supports filtering clients by PID, user ID or
group ID, for clients connected over a Unix domain socket. Also you
can filter clients using "AF_VSOCK" and vsock port number.
nbdkit-log-filter(1) now logs "get_ready", "after_fork" and
"preconnect" methods, and there is a new "logscript" feature allowing
scripts to be run on logging events.
nbdkit-ext2-filter(1) new option "ext2file=exportname" can be used to
allow the client to select which file to see from the filesystem using
the NBD export name (Eric Blake).
Language bindings
Python style cleanups (Eric Blake).
The OCaml plugin now correctly acquires and releases the GC lock on all
paths in and out.
There is a new OCaml "NBDKit.version" function returning the version of
nbdkit that the plugin was compiled against.
Multiple enhancements to the Rust plugin (Alan Somers).
API
New ".list_exports", ".default_export" and ".export_description" plugin
methods allowing plugins to be queried about what export names they
support, and give additional descriptions of exports. New
"nbdkit_use_default_export" helper function (Eric Blake).
New "nbdkit_strdup_intern", "nbdkit_strndup_intern"
"nbdkit_printf_intern" and "nbdkit_vprintf_intern" functions which
allow you to allocate a string in a plugin without worrying about
freeing it (Eric Blake).
New "nbdkit_peer_pid", "nbdkit_peer_uid" and "nbdkit_peer_gid" allows
plugins and filters to read the client’s credentials, for clients
connected over a Unix domain socket.
Tests
Many tests now use libnbd(3), nbdsh(1), nbdinfo(1) and nbdcopy(1) as
lighter weight replacements for qemu tools.
Fix compatibility with qemu > 5.2.0.
Build
Downstream packagers can now use this to add extra downstream
information which is printed in version strings etc:
./configure --with-extra=...
If ocamldoc(1) is installed at build time, then it will be used to
build the NBDKit(3) manual page for OCaml documentation.
SEE ALSO
nbdkit(1).
AUTHORS
Authors of nbdkit 1.24:
• Alan Somers
• Eric Blake
• Richard W.M. Jones
COPYRIGHT
Copyright (C) 2020-2021 Red Hat Inc.
LICENSE
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met:
• Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
• Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the
distribution.
• Neither the name of Red Hat nor the names of its contributors may
be used to endorse or promote products derived from this software
without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY RED HAT AND CONTRIBUTORS ''AS IS'' AND ANY
EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL RED HAT OR CONTRIBUTORS BE
LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
nbdkit-1.24.0 2021-01-07 nbdkit-release-notes-1.24(1)
-------
These are the release notes for libnbd stable release 1.6. This
describes the major changes since 1.4.
libnbd 1.6.0 was released on 7 January 2021.
Security
There were no security issues found in this release.
If you find a security issue, please read SECURITY in the source
(online here:
https://github.com/libguestfs/libnbd/blob/master/SECURITY). To find
out about previous security issues in libnbd, see libnbd-security(3).
New APIs
nbd_set_strict_mode(3)
nbd_get_strict_mode(3)
This API allows you to control how libnbd handles requests from the
program that it thinks would trigger undefined behaviour in the
server (such as sending unknown commands, zero-sized or out-of-
bounds requests, etc). Normally libnbd is very strict and will
prevent you from sending such requests, but you can use this API to
relax these restrictions, leaving it up to the server to handle or
reject them. Some servers may crash if you do this.
nbd_get_nr_meta_contexts(3)
nbd_get_meta_context(3)
nbd_clear_meta_contexts(3)
These APIs allow you to review or clear the requested metadata
contexts.
nbd_opt_list_meta_context(3)
nbd_aio_opt_list_meta_context(3)
Request that the server lists available metadata contexts. You can
only use this in opt mode.
Thanks: Eric Blake for all of the new APIs.
Enhancements to existing APIs
nbd_shutdown(3) new flag "LIBNBD_SHUTDOWN_ABANDON_PENDING" drops any
commands in flight which have not been sent to the server yet (Eric
Blake).
All APIs which have flag (bitmask) parameters now define a
"LIBNBD_*_MASK" constant allowing you to tell which bits represent
valid flags at compilation time (Eric Blake).
New features
The performance of the nbdcopy(1) tool has been greatly improved. Also
it supports numerous new features.
New nbdinfo(1) --map option showing the allocated and sparse extents of
an NBD server. This can also show other information such as dirty
bitmaps.
Tools
nbdfuse(1) can now mount the NBD export on top of any regular file, it
does not have to mount over a directory.
nbdsh(1) now produces a nice error message if the URI in the -u option
or the command in the -c option is wrong (Eric Blake).
New nbdsh(1) --opt-mode option which requests opt mode on the handle
before connecting.
nbdinfo(1) --list option now shows the supported metadata contexts of
the server (Eric Blake).
The output of nbdinfo(1) is now usually printed atomically, ie. it will
either print the complete output or an error message, but not partial
output followed by an error.
nbdinfo(1) can now decode "qemu:allocation-depth" metacontext (Eric
Blake).
Other improvements and bug fixes
Multiple improvements to handling of NBD protocol (Eric Blake).
Fix handling of booleans in Python bindings (Eric Blake).
Fix handling of flags parameters in OCaml bindings (Eric Blake).
Python style fixes (Eric Blake).
Fix multiple memory leaks (Eric Blake).
OCaml bindings now include ocamldoc-generated documentation, if
ocamldoc is installed at build time.
The "vector" library from nbdkit is now used by libnbd, simplifying
places where we used to use realloc(3).
SEE ALSO
libnbd(3).
AUTHORS
Eric Blake
Richard W.M. Jones
COPYRIGHT
Copyright (C) 2020-2021 Red Hat Inc.
LICENSE
This library is free software; you can redistribute it and/or modify it
under the terms of the GNU Lesser General Public License as published
by the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
This library is distributed in the hope that it will be useful, but
WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
Lesser General Public License for more details.
You should have received a copy of the GNU Lesser General Public
License along with this library; if not, write to the Free Software
Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA
02110-1301 USA
libnbd-1.6.0 2021-01-07 libnbd-release-notes-1.6(1)
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
Fedora Windows cross-compiler. Compile Windows programs, test, and
build Windows installers. Over 100 libraries supported.
http://fedoraproject.org/wiki/MinGW
3 years, 4 months
ANNOUNCE: libguestfs 1.44 released
by Richard W.M. Jones
This is only a small release because I wanted to get something out
before the big refactoring I'm doing this week. The release notes are
below.
Rich.
RELEASE NOTES FOR LIBGUESTFS 1.44
Language bindings
Python 2 support has been dropped. The minimum version of Python
required is 3.6.
Python bindings no longer use deprecated "PyEval_ThreadsInitialized".
Python bindings now include type hints (Sam Eiderman).
Erlang bindings now use libei instead of liberl_interface (Sergei
Golovan).
Tools
virt-get-kernel(1) can now find uncompressed kernels (Pino Toscano).
virt-sysprep(1) now regenerates the guest certificate store when a
certificate is removed from the guest (Pino Toscano).
virt-sysprep(1) can now remove IPA enrollment files and Kerberos
keytabs (Pino Toscano, Christian Heimes and François Cami).
API
New APIs
"cryptsetup-open" and "cryptsetup-close" replace "luks-open", luks-
open-ro and luks-close. The new APIs add support for BitLocker
encryption.
Other API changes
"lvm-canonical-lv" no longer produces a noisy error message when called
with a non-LV parameter.
Build changes
C programs using libguestfs can now be compiled against the build
directory:
../libguestfs/run ./configure
../libguestfs/run make
OCaml components are now linked correctly when building in a different
directory from the source (Geoff Toole).
GCC LTO is now supported.
Weblate is now used for localization instead of Zanata (Pino Toscano).
The dependencies for guestfsd are no longer hard-coded but are now
generated from the built binary, ensuring that they shouldn't get out
of synch in future (Hilko Bengen).
Internals
lib/guestfs.h was moved to include/guestfs.h in the source. This is
not an externally visible change but affected a lot of places inside
the build system.
Bugs fixed
https://bugzilla.redhat.com/1811539
The virt-diff command doesn't work on windows 2019 image
https://bugzilla.redhat.com/1384241
The tar-in command does not allow restoring file capabilities
SEE ALSO
guestfs-examples(1), guestfs-faq(1), guestfs-performance(1),
guestfs-recipes(1), guestfs-testing(1), guestfs(3), guestfish(1),
http://libguestfs.org/
AUTHORS
· Andrey Shinkevich
· Dmitry Tantsur
· Geoff Toole
· Hilko Bengen
· Pino Toscano
· Richard W.M. Jones
· Sam Eiderman
· Sergei Golovan
· Thierry Vignaud
· Yuri Chornoivan
COPYRIGHT
Copyright (C) 2009-2021 Red Hat Inc.
LICENSE
This program is free software; you can redistribute it and/or modify it
under the terms of the GNU General Public License as published by the
Free Software Foundation; either version 2 of the License, or (at your
option) any later version.
This program is distributed in the hope that it will be useful, but
WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
General Public License for more details.
You should have received a copy of the GNU General Public License along
with this program; if not, write to the Free Software Foundation, Inc.,
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
BUGS
To get a list of bugs against libguestfs, use this link:
https://bugzilla.redhat.com/buglist.cgi?component=libguestfs&product=Virt...
To report a new bug against libguestfs, use this link:
https://bugzilla.redhat.com/enter_bug.cgi?component=libguestfs&product=Vi...
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 report.
libguestfs-1.44.0 2021-01-05 guestfs-release-notes-1.44(1)
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-builder quickly builds VMs from scratch
http://libguestfs.org/virt-builder.1.html
3 years, 4 months
Trying to use libnguestfs for a virtual machine on manjaro
by James Swartz
Hello, I'm trying to follow a million and one guides online so that I can enable GPU passthrough and get a virtual machine running for windows so I can just open that window to game. Right now I'm experiencing two issues, virtual machine manager is complaining about libguestfs, and the guest machine runs really slowly, while only outputting as a window on my host machine, but only displaying a weird firmware thing on the gpu output. Ill answer the questions below, and then paste the output from libguestfs-test-tool at the end.
Thanks!
jamess7995(a)pm.me
James S.
What are you trying to do?
Run a virtual machine of windows on Manjaro
What exact command(s) did you run?
I installed using the gui package manager(pamac) on manjaro, I'm just opening the virtual machine manager to see the error.
What was the precise error or output of these commands?
[image]
Enable debugging, run the commands again, and capture the complete output, do not edit the output.
Basically got no output if that's all I was supposed to run
[james@jamesbuild1 ~]$ export LIBGUESTFS_DEBUG=1
[james@jamesbuild1 ~]$ export LIBGUESTFS_DEBUG=1
[james@jamesbuild1 ~]$ export LIBGUESTFS_DEBUG=1 LIBGUESTFS_TRACE=1
[james@jamesbuild1 ~]$ export LIBGUESTFS_DEBUG=1 LIBGUESTFS_TRACE=1
[james@jamesbuild1 ~]$
Include the version of libguestfs, the operating system version, and how you installed libguestfs (eg. from source, yum install, etc.)
libguestfs 1.42.0-4 on Manjaro 5.10.0-1
Output of libguestfs-test-tool
************************************************************
* IMPORTANT NOTICE
*
* When reporting bugs, include the COMPLETE, UNEDITED
* output below in your bug report.
*
************************************************************
libguestfs: trace: set_verbose true
libguestfs: trace: set_verbose = 0
libguestfs: trace: set_verbose true
libguestfs: trace: set_verbose = 0
LIBGUESTFS_TRACE=1
LIBGUESTFS_DEBUG=1
PATH=/home/james/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl:/var/lib/snapd/snap/bin
XDG_RUNTIME_DIR=/run/user/1000
SELinux: sh: getenforce: command not found
libguestfs: trace: add_drive_scratch 104857600
libguestfs: trace: get_tmpdir
libguestfs: trace: get_tmpdir = "/tmp"
libguestfs: trace: disk_create "/tmp/libguestfsvE2Jy4/scratch1.img" "raw" 104857600
libguestfs: trace: disk_create = 0
libguestfs: trace: add_drive "/tmp/libguestfsvE2Jy4/scratch1.img" "format:raw" "cachemode:unsafe"
libguestfs: trace: add_drive = 0
libguestfs: trace: add_drive_scratch = 0
libguestfs: trace: get_append
libguestfs: trace: get_append = "NULL"
guestfs_get_append: (null)
libguestfs: trace: get_autosync
libguestfs: trace: get_autosync = 1
guestfs_get_autosync: 1
libguestfs: trace: get_backend
libguestfs: trace: get_backend = "direct"
guestfs_get_backend: direct
libguestfs: trace: get_backend_settings
libguestfs: trace: get_backend_settings = []
guestfs_get_backend_settings: []
libguestfs: trace: get_cachedir
libguestfs: trace: get_cachedir = "/var/tmp"
guestfs_get_cachedir: /var/tmp
libguestfs: trace: get_hv
libguestfs: trace: get_hv = "/usr/bin/qemu-system-x86_64"
guestfs_get_hv: /usr/bin/qemu-system-x86_64
libguestfs: trace: get_memsize
libguestfs: trace: get_memsize = 768
guestfs_get_memsize: 768
libguestfs: trace: get_network
libguestfs: trace: get_network = 0
guestfs_get_network: 0
libguestfs: trace: get_path
libguestfs: trace: get_path = "/usr/lib/guestfs"
guestfs_get_path: /usr/lib/guestfs
libguestfs: trace: get_pgroup
libguestfs: trace: get_pgroup = 0
guestfs_get_pgroup: 0
libguestfs: trace: get_program
libguestfs: trace: get_program = "libguestfs-test-tool"
guestfs_get_program: libguestfs-test-tool
libguestfs: trace: get_recovery_proc
libguestfs: trace: get_recovery_proc = 1
guestfs_get_recovery_proc: 1
libguestfs: trace: get_smp
libguestfs: trace: get_smp = 1
guestfs_get_smp: 1
libguestfs: trace: get_sockdir
libguestfs: trace: get_sockdir = "/run/user/1000"
guestfs_get_sockdir: /run/user/1000
libguestfs: trace: get_tmpdir
libguestfs: trace: get_tmpdir = "/tmp"
guestfs_get_tmpdir: /tmp
libguestfs: trace: get_trace
libguestfs: trace: get_trace = 1
guestfs_get_trace: 1
libguestfs: trace: get_verbose
libguestfs: trace: get_verbose = 1
guestfs_get_verbose: 1
host_cpu: x86_64
Launching appliance, timeout set to 600 seconds.
libguestfs: trace: launch
libguestfs: trace: max_disks
libguestfs: trace: max_disks = 255
libguestfs: trace: version
libguestfs: trace: version = <struct guestfs_version = major: 1, minor: 42, release: 0, extra: , >
libguestfs: trace: get_backend
libguestfs: trace: get_backend = "direct"
libguestfs: launch: program=libguestfs-test-tool
libguestfs: launch: version=1.42.0
libguestfs: launch: backend registered: unix
libguestfs: launch: backend registered: uml
libguestfs: launch: backend registered: libvirt
libguestfs: launch: backend registered: direct
libguestfs: launch: backend=direct
libguestfs: launch: tmpdir=/tmp/libguestfsvE2Jy4
libguestfs: launch: umask=0022
libguestfs: launch: euid=1000
libguestfs: trace: get_cachedir
libguestfs: trace: get_cachedir = "/var/tmp"
libguestfs: begin building supermin appliance
libguestfs: run supermin
libguestfs: command: run: /usr/bin/supermin
libguestfs: command: run: \ --build
libguestfs: command: run: \ --verbose
libguestfs: command: run: \ --if-newer
libguestfs: command: run: \ --lock /var/tmp/.guestfs-1000/lock
libguestfs: command: run: \ --copy-kernel
libguestfs: command: run: \ -f ext2
libguestfs: command: run: \ --host-cpu x86_64
libguestfs: command: run: \ /usr/lib/guestfs/supermin.d
libguestfs: command: run: \ -o /var/tmp/.guestfs-1000/appliance.d
supermin: version: 5.2.0
supermin: package handler: arch/pacman
supermin: acquiring lock on /var/tmp/.guestfs-1000/lock
supermin: build: /usr/lib/guestfs/supermin.d
supermin: reading the supermin appliance
supermin: build: visiting /usr/lib/guestfs/supermin.d/base.tar.gz type gzip base image (tar)
supermin: build: visiting /usr/lib/guestfs/supermin.d/daemon.tar.gz type gzip base image (tar)
supermin: build: visiting /usr/lib/guestfs/supermin.d/excludefiles type uncompressed excludefiles
supermin: build: visiting /usr/lib/guestfs/supermin.d/hostfiles type uncompressed hostfiles
supermin: build: visiting /usr/lib/guestfs/supermin.d/init.tar.gz type gzip base image (tar)
supermin: build: visiting /usr/lib/guestfs/supermin.d/packages type uncompressed packages
supermin: build: visiting /usr/lib/guestfs/supermin.d/udev-rules.tar.gz type gzip base image (tar)
supermin: mapping package names to installed packages
supermin: resolving full list of package dependencies
supermin: failure: failed to parse epoch:version-release field 29-1.0
libguestfs: error: /usr/bin/supermin exited with error status 1, see debug messages above
libguestfs: trace: launch = -1 (error)
libguestfs: trace: close
libguestfs: closing guestfs handle 0x561a8f5462c0 (state 0)
libguestfs: command: run: rm
libguestfs: command: run: \ -rf /tmp/libguestfsvE2Jy4
3 years, 4 months
[PATCH nbdkit 0/2 PROPOSAL] log: Add logscript feature.
by Richard W.M. Jones
This patch series isn't finished - at a minimum it needs tests.
As you may have seen I've been fiddling around with nbdkit-log-filter,
generally tidying up the code. However the big change I want to make
is to allow a script to be triggered from logging events. The two
patches that follow show where this is going.
The first patch cleans up the log format itself so that we
consistently use shell (actually _bash_) quoting for the parameters
that we print in the log file. Note this introduces some minor
incompatibilities.
This allows the second patch which implements the logscript feature by
passing the same parameters directly to an external script.
Rich.
3 years, 4 months