similar to: Patches for Xen 3.1 packaging, changes for pygrub and man pages

Package: xen-utils-3.2-1 Version: 3.2.0-4 Severity: important Tags: patch pygrub uses tools/libfsimage to read a guest filesystem. Unfortunately the grub derived code does not support 256 byte inodes. Grub itself has been patched (see #463236 and #463123) and this patch has now been applied to the upstream Xen tree. See <http://xenbits.xensource.com/staging/xen-unstable.hg?rev/c777e572a467>

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-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-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-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-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~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.1 Version: 4.1.3-7 Severity: normal pygrub looks for extlinux config files "/boot/isolinux/isolinux.cfg" and "/boot/extlinux.conf", but the default Debian installation uses the config file "/boot/extlinux/extlinux.conf". (See /usr/lib/xen-4.1/bin/pygrub lines 405-407.) ...Marvin -- System Information: Debian Release: 7.0 APT prefers testing

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.1 Version: 4.1.3-7 Severity: normal The grub.cfg created by a default Debian installation uses many configuration statements that pygrub does not recognize, and pygrub is unable to find any kernel to load. ...Marvin -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (990, 'testing'), (500, 'stable-updates'), (500,

Package: xen-utils-4.1 Version: 4.1.3-7 Severity: normal pygrub does not recognize the include statement in extlinux.conf. The default Debian installation of extlinux creates a stub extlinux.conf which includes linux.cfg, where all the linux image entries are. This means that even if bugs 697407 and 697409 are fixed, pygrub still can't find the right kernel on a default Debian installation

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-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.4 Version: 4.4.1-9+deb8u8 Severity: normal Under Xen 4.1 in Debian 7 (wheezy), the following works when included in a DomU configuration in "/etc/xen/cfg/" -- bootloader = '/usr/lib/xen-default/bin/pygrub' After upgrading to Xen 4.4 as part of an upgrade to Debian 8 (jessie), the DomU silently fails to start. Examination of the log files shows that the

Package: xen-utils-4.1 Version: 4.1.3-7 Severity: normal The function is_disk_image in /usr/lib/xen-4.1/bin/pygrub at line 45 distinguishes a partitioned disk from a partition by looking for 0xaa55 at offset 0x1fe in the image, but this is the bootsector signature, not the partition table signature. extlinux and other bootloaders put this signature there on bootable partitions (which don't

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

Hi I have been using pygrub for most of the needs. Was trying out some stuff on SLES 10 SP1. It seems that it does not have pygrub!! On the other hand,they have domUloader.py which requires bootargs="--entry=hda:/boot/vmlinuz...., path to ramdisk. It is quite strange to be asking for the path of the kernel and the ramdisk to be supplied in the conf file!!. Am I missing something

Hi I have been using pygrub for most of the needs. Was trying out some stuff on SLES 10 SP1. It seems that it does not have pygrub!! On the other hand,they have domUloader.py which requires bootargs="--entry=hda:/boot/vmlinuz...., path to ramdisk. It is quite strange to be asking for the path of the kernel and the ramdisk to be supplied in the conf file!!. Am I missing something

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