search for: virtqemud

...at all. The option was added when virt-v2v was rewritten in 2014. It is possible to specify a format string for controlling the output; see L<guestfs(3)/ADVANCED MACHINE READABLE OUTPUT>. +=head2 Starting the libvirt system instance + + Failed to connect socket to '/var/run/libvirt/virtqemud-sock': No such file or directory + Failed to connect socket to '/var/run/libvirt/virtqemud-sock-ro': Connection refused + +If you have just installed libvirt and virt-v2v, then you may see the +errors above. This is caused by libvirt daemons that provide various +services not running s...

..., then indeed those bits, show above, are not there. I'd grateful for any/all thoughts shared on - what is not/happening there. Is there something else which is a prerequisite to 'qemu:commandline' but if yes and I'm missing those, why would not then 'virsh' and/or 'virtqemud' say something? many thanks, L. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://listman.redhat.com/archives/libvirt-users/attachments/20230515/3db63f71/attachment.htm>

> Is there something else which is a prerequisite to 'qemu:commandline' > but if yes and I'm missing those, why would not then 'virsh' and/or > 'virtqemud' say something? No what you have looks ok, this is what I have as a test and is working ok. You can try and these to see if something is shown in the guest. <qemu:commandline> <qemu:arg value='-cpu'/> <qemu:arg value='host,hv_time,-hypervisor'/>...

...sh stopped talking to the libvirtd. Both stopped within a few days of each other. Currently if I run: virsh uri virsh version virsh list # virsh list ..nothing just hangs When I ran strace on these broken machines it get stuck at same spot: strace virsh list ... access("/var/run/libvirt/virtqemud-sock", F_OK) = -1 ENOENT (No such file or directory) access("/var/run/libvirt/libvirt-sock", F_OK) = 0 socket(AF_UNIX, SOCK_STREAM, 0) = 5 connect(5, {sa_family=AF_UNIX, sun_path="/var/run/libvirt/libvirt-sock"}, 110) = 0 getsockname(5, {sa_family=AF_UNIX}, [128 =&g...

...tart the appliance via libvirt, or virt-v2v fails to make a read-write connection to libvirtd (for -i libvirt or -o libvirt), then those are all fatal errors, and whatever exception the outermost handler reports, it will contain some variation of Failed to connect socket to '/var/run/libvirt/virtqemud-sock': No such file or directory Failed to connect socket to '/var/run/libvirt/virtqemud-sock-ro': Connection refused (Note: already two socket pathnames and two possible errno values -- 4 variations.) (2) If the logic from commit 4e7f20684373 fails to make a read-only connection to...

Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2182024 v1 was here: <https://listman.redhat.com/archives/libguestfs/2023-June/031910.html>. Make any "chown_for_libvirt_rhbz_1045069" failure a hard one; that way the user gets to see more direct and more uniform error messages (namely that we couldn't connect to libvirt). Document those connection problems, and a simple

...bvirt, or virt-v2v > fails to make a read-write connection to libvirtd (for -i libvirt or -o > libvirt), then those are all fatal errors, and whatever exception the > outermost handler reports, it will contain some variation of > > Failed to connect socket to '/var/run/libvirt/virtqemud-sock': No such file or directory > Failed to connect socket to '/var/run/libvirt/virtqemud-sock-ro': Connection refused > > (Note: already two socket pathnames and two possible errno values -- 4 > variations.) I think it just needs to give an example or two of the error....

...it almost certainly leads to later errors, but those errors are less clear than the original (suppressed) exception. Namely, the user sees something like > Failed to connect to '/tmp/v2v.sKlulY/in0': Permission denied rather than > Failed to connect socket to '/var/run/libvirt/virtqemud-sock-ro': > Connection refused So just allow the exception to propagate outwards. And then, now that "chown_for_libvirt_rhbz_1045069" will be able to fail, hoist the call to "On_exit.rm_rf" before the call to "chown_for_libvirt_rhbz_1045069", after creating th...

...rs, but > those errors are less clear than the original (suppressed) exception. > Namely, the user sees something like > > > Failed to connect to '/tmp/v2v.sKlulY/in0': Permission denied > > rather than > > > Failed to connect socket to '/var/run/libvirt/virtqemud-sock-ro': > > Connection refused > > So just allow the exception to propagate outwards. > > And then, now that "chown_for_libvirt_rhbz_1045069" will be able to fail, > hoist the call to "On_exit.rm_rf" before the call to > "chown_for_libvirt_rh...

...rs are less clear than the original (suppressed) exception. >> Namely, the user sees something like >> >>> Failed to connect to '/tmp/v2v.sKlulY/in0': Permission denied >> >> rather than >> >>> Failed to connect socket to '/var/run/libvirt/virtqemud-sock-ro': >>> Connection refused >> >> So just allow the exception to propagate outwards. >> >> And then, now that "chown_for_libvirt_rhbz_1045069" will be able to fail, >> hoist the call to "On_exit.rm_rf" before the call to >> &...

On Tue, Jun 27, 2023 at 07:14:36PM +0200, Laszlo Ersek wrote: > It has frequently tripped us up that on RHEL / Fedora, installing the > right set of libvirt RPMs (such as the one pulled in by > "libvirt-daemon-kvm") does not result in an immediately running libvirt > system instance. Document the need, and the simplest method, for starting > libvirt up manually. >

...(suppressed) exception. > >> Namely, the user sees something like > >> > >>> Failed to connect to '/tmp/v2v.sKlulY/in0': Permission denied > >> > >> rather than > >> > >>> Failed to connect socket to '/var/run/libvirt/virtqemud-sock-ro': > >>> Connection refused > >> > >> So just allow the exception to propagate outwards. > >> > >> And then, now that "chown_for_libvirt_rhbz_1045069" will be able to fail, > >> hoist the call to "On_exit.rm_rf"...

...on. >>>> Namely, the user sees something like >>>> >>>>> Failed to connect to '/tmp/v2v.sKlulY/in0': Permission denied >>>> >>>> rather than >>>> >>>>> Failed to connect socket to '/var/run/libvirt/virtqemud-sock-ro': >>>>> Connection refused >>>> >>>> So just allow the exception to propagate outwards. >>>> >>>> And then, now that "chown_for_libvirt_rhbz_1045069" will be able to fail, >>>> hoist the call to "O...