some other netcat software needs to be adopted in gentoo. Reproducible: Always Steps to Reproduce: 1. emerge netcat (on the libvirt host) 2. virsh -c qemu+ssh://host/system 3. emerge gnu-netcat (on the libvirt host) 4. ln -s /usr/bin/netcat /usr/bin/nc 5. virsh -c qemu+ssh://host/system Actual Results: luca@doomsday:~$ virsh -c qemu+ssh://root@kvm01/ Connecting to uri: qemu+ssh://root@kvm01/ Password: nc: invalid option -- U Try `nc --help' for more information. libvir: Remote error : socket closed unexpectedly error: failed to connect to the hypervisor luca@doomsday:~$ the openbsd netcat has the needed feature in the libvirt thing. a porting for linux is atm in redhat, fedora, centos os, debian and ubuntu and it is included as dependancy of libvirt executable binaries (i.e. virsh).
feel free to write the ebuild then change the KEYWORDS to "EBUILD"
well i guess it's quite doable. I'll test which netcat-openbsd linux (debian or red-hat ones i.e.) port is more reusable for gentoo and I'll try to write an ebuild against it. Just one thing concerns me in portage's acquisition of such package, libvirt isn't designed to be a linux-only API. I mean that at least for a client-side usage, it probably will be usable on *BSD desktop systems to manage virtual environments. Anyway an usable linux only ebuild for netcat-openbsd is my first entry in my todo list, stating I need it. cheers, luca (In reply to comment #1) > feel free to write the ebuild then change the KEYWORDS to "EBUILD" >
Created attachment 165250 [details] ebuild, changelog and metadata file for netcat-openbsd howdy, the starting ebuild done. I synced it from centos 5.2 repository (1.84-10.fc6) this package provides virtual/netcat, is this wrong? I don't need to be able to emerge both net-analyzer/netcat or net-analyzer/gnu-netcat too.
(In reply to comment #1) > feel free to write the ebuild then change the KEYWORDS to "EBUILD" > howdy, do I need to do anything else to be done from my side to get this package go in portage? should I poke some gentoo developer on irc o something like that? cheers! -- luca
Tested on amd64. Builds and installs as /usr/bin/nc.openbsd. After manual replacement of the normal nc with the new binary, I am able to use libvirt & virt-manager over ssh. Perhaps there needs to be a virtual/netcat to allow for 2 packages providing the same binary? Would it help if the ebuild was attached as a plain text file? (currently a tbz2)
Created attachment 185198 [details] netcat-openbsd-1.84.ebuild This is a slightly modified ebuid based upon luca's ebuild. - added blockers about netcat and gnu-netcat - dosym nc.openbsd -> nc
(In reply to comment #6) > Created an attachment (id=185198) [edit] > netcat-openbsd-1.84.ebuild > > This is a slightly modified ebuid based upon luca's ebuild. > - added blockers about netcat and gnu-netcat > - dosym nc.openbsd -> nc > Now the "nc: invalid option -- U" message dissappeared but I cant connect anyway. $ virsh -c xen+ssh://root@192.168.253.41/ Connecting to uri: qemu:///session libvir: Remote error : socket closed unexpectedly
(In reply to comment #7) > Now the "nc: invalid option -- U" message dissappeared but I cant connect > anyway. > > $ virsh -c xen+ssh://root@192.168.253.41/ > Connecting to uri: qemu:///session > libvir: Remote error : socket closed unexpectedly Make sure you have this 'netcat-openbsd' on *both* systems. It's not going to do you any good on just one of them. ;) I can confirm that with netcat-openbsd on both a local and remote system, libvirt and virt-manager work excatly as they should over SSH. Either a warning needs to be added to the libvirt ebuild indicating that OpenBSD netcat is required for SSH connections, or this ebuild should be added to the tree and libvirt changed to DEPEND on 'netcat-openbsd'. What needs to be done to add this to the tree?
Hi, I think this bug report needs a boost! I ran into exactly this problem. I installed in my OVERLAY-directory: - the tarball as attached to this bug report by Luca - the enhanced ebuild script as attached by Balazs It solved my problem. Now I can connect to the libvirt daemon from a remote virt-manager instance via an SSH tunnel. Great!!! Please introduce a virtual netcat metapackage and accept this ebuild into the tree.
http://bugs.gentoo.org/show_bug.cgi?id=280650 proposes another solution to the same problem.
Hi there, I've the exact same problem and it have cost me 6 hours on finding this bug report because neither libvirt nor virt-manager displays a good error message. It's very annoying and a big waste of time. Please do anything - at least add a warning in the ebuild of libvirt with the problem and a link to this bug report, when emerging it. Better fix the problem. But please do something.
+ 08 Sep 2009; Patrick Lauer <patrick@gentoo.org> +libvirt-0.6.5-r1.ebuild: + Fixing netcat dep #280650 #237277 #283884
