Bug#666794: Any help?

It caught me, too! And now I'am totally lost where to look after to get my subversion working again! Any advices? NicoP. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#679899: qemu-kvm 1.1 - amd64 - undefined symbol: usbredirfilter_string_to_rul

Package: qemu-kvm Hello qemu-kvm maintainer, on Linux 3.2.0-2-amd64 #1 SMP Mon May 21 17:45:41 UTC 2012 x86_64 GNU/Linux with qemu-kvm package 1.1~z0+dfsg-1 I do receive the following error: kvm --version kvm: symbol lookup error: kvm: undefined symbol: usbredirfilter_string_to_rules The

Bug#679904: qemu-kvm 1.1 - amd64 - undefined symbol: usbredirfilter_string_to_rules

Package: qemu-kvm Version: 1.1~z0+dfsg-1 Justification: renders package unusable Severity: grave Dear Maintainer, with qemu-kvm package I do receive the following error with amd64 kernel: kvm --version kvm: symbol lookup error: kvm: undefined symbol: usbredirfilter_string_to_rules On my

Bug#679904: qemu-kvm 1.1 - amd64 - undefined symbol: usbredirfilter_string_to_rules

An: Michael Tokarev m...@tls.msk.ru, 679...@bugs.debian.org Von: Michael Tokarev m...@tls.msk.ru Datum: 02.07.2012 14:15 Kopie: Nico Prenzel nico.pren...@pn-systeme.de Betreff: Re: Bug#679904: qemu-kvm 1.1 - amd64 - undefined symbol: usbredirfilter_string_to_rules 02.07.2012 15:59, Michael

Bug#679068: qemu-kvm release 1.1?

Package: qemu-kvm Hello qemu-kvm maintainer. I've seen on kvm devel list that there were serveral problems with the qemu-kvm 1.1 release: http://www.spinics.net/lists/kvm/msg73755.html Since these last posts, there seems to be no movement with that release. Will there be a qemu-kvm 1.1 release?

Bug#651262: Please consider upgrade of all spice tools to latest stable release 0.10.x

Package: libspice-server1 Version: 0.8.3-1 Hello Debian maintainer, please consider to upgrade all spice related packages to the latest stable release 0.10.x as a lot of bugs have been fixed with this release. Also the usb redirection support requires at least the 0.9.x release. So an upgrade

Bug#651294: Please consider upgrade of libusb

Package: libusb-1.0-0 Version: 2:1.0.8-6 Hello Debian maintainer, please consider to upgrade the libusb package to the latest trunk version: http://git.libusb.org/?p=libusb.git;a=summary;js=1 ... or consider to upgrade to the libusb-1.0.9-rc3 release. At least the patch provided by Hans de

Bug#597508: please update qemu-kvm to be 0.13.0-rc1 from qemu-kvm git :)

I would second this request as there are so many nice features/bug fixes within qemu 0.13! Pherhaps there are some bugs within 0.13 we are able to diagnose and sent them back to the developers. Thanks Nico -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject

Bug#561253: hylafax-server: /etc/default/hylafax leads to wrong usage of BINDTO parameter

Package: hylafax-server Version: 2:6.0.3-5.1 Severity: normal The documentation to the BINDTO parameter leads to a wrong usage, as it won't bind to all known IP addresses if you'll leave it commented. /etc/default/hylafax # # If you need to bind hylafax to one address only, just uncomment #

Bug#536862: Upstream kvm is at version 88

Package: kvm Version: 85+dfsg-4 Hello packagers, since upstream kvm is now at 88 and the current debian version is at 85. Are there any plans to upgrade? Thanks. NicoP. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact

Bug#529743: with KVM 85 my guest jump to 100% cpu usage

Package: kvm Version: 85+dfsg-3 Hello packagers, I've upgraded from kvm 84 to 85. After this upgrade all my guests (debian 2.6.26-2-686, windows 2003) jump to 100% cpu usage. So the machine gets unresponsiveness. Could you consider to package the latest kvm release (86)? Thanks. NicoP.

Bug#529324: Cannot determine QEMU argv syntax /usr/bin/kvm

Package: libvirt-bin Version:0.6.3-2 Hello libvirt-Maintainer, please consider to package the following patch for next libvirt release. Without this patch kvm = 85 won't work with the latest (possible older releases too) release, as it reports: error: Failed to start domain *** error:

Bug#514803:

If I remember the behaviour correctly I've had my default network disabled and set to another IP adress/subnet. After I've enabled the network the guest started. But why I have to mantain an, unwanted default network? Of course, I've configured my own DMZ virtual network. Or, do I've undestood

Bug#520894: build qemu with kvm support

Package: qemu Version: 0.10.1-1 Please compile qemu with kvm integration. See the qemu doc: -enable-kvm Enable KVM full virtualization support. This option is only available if KVM support is enabled when compiling. Thanks. NicoP. -- To UNSUBSCRIBE, email to

Bug#514803: internal error Failed to add tap interface 'vnet%d' to bridge 'virbr0' : No such device

Package: libvirt-bin Version:0.6.0-1 Hi, After upgrade to libvirt-bin 0.6.0-1 I do get the following error message when I try to start a guest: internal error Failed to add tap interface 'vnet%d' to bridge 'virbr0' : No such device With libvirt-bin version 0.5.1-5 everything worked with the

Bug#505298: now, upstream is at 79

would be really nice to get KVM-79 into experimental. There are so many important fixes to me. NicoP.