Displaying 20 results from an estimated 4436 matches for "grubs".
Did you mean:
grub
2019 Jan 06
2
Bug#776450: Xen PVH support for grub-xen in Buster
On Sun, Jan 06, 2019 at 01:45:53AM +0100, Hans van Kranenburg wrote:
> Hm, so I have a PV (or PVH) domU in a test environment here, and I tried
> to use it in the Debian way of booting it.
>
> If I install grub-xen-bin inside the domU then I get some stuff, but not
> update-grub. When I just also install grub2 it drags in more stuff, and
> then I end up with update-grub and a
2015 Aug 05
2
CentOS 5 grub boot problem
I never thought I'd say this, but I think it's easier to do this with
GRUB 2. Anyway I did an installation to raid1's in CentOS 6's
installer, which still uses GRUB legacy. I tested removing each of the
two devices and it still boots. These are the commands in its log:
: Running... ['/sbin/grub-install', '--just-copy']
: Running... ['/sbin/grub',
2019 Jan 05
4
Bug#776450: Xen PVH support for grub-xen in Buster
Hi Colin,
Thanks for the quick reply.
On 1/5/19 8:04 PM, Colin Watson wrote:
> On Thu, Jan 03, 2019 at 01:02:47AM +0100, Hans van Kranenburg wrote:
>> In december, Xen PVH support has been committed in grub master:
>> https://www.mail-archive.com/grub-devel at gnu.org/msg28125.html
>>
>> The last pieces needed in the Linux kernel to boot PVH with grub2 landed
>>
2013 Dec 12
10
[PATCH 0/4] Turn-key PV-GRUB2 installation
This patch set should make it easier to maintain PV-GRUB2 installations.
The general idea is based on discussions I had with Xen developers
(mainly Ian Jackson) at the Ubuntu Developer Summit in May 2011; though
I never did manage to get the core port done and Vladimir beat me to
that, I think the configuration approach we discussed there is still
valid and useful.
The idea here is that people
2016 Mar 07
0
Module Versioning
On 2016.03.06 23:25, Shao Miller via Syslinux wrote:
> Having typed that, perhaps we could discuss your (or Rufus') specific
> needs, in parallel?
I think that is probably worthwhile, as I wouldn't mind having a second
opinion from Syslinux developers on whether my current ISO -> USB
conversion process could be improved.
> Do I understand correctly that the primary
>
2019 Jan 03
2
Xen PVH support for grub-xen in Buster
Hi Debian Grub maintainer,
In december, Xen PVH support has been committed in grub master:
https://www.mail-archive.com/grub-devel at gnu.org/msg28125.html
The last pieces needed in the Linux kernel to boot PVH with grub2 landed
in Linux 4.20. I asked our kernel team to carry those patches on top of
the Linux 4.19 kernel that is going to ship in Buster, and that wish was
granted:
2016 Mar 06
5
Module Versioning
On 3/3/2016 07:43, Pete Batard via Syslinux wrote:
> [...] as far as I am concerned, 'A "version" such as "6.03" [is not]
> enough'. [...]
I'd like to help to improve Syslinux with regards to version-related
concerns.
Having typed that, perhaps we could discuss your (or Rufus') specific
needs, in parallel? Do I understand correctly that the primary
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
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
2013 Sep 29
2
Bug#603391: Workaround PyGrub issue
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
2009 Sep 24
6
[patch 1/2] grub-0.97: btrfs support for a singe device configuration
2015 Aug 06
3
CentOS 5 grub boot problem
On 08/05/2015 10:23 AM, Chris Murphy wrote:
> Nothing about hd0 or hd1 gets baked into the bootloader code. It's an
> absolute reference to a physical drive at the moment in time the
> command is made.
Is that true? If I have a system with two disks, where device.map
labels one as hd0 and the other as hd1, and I swap those numbers, the
resulting boot sector will differ by one bit.
2010 Jun 26
9
xen 4.0-testing: cannot install grub in debian domU (both hvm and pv)
# dd if=/dev/zero of=/srv/xen/webserver.img oflag=direct bs=1M seek=4095 count=1
# dd if=/dev/zero of=/srv/xen/webserver.img oflag=direct bs=1M count=4096
root@debian:~# grub-install /dev/xvda
Searching for GRUB installation directory ... found: /boot/grub
The file /boot/grub/stage1 not read correctly.
Darkbasic
_______________________________________________
Xen-users mailing list
2007 Jan 04
0
GRUB CD errors on CentOS 4
Background: I am in the habit of making bootable GRUB CDs with menus
and copies of working kernels and initrds, particularly for
multiple-boot testing machines with multiple distros and/or the Redmond
OS. This has helped pull my fat out of the fire more than once when a
system was rendered unbootable by hardware changes, or when Bill Gates
decided the MBR should be taken over. This generally
2005 Dec 02
1
FIXED Re: Re: MD Raid 1 software device not booting not even reaching grub
doing that grub-install /dev/sda will give me the "corresponding BIOS
device" error.
But now I fixed it by doing a manual grub install.
first boot with cd1 and type linux rescue at the prompt
when you're at the linux prompt after detecting and mounting the
partitions, do a "chroot /mnt/sysimage"
then
# grub --batch
#grub> root (hd0,0)
Filesystem type is ext2fs,
2009 Aug 13
1
[PATCH] Don't assume grub is on a separate boot filesystem
Paths in grub.conf are relative to the filesystem containing it. grub parsing
currently assumes that it is on /boot, and will fail if it isn't, for example
because a guest only has a single partition.
This patch makes grub parsing work harder to work out what grub paths are
relative to. Firstly, it looks for a previous detected 'linux-grub' filesystem.
If this isn't found, it
2016 Nov 01
3
[PATCH v3] v2v: bootloaders: search grub config for all distributions
From: Pavel Butsykin <pbutsykin@virtuozzo.com>
This patch improves the search of grub config on EFI partition. This
means that the config will be found not only for rhel but also for
many other distributions. Tests were performed on the following
distributions: centos, fedora, ubuntu, suse. In all cases, the config
path was /boot/efi/EFI/*distname*/grub.cfg
The main purpose of the patch
2013 Jan 05
14
/boot as a btrfs subvolume
As of the latest updates to anaconda and grub2 for Fedora 18, it is now
possible to install with /boot as a btrfs subvolume. The way that grub2
is handling this is the "reach down" to the files it needs as if the
subvolume was a directory.
Is this OK?
At this point I am not worried about snapshots or any other
complexities. If the subvolume name is known. should grub2 be able to
2016 Nov 02
4
[PATCH v4 1/2] v2v: bootloaders: search grub config for all distributions
From: Pavel Butsykin <pbutsykin@virtuozzo.com>
This patch improves the search of grub config on EFI partition. This
means that the config will be found not only for rhel but also for
many other distributions. Tests were performed on the following
distributions: centos, fedora, ubuntu, suse. In all cases, the config
path was /boot/efi/EFI/*distname*/grub.cfg
The main purpose of the patch
2006 Feb 10
1
4.2 install w/250GB raid arrays won't boot
hi!
raid 1 arrays: I already have 2 systems running this same raid1 config.
1 sys has 2 120 gb
1 sys has 1 120gb and 1 200gb but matching the raid partitions
this system here that is giving me fits right now has 1 250gb and 1
200gb. I tried it w/a new 250 gb for the 2nd drive but the same
results. Will not boot.
in druid, when I am config. the raid arrays, I always create the
boot partitions