similar to: Bug#702046: Update to 4.0.1-5.7 breaks pygrub here too

Package: xen-utils-4.0 Version: 4.0.1-5.7 Severity: normal Just dropping the note that my xen hosts suffer from this bug (#702046) -- System Information: Debian Release: 6.0.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-xen-amd64 (SMP w/12 CPU cores) Locale: LANG=en_US.UTF-8,

Package: xen-utils-4.0 Version: 4.0.1-5.7 Severity: important After Upgrading to xen-utils 4.0.1-5.7 my pygrub Xen VMs won't boot. Running pygrub manually shows: /usr/lib/xen-default/bin/pygrub --args=root="/dev/xvda ro" --output=/tmp/foo /dev/vg0/vm-disk Using <class 'grub.GrubConf.Grub2ConfigFile'> to parse /boot/grub/grub.cfg WARNING:root:Unknown directive

Patch works for me as well. /Andreas

Package: xen-utils-4.0 Version: 4.0.1-5.2 Severity: important Tags: upstream patch pygrub in Debian Squueze does not support Grub2 submenus. At least Ubuntu Precise uses a submenu for older kernel versions, so a Precise domU with more than one kernel installed will be unbootable (without manual fixes) on a Squeeze dom0. Attached is a patch that adds submenu support to pygrub. -- System

Package: xen-utils-4.0 Version: 4.0.1~rc3-1 Severity: important When invoking pygrub either via command line or via bootloader being set in the configuration file, pygrub fails because it cannot import xen.lowlevel.xc. Example output: # /usr/lib/xen-default/bin/pygrub Traceback (most recent call last): File "/usr/lib/xen-default/bin/pygrub", line 20, in <module> import

Package: xen-utils-4.0 Version: 4.0.1-1 Severity: normal File: pygrub The pygrub awesome error messages are captured below. Please tell me what pygrub was doing and why it failed. I also don't understand why <image> is supposed to be an integer. # '/usr/lib/xen-4.0/bin/pygrub' '--kernel=/vmlinuz' '--ramdisk=/initrd.img' '/dev/sda3' linux (kernel

Package: xen-utils-4.0 Version: 4.0.1-1 Severity: normal Tags: patch pygrub could not boot a newly-updated Debian/testing domU with a non-chained grub2. The traceback was: Using <class 'grub.GrubConf.Grub2ConfigFile'> to parse /grub/grub.cfg WARNING:root:Unknown directive load_video WARNING:root:Unknown directive terminal_output Traceback (most recent call last): File

Package: xen-utils-4.0 Version: 4.0.1-2 Severity: normal Trying to get a system that I've long had runing on the bare metal to boot as a VM, I discovered that pygrub would not parse my menu.lst. The problematic entry is this: # This is a divider, added to separate the menu items below from the Debian # ones. title Other operating systems: root pygrub's parser seems to

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-2 Severity: normal Tags: upstream When creating Xen DomU's, at some point xend invokes the oom-killer and the entire machine restarts: Sep 5 12:04:59 arbiter kernel: [259697.101212] __ratelimit: 136 callbacks suppressed Sep 5 12:04:59 arbiter kernel: [259697.101218] xend invoked oom-killer: gfp_mask=0x200da, order=0, oom_adj=0 Sep 5

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-4.0 Version: 4.0.1-2 Severity: normal File: pygrub pygrub error when trying to run a image created by xen-create-image with partitions option. ---------------------------------------------------------------------------------------------------------------------------------------- [2011-10-02 21:36:08 1512] DEBUG (XendDomainInfo:101) XendDomainInfo.create(['vm',

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.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-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

I recently updated the kernel on an Ubuntu 11.04 PVM domU. The dom0 is an up to date Debian Squeeze host (Xen 4.0.1). Attempting to start the domU after this with xm create gives "Error: Boot loader didn''t return any data!". I ran pygrub against the domU manually, I got the following: Traceback (most recent call last): File "/usr/lib/xen-default/bin/pygrub", line

Package: xen-utils-3.2-1 Version: 3.2.0-3~bpo4+2 Severity: normal Hi, pygrub has problems parsing block devices partitioned with Lenny Beta 2 and ext3 on paravirt guests: # /usr/lib/xen-3.2-1/bin/pygrub /var/lib/xen/images/test2.img Traceback (most recent call last): File "/usr/lib/xen-3.2-1/bin/pygrub", line 653, in ? chosencfg = run_grub(file, entry, fs) File

Hello, xen-utils-4.1's pygrub is unable to boot VMs from a partitionless blockdev that has grub installed in first sector. I'm not sure it deserves a bug report, although it is kind of a regression from 4.0. Long story short: zeroing first sector of domU's boot blockdev fixes it. Maybe some of this report would be useful in the wiki, if someone else has the same (odd) setup. --- The

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

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

Tags: patch I think this can be fixed with the following patch; it at least worked for me: http://lists.xen.org/archives/html/xen-devel/2011-01/txtLboGgCEUdF.txt -- Adi --- xen-4.1.0/tools/pygrub/src/pygrub.orig 2010-12-31 15:24:11.000000000 +0000 +++ xen-4.1.0/tools/pygrub/src/pygrub 2011-01-30 18:58:17.000000000 +0000 @@ -96,6 +96,7 @@ fd = os.open(file, os.O_RDONLY) buf =