similar to: Bug#485598: Confirmed.

Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: important Once installed, the python library of Xen are not in the python search path. Concequently, it's impossible to import anything from the xen-utils in another application. The only way to fix it is to do: cd /usr/lib/python2.5/site-packages ln -s /usr/lib/xen-3.2-1/lib/python/xen xen xen-utils-3.2-1 should in fact use the folder

Package: xen-utils-unstable Version: 3.3-unstable+hg17961-1 Severity: important if I try to start or restart xend, I get this errors: /etc/init.d/xend restart Restarting XEN control daemon: xendTraceback (most recent call last): File "/usr/lib/xen-unstable/bin/xend", line 146, in <module> sys.exit(main()) File "/usr/lib/xen-unstable/bin/xend", line 123, in main

Package: xen-utils-3.2-1 Version: 3.2.1-2 Followup-For: Bug #477525 I have the same problem after updating from etch to lenny. (Thus updating Xen from 3.0 to 3.2) Does anyone know how to fix this? -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-1-xen-amd64 (SMP w/2 CPU cores) Locale:

Package: xen-utils-3.4 Version: 3.4.3~rc6-1 Severity: important blktapctrl isn't started by default. If blktapctrl isn't started then none of the tap: disks (eg tap:aio) work. This functionality has been removed in tools-misc-xend-startup.diff @@ -120,24 +86,14 @@ if not sys.argv[1:]: print 'usage: %s {start|stop|reload|restart}' % sys.argv[0] elif

Package: xen-utils-3.4 Version: 3.4.3~rc6-1 Severity: important blktapctrl doesn't start. This means that none of the tap: disks work (eg tap:aio). It produces this in the log BLKTAPCTRL[6569]: blktapctrl.c:788: blktapctrl: v1.0.0 BLKTAPCTRL[6569]: blktapctrl.c:790: Found driver: [raw image (aio)] BLKTAPCTRL[6569]: blktapctrl.c:790: Found driver: [raw image (sync)]

Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: grave I tried to start an HVM guest to setup Windows 2003 64 bits entreprise R2, and I spent a long time figuring out that there is no /usr/lib/xen folder by default, and this is where Xen is searching for it's file when using HVM, VNC and all. Doing a simple symlink with ln -s /usr/lib/xen-3.2.1 /usr/lib/xen made it working, if it's not

Package: xen-utils-3.4 Version: 3.4.0-1 Severity: grave Justification: renders package unusable This packages should depend on the 3.4 version of xenstore utils and library, because it the Lenny versions are installed, xend crashes instead of starting up. (Many users choose to run lenny/sid hybrid systems, with lenny as default, so it's completely plausible that the wrong package will be

Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: normal Tags: patch Hi, There is a bug xen-3-3.2.1/tools/libfsimage/reiserfs/fsys_reiserfs.c, it is using "unsigned long" which is 64 bits on amd64 arch and 32 bits on i386 arch. This makes pygrub can't work on reiserfs on amd64 arch. You can easily reproduce it. A patch is included for fixing this problem. diff

Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: normal *** Please type your report below this line *** When live migrating a PV guest from one Lenny dom0 to another, the migration fails with the following error: libvir: Xen Daemon error : POST operation failed: xend_post: error from xen daemon: (xend.err '/usr/lib/xen-3.2-1/bin/xc_save 28 39 0 0 1 failed') The kernel messages

Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: important /usr/lib/xen-3.2-1/bin/blktapctrl searches for tapdisk executable in /usr/bin while is in /usr/lib/xen-3.2-1/bin this makes tap:aio unusable I've linked to /usr/bin and everything went fine perhaps the idea is to patch sources to pick executable from the right directory Regards -- System Information: Debian Release: 5.0

Package: xen-utils-3.4 Version: 3.4.0-1 Severity: important The current version of the package does not contain the IOEMU tools. This makes HVM domains, and PV domains with emulated features like VFB impossible to run. There might be good reasons for this, but then at least the package description should contain a warning that makes this obvious, so that users know that they can not simply

Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: important Please can you add python-xml as a dependancy for xen-utils-3.2-1 on lenny and above. Without python-xml a dependancy for "xm new" isn't satified. Thanks, Matthew Millar -- System Information: Debian Release: 5.0.7 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux

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-utils-3.4 Version: 3.4.0-1 Severity: important pygrub uses the fsimage library to read contents of the filesystems to boot. This package install the plugins for different filesystems at /usr/lib/xen-3.4/lib/fs/, but searches for them under /usr//usr/lib/fs. (The debian patch tools-libfsimage-prefix.diff explicitly tinkers with this path, but it fails.) This breaks pygrub. --

Package: xen-utils-3.0.3-1 Version: 3.0.3-0-4 Severity: important # /etc/init.d/xend start Restarting XEN control daemon: xendTraceback (most recent call last): File "/usr/lib/xen-3.0.3-1/bin/xend", line 40, in <module> from xen.xend.server import SrvDaemon File "/usr/lib/xen-3.0.3-1/lib/python/xen/xend/server/SrvDaemon.py", line 17, in <module> import

Package: xen-utils-3.4 Version: 3.4.0-1 Severity: critical Justification: breaks unrelated software After installing xen-utils-3.4 besides my existing xen-3.2 system, I could not start xend-3.2 anymore. The message I was getting is this: "Failed to initialize dom0 state." As far as I know, xen 3.2 and 3.4 are supposed to be able to live peacefully on the same system. (The

Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: normal When my domU uses this configuration: --- root = '/dev/sda2 ro' disk = [ 'phy:/dev/volume0/lenny.vandervlis.nl-swap,sda1,w', 'phy:/dev/volume0/lenny.vandervlis.nl-disk,sda2,w', ] --- Pygrub gives the error "Error: Boot loader didn't return

Package: xen-utils-3.4 Version: 3.4.0-2 Severity: normal Hi, the variable $DAEMON in /etc/init.d/xend is not set and thus the init.d/-script is not usable. I think it's supposed to be $XEND. Any ideas on that one? regards, Patrick -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux

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.2-1 Version: 3.2.1-2 Severity: important Intel processors have a bug with Vt that causes problems with Xen real-mode emulation. This renders FreeBSD (and possibly other OS'es) unbootable in Xen with HVM. Later versions of Xen 3.2 (and 3.3) emulate real-mode instructions so this problem doesn't exist. I would provide the relevant patches, but I do not have much