There are two main applications.
1. Omit install device to create generic image intended for chainloading
from other master loader. Such image can be put on any device (or file
system) and will still be able to find its $root. Currently even with
--no-bootsector grub-install optimizes image by ski
В Fri, 8 May 2015 20:05:51 +0200
Olaf Hering пишет:
>
> In my testing with a PV guest I notice that the cursor during input
> remains at the 24th row. The actual output of the help command for
> example lists all possible commands and causes scrolling. If I enter
> something the input does not a
On Fri, May 08, Olaf Hering wrote:
> In my testing with a PV guest I notice that the cursor during input
> remains at the 24th row. The actual output of the help command for
> example lists all possible commands and causes scrolling. If I enter
> something the input does not appear at the bottom b
In my testing with a PV guest I notice that the cursor during input
remains at the 24th row. The actual output of the help command for
example lists all possible commands and causes scrolling. If I enter
something the input does not appear at the bottom but at the 24 row.
Where is the code which
On May 8, 2015 1:58 PM, "Olaf Hering" wrote:
>
> On Fri, May 08, Andrei Borzenkov wrote:
>
> > On Fri, May 8, 2015 at 2:15 PM, Olaf Hering wrote:
> > > On Fri, May 08, Vladimir 'phcoder' Serbinenko wrote:
> > >
> > >> That's not the plan which is pushed by xen guys. They propose to
make grub
> >
On Fri, May 08, Andrei Borzenkov wrote:
> On Fri, May 8, 2015 at 2:15 PM, Olaf Hering wrote:
> > On Fri, May 08, Vladimir 'phcoder' Serbinenko wrote:
> >
> >> That's not the plan which is pushed by xen guys. They propose to make grub
> >> stored on dom0 to just load grub from a predefined place i
On Fri, May 8, 2015 at 2:15 PM, Olaf Hering wrote:
> On Fri, May 08, Vladimir 'phcoder' Serbinenko wrote:
>
>> That's not the plan which is pushed by xen guys. They propose to make grub
>> stored on dom0 to just load grub from a predefined place in domU. This I.a.
>> allows easier upgrade of bootl
On Fri, May 08, Vladimir 'phcoder' Serbinenko wrote:
> That's not the plan which is pushed by xen guys. They propose to make grub
> stored on dom0 to just load grub from a predefined place in domU. This I.a.
> allows easier upgrade of bootloader for distros as they don't have to worry
> about dom0
On Fri, May 08, Andrei Borzenkov wrote:
> that's fine but you need to be able to confgure at least disk on which
> guest grub is located, even if path to binary is fixed. How do you do
> it wihout passing some information to dom0 grub?
If a domU starts to be able to modify its "firmware" in dom0
On Fri, May 8, 2015 at 1:57 PM, Vladimir 'phcoder' Serbinenko
wrote:
>
> On May 8, 2015 12:10 PM, "Olaf Hering" wrote:
>>
>> On Thu, May 07, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
>>
>> > most other firmwares like EFI or BIOS look for boot image at hardcoded
>> > place e.g. MBR or ESP at pr
On May 8, 2015 12:10 PM, "Olaf Hering" wrote:
>
> On Thu, May 07, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
>
> > most other firmwares like EFI or BIOS look for boot image at hardcoded
> > place e.g. MBR or ESP at predefined locations or uses NVRAM. The trouble
> > with passing this info from d
2015-05-07 23:03 GMT+08:00 Andrei Borzenkov :
> On Thu, May 7, 2015 at 5:59 PM, Vladimir 'φ-coder/phcoder' Serbinenko
> wrote:
>> On 07.05.2015 16:54, Olaf Hering wrote:
>>> On Thu, May 07, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
> The way pv-grub2 is built by distributions now is grub-mksta
On Thu, May 07, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
> most other firmwares like EFI or BIOS look for boot image at hardcoded
> place e.g. MBR or ESP at predefined locations or uses NVRAM. The trouble
> with passing this info from dom0 is that it's difficult to discover for
> grub-install
13 matches
Mail list logo
