Displaying 20 results from an estimated 3000 matches similar to: "[PATCH] pygrub: always append --args"
2007 Jan 05
10
[PATCH 1/7] Fix pygrub path on Solaris
Fix for pygrub path on Solaris.
Signed-off-by: John Levon <john.levon@sun.com>
diff --git a/tools/python/xen/xend/XendDomainInfo.py b/tools/python/xen/xend/XendDomainInfo.py
--- a/tools/python/xen/xend/XendDomainInfo.py
+++ b/tools/python/xen/xend/XendDomainInfo.py
@@ -37,7 +37,7 @@ from xen.util.blkif import blkdev_uname_
from xen.util.blkif import blkdev_uname_to_file
from xen.util
2011 Oct 20
2
[PATCH] pygrub: do not overload RuntimeError for "no menu.lst found"
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
2011 Jul 14
1
PyGrub And Grub2 Submenus
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
2013 Jan 09
2
[PATCH] Fix pygrub handling non-default entry
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
+++
2012 Mar 07
2
PV DomU stopped responding, won't boot, stuck in paused state
Yesterday, I had a PV OpenSolaris DomU stop responding. I looked on my xen machine and it was in a paused state. I ended up destroying it and then doing xm create to bring it back up.
It won''t boot, and I think PyGrub is hanging. Not sure how to resolve this, there aren''t any errors being presented in xen/xm itself. If I try ''xm create config.conf'' it just
2012 Jul 19
2
[PATCH] pygrub: add syslog support to pygrub
# 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
2010 Aug 15
2
trouble launching vm''s
Hello,
I must be missing something very very basic. Because I am having
trouble launching some vm''s that I recently built whereas I don''t have
any problem at all launching some older images I made in very much the
same way!
First there is vm01 which works just fine:
[root@lcent5-1:/etc/xen]$:xm create vm01
Using config file "./vm01".
Started domain vm01
2010 Aug 15
2
trouble launching vm''s
Hello,
I must be missing something very very basic. Because I am having
trouble launching some vm''s that I recently built whereas I don''t have
any problem at all launching some older images I made in very much the
same way!
First there is vm01 which works just fine:
[root@lcent5-1:/etc/xen]$:xm create vm01
Using config file "./vm01".
Started domain vm01
2010 Jun 30
1
(no subject)
>From 1db8a8919482dbed4cc15509d8078b2f16a289bb Mon Sep 17 00:00:00 2001
From: Gert Hulselmans <gerth at zytor.com>
Date: Wed, 30 Jun 2010 14:10:23 +0200
Subject: [PATCH] chain.c32: add grubcfg= for passing an alternative config
filename to GRUB Legacy
GRUB Legacy reserves 89 bytes for storing the filename of the configfile
from memory address 0x8217 to 0x826f.
We allow overwriting the
2010 Dec 21
2
[PATCH] chain.c32: support chainloading GRUB2 core.img
Here is a patch that makes it possible to chainload GRUB2 core.img form
chain.c32.
It reuses the grub= parameter (used for chainloading GRUB Legacy stage2):
- both loaded at 0x8000
- start execution at offset 0x200 (0x8200 in memory)
GRUB2 allows to specify another "GRUB home dir" than the standard /boot/grub
GRUB2 doesn't allow to change the configfile 'grub.cfg' name
2009 May 11
9
vmx_update_guest_cr() losing EXCEPTION_BITMAP setting
Running a heavily modified xen-unstable changset 19590:f80cf52a4fb6 with debugger_attached set, I was seeing the debug traps getting lost from the EXCEPTION_BITMAP in vmx_update_guest_cr() when transitioning from real to protected mode. In my codebase, I could fix this trivially by clearing the debug_state_latch and letting vmx_do_resume() reapply the setting. However, while it looks like a valid
2008 Jan 11
5
domUloader Vs pygrub
Hi
I have been using pygrub for most of the needs. Was
trying out some stuff on SLES 10 SP1. It seems that it
does not have pygrub!!
On the other hand,they have domUloader.py which
requires bootargs="--entry=hda:/boot/vmlinuz...., path
to ramdisk.
It is quite strange to be asking for the path of
the kernel and the ramdisk to be supplied in the conf
file!!.
Am I missing something
2008 Jan 11
5
domUloader Vs pygrub
Hi
I have been using pygrub for most of the needs. Was
trying out some stuff on SLES 10 SP1. It seems that it
does not have pygrub!!
On the other hand,they have domUloader.py which
requires bootargs="--entry=hda:/boot/vmlinuz...., path
to ramdisk.
It is quite strange to be asking for the path of
the kernel and the ramdisk to be supplied in the conf
file!!.
Am I missing something
2008 Aug 03
1
Bug#493592: pygrub fails on lenny's ext3
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
2011 Mar 19
1
Dual-booting VMware and chainbooting GRUB
Dear All:
I am having trouble trying to dual-boot VMware and Linux, and I tried
everything I could come up with.
The situation is that /dev/sda is fully used by VMware and /dev/sdb
is used by Linux. VMware uses Syslinux, so I thought this would be
simple... However, it is not. The bootable FAT partition is too smal
to have kernels in it. As a fallback I tried to chain-load GRUB,
but that did not
2011 Oct 01
2
Bug#643953: xen-utils-4.0: pygrub can not parse empty "root" statement in menu.lst
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
2010 Oct 06
1
Bug#599243: xen-utils-4.0: pygrub does not understand grub2 partition types (e.g. (hd0, msdos1) instead of (hd0, 1))
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
2012 Oct 19
3
[PATCH] pygrub: Add option to list grub entries
# 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
2012 Jun 28
10
Error: Boot loader didn't return any data [pygrub boot debian wheezy alpha1 netinst ISO]
Note: I could simply direct boot the appropriate kernel/initrd to get
the alpha1 installation going as always done in the past, but I think
this should work. The Debian alpha 1 installer page says it should.
Details
$ sudo xm create -c wheezytest.cfg
Using config file "./wheezytest.cfg".
Error: Boot loader didn''t return any data!
direct pygrub test run:
# pygrub
2013 Jul 18
3
Chaining with chain.c32 from syslinux 6.01 error
Hi,
?
? I have a bootable usb with syslinux 5.10 on wich the following?code is working ok.
??? LABEL -
?? MENU LABEL GRUB LEGACY
?? MENU INDENT 1
???? COM32 chain.c32
???? APPEND boot fs grub=/boot/grub-legacy/stage2 grubcfg=/boot/grub-legacy/grub-legacy.cfg nohand nosect
?
?After upgrading to syslinux 6.01 (using bios) I receive the following errors when selecting that menu option :
?
? ERR: