similar to: Bug#697417: xen-utils-4.1: pygrub is unable to parse default Debian grub.cfg

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

Booting a fedora 19 domU failed because a it could not properly parse the grub.cfg file. This was cased by set default="${next_entry}" This statement actually is within an ''if'' statement, so maybe it would be better to skip code within if/fi blocks... But this patch seems to work fine. --- tools/pygrub/src/GrubConf.py | 2 ++ 1 files changed, 2 insertions(+), 0

This grub.cfg from a default fedora 19 Beta install caused pygrub failures.The previous pygrub commit fixed taht. So this example file added for reference. Signed-off-by: Marcel Mol <marcel@mesa.nl> --- tools/pygrub/examples/fedora-19.grub2 | 117 +++++++++++++++++++++++++++++++++ 1 files changed, 117 insertions(+), 0 deletions(-) create mode 100644 tools/pygrub/examples/fedora-19.grub2

Processing commands for control at bugs.debian.org: > merge 697407 697409 697412 697417 Bug #697407 [xen-utils-4.1] xen-utils-4.1: pygrub doesn't find extlinux.conf in default Debian location Bug #697409 [xen-utils-4.1] xen-utils-4.1: pygrub does not correctly distinguish between "disk with partitions" and "partition" Bug #697412 [xen-utils-4.1] xen-utils-4.1: pygrub

# HG changeset patch # Parent aa479945f718ff775c18afa2f37a391fca573114 # User carnold@suse.com # Date 1350668686 21600 pygrub: Add option to list grub entries The argument to "--entry" allows 2 syntaxes, either directly the entry number in menu.lst, or the whole string behind the "title" key word. This poses the following issue: From Dom0 there is no way to guess the number

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-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-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-hypervisor-4.1-amd64 Version: 4.1.1-3 Severity: important Whenever I try to start a domU, xm create failed for 'Boot loader didn't return any data!'. % sudo xm create -c squeeze.cfg Using config file "/etc/xen/squeeze.cfg". Error: Boot loader didn't return any data! It seems related to the following error in dmesg [1440.163935] pygrub[3654] trap invalid

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-common Version: 4.0.0-1 Severity: wishlist Tags: patch I am not a gawk/mawk expert, but I looked carefully at the few uses of gawk that I saw in /etc/xen/scripts/vtpm-common.sh and network-bridge, and I did not see anything that was gawk-specific. It would be nice if they could be changed to awk and the dependency on gawk removed. base-files is Essential: yes and it

Processing commands for control at bugs.debian.org: > tags 697412 + moreinfo Bug #697412 [src:xen] xen-utils-4.1: pygrub does not recognize the include statement in extlinux.conf Bug #697407 [src:xen] xen-utils-4.1: pygrub doesn't find extlinux.conf in default Debian location Bug #697409 [src:xen] xen-utils-4.1: pygrub does not correctly distinguish between "disk with partitions"

Package: xen-utils-4.1 Version: 4.1.4-3+deb7u1 Severity: important When an LVM LV that serves as the root disk for a Xen DomU contains a boot loader (or possibly other data) in its volume boot record, pygrub fails to boot it, printing "Error: boot loader didn't return any data" before exiting. I think this is because of the function "is_disk_image" on line 45 of

Subject: xen-utils-4.1: /usr/lib/xen-default missing Package: xen-utils-4.1 Version: 4.1.3-1 Severity: important Dear Maintainer, when using paravirtualization with xen and libvirt the path for pygrub is: /usr/lib/xen-default/bin/pygrub But this path is not provided with xen-utils-4.1 and will brake upgrades to wheezy. With xen-utils-4.0 and debian squeeze this path is provided with

This patch removes the extra command `install pygrub` because this is already done by the setup.py script. Signed-off-by: Anthony PERARD <anthony.perard@citrix.com> --- This patch need to be applied after the patch named "Fix pygrub install." tools/pygrub/Makefile | 1 - 1 files changed, 0 insertions(+), 1 deletions(-) diff --git a/tools/pygrub/Makefile

If we pass 0 as pygrub --entry argument (i.e. we want to boot first item), default value is used instead. This is dueto wrong check for range of allowed values of index - 0 is index of first item. Signed-off-by: Miroslav Rezanina <mrezanin@redhat.com> Patch: --- diff --git a/tools/pygrub/src/pygrub b/tools/pygrub/src/pygrub index 1845485..eedfdb2 100644 --- a/tools/pygrub/src/pygrub +++

Hello! My Dom0 config: Xubuntu 8.10 + "Xen-3.3.1 and kernel-2.6.18-xen.hg" I have Nexenta CP2 RC1 (Opensolaris b104) on ZFS file system. I installed this OS in HVM. For PV i used pygrub. My config file: ''ncp2.pygrub'' bootloader = "/usr/bin/pygrub" boot = "c" memory = 512 name = "NexentaPV" uuid =

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