similar to: Debugging libguestfs

Rich, Thank you for the very quick response. I tried the echo command that you listed and it still gives me the same error: Any other possible suggestions? On Monday, October 5, 2020, 02:42:08 PM EDT, Richard W.M. Jones <rjones@redhat.com> wrote: On Mon, Oct 05, 2020 at 06:28:06PM +0000, Alexander Prada wrote: > Here is my output I am getting on my kali machine. I believe

Here is the updated libguestfs-test-tool output after the command below: echo /usr/lib/x86_64-linux-gnu/libtsk.so.19 > /usr/lib/x86_64-linux-gnu/guestfs/supermin.d/zz-libtsk On Monday, October 5, 2020, 03:56:34 PM EDT, Richard W.M. Jones <rjones@redhat.com> wrote: On Mon, Oct 05, 2020 at 07:51:56PM +0000, Alexander Prada wrote: > Rich, > > Thank you for the very quick

On Mon, Oct 05, 2020 at 06:28:06PM +0000, Alexander Prada wrote: > Here is my output I am getting on my kali machine. I believe that the error is: > > guestfsd: error while loading shared libraries: libtsk.so.19: cannot open > shared object file: No such file or directory > > I tried to change the LD_LIBRARY_PATH to numerous locations and libtsk.so.19 is > inside

On Fri, Aug 7, 2020 at 1:10 PM Erik Skultety <eskultet@redhat.com> wrote: > On Wed, Aug 05, 2020 at 10:13:57PM +0530, Kaushal Shriyan wrote: > > On Wed, Aug 5, 2020 at 1:32 PM Pavel Hrdina <phrdina@redhat.com> wrote: > > > > > On Wed, Aug 05, 2020 at 06:57:11AM +0530, Kaushal Shriyan wrote: > > > > Hi, > > > > > > > > I am

On Wed, Aug 5, 2020 at 1:32 PM Pavel Hrdina <phrdina@redhat.com> wrote: > On Wed, Aug 05, 2020 at 06:57:11AM +0530, Kaushal Shriyan wrote: > > Hi, > > > > I am trying to install kali-linux-2020.2-installer-amd64.iso ( > > https://www.kali.org/downloads/) using KVM virt-install tool > > > > #virt-install --name=kalilinux

Hi, I am trying to install kali-linux-2020.2-installer-amd64.iso ( https://www.kali.org/downloads/) using KVM virt-install tool #virt-install --name=kalilinux --file=/linuxkvmaddgbdisk/kalilinux.img --file-size=50 --nonsparse --vcpu=2 --ram=4096 --network=bridge:br0 --os-type=linux --os-variant=debian9 --graphics none --location=/linuxkvmaddgbdisk/kali-linux-2020.2-installer-amd64.iso

Hi Pavel, I am running virt-install version 1.5.0 on CentOS Linux release 7.6.1810 (Core) server. #virt-install --name=kalilinux --file=/linuxkvmaddgbdisk/kalilinux.img --file-size=50 --nonsparse --vcpu=2 --ram=4096 --network=bridge:br0 --os-type=linux --os-variant=debian9 --graphics none --location

Hello! Compile the environment information: centos7.4 libguestfs-1.36.3.tar.gz I encountered supermin and supermin5 problems while compiling libguestfs command: ./configure checking for tsk/libtsk.h... yes checking if we should build the appliance... yes checking for supermin... /usr/bin/supermin checking for --with-supermin-packager-config option... not set checking for

Hi Rich I using ubuntu 13.10 with powerpc arch. I tried the above stepss and below are the output of the related commands.. nm -D /usr/lib/powerpc-linux-gnu/libtinfo.so | grep tgetent 0000def0 T tgetent ubuntu@t4240-ubuntu1310:~$ dpkg -S /usr/lib/powerpc-linux-gnu/libtinfo.so libtinfo-dev:powerpc: /usr/lib/powerpc-linux-gnu/libtinfo.so However I'm not able to perform rm -f config.cache

On Sunday 03 April 2016 16:30:48 Matteo Cafasso wrote: > The internal_filesystem_walk command walks > through the FS structure of a disk partition > and returns all the files or directories > which could be found. > > The command is able to retrieve information > regarding deleted or unaccessible files as well > where other commands such as stat or find > would fail.

v3: - File size will be reported as - 1 if it cannot be retrieved. - Code improvements based on comments. Matteo Cafasso (5): generator: Added tsk_dirent struct configure: Added libtsk compile-time check daemon: Added internal_filesystem_walk command appliance: Added filesystem_walk command appliance: Added filesystem_walk command tests daemon/Makefile.am | 4 +-

This takes advantage of glibc's MALLOC_PERTURB_. If you develop on glibc-based systems and don't yet set this via your shell's init scripts, add something like this to e.g., .bashrc: export MALLOC_PERTURB_=$(($RANDOM % 255 + 1)) This change ensures that it's enabled for anyone running "make check" and in particular for koji. There's probably documentation

v5: - fixed compile-time warning - removed unused flag enumeration - new version 1.33.19 Patch ready for review. Matteo Cafasso (5): generator: Added tsk_dirent struct configure: Added libtsk compile-time check New API: internal_filesystem_walk New API: filesystem_walk lib: Added filesystem_walk command tests daemon/Makefile.am | 4 +- daemon/tsk.c

v4: - Changed tsk_allocated struct field into tsk_flags. - Added optional dependency in documentation. - Use asprintf and perror instead of asprintf_nowarn and fprintf. - Ensure CLEANUP_FREE vars are initialised. - Reworked the function documentation. - Improved tests robustness. Matteo Cafasso (5): generator: Added tsk_dirent struct configure: Added libtsk compile-time check

On 4/07/24 17:38, Joachim Lindenberg via samba wrote: > Afaik or understand, enum4linux uses samba-tool (https://www.kali.org/tools/enum4linux/) and not ldap. Did you try enum4linux on a member (probably after some authentication) or some other non-member linux? I don't think that is quite the right distinction, because samba-tool would probably use ldap for this. Also, I see ldapsearch

v7: - iterate over output file instead of reading it into memory Instead of reading the whole output file in memory and iterating over the resulting buffer, use XDR primitives to directly iterate over the file itself. This should reduce the API memory consumption. Patch ready for review. Code available at: https://github.com/noxdafox/libguestfs/tree/filesystem_walk Matteo Cafasso

v6: - added metadata reallocation flag in tsk_flags Certain filesystems separate file name structures and metadata ones. Therefore, deleted entries with file name structures in an unallocated state might point to metadata structures which have been reallocated to new files. A flag set to 1 is generally an indication that the information gathered from the metadata structure (file

v2: - Increased the amount of collected information from the FS content. - Moved filesystem_walk0 as internal command. - Code improvement based on comments. - Adhere to project's coding style. - Better command documentation. - More robust tests. Patch ready for review, code available at: https://github.com/noxdafox/libguestfs/tree/filesystem_walk Matteo Cafasso (5): generator:

Read the information from os-release, and make it behave like a Debian distribution (i.e. using dpkg, and apt). --- daemon/inspect_fs.ml | 2 ++ daemon/inspect_fs_unix.ml | 1 + daemon/inspect_types.ml | 2 ++ daemon/inspect_types.mli | 1 + generator/actions_inspection.ml | 4 ++++ 5 files changed, 10 insertions(+) diff --git a/daemon/inspect_fs.ml

Heya, With latest Fedora Rawhide Kernel, I see a nested KVM guest hanging at boot (not unusual). Rich once suggested this[1] to try to attach gdb to the nested L2 guest to find out where_ it's stuck, tonight I set out to try it out (with KVM & TCG). Below is all what I tried. In guest hypervisor (L1): $ git clone git://github.com/libguestfs/libguestfs.git $ git log | head -1