similar to: Bug#603391: Do you have a copy of the problematic grub configuration file?

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 #603391 [xen-utils-4.0]

Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: normal When my domU uses this configuration: --- root = '/dev/sda2 ro' disk = [ 'phy:/dev/volume0/lenny.vandervlis.nl-swap,sda1,w', 'phy:/dev/volume0/lenny.vandervlis.nl-disk,sda2,w', ] --- Pygrub gives the error "Error: Boot loader didn't return

Control: tag -1 +moreinfo Hi Marco, Thanks for your report. Unfortunately the logs you've provided are from a system booted without Xen, and due to the nature of the bug it is unlikely that any relevant logs made it onto the disk in order to survive the resulting reboot. Please could you try setting up a serial console and collect the full boot log.

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

Does anyone know how to get CID working in AEL2 ? In extensions.conf you can do: exten => 111/666,1,PlayBack(demo-congrats) exten => 111/666,2,Hangup() exten => 111,1,PlayBack(demo-moreinfo) exten => 111,2,Hangup() and if callerid 666 dialed 111, they would get demo-congrats, everyone else gets demo-moreinfo. In AEL: 111 => { Playback(demo-moreinfo);

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

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

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

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 data.frame is constructed by one of the following functions: funweek <- function(df) if (length(df$elapsed_time) > 5) { rv = fitdist(df$elapsed_time,"exp") rv$year = df$sale_year[1] rv$sample = df$sale_week[1] rv$granularity = "week" rv } funmonth <- function(df) if (length(df$elapsed_time) > 5) { rv =

>From the documentation I have found, it seems that one of the functions from package plyr, or a combination of functions like split and lapply would allow me to have a really short R script to analyze all my data (I have reduced it to a couple hundred thousand records with about half a dozen records. I get the same result from ddply and split/lapply: >

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>

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

I just tripped over this issue with pygrub. The code is written such that saying bootloader="pygrub" should cause the correct path to be used, the attached patch simply fixes this path to be correct. I don't have an HVM capable test machine handy (so I can't actually confirm this works) but I think changing the default "kernel" for an HVM guest to point to the correct

Here is the function that makes the data.frames in the list: funweek <- function(df) if (length(df$elapsed_time) > 5) { res = fitdist(df$elapsed_time,"exp") year = df$sale_year[1] sample = df$sale_week[1] mid = df$m_id[1] estimate = res$estimate sd = res$sd samplesize = res$n loglik = res$loglik aic = res$aic bic = res$bic chisq =

I must have missed something simple, but still, i don't know what. I obtained my basic data as follows: x <- sprintf("SELECT m_id,sale_date,YEAR(sale_date) AS sale_year,WEEK(sale_date) AS sale_week,return_type,0.0001 + DATEDIFF(return_date,sale_date) AS elapsed_time FROM `merchants2`.`risk_input` WHERE DATEDIFF(return_date,sale_date) IS NOT NULL") moreinfo <- dbGetQuery(con,

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

Hi Phil, Do you by any chance have a copy of the problematic configuration file? Thanks, Ian.