Hi,
On Thu, 5 Dec 2019 11:12:56 + "Richard W.M. Jones"
wrote:
> I believe this is a new bug and nothing much to do with:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775761
So I just cloned the bug into #946594 in order to manage the bug reported
by Pierre Neyron.
> However abou
I believe this is a new bug and nothing much to do with:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775761
However about this new bug, what is supposed to happen is that
common/mlstdutils/guestfs_config.ml is generated by ./configure with
the correct @host_cpu@ substituted. If that's not h
Hi,
I also have an issue with libguestfs incorrectly detecting the host CPU
architecture in Debian, when using the virt-customize command on a
aarch64 machine.
E.g.:
neyron@digarm:~/scm/environments-recipes/build/debian-buster-arm64$
virt-customize -a base_debian-buster-arm64.qcow2 --run-command
On Tue, Jan 20, 2015 at 07:42:10AM -0800, Rogier wrote:
> > It looks as if libguestfs is configured wrongly, or maybe you've got
> > the 32 bit version of libguestfs installed on your system.
>
> I do have a 32-bit version (my entire userland is still 32-bit - it
> used to be the better choice, a
I wonder why it chose to run /usr/bin/qemu-system-i386 ?
Is $LIBGUESTFS_HV or $LIBGUESTFS_QEMU set?
What is the output of:
guestfish get-hv
What happens if you do:
LIBGUESTFS_HV=/usr/bin/qemu-system-x86_64 libguestfs-test-tool
It looks as if libguestfs is configured wrongly, or maybe you
Source: libguestfs
Version: 1:1.26.9-1
Severity: important
Dear Maintainer,
When trying to use virt-sparsify, I got the failure message:
libguestfs error: guestfs_launch failed
Running libguestfs-test-tool shows that libguestfs incorrectly detects
the CPU type / architecture. It mentions:
6 matches
Mail list logo
