It looks like the issue has already been reported to the kernel: #897427
Feel free to close this bug here if nothing needs to be done in libvirt.
Sorry for the noise.
Package: libvirt-daemon
Version: 1.2.9-9+deb8u5
Hello,
I'm using libvirt on jessie to manage several qemu based vms.
After upgrading my host kernel from linux-image-3.16.0-5-amd64 to
linux-image-3.16.0-6-amd64 and restarting the system, only a single vm
came up. Syslog shows:
libvirtd: Cannot ge
Hello,
thanks @Jakob for pointing out the upstream issue.
Is there any plan to backport the fix into Debian stretch?
The issue is quite annoying and downgrading or using the package from
sid/buster feels uncomfortable.
Upstream issue 214 [1] is marked as duplicate of 348. There [2] you can
find
Package: wnpp
Severity: wishlist
"tcpproxy is a simple tcp connection proxy which combines the features
of rinetd and 6tunnel. tcpproxy supports IPv4 and IPv6 and also supports
connections from IPv6 to IPv4 endpoints and vice versa."
Since rinetd does not support IPv6 I was looking for alternativ
Package: libspf2-2
Version: 1.2.10-5
Tags: patch
Dear Maintainer,
the library does not provide any data for the Received-SPF header or the
explanation when:
a) the domain does not publish any SPF records or
b) the domain publishes more than one SPF record (which is a permerror)
This is annoying
On 11/17/2015 08:36 PM, Guido Günther wrote:
>> We should specify a timeout in the libvirt-guests.service file, ideally
>> take directly the configured timeout from /etc/default/libvirt-guests .
>
> This could be done using a generator _but_ since we don't know the
> number of guests and the overa
Package: libvirt-daemon-system
Version: 1.2.9-9+deb8u1
In /etc/default/libvirt-guests the default timeout for guests shutting
down or suspending on host shutdown/reboot is 300 seconds. However,
systemd has timeouts for service units to stop. The default is 90
seconds, as viewable by:
systemctl sho
7 matches
Mail list logo
