[Pkg-xen-changes] r1008 - trunk/xen/debian

[Bastian Blank]

Author: waldi
Date: Sun May  6 14:11:29 2012
New Revision: 1008

Log:
* debian/changelog: Update.
* debian/xen-utils-common.README.Debian:
  Remove incorrect sentence about loop devices.

Modified:
   trunk/xen/debian/changelog
   trunk/xen/debian/xen-utils-common.README.Debian

Modified: trunk/xen/debian/changelog
==============================================================================
--- trunk/xen/debian/changelog	Sat May  5 19:24:54 2012	(r1007)
+++ trunk/xen/debian/changelog	Sun May  6 14:11:29 2012	(r1008)
@@ -1,6 +1,7 @@
 xen (4.1.2-6) UNRELEASED; urgency=low
 
   * Fix generation of architectures for hypervisor packages.
+  * Remove information about loop devices, it is incorrect. (closes: #503044)
 
  -- Bastian Blank <waldi at debian.org>  Sat, 05 May 2012 21:24:18 +0200
 

Modified: trunk/xen/debian/xen-utils-common.README.Debian
==============================================================================
--- trunk/xen/debian/xen-utils-common.README.Debian	Sat May  5 19:24:54 2012	(r1007)
+++ trunk/xen/debian/xen-utils-common.README.Debian	Sun May  6 14:11:29 2012	(r1008)
@@ -27,27 +27,3 @@
 included network setup by adding
   (network-script network-bridge)
 to the file. But please note that this may or may not work.
-
-Loop devices
-------------
-
-If you plan hosting virtual domains with file backed block devices (ie. the
-ones xen-tools creates by default) be careful about two issues:
-
-1. Maximum number of loop devices
-   By default the loop driver supports a maximum of 8 loop devices. Of
-   course since every Xen domain uses at least two (one for the data and one
-   for the swap) this number is absolutely insufficient. You should increase
-   it by adding a file named local-loop in /etc/modprobe.d containing the
-   string "options loop max_loop=128", if the loop driver is compiled as a
-   module, or by appending the string max_loop=128 to your kernel parameters
-   if the driver is in-kernel. Of course you can increase or decrease the
-   number 128 as you see fit.
-
-2. Driver loading (only if loop is compiled as a module)
-   Normally the loop driver gets loaded when the first loop device is
-   accessed. When using udev, though, the loop devices get created only
-   after the driver gets loaded. This means that Xen will fail if the loop
-   driver is not already loaded when it tries to start a file-backed virtual
-   domain.  To fix this just add "loop" in your /etc/modules file, thus
-   forcing it to be loaded at boot time.