similar to: Bug#374876: xen-utils-3.0: mandatory items of README.Debian should be handled automatically

Package: xen-utils-3.0 Version: 3.0.2+hg9681-1 Severity: normal In the tls section: it fails to mention the better solution (apt-get install libc6-xen) In the kernel section: where it says "for now we cannot provide precompiled Linux kernels with the xen patch applied", that's not true either. apt-get install linux-image-2.6-xen-k7 or some such. -- System Information: Debian

Package: xen-utils-3.0 Version: 3.0.2+hg9681-1 Severity: normal I get this error with xen after some debug cycles, start / stopping nodes. I found this fix on the net, which fixes the problem: http://lists.xensource.com/archives/html/xen-users/2006-04/msg01070.html in /etc/init.d/xen: start) + modprobe loop max_loop=64 + cd /dev && /dev/MAKEDEV loop xend start

Package: xen-utils-3.0 Version: 3.0.2+hg9681-1 Severity: important When trying to install xen-utils, I get the following message: Unpacking xen-utils-3.0 (from .../xen-utils-3.0_3.0.2+hg9681-1_i386.deb) ... Setting up xen-utils-3.0 (3.0.2+hg9681-1) ... Starting XEN: invoke-rc.d: initscript xend, action "start" failed. dpkg: error processing xen-utils-3.0 (--configure): subprocess

Package: xen-utils-3.0 Version: 3.0.2+hg9681-0bpo1 Severity: important Disclaimer: I'm using the packages from www.backports.org here (in the box where the problem manifested), but I've seen that it happens too with the packages straight from sid. When I installed the packages for Xen and created a domU ("chen.cfg"), it couldn't be brougth up. The error that was displayed

Package: xen-utils-3.0 Version: 3.0.2+hg9697-1 Severity: normal On unstable, xen-utils-3.0 can't be installed, due to dependencies. Reproducable: yes. Just install unstable and try to install xen-utils-3.0. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash

As a quick extra note, /usr/share/doc/xen-utils-4.1/README.Debian from xen-utils-4.1 version 4.1.2-2 still reads: | 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

On Wed, 22 Oct 2008, Russell Coker wrote: > It seems reasonable to create a file /etc/modprobe.d/xen that contains > the following line to alleviate this: > options loop max_loop=32 Since kernel 2.6.22, loop devices are allocated dynamically, so that you can `mknod /dev/loopN b 7 N` for any N and start using it immediately. The max_loop option causes more loop devices to be

FYI: The status of the xen-3.0 source package in Debian's testing distribution has changed. Previous version: 3.0.2+hg9656-1 Current version: 3.0.2+hg9681-1 -- This email is automatically generated; henning@makholm.net is responsible. See http://people.debian.org/~henning/trille/ for more information.

Package: xen-utils-3.0 Severity: wishlist Please include support for HVM-based guests. This allows hardware virtualization on systems with Intel's chips with VT (IE, Pentium D 930), and AMD's future chips with Pacifica. HVM allows you to run unmodified operating systems under Xen, such as Windows XP/2003. The following files are needed: /usr/lib/xen/bin/qemu-dm

Package: xen-utils-4.0 Version: 4.0.1-1 Severity: normal When I invoke me at dev:~# xentrace_format I get exec: 22: /usr/lib/xen-4.0/bin/xentrace_format: not found as result. The missing python script is referenced by the /usr/sbin/xentrace_format script from the xen-utils-common package. Using the python script from another (xen 4.0.0) distribution works fine. So I assume the file is

Package: xen-utils-common Version: 3.0.3-0-2 Severity: normal On my systen, the script vif-common fails to retrieve the primary IP address of my ethernet device, preventing a domU from starting. I tracked this issue down to the file /etc/xen/script/vif-common. The function ip_of uses the following shell code to extract the address: ip addr show "$1" | awk "/^.*inet.*$1\$/{print

Package: xen-utils-4.0 Version: 4.0.0-2 Severity: important xend does not start because of a bug in option parsing. Error described here: http://www.gossamer-threads.com/lists/xen/devel/172035 Patch: --- a/tools/python/xen/xend/XendOptions.py Mon Apr 26 12:13:23 2010 +0100 +++ b/tools/python/xen/xend/XendOptions.py Wed Apr 28 16:54:04 2010 +0200 @@ -207,18 +207,18 @@ def

Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: grave Justification: renders package unusable qemu-dm sends out this: - supported machines are: pc Standard PC (default) isapc ISA-only PC - instead of: - Supported machines are: xenfv Xen Fully-virtualized PC (default) xenpv Xen Para-virtualized PC - this renders any tries to use HVM fail. -- System Information:

Package: xen-3.0 Version: 3.0.2+hg9681-1 Your package fails to build with GCC 4.2. Version 4.2 has not been released yet but I'm building with a snapshot in order to find errors and give people an advance warning. The bug below is in your package though and not because I'm using a snapshot of the compiler so please take a look at it. You can reproduce this with the gcc-snapshot

Package: xen-utils-3.4 Version: 3.4.3~rc3-1 Severity: wishlist the upstream version of pygrub in 3.4.3 already supports grub2. It would be very nice to update pygrub in your package to the current version. Thanks in advance. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64)

Package: xen-utils-3.4 Version: 3.4.2-2 Severity: important *** Please type your report below this line The Package is fail cause the directoryname /usr/lib/xen-3.4 is wrong when i call the xm tool a wrapperscript searching for version 3.4.0 and dont find 3.4.0 it must be /usr/lib/xen-3.4.0 and all is fine *** -- System Information: Debian Release: squeeze/sid APT prefers testing APT

Package: xen-utils-3.4 Version: 3.4.0-0~ct Severity: important After installation of linux 2.6.26-2-xen-686 and xen-utils-3.4 the 2 onboard NICs 82574L (driver e1000e) are not working. ping results always in unreachable hostname ethtool seems fine for the eth's mii-tool has no transceiver for the eth's ip link show shows an UNKNOWN state for the eth's With linux 2.6.26-2-xen-686 and

Package: xen-utils-common Version: 3.2.0-2 Severity: normal When file: sources are used for Xen block devices the Xen system will use a loopback device for each one. It's quite common for DomUs to be configured with two block devices (one for storage and one for swap) and not uncommon to have a block device for each filesystem (which makes it easier to grow filesystems). Therefore the

All, I've spent quite a few hours trying to figure this out to no avail... I have two machines and the result is the same on both. Additionally, each machine does not support full hardware virtualization... I am able to create 8 VMs. When attempting to create ninth VM, I get the following error: Error: Device 51712 (vbd) could not be connected. /etc/xen/scripts/block failed; error

Linus, On Wed, 2008-03-05 at 23:21 +0100, Linus Neumann wrote: > I read your "rsync on Mac" Discussion dated January 2008. > I would be very thankful if you could help me with the exact same > problem. This kind of message should go to the rsync list for archival even if you have a good guess of who will answer it. > --iconv=UTF8-MAC,ISO-8859-15 > Linux: >