similar to: error make guestfs: relocation libfuse.a Bad value

On Tue, Apr 09, 2013 at 10:18:50AM -0400, Skippy VonDrake wrote: > Hello, > > Apologies upfront if posting to this list is inappropriate. > > I have an app that forks a process with calls qemu-nbd with an offset > into an image. > The app then uses libguestfs to attach the nbd device. > But it appears that qemu is failing. When you say "qemu is failing", do you

Did install from source of libguestfs-1.20.1 on Ubuntu-12.10. And libguestfs-test-tool complains about not finding libcap.so.2 uptime: 2.26 1.00 guestfsd: error while loading shared libraries: libcap.so.2: cannot open shared object file: No such file or directory [ 2.277795] Unregister pv shared memory for cpu 0 [ 2.278324] kvm: exiting hardware virtualization [ 2.278763] sd 2:0:1:0:

The error message: hivex_close: do_hivex_close: you must call 'hivex-open' first to initialize the hivex handle This is the process flow: g = guestfs_create (); guestfs_add_drive_opts (g, diskFile,GUESTFS_ADD_DRIVE_OPTS_FORMAT, "raw",-1); guestfs_launch (g) char **roots = guestfs_inspect_os (g); guestfs_inspect_os returns NULL, guestfs_last_error(g) returns

Hello, Been a long time since I broke out your libguestfs tools. Current employer has some old machines they want to virtualize before they croak. I was able to virtualize a Win2000 box but when I tried the same with a Windows 95 machine the call to guestfs_list_partitions returned null. I did make that image with a different tool (my linux box wasn't available so I wound up using Macrium

This error is with libguestfs 1.20. Calling guestfs_launch() with tracing on: supermin helper [00065ms] finished creating appliance libguestfs: checksum of existing appliance: 2bd6811426e14b6fb661b4d52cebd6c21a41df1a068e8acf6a7a08e3b3bd4ada libguestfs: trace: get_cachedir libguestfs: trace: get_cachedir = "/var/tmp" libguestfs: [00071ms] begin building supermin appliance libguestfs:

Is there any sample code available to demonstrate the use of the guestfs_hivex_node_set_value API? I have no problem traversing and reading keys using libguestfs hivex wrappers - but continue to fail on any write attempts. The return is always -1 and errno is unchanged. I've set the environment variable HIVEX_DEBUG to 1 on a chance that this may help - but it doesn't. The only sample I

Following a Xen tutorial but can''t get the VM (PV Squeeze) running. After doing: # xm create -c /etc/xen/tutorial-pv-guest.cfg The prompt just sits there. Opening another terminal: # xm list /usr/lib/python2.7/dist-packages Name ID Mem VCPUs State Time(s) Domain-0 0 7199 4 r----- 40.6

I get the following error when I try installing fuse-ntfs-3g even though I have installed fuse-2.7 and fuse-kmdl-2.7 error: Failed dependencies: libfuse.so.2 is needed by fuse-ntfs-3g-1.913-1.el5.rf.i386 libfuse.so.2(FUSE_2.2) is needed by fuse-ntfs-3g-1.913-1.el5.rf.i386 libfuse.so.2(FUSE_2.5) is needed by fuse-ntfs-3g-1.913-1.el5.rf.i386 libfuse.so.2(FUSE_2.6) is

I've been using libguestfs-1.18.9 but decided to "upgrade" to 1.19.60. Using Ubuntu 12.04 with the older version installed via source. So I went through the same process with the new version of guestfs sources and got the following errors on 'make install': make[2]: Nothing to be done for `install-exec-am'. make install-data-hook make[3]: Entering directory

On 04/27/2013 08:07 AM, Yuri wrote: > ELF module of type ET_REL (Relocable module), generated by LLVM, > always has some R_X86_64_32 in debug information sections. > This happens with Reloc models Default,Static,PIC_ and with CodeModel > set to Large. > > What is the way to prevent R_X86_64_32 ELF from ever appearing in ELF? Hi Yuri, why do you want to prevent R_X86_64_32

On 04/26/2013 19:50, Jiong Wang wrote: > > > why do you want to prevent R_X86_64_32 generation? for 32bit dwarf, > I think generation of R_X86_64_32 is reasonable. > > you can check http://dwarfstd.org/doc/DWARF4.pdf. Because R_X86_64_32 elements are 4-byte addresses and can't be relocated for the 64-bit address space over 32-bit limit. Dwarf2 actually allows for

ELF module of type ET_REL (Relocable module), generated by LLVM, always has some R_X86_64_32 in debug information sections. This happens with Reloc models Default,Static,PIC_ and with CodeModel set to Large. What is the way to prevent R_X86_64_32 ELF from ever appearing in ELF? Yuri

Ubuntu 12.04, Xen 4.2.1 ./configure --libdir=/usr/lib/x86_64-linux-gnu make world make[4]: Entering directory `/home/skippy/Downloads/xen/xen-4.2.1/tools/qemu-xen-traditional-dir'' make[4]: *** No rule to make target `clean''. Stop. First time it failed because of a missing dependency. Fixed that but now can''t get past the "cleaning stage". tried "make

> > Looks like a disk sector to me too. However the partition table > is further on. See: > > https://en.wikipedia.org/wiki/Master_boot_record#Sector_layout So that reference says the "classical generic MBR" partition entry # 1 is offset 0x1BE. Which in this image is right in the error strings (?) section. 00000170 13 59 5A 58 72 09 40 75 01 42 03 5E 0B E2 CC C3

I think that you may have confused 2 separate issues here; the size of the DWARF tables with the size of addresses on the target system. The 32-bit DWARF vs. 64-bit DWARF is all about the size of the tables in the DWARF sections (and hence also the size of the references between entries in the tables). So a 32-bit DWARF section can correctly describe code/data addresses that are 64-bit, and any

I hope someone can point me, a newcomer to building R as well as 64-bit R, in a useful direction. I have a dual Opteron 275 box running RedHat EL4. I ran configure successfully, and, then, get the following error while running make: make[4]: Entering directory `/tmp/R-2.2.0/src/modules/lapack' g77 -fPIC -g -O2 -ffloat-store -c dlamc.f -o dlamc.lo g77 -fPIC -g -O2 -c dlapack0.f -o

On 04/29/2013 09:12, Keith Walker wrote: > You only need to go to 64-bit DWARF when your debugging information becomes > too large to fit in 32-bit DWARF tables. I am not sure if this is true. Currently R_X86_64_32 EL relocations are issued for DWARF-32 debug info sections. This is because the size of address in DWARF-32 is only 32-bits, according to the above mentioned specification.

I'm using qemu-nbd to setup the device with an offset into the image. Using libguestfs version 1.21.22 Code for adding the drive: char *server[] = { "localhost:3000", NULL }; if (guestfs_add_drive_opts (g, "" /* export name - see below */, GUESTFS_ADD_DRIVE_OPTS_FORMAT, "raw", GUESTFS_ADD_DRIVE_OPTS_PROTOCOL, "nbd",

I'm using a Windows raw disk image that is "converted" to the VDI format by custom code that prepends a header to the image. I use 'vdi' for GUESTFS_ADD_DRIVE_OPTS_FORMAT of guestfs_add_drive_opts(). After launching the appliance, the call to guestfs_list_partitions() results in an empty list. Is there a way to add the drive but have an offset into the image file as a

Upon seeing RWM Jones article "Using mount-local API from C" I became curious because I thought there WAS a way to combine aspects of FUSE with the tools provided by libguestfs. So if I wanted to create my own filesystem using callbacks placed in the 'fuse_operations' struct (parameter to 'fuse_main()'), I could do so using guestfs. But after reading the article and