Your message dated Fri, 22 Feb 2019 22:28:03 +0100
with message-id <[email protected]>
and subject line Re: xen-utils-3.2-1: inadequate error handling for the case of
a failure to use a loopback device
has caused the Debian Bug report #503046,
regarding xen-utils-3.2-1: inadequate error handling for the case of a failure
to use a loopback device
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
503046: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=503046
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: xen-utils-3.2-1
Version: 3.2.1-2
Severity: normal
When a DomU is defined as using a file: device the loopback driver will
be used to make it appear to be a regular block device. The loopback
driver will by default only support 8 nodes so this is a limited
resource.
http://etbe.coker.com.au/2008/10/22/kernel-issues-with-debian-xen-and-centos-kernels/
If there is a problem that prevents correctly allocating the block
device (see the above URL for a description of how I encountered it when
using a CentOS kernel) then it will not free the loop device. When the
domain is destroyed with "xm destroy" it will leave the loopback device,
if you run that a few times (EG you have a script to restart DomU's on
error) then you run out of loopback devices for the system.
The error handling code needs to deal with this case.
--- End Message ---
--- Begin Message ---
On 2/22/19 4:35 PM, Hans van Kranenburg wrote:
> [...]
>
> Please note that unless there's a response within a while from now, we
> will close the bug report.
Closing now.
Hans
--- End Message ---
