similar to: Bug#745419: [PATCH] tools: pygrub: if partition table is empty, try treating as a whole disk

Yes, build issue has been resolved perfectly by Changeset 19594. However, NO  hotplug logs again. root@ServerJaunty:/var/log/xen# ls -l total 788 -rw-r--r-- 1 root root 184025 2009-05-15 11:12 domain-builder-ng.log -rw-r--r-- 1 root root 157480 2009-05-15 11:09 xend-debug.log -rw-r--r-- 1 root root 446867 2009-05-15 11:14 xend.log I''ve also made same test on F11 preview ( obviously not

I can confirm that I'm also seeing this issue with DRBD backed block devices. A test dom0 pair that I've just dist upgraded from Wheezy to Jessie is no longer able to boot any domUs via pygrub. As a test I've just pulled pygrub out of xen-tools-4.5 from experimental but I'm still getting the same error in the bootloader.log: ---- Traceback (most recent call last): File

>That is, I think the following config should work on those Ubuntu >systems > PYTHON=python > PYTHON_PREFIX_ARG='''' >although you may need to do > PREFIX=/usr/local >too. # make tools fails on Ubuntu 9.04 Server with Config.mk suggested above This one Config.mk (untouched) works fine:- PYTHON ?= python PYTHON_PREFIX_ARG ?=

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

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

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

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 =

Hi, we are still experiencing this error on stable jessie with xen 4.4.1 and it does not appear to be fixed in that version at all. The actual error is: -- snip -- Traceback (most recent call last): File "/usr/lib/xen-4.4/bin/pygrub", line 809, in <module> part_offs = get_partition_offsets(file) File "/usr/lib/xen-4.4/bin/pygrub", line 106, in

On Mon, 2014-04-21 at 15:43 +0200, Sjors Gielen wrote: > 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.

# HG changeset patch # User Zhigang Wang <zhigang.x.wang@oracle.com> # Date 1342720736 14400 # Node ID ec9655b30a5fa5b5abb3e05505f681f9be559613 # Parent 43e21ce7f22151524b800a6cf0ac4ba1233b34a7 pygrub: add syslog support to pygrub Currently, when pygrub failed, we don''t know the reason because xend/xl will not capture the stderr message. This patch will log the error message to

reopen 767295 thanks The 4.4.1-4 release only included one related fix there are actually two more: commit 379b351889a8f02abe30a06e2ce9ba8b381b91ab Author: Ian Campbell <ian.campbell at citrix.com> Date: Thu Nov 6 13:00:31 2014 +0000 tools: libxl: do not leak diskpath during local disk attach

Hi everybody, my background: I'm doing Xen since 10++ years, many years with DRBD for high availability, since some time I'm using preferable GlusterFS with FUSE as replicated storage, where I place the image-files for the vms. In my current project we started (successfully) with Xen/GlusterFS too, but because the provider, where we placed the servers, uses widely CEPH, we decided to

flight 5665 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/5665/ Regressions :-( Tests which did not succeed and are blocking: build-amd64-oldkern 4 xen-build fail REGR. vs. 5640 build-amd64 4 xen-build fail REGR. vs. 5640 build-i386-oldkern 4 xen-build fail REGR. vs. 5640

# 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

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

Hello, PyGrub scans the partition table for the first partition, where the "bootable"-flag is set. If no partition is marked, PyGrub falls back to the first partition from the table. This looks like a Bug in xen-create-image (or whatever), which doesn't set the bootbale flag and doesn't put the partition containing /boot/ as the first partition. BYtE Philipp -- Philipp

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

flight 8091 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/8091/ Regressions :-( Tests which did not succeed and are blocking: test-amd64-i386-rhel6hvm-intel 12 guest-localmigrate/x10 fail REGR. vs. 8071 Tests which did not succeed, but are not blocking, including regressions (tests previously passed) regarded as allowable: test-amd64-amd64-xl-pcipt-intel 9

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