Displaying 20 results from an estimated 3000 matches similar to: "Bug report."
2018 Jan 10
1
guestmount fails after linux kernel update 01/10/2018
Hello,
I had been using guestmount to mount a raw image and it has been working
great until I updated the kernel on 01/10/2018. I am running ubuntu 16.04
LTS, and have changed the read permissions to the vmlinuz as I have done
with previous kernels. The only change to my system between working and not
working is the kernel update from this morning. I am concerned this might
be related to the
2012 Jul 25
1
qemu:could not load kernel
Hi,
I have a problem when i run java examples of libguestfs. It needs root
privileges. This is the output of libguestfs-test-tool:
<libguestfs at redhat.com>===== Test starts here =====
LIBGUESTFS_DEBUG=1
TMPDIR=(not set)
libguestfs: new guestfs handle 0x9871c80
library version: 1.14.10
guestfs_get_append: (null)
guestfs_get_attach_method: appliance
guestfs_get_autosync: 1
2014 Jan 23
0
Re: Errors Running on Ubuntu 13.10
On Thu, Jan 23, 2014 at 12:22:43AM -0800, Tim Fall wrote:
> Running libguestft-test-tool yields:
>
>
> ************************************************************
> * IMPORTANT NOTICE
> *
> * When reporting bugs, include the COMPLETE, UNEDITED
> * output below in your bug report.
> *
>
2011 Oct 28
2
Inspecting VMware OVFs
Hi,
Maybe this is just a newbie question. I am trying to inspect VMware images
with guestfish.
I am running Fedora 15 in a VSphere VM. Once Fedora is installed I do:
yum update
yum install '*guestf*'
Then I run guesfish on a copy of a Fedora 15 disk.
guestfish -rw -I -a Fedora15-2-disk1.vmdk
with the following result:
libguestfs: error: unexpected end of file
2014 Jan 23
0
Re: Errors Running on Ubuntu 13.10
Please keep libguestfs mailing list in the CC.
On Thu, Jan 23, 2014 at 01:44:46PM -0800, Tim Fall wrote:
>
> On Jan 23, 2014, at 4:47 AM, Richard W.M. Jones <rjones@redhat.com> wrote:
>
> > On Thu, Jan 23, 2014 at 12:22:43AM -0800, Tim Fall wrote:
> >> Running libguestft-test-tool yields:
> >>
> >>
> >>
2018 Jan 15
2
but report
uname -a
Linux drh-MS-7888 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9
22:00:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
dpkg -l libguest*
Desired=Unknown/Install/Remove/Purge/Hold
|
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version
Architecture
2016 Mar 03
1
Re: "guestmount --rw" fails but "guestmount --ro" succeeds on Ubuntu 14.04
Thanks for your response Rich. Please see the output of --trace --verbose
below. Regarding your suggestion to convert the vmdk to some other format,
I do not want to do it. A security consultant said by modifying certain
files in our VM and restarting the VM, one can gain access to encrypted
data in our VM. I want to reproduce it. I am able to mount the VM but not
able to modify files since it can
2014 Jan 23
2
Re: Errors Running on Ubuntu 13.10
On Jan 23, 2014, at 1:54 PM, Richard W.M. Jones <rjones@redhat.com> wrote:
> Please keep libguestfs mailing list in the CC.
Sorry I realized that just after I sent it.
>
> On Thu, Jan 23, 2014 at 01:44:46PM -0800, Tim Fall wrote:
>>
>> On Jan 23, 2014, at 4:47 AM, Richard W.M. Jones <rjones@redhat.com> wrote:
>>
>>> On Thu, Jan 23, 2014 at
2011 Sep 27
1
"make check" on ArchLinux: "This kernel requires an x86-64 CPU, but only detected an i686 CPU"
I'm updating the ArchLinux libguestfs package to 1.12.7, but the "make check" tests fail in qemu with:
Booting from ROM...
This kernel requires an x86-64 CPU, but only detected an i686 CPU.
Unable to boot - please use a kernel appropriate for your CPU.
How does qemu detect the CPU type? I'm running a 64-bit ArchLinux (without KVM) on an Intel Xeon E5420 processor. I'm
2013 Aug 22
1
Re: --disable-appliance creates supermin.d files
On Thu, Aug 22, Richard W.M. Jones wrote:
> On Thu, Aug 22, 2013 at 09:28:36AM +0200, Olaf Hering wrote:
> > Why does the toplevel Makefile process appliance/, and creates
> > supermin.d during make install, whith configure --disable-appliance? I
> > have to double check what actually happens, it seems it causes startup
> > failures if the resulting binary packages are
2011 Dec 30
3
libguestfs-test-tool say "child process died" on ubuntu 11.10 x64
Hi all,
As title, thanks a lot. My test host configurations:
Linux desktop 3.0.0-14-generic #23-Ubuntu SMP Mon Nov 21 20:28:43 UTC
2011 x86_64 x86_64 x86_64 GNU/Linux
The test tool output as following:
xxx at desktop:~$ sudo libguestfs-test-tool
[sudo] password for xxx:
===== Test starts here =====
LIBGUESTFS_DEBUG=1
TMPDIR=(not set)
libguestfs: new guestfs handle 0x16cd0f0
library version:
2013 May 31
3
Re: How to use libguestfs access LVM as non-root user?
On Fri, May 31, 2013 at 4:17 PM, Richard W.M. Jones <rjones@redhat.com>wrote:
> On Fri, May 31, 2013 at 04:03:32PM +0800, Qiu Yu wrote:
> > Actually I'm looking into an issue with OpenStack / Libvirt manipulating
> > LVM as an image backend. When the logical volume is created, udev rules
> > will set the ownership to root:disk. After libvirt actually starting an
2014 Aug 21
2
libguest-test-tool error report
Hello,
I am trying to use virt-resize. It does not work. I set the debug environment variables and ran libguestfs-test-tool. The following is its output. I am running RHEL 6.5 desktop with kernel:
Linux hustedm-lnx4 2.6.32-431.5.1.el6.x86_64 #1 SMP Fri Jan 10 14:46:43 EST 2014 x86_64 x86_64 x86_64 GNU/Linux
Please let me know what I have missed.
Thanks,
Mark
bash-4.1$
2013 Nov 25
4
Problem Connecting to RBD images using Sys::Guestfs Perl Module
Hello,
I'm having trouble connecting to rbd images. It seems like somewhere the
name is getting chewed up. I wonder if this is related to my previous
troubles [1] [2] with rbd images.
I'm trying to add an rbd image, but when I launch the guestfs object I get
an error:
>> libguestfs: trace: launch = -1 (error)
I'm adding a single RBD
>> libguestfs: trace: add_drive
2011 Jul 21
2
Libguestfs hangs after issuing a launch command
Hi,
I am using libguestfs 1.12.0 and I am facing a problem with it .
I am using guestfs python bindings to "launch" a vdi image file .
It works fine except immediately after a VM is stopped(which uses the same
vdi file)
i.e in normal conditions launch command works but when a vm (which uses the
same vdi file) is started - stopped , a call to "launch" command hangs the
2014 Jan 23
2
Errors Running on Ubuntu 13.10
I'm trying to use virt-sysprep on an Ubuntu 13.10 vm running on OpenStack.
I've followed the command "gotchas" from the FAQ and still not had any luck.
*What are you trying to do?*
Attempting to use virt-sysprep on a qcow2 image made with virt-install
*What commands?*
I've run virt-sysprep (with both -d and -a options) and gotten the
following error:
Fatal error:
2014 Jan 23
3
Re: Errors Running on Ubuntu 13.10
On Jan 23, 2014, at 4:47 AM, Richard W.M. Jones <rjones@redhat.com> wrote:
> On Thu, Jan 23, 2014 at 12:22:43AM -0800, Tim Fall wrote:
>> Running libguestft-test-tool yields:
>>
>>
>> ************************************************************
>> * IMPORTANT NOTICE
>> *
>> * When reporting bugs, include the
2014 Dec 11
2
Re: virt-df error, help
Hi, Rich, follow your advice, I have succeeded in compiling the “libguestfs-1.26.5”
my ”libguestfs-test-tool is passed “
“ libguestfs: command: run: rm
libguestfs: command: run: \ -rf /tmp/libguestfs7jxKy0
===== TEST FINISHED OK =====”
But, When I run “virt-df `virsh domuuid 147`”
the error show:(debug mode)
“supermin helper [00000ms] host_cpu = x86_64
supermin helper [00000ms]
2014 Jun 04
2
Re: libguestfs supermin error
Hi Rich..
I'm now getting following logs after following your instructions..
libguestfs-test-tool
************************************************************
* IMPORTANT NOTICE
*
* When reporting bugs, include the COMPLETE, UNEDITED
* output below in your bug report.
*
************************************************************
2018 Mar 08
2
Re: febootstrap: no ext2 root device found
Here you go, from the newest version:
************************************************************
* IMPORTANT NOTICE
*
* When reporting bugs, include the COMPLETE, UNEDITED
* output below in your bug report.
*
************************************************************