similar to: Speeding up Windows upload script

This worked wonderfully!  What are the odds of getting this upstream in the near future?  I'd rather not build from source in production. # ./run guestfish --format=raw --ro -a rbd://[fd00::cefc:1]:6789/images/CentOS-7-x86_64-GenericCloud-1901 libguestfs: trace: set_verbose true libguestfs: trace: set_verbose = 0 libguestfs: trace: set_tmpdir "/root/libguestfs/tmp" libguestfs:

I believe the bug lies in libguestfs. Taking out the commands being sent to QEMU and using qemu-img info I can recreate the error: # qemu-img info "rbd:images/CentOS-7-x86_64-GenericCloud-1901:mon_host=[fd00::cefc:1]\:6789:auth_supported=none" qemu-img: Could not open 'rbd:images/CentOS-7-x86_64-GenericCloud-1901:mon_host=[fd00::cefc:1]\:6789:auth_supported=none': invalid

Hi all, experimenting with vol-create-as, I think it should autodetect some data - filesize and backing file format, specifically. However, the current implementation require us to specify both filesize and backing file format. Considering that qemu-img already autodetects these data, there are any reason for the lack of autodetect by libvirt? Should I open a bugzilla issue? Below you can

I am unable to convert a vm using virt-v2v. From the trace and debug logs I am unable to understand the cause of the problem. I assume it is a permission or configuration issue but I don't know where to start looking. The following command was issued: LIBGUESTFS_TRACE=1 LIBGUESTFS_DEBUG=1 virt-v2v -ic qemu+ssh://xxx at 192.168.xxx.xxx/system -o rhev -os 192.168.xxx.xxx:/mnt/exports -of

On Wed, Nov 07, 2018 at 12:32:48PM +0200, Peter Dimitrov wrote: > Thank you, Rich, > This was the issue indeed. export LIBGUESTFS_BACKEND=direct fixed it. > > The next step I tried was to integrate libguestfs in collectd virt plugin > to collect this data automatically. > In this case I'm having an unknown error in add_libvirt_dom() (same with > add_domain) when it's

> Delete what you've done and start from the beginning. Describe > exactly how you created the guest. Use 'qemu-img info' to show the > format of the input file. Show precisely the virt-sparsify command > you are running. And use 'qemu-img info' on the output file too. Okay, here goes. Start off with an install root@testingbox:~ # virt-install --name

Unfortunately I do need to use the address explicitly as opposed to hostnames because the source of the data fed here is Ceph's monmap which returns the addresses explicitly. I've tried all the common ways to escape the : in the v6 address to no avail.  I definitely agree that the problem looks to be it parsing the colons as if the port comes next and then everything after that is

Hi (Eric?), A couple of questions while using the 'virsh blockpull' Summary: 1] Created snapshots this way: base<-snap1<-snap2<-snap3 (online, external snapshot --disk-only) 2] I did a 'virsh blockpull' from snap2 into snap3 3] Next, did another 'virsh blockpull' from snap1 into snap3 - Here, 'qemu-img info /path/to/snap3' shows its backing file

On Fri, Mar 29, 2019 at 06:17:17PM -0500, Jonathan Wright wrote: > I have scoured the web and can't find anything on the topic: Is IPv6 > supported for remote image targets? It definitely should work, although I don't know if anyone has tried using the address explicitly (rather than a hostname which resolves to an AAAA record). > For example: > > guestfish --format=raw

I have scoured the web and can't find anything on the topic: Is IPv6 supported for remote image targets? For example: guestfish --format=raw --ro -a rbd://[fd00::cefc:1]:6789/images/CentOS-7-x86_64-GenericCloud-1901 Does not work citing the following: libguestfs: trace: set_verbose true libguestfs: trace: set_verbose = 0 libguestfs: create: flags = 0, handle = 0x5560231bdfb0, program =

On Mon, Apr 01, 2019 at 08:45:48AM -0500, Jonathan Wright wrote: > Unfortunately I do need to use the address explicitly as opposed to > hostnames because the source of the data fed here is Ceph's monmap > which returns the addresses explicitly. > > I've tried all the common ways to escape the : in the v6 address to > no avail.  I definitely agree that the problem looks

On Sat, May 30, 2015 at 02:35:51AM +0000, Boylan, Ross wrote: > Does libvirt support snapshotting when the virtual disk comes from a > vmdk file? >From my quick test (refer below), seems like you can at-least use VMDK as a backing file. > http://wiki.libvirt.org/page/Snapshots#Desired_functionality seems to > say no, since it says "'virsh snapshot', which requires all

> That makes no sense because we are supposed to have just forked successfully I just realized libguestfs uses fork. Now we know why qemu-img worked - I launched it with popen. > So it must be something to do with collectd and how it runs programs. > Is it using LD_PRELOAD trickery, or replacing libc, or using seccomp? If I understand the question correctly - it's about how

Hi,Richard: &nbsp; &nbsp; &nbsp; &nbsp;I use&nbsp;/bin/virt-copy-in&nbsp; failed , virt-copy-in&nbsp;&nbsp;have no diff with other nomarl machine(work well ) ,&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; /bin/virt-copy-in: symbol lookup error: /lib64/libguestfs.so.0: undefined symbol: json_string_length&nbsp; &nbsp; &nbsp; &nbsp;here are

I have a Fedora 24 system I can already get this working for most OVA files, just the BSD and atomic ones weren't recognized. Assuming my version of virt-v2v is just old, I installed rawhide on a different system and tried with virt-v2v-1.37.8-1.fc27.x86_64 and now its having another problem. Is there a known version of virt-v2v I should be using? Here is the output from the rawhide attempt

Thank you, Rich, This was the issue indeed. export LIBGUESTFS_BACKEND=direct fixed it. The next step I tried was to integrate libguestfs in collectd virt plugin to collect this data automatically. In this case I'm having an unknown error in add_libvirt_dom() (same with add_domain) when it's invoking qemu-img to create overlay image. There is no difference between manual and service

On Tuesday 04 February 2014 09:54:58 Richard W.M. Jones wrote: > On Mon, Feb 03, 2014 at 09:14:09PM +0000, Richard W.M. Jones wrote: > > On Mon, Feb 03, 2014 at 03:29:37PM -0500, Andre Goree wrote: > > > Ahhh, understood. I do have have an image I can provide that was > > > installed onto and MBR layout (seemed the easiest for libguestfs > > > to > > >

On Mon, Mar 24, 2014 at 08:22:46AM -0400, Arup Raton Roy wrote: > Hi Richard, > > Thanks a lot for your prompt response. I am enumerating the steps that I > followed during the provisioning, if it helps. Thanks ... > 1. These are the commands that I used to create the disk image. > > qemu-img create -f qcow2 base_VM.qcow2 512M > kvm -m 512 -cdrom Core-current.iso -hda

Hi All, I've been chasing down an issue in recent weeks (my own lab, so no prod here) and I'm reaching out in case someone might have some guidance to share. I'm running fairly large VMs (RHOSP underclouds - 8vcpu, 32gb ram, about 200gb single disk as a growable qcow2) on some RHEL7.6 hypervisors (kernel 3.10.0-927.2x.y, libvirt 4.5.0, qemu-kvm-1.5.3) on top of SSD/NVMe drives

On Mon, Feb 03, 2014 at 09:14:09PM +0000, Richard W.M. Jones wrote: > On Mon, Feb 03, 2014 at 03:29:37PM -0500, Andre Goree wrote: > > Ahhh, understood. I do have have an image I can provide that was > > installed onto and MBR layout (seemed the easiest for libguestfs to > > understand, GPT is preferred if libguestfs works well with it, but > > that's another matter