search for: cefc

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 conf option :cefc:1]:6789:auth_supported: No such file or directory When escaping the : in the v6 address (just like is do...

...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 --ro -a >> rbd://[fd00::cefc:1]:6789/images/CentOS-7-x86_64-GenericCloud-1901 >> >> Does not work citing the following: > The important lines are these. Firstly guestfish parses the URL into > an actual libguestfs API call, which looks fine to me: > >> libguestfs: trace: add_drive >> "ima...

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: trace: set_tmpdir = 0 libguestfs: trace: set_cachedir "/root/libguestfs/tmp" libguestfs: trace...

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 = guestfish libguestfs: trace: set_pgroup true libguestfs: trace: set_pgroup...

...he 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 --ro -a > rbd://[fd00::cefc:1]:6789/images/CentOS-7-x86_64-GenericCloud-1901 > > Does not work citing the following: The important lines are these. Firstly guestfish parses the URL into an actual libguestfs API call, which looks fine to me: > libguestfs: trace: add_drive > "images/CentOS-7-x86_64-GenericC...

...;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 --ro -a > >>rbd://[fd00::cefc:1]:6789/images/CentOS-7-x86_64-GenericCloud-1901 > >> > >>Does not work citing the following: > >The important lines are these. Firstly guestfish parses the URL into > >an actual libguestfs API call, which looks fine to me: > > > >>libguestfs: trace: ad...

...01, 2019 at 09:45:56AM -0500, Jonathan Wright wrote: > 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 conf option :cefc:1]:6789:auth_supported: No such file or > directory > > When escaping the : in the v6 a...

...tive tools ii xen-utils-common 4.0.0-1 XEN administrative tools - common files ii xenstore-utils 3.4.3-1 Xenstore utilities for Xen # cat /etc/fstab proc /proc proc defaults 0 0 UUID=c565893c-cefc-47f3-b6f8-008e948d4b02 / ext4 errors=remount-ro 0 1 UUID=dc60eb97-4ca3-4fa1-b7ba-2fdcd88eddc9 /boot ext4 defaults 0 2 /dev/mapper/vg0-tmp /tmp ext4 noatime,nodev,nosuid 0 2 /dev/mapper/vg0-usr /usr ext4 defaults 0 2 /dev/m...

Hi, I have a glusterfs volume replicated on three nodes. I am planing to use the volume as storage for vMware ESXi machines using NFS. The reason for using tree nodes is to be able to configure Quorum and avoid split-brains. However, during my initial testing when intentionally and gracefully restart the node "ned", a split-brain/self-heal error occurred. The log on "todd"