similar to: Bug#409392: xen-utils-3.0-unstable-1: xenstored creates /dev/xen/evtchn with the wrong minor

close 409392 thanks Disregard - I should be using the stable hypervisor. -- nate carlson / ncarlson@ibsys.com / 651-365-4124 sr. systems administrator - nbcsports.com @ ib

Anyone else seeing problems with this combo? I'm running: linux-image-2.6.18-4-xen-686 2.6.18.dfsg.1-9 linux-modules-2.6.18-4-xen-686 2.6.18.dfsg.1-9 xen-hypervisor-3.0-unstable-1-i386-pae 3.0-unstable+hg11561-1 xen-utils-3.0-unstable-1 3.0-unstable+hg11561-1 xen-utils-common 3.0.3-0-2 When I try to fire up xend, it bombs.. doing some

Package: xen-ioemu-3.0-unstable Version: 3.0-unstable+hg11561-1 Severity: normal When trying to create an HVM domain with vif settings enabled (as default) qemu-dm fails to start the virtual machine claiming that the tap device cannot be found. This is because qemu-dm tries to execute /etc/xen/qemu-ifup which is instead located in /etc/xen/scripts/qemu-ifup. As a side note qemu-dm seems to be

Package: xen-ioemu-3.0-unstable Version: 3.0-unstable+hg11561-1 Severity: normal Hi, in #393609 /etc/xen/scripts/qemu-ifup is wrongly placed/referred. This script is missing from the amd64 package, making network enabled HVM domain not startable. Regards, L -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture:

Processing commands for control@bugs.debian.org: > # Automatically generated email from bts, devscripts version 2.9.27 > # closing per submitter > close 409392 Bug#409392: xen-utils-3.0-unstable-1: xenstored creates /dev/xen/evtchn with the wrong minor 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Nate

Package: xen-utils-common Version: 3.0.3-0-2 Severity: important I have installed all the packages I can think of to get Xen going and it still fails with the following : /var/log/xen/xend-debug.log: Exception starting xend: (111, 'Connection refused') er.py", line 463, in process_request_thread self.finish_request(request, client_address) File "SocketServer.py",

Package: xen-utils-3.0.3-1 Version: 3.0.3-0-2 Severity: normal # xentrace /usr/lib/xen-3.0.3-1/bin/xentrace: error while loading shared libraries: libxenctrl.so: cannot open shared object file: No such file or directory It seems that we need a /etc/ld.so.conf.d/xen file that includes directory /usr/lib/xen-3.0.3-1/lib . -- System Information: Debian Release: 4.0 APT prefers testing APT

Package: xen-utils-3.0.3-1 Version: 3.0.3-0-2 Severity: normal pygrub can't work with this package, because the fsys filesystem modules included in the source package are missing. As a workaround, I downloaded the xen-3.0 source package, went into tools/pygrub/src/, installed e2fslibs-dev and libreiserfs0.3-dev, ran "make", and copied stuff from

Package: xen-utils-3.0.3-1 Version: 3.0.3-0-2 Severity: normal It seems that the blktap module is not included. As loopback images are deprecated in Xen, theis module is vital for using file backed VBDs in Xen. -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable'), (200, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to

Package: xen-utils-3.0.3-1 Version: 3.0.3-0-2 Severity: normal Since this package installs python modules in /usr/lib/xen-3.0.3-1/lib/python/, and uses them directly from there, not following the python policy, once xend has started up, lots of .pyc files are created there, which will not be removed if the package is purged. These pyc files may also cause problem for future python upgrades, I

Package: xen-utils-3.0.3-1 Version: 3.0.3-0-2 Severity: important the xen-utils packages lack xfrd, which is required for live domain migrations using xm migrate. -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-1-686 Locale:

Package: xen-utils-3.0.3-1 Version: 3.0.3-0-3 Severity: grave Tags: security Justification: user security hole Xen versions 3.x, and 3.1 contain a tool for processing Xen trace buffer information. This tool uses the static file /tmp/xenq-shm insecurely allowing a local user to truncate any local file when xenbaked or xenmon.py are invoked by root. Sample session: # setup. skx

Package: xen-utils-3.0.3-1 Version: 3.0.3-0-4 Severity: normal Booting with pygrub doesn't work. First problem is the path to libraries (/usr/lib/python is used instead of /usr/lib/xen-3.0.3-1/lib/python): $ /usr/lib/xen-3.0.3-1/bin/pygrub Traceback (most recent call last): File "/usr/lib/xen-3.0.3-1/bin/pygrub", line 25, in ? import grub.GrubConf ImportError: No module

Package: xen-unstable Version: 3.0-unstable+hg11561-1 Followup-For: Bug #399700 The included patch overcomes the old build dependency on linux-support-2.6.17-2, and replaces it with linux-support-2.6.22-3. I filed a previous bug #453912 - but I guess it doesn't apply? -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable')

Package: xen-utils-3.0.3-1 Version: 3.0.3-0-2 Severity: wishlist Xen can run 32bit domU clients on 64bit (amd64) dom0. Unfortunately only amd64 linux-image-xen packages are available on arch amd64. Please provide 686 packages as well (if possible). This would enable the installation of 32bit clients without the need to manually compile a kernel. Feel free to reassign this bug to the correct

Package: xen-utils-3.0.3-1 Version: 3.0.3-0-2 Severity: important After installing Xen and setting up (network-script 'network-bridge netdev=eth0') I no longer have a sane IPv6 address in the dom0: inet6 2001:700:300:d03f:fcff:ffff:feff:ffff/64 scope global dynamic valid_lft 2591977sec preferred_lft 604777sec This is probably since xenbr0 has a MAC address of fe:ff:ff:ff:ff:ff;

a separate partition Reply-To: Csillag Kristof <kristof.csillag@ge.com>, 397758@bugs.debian.org Resent-From: Csillag Kristof <kristof.csillag@ge.com> Resent-To: debian-bugs-dist@lists.debian.org Resent-CC: Debian Xen Team <pkg-xen-devel@lists.alioth.debian.org> Resent-Date: Thu, 09 Nov 2006 09:33:19 +0000 Resent-Message-ID: <handler.397758.B.11630647553439@bugs.debian.org>

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

Package: xen-hypervisor-3.0-unstable-1-i386 Version: 3.0-unstable+hg11561-1 Severity: important I've installed xen-linux-system-2.6.17-2-xen-k7 (version 2.6.17-9) on a server, and planned to run 3 Xen domUs on it. Creating the domUs was no problem, and running two of them works well. Starting the third one however will crash the dom0 and forces it to reboot. The machine is a Athlon64 3800+

Package: xen-utils-3.0.3-1 Version: 3.0.3-0-4 Severity: normal Rebooting from inside domU hangs in initrd: Begin: Waiting for root file system... ... Root file system is not available because underlying DRBD device got deactivated during reboot: $ cat /proc/drbd version: 8.0.13 (api:86/proto:86) GIT-hash: ee3ad77563d2e87171a3da17cc002ddfd1677dbe build by phil at fat-tyre, 2008-08-04