[RFC] First (incomplete) cut of Xen paravirt binding

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Eric W. Biederman wrote:
> To pick a nit.  Bootloaders should never use ELF sections only ELF segments.
> In particular that is what the note segment is for.
>   

Yes, that's definitely the right answer in this case.  I'll give this a 
spin and see how it looks.

> Just to verify, the goal when we are done is to have one binary
> kernel that will run on real hardware, under Xen, and paravirtualized VMware,
> and on any other hypervisor that comes along.
>   

Correct.  Though as you point out, you may need both the bzImage and the 
vmlinux files from a particular build for file-format reasons.

> As I understand it.  That goal requires a bzImage with an ELF header :)
> Which we will have shortly.
>   

OK.  Is there some documentation or discussion I can look at to see how 
that would fit together?  What's actually in the ELF header?

> And no the kernel will not be multiboot as that is not an extensible standard.
> Which makes multiboot useless, in the long term.
>   

Xen and dom0 relies on grub to load the hypervisor, the dom0 kernel and 
the dom0 initrd, which I guess uses multiboot.  But we don't otherwise 
rely on it.

    J


[Index of Archives]     [KVM Development]     [Libvirt Development]     [Libvirt Users]     [CentOS Virtualization]     [Netdev]     [Ethernet Bridging]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite Forum]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux