similar to: Bug#644100: PyGrub is missing bootable flag in partition

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

Control: tag -1 +fixed-upstream On Wed, 2015-11-11 at 15:39 +0000, Ian Jackson wrote: > Wei Liu writes ("Re: [PATCH] tools: pygrub: if partition table is empty, > try treating as a whole disk"): > > On Thu, Nov 05, 2015 at 02:46:12PM +0000, Ian Campbell wrote: > > > pygrub (in identify_disk_image()) detects a DOS style partition table > > > via the presence

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

Forwarding to you original patch requested. It works for me. Boris --- On Sun, 7/11/10, eXeC001er <execooler@gmail.com> wrote: From: eXeC001er <execooler@gmail.com> Subject: [Xen-devel] [PATCH] blktap2: blktap2 and pygrub (xen-unstable) To: "Xen-devel" <xen-devel@lists.xensource.com> Date: Sunday, July 11, 2010, 9:18 AM 1. Bug fix for error: "Error: Device

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

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

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

# HG changeset patch # User john.levon@sun.com # Date 1169173194 28800 # Node ID 4dcfc81c997ef92f8fa8e1622655007a0e634bca # Parent cef8ae47e6d6a70817d67849a59c0315f6cddbba Update pygrub for new Solaris directory names. Signed-off-by: John Levon <john.levon@sun.com> diff --git a/tools/pygrub/src/pygrub b/tools/pygrub/src/pygrub --- a/tools/pygrub/src/pygrub +++ b/tools/pygrub/src/pygrub @@

I just installed a CentOs 5 domU system on a CentOS 5 dom0 system following the instructions detailed here: http://wiki.centos.org/HowTos/Xen/InstallingCentOSDomU. The installation went through successfully. After installation, however, pygrub can't find a kernel. This is the xen cfg file I'm using: bootloader="/usr/bin/pygrub" name = "testsrv" memory =

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

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

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

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

hello, here is a patch to improve and fix few bugs in pygrub of xen-booloader. 1) If you already patched my last 2 patches on top of last Jeremy''s patch, then go on to apply pygrub.aq.patch. # diffstat pygrub.aq.patch pygrub | 53 +++++++++++++++++++++++++++-------------------------- 1 files changed, 27 insertions(+), 26 deletions(-) 2) If you havent applied any patches on top of

Hi, I am running Xen 3.3.1 built from Source with Debian Lenny as the dom0. Everything works fine so far except pyGRUB. So, what I did was install CentOS (latest version ... 5.3 or something) using qemu to a LVM logical volume and from within CentOS I installed the Xen Kernel. Now pyGRUB shows me 3 grub entries: 1) CentOS (2.6.18-128.1.10.el5xen) <= xen hypervisor 2) CentOS

Preamble: dom0: Xen 3.0.4 running on Ubuntu 6.06 x86_64. domU: Xen 3.0.4 or 3.1.0 kernel booting from host pygrub. File backed. ------------- I am having this strange problem getting pygrub to load consistently. When I start a domU, I sometimes get this. Error: Boot loader didn''t return any data! ... and nothing else. When I look in the xend-debug.log log, I see this.

From: pbonzini@redhat.com # HG changeset patch # User Paolo Bonzini <pbonzini@redhat.com> # Date 1319096986 -7200 # Node ID bd1f7361d3d7f4c767af21317fb4ec7ea1372f42 # Parent 1b110e895e285f43f14532e14c77597e54a0bcd2 pygrub will still try the next partition if run_grub exits with a "real" error, thus hiding the root cause from the trace. Defining a separate exception for "no

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

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