David Lang wrote:
so if I understand this correctly we are saying that a kernel compiled
to run on hypervisor A would need to be recompiled to run on
hypervisor B, and recompiled again to run on hypervisor C, etc
where A could be bare hardware, B could be Xen 2, C could be Xen 3, D
could be vmware, E could be vanilla Linux, etc.
Yes, but you can compile one kernel for any set of hypervisors, so if
you want both Xen and VMI, then compile both in. (You always get bare
hardware support.)
this sounds like something that the distros would not support, they
would pick their one hypervisor to support and leave out the others.
the big problem with this is that the preferred hypervisor will change
over time and people will be left with incompatable choices (or having
to compile their own kernels, including having to recompile older
kernels to support newer hypervisors)
Why? That's like saying that distros will only bother to compile in one
scsi driver.
The hypervisor driver is tricker than a normal kernel device driver,
because in general it needs to be present from very early in boot, which
precludes it from being a normal module. There's hope that we'll be
able to support hypervisor drivers as boot-time grub/multiboot modules,
so you'll be able to compile up a new hypervisor driver for a particular
kernel and use it without recompiling the whole thing.
J
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
