similar to: Bug#500557: xen-utils-3.0.3-1: pygrub boot not working

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

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

On Tue, 2013-10-01 at 09:10 -0700, Tril wrote: > Sorry didn't work. Hrm, odd, it worked when based on the upstream xen-unstable tree. Perhaps something else is needed against 4.1 for the backport to work. > Aso it will only handle this special case, not the > general case of /dev/something. Right, in this context there isn't really a general case since for things to work with

Sorry didn't work. Aso it will only handle this special case, not the general case of /dev/something. # python GrubConf.py grub2 /home/tehadmin/snail-grub.cfg WARNING:root:Unknown directive load_video WARNING:root:Unknown directive terminal_output WARNING:root:Unknown image directive load_video Traceback (most recent call last): File "GrubConf.py", line 467, in <module>

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

On Sat, 2013-09-28 at 20:59 -0700, Tril wrote: > Backtrace from manual run of the buggy GrubConf.py: > # python /usr/lib/xen-4.1/lib/python/grub/GrubConf.py grub2 grub.cfg > WARNING:root:Unknown directive load_video > WARNING:root:Unknown directive terminal_output > WARNING:root:Unknown image directive load_video > Traceback (most recent call last): > File

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

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

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-3.0 Version: 3.0.2+hg9697-1 Severity: important Hello, There was a problem while autobuilding your package: > Automatic build of xen-3.0_3.0.2+hg9697-1 on avidan by sbuild/i386 0.49 > Build started at 20060725-0410 > ****************************************************************************** ... > CFLAGS="-O2 -fomit-frame-pointer -DNDEBUG -m32 -march=i686 -Wall

You get these if you install Debian Wheezy as HVM and then try to convert to PV. This is Debian bug #603391. Signed-off-by: Ian Campbell <ian.campbell@citrix.com> Tested-by: Tril <tril@metapipe.net> --- tools/pygrub/examples/debian-wheezy-hvm.grub2 | 104 +++++++++++++++++++++++++ tools/pygrub/src/GrubConf.py | 6 +- 2 files changed, 109 insertions(+), 1

Confirmed this issue. To reproduce: Install a fresh Wheezy AMD64 guest under Xen 4.1 (hypervirtualized, boot from the debian-7.1.0-amd64-CD-1.iso). Use "entire disk" automatic layout for partitioning, this creates /dev/xvda1 for / and /dev/xvda5 for swap. It will create /boot/grub/grub.cfg with many references to (/dev/xvda,msdos1) which works fine when the machine is booted

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

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

Keir, This would also be appropriate for 3.1.0, since the /usr/lib fix makes pygrub work on ia64 Presently pygrub only looks in /efi/redhat/elilo.conf. It should check for other distributions, plus a couple fallback locations. Signed-off-by: Aron Griffis <aron@hp.com> diff -r 6d64f9eefad5 -r 67df28389f46 tools/pygrub/src/pygrub --- a/tools/pygrub/src/pygrub Wed May 02 14:50:56 2007

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

# 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

Control: tags -1 +moreinfo On Wed, 24 Sep 2008 17:19:08 +0200 Valentin Vidic <vvidic at carnet.hr> wrote: > 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