search for: 603391

I double-checked, I edited the file correctly. I don't know python much, but it seems the lower stack traces are deeper than the upper ones, which means somehow your calling "self.disk =" inside a set_disk method seems to have re-entered itself as if set_disk is a handler for self.disk =...

On Mon, 2013-10-07 at 21:13 -0700, Tril wrote: > I double-checked, I edited the file correctly. > > I don't know python much, but it seems the lower stack traces are > deeper than the upper ones, which means somehow your calling > "self.disk =" inside a set_disk method seems to have re-entered itself > as if set_disk is a handler for self.disk =... It should be

got it, added underscore, my mistake. Patch works.

Processing commands for control at bugs.debian.org: > close 603391 4.4.0-1 Bug #603391 [xen-utils-4.0] pygrub: unintelligible error messages There is no source info for the package 'xen-utils-4.0' at version '4.4.0-1' with architecture '' Unable to make a source version for version '4.4.0-1' Marked as fixed in versions 4.4.0-1. Bug...

tags 603391 +moreinfo thanks Hello, It's been quite a while so I suspect the answer will be no but do you happen to have a copy of the problematic grub configuration file? Thanks, Ian.

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>

...c2f1ba1ccc89658257fc746 Author: Ian Campbell <ian.campbell at citrix.com> Date: Tue Oct 1 10:46:07 2013 +0100 pygrub: Support (/dev/xvda) style disk specifications 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 at citrix.com> diff --git a/tools/pygrub/examples/debian-wheezy-hvm.grub2 b/tools/pygrub/examples/debian-wheezy-hvm.grub2 new file mode 100644 index 0000000..b5ee9e2 --- /dev/null +++ b/tools/pygrub/examples/debian-wheezy-hvm.grub2 @@ -0,0...

This indeed still happens with xen-utils-4.1 4.1.4-3+deb7u1 Additionally, the problem is hard to figure out (as it simply excepts with "RuntimeError: Unable to find partition containing kernel", which it does in many other cases as well; perhaps it should collect other caught exceptions for debug purposes). The grub.cfg, in my case, was generated by update-grub (from inside the guest)

The image argument to pygrub does not need to be an integer. The "invalid literal for int()" error probably means that your menu.lst contains something like "root=(/dev/sda)". The root should be specified in grub notation like "root=(hd0)". You might want to have a look at /boot/grub/devices.map. To map /dev/sda to hd0, you could add an entry like: (hd0) /dev/sda

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

...sor-4.0-amd64] xen-hypervisor-4.0-amd64: Different network traffic values from dom0 vs domU Added tag(s) upstream. > tags 659642 + upstream Bug #659642 [xen-hypervisor-4.0-amd64] xen-hypervisor-4.0-amd64: outl segfaults when restoring monitor from sleep with DPMS Added tag(s) upstream. > tags 603391 + upstream Bug #603391 [xen-utils-4.0] pygrub: unintelligible error messages Added tag(s) upstream. > tags 614101 + upstream Bug #614101 [xen-hypervisor-4.0-amd64] Debian 6.0 amd64 doesn't boot with Xen on Toshiba u300-13u Added tag(s) upstream. > thanks Stopping processing here. Please...

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

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 deletion(-) cr...