Hannes Reinecke wrote:
So back to the zipl question, it might be an idea to support initially
the SCSI disk layout only. This has the advantage of being far simpler
as the DASD disk layout and should be pretty straightforward to handle.
Issue is, the dasd disk layout is made for dasds. For eckd,
Anthony Liguori wrote:
I do, that's why I brought it up. AFAICT, there hasn't been a lot of
progress with kboot. Carsten or Alex would probably know better if
anyone is actually using it on s390s.
I fail to see how kboot would solve this problem.
Anthony Liguori wrote:
Can't you just use kboot?
Use a kernel loader to load the kboot module/initrd, include kboot as
our firmware, then let kboot do the magic to launch the real linux
kernel from disk.
Hehe, and how would you load that initial kernel if you don't have bios?
No matter what,
Anthony Liguori wrote:
This is a bit unfortunate. Wouldn't it be better to write a custom
version of zipl that ran in the guest?
This is like implementing grub in qemu (or pygrub in Xen). The level of
security exposure this introduces is really scary.
Oh that's really the wrong way to see it
On 25.11.2009, at 09:35, Hannes Reinecke wrote:
> On Tue, Nov 24, 2009 at 03:10:24PM -0600, Anthony Liguori wrote:
>> Hi Mark!
>>
>> Mark Williamson wrote:
>>> Way back in the mists of time (uh, something like that 2004-05) I had some
>>> discussions with some of the S390 people about using kbo
On Tue, Nov 24, 2009 at 03:10:24PM -0600, Anthony Liguori wrote:
> Hi Mark!
>
> Mark Williamson wrote:
>> Way back in the mists of time (uh, something like that 2004-05) I had some
>> discussions with some of the S390 people about using kboot for more
>> flexible boot, since it tallied with their
> > Can't you just use kboot?
> >
> > Use a kernel loader to load the kboot module/initrd, include kboot as our
> > firmware, then let kboot do the magic to launch the real linux kernel
> > from disk.
>
> Hm, so we'd have to rely on kexec working properly? I've seen how badly
> that turned out on
Hi Mark!
Mark Williamson wrote:
Way back in the mists of time (uh, something like that 2004-05) I had some
discussions with some of the S390 people about using kboot for more flexible
boot, since it tallied with their interests. Although at that point I had the
impression that zipl was restri
On 24.11.2009, at 20:26, Anthony Liguori wrote:
> Alexander Graf wrote:
>> On 24.11.2009, at 19:53, Anthony Liguori wrote:
>>
>>
>>> Alexander Graf wrote:
>>>
The default bootloader on S390 is zipl. Because we don't emulate normal
S390
hardware we need to write our own pars
Alexander Graf wrote:
On 24.11.2009, at 19:53, Anthony Liguori wrote:
Alexander Graf wrote:
The default bootloader on S390 is zipl. Because we don't emulate normal S390
hardware we need to write our own parser for the bootloader configuration,
so we can boot off real hard disks.
This
On 24.11.2009, at 19:53, Anthony Liguori wrote:
> Alexander Graf wrote:
>> The default bootloader on S390 is zipl. Because we don't emulate normal S390
>> hardware we need to write our own parser for the bootloader configuration,
>> so we can boot off real hard disks.
>>
>> This patch adds a pre
Alexander Graf wrote:
The default bootloader on S390 is zipl. Because we don't emulate normal S390
hardware we need to write our own parser for the bootloader configuration,
so we can boot off real hard disks.
This patch adds a pretty simple implementation of such an interpreter. It only
support
The default bootloader on S390 is zipl. Because we don't emulate normal S390
hardware we need to write our own parser for the bootloader configuration,
so we can boot off real hard disks.
This patch adds a pretty simple implementation of such an interpreter. It only
supports 512 bytes sector sizes
13 matches
Mail list logo
