similar to: Bug#403105: seconded; pygrub

Package: xen-utils-common Version: 4.1.3-4 Function check_running in /etc/init.d/xendomains incorrectly detects a not running domain as running. As a consequence thereof "/etc/init.d/xendomains stop" needs more than XENDOMAINS_STOP_MAXWAIT * "number of xen domains known to xend" seconds to run. Here is a pseudo call trace: do_stop_shutdown() { ... while read id name

Package: xen-utils-3.0.2-1 Version: 3.0.2-3+hg9762-1 >From /usr/lib/xen-3.0.2-1/lib/bin/pygrub: > sys.path = [ '/usr/lib/python' ] + sys.path > > import grub.GrubConf > import grub.fsys But grub.GrubConf, for example, is at /usr/lib/xen-3.0.2-1/lib/python/grub/GrubConf.py. Fix: change the added sys.path entry to point to /usr/lib/xen-3.0.2-1/lib/python.

Skipped content of type multipart/mixed-------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Digital signature Url : http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20061225/6b78e0ae/attachment-0002.pgp

Hi folks I propose the following changes for 3.1: - Rename source to xen-3. Upstream stripped one part of the version, so the next should be 3.2. - pygrub as extra package. - Rename i386 to i386-nonpae - Rename i386-pae to i386. PAE is upstream default now and pae images works with a 64bit hypervisor. We should think about supporting libvirt. It provides an AFAIK stable interface on the

Hi Keir, Attached patch gets rid of the global attr variable and adds support for NetBSD. Signed-off-by: Christoph Egger <Christoph.Egger@amd.com> -- AMD Saxony, Dresden, Germany Operating System Research Center Legal Information: AMD Saxony Limited Liability Company & Co. KG Sitz (Geschäftsanschrift): Wilschdorfer Landstr. 101, 01109 Dresden, Deutschland Registergericht

I've just done a fresh lenny amd64 install, and taken the xm-debian.cfg example: http://people.debian.org/~joeyh/d-i/images/daily/netboot/xen/xm-debian.cfg and built a 32 bit lenny inside a 64 bit lenny dom0 # xm create -c xm-th2.cfg install=true install-installer=http://people.debian.org/~joeyh/d-i/images/daily/ When I try to boot the domU: # xm create -c xm-debian.cfg it

Package: xen-3.0 Version: 3.0.3-0-2 Severity: serious This source package is not binNMU safe, which I understand is an RC bug. If the changelog, or any of several other files are changed, the build process wants to rebuild debian/control, and tries to use files from linux-support-2.6.18-1 to do it. This fails, since that package is a) not a build dependency b) not in the archive under that name

I just tripped over this issue with pygrub. The code is written such that saying bootloader="pygrub" should cause the correct path to be used, the attached patch simply fixes this path to be correct. I don't have an HVM capable test machine handy (so I can't actually confirm this works) but I think changing the default "kernel" for an HVM guest to point to the correct

I have recently discovered when trying to configure a new domU that pygrub is completely broken. That is, the missing Build-Depend on e2fslibs-dev in xen-3.0 causes the ext2/3 python module to not be build. Consequently, using pygrub fails miserably since the filesystem cannot be read at all by pygrub. Additionally, it is apparently not possible for pygrub to find its library directory without

This is a relatively simple fix i found, I don't know if it need to be reported to upstream. Since the script resolves additional dependencies anyway by appending the path, we simply move the import xen.lowlevel.xc line to below the line that appends path. Worked like a charm for me. Rergards, Dmitry -------------- next part -------------- A non-text attachment was scrubbed... Name:

Hi Bastian, I'd like to propose backporting the following changesets from upstream xen-unstable into the xen-3 package. With these it is possible to boot a default installation of Squeeze (using d-i) in a domU using pygrub. 20480:c2c2e67b8198 pygrub: if default entry is "saved" then use first entry. 20481:8f4e0adc2b3b pygrub: expands tabs before displaying menus. 20485:086a6a0c3f37

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: libxen-dev Version: 3.2.0-2 Severity: wishlist Tags: patch Hi, libvirt needs privcmd.h to build. Please apply. Thanks for building a libxen-dev package, -- Guido Index: xen-3-3.2.0/debian/libxen-dev.install =================================================================== --- xen-3-3.2.0.orig/debian/libxen-dev.install 2008-01-28 18:43:43.000000000 +0000 +++

I''m trying to get ceph working with decent performance (currently getting kb/second write performance!) and it seems that maybe the Debian wheezy kernel is just a bit too ancient. The 3.8 kernel from experimental works on bare metal, but when booting as dom0 under the xen hypervisor it crashes. I just figured out how to redirect xen output to my IPMI/BMC serial port and I see this:

Hi There, I have a bit of an odd issue. I am testing Xen 3.0.2 on a machine before fully migrating to it from 2.0.7. The host OS is Ubuntu 6.06, and I am running the pre-compiled Xen code (kernel, tools) from the Xen site. I have two NICs, both if which I amhidung from Dom0 via the ''pciback.hide'' grub entry. I am have the bridges setup in the

There''s few CVE for Xen, are we affected, and are fixes planned for Lenny, Squeeze and Unstable? * A denial of service (Host Crash) in the XEN hypervisor. (CVE-2011-2901) * A bug was found in the way Xen handles CPUID instruction emulation during VM exits. An unprivileged guest user can potentially use this flaw to crash the guest. (CVE-2011-1936) * A 64-bit guest can get one

On Mon, 2013-08-19 at 13:28 +0200, Bastian Blank wrote: > On Fri, Aug 16, 2013 at 03:16:49PM +0100, Ian Campbell wrote: > > Looking through http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=xen I > > think it would be useful to add some usertags, in particular to easily > > filter for toolstack specific (i.e xend) bugs. > > I've never seen the use for this. I was

Hi all, I''m running XP and 2003 Server fine as HVM guests (under a 32 bit non-pae Xen 3.0.3 self-compiled). I''ve read that Vista can *not* be /installed/ under Xen for it checks for ACPI support and install fails if it isn''t present. What if I do the install first from, say, plain Qemu (I''re reused qemu images from Xen) or VMWare (I''ve converted

Package: xen-utils-common Version: 4.1.3-2 Severity: important IMPORTANT NOTE: This bug has been generated using reportbug run from a debian stable system. The affected debian testing systems are isolated in a lab and do not have internet access. The issue is wholly reproducible on several different debian testing installations. xen-utils-common fails to install if xen cannot be started.

Howdy, The attached bug report was sent to the Debian bug tracking system. If you please preserve the CC to 405058-forwarded at bugs.debian.org on any responses? ----- Forwarded message from Joey Hess <joeyh at debian.org> ----- From: Joey Hess <joeyh at debian.org> To: Debian Bug Tracking System <submit at bugs.debian.org> Subject: Bug#405058: does not properly support