Created attachment 356856 [details] virt-manager error Package: virt-manager Version: 0.7.0-4+b1 Severity: normal The current version of virt-manager in Debian, when connecting to a Fedora 11 KVM VM, gives a very mis-leading error message. Attached screenshot with this bug report explains it. How does one mitigate such problems? All distributions almost share the same common codebase but still can't guarantee interoperability. In this case, the version of netcat shipped in Debian supports "-q", where as the version in Fedora doesn't. I know I'm using testing/squeeze and this might be expected, but then how do we fix it. Is there any LSB compliance by the distributions ? -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (101, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.30-custom (SMP w/1 CPU core; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages virt-manager depends on: ii libatk1.0-0 1.26.0-1 The ATK accessibility toolkit ii libc6 2.9-23 GNU C Library: Shared libraries ii libcairo2 1.8.6-2+b1 The Cairo 2D vector graphics libra ii libfontconfig1 2.6.0-4 generic font configuration library ii libfreetype6 2.3.9-4.1 FreeType 2 font engine, shared lib ii libglib2.0-0 2.20.1-2 The GLib library of C routines ii libgtk2.0-0 2.16.1-2 The GTK+ graphical user interface ii libpango1.0-0 1.24.0-3+b1 Layout and rendering of internatio ii librsvg2-common 2.26.0-1 SAX-based renderer library for SVG ii python-dbus 0.83.0-1 simple interprocess messaging syst ii python-glade2 2.14.1-3 GTK+ bindings: Glade support ii python-gnome2 2.26.1-1 Python bindings for the GNOME desk ii python-gtk-vnc 0.3.8-2 A VNC viewer widget for GTK+ (Pyth ii python-gtk2 2.14.1-3 Python bindings for the GTK+ widge ii python-libvirt 0.6.4-1 libvirt Python bindings ii python-urlgrabber 3.1.0-4 A high-level cross-protocol url-gr ii python-vte 1:0.20.5-1 Python bindings for the VTE widget ii python2.5 2.5.4-1 An interactive high-level object-o ii virtinst 0.500.0-1 Programs to create and clone virtu Versions of packages virt-manager recommends: ii hal 0.5.12~git20090406.46dc48-2 Hardware Abstraction Layer pn libvirt-bin <none> (no description available) Versions of packages virt-manager suggests: ii virt-viewer 0.0.3-2 Displaying the graphical console o -- no debconf information
Here's the error message you see, if you use --no-fork (which a normal user wouldn't know to use seeing the error message). rrs@champaran:~$ virt-manager --no-fork nc: invalid option -- 'q' usage: nc [-46DdhklnrStUuvzC] [-i interval] [-p source_port] [-s source_ip_address] [-T ToS] [-w timeout] [-X proxy_version] [-x proxy_address[:port]] [hostname] [port[s]] nc: invalid option -- 'q' usage: nc [-46DdhklnrStUuvzC] [-i interval] [-p source_port] [-s source_ip_address] [-T ToS] [-w timeout] [-X proxy_version] [-x proxy_address[:port]] [hostname] [port[s]] nc: invalid option -- 'q' usage: nc [-46DdhklnrStUuvzC] [-i interval] [-p source_port] [-s source_ip_address] [-T ToS] [-w timeout] [-X proxy_version] [-x proxy_address[:port]] [hostname] [port[s]] nc: invalid option -- 'q' usage: nc [-46DdhklnrStUuvzC] [-i interval] [-p source_port] [-s source_ip_address] [-T ToS] [-w timeout] [-X proxy_version] [-x proxy_address[:port]] [hostname] [port[s]] nc: invalid option -- 'q' usage: nc [-46DdhklnrStUuvzC] [-i interval] [-p source_port] [-s source_ip_address] [-T ToS] [-w timeout] [-X proxy_version] [-x proxy_address[:port]] [hostname] [port[s]] nc: invalid option -- 'q' usage: nc [-46DdhklnrStUuvzC] [-i interval] [-p source_port] [-s source_ip_address] [-T ToS] [-w timeout] [-X proxy_version] [-x proxy_address[:port]] [hostname] [port[s]] Then, the assumption can also be that the "General User" isn't supposed to use such distribution releases. That's why this bugzilla. I'm just curious to know how we want to inter-operate within the distributions.
Please file a bug against Debian - they will need to fix their version of libvirt Perhaps this might be of interest to them: http://www.redhat.com/archives/libvir-list/2009-August/msg00068.html