Xu, Anthony wrote:
> following is my thinking, it may be wrong.
>
> If we want to run dom0 on VTi, we still need to support of paravitualization,
> madison is still being used.
> We can have two branch, one VT-i dom0, the other is para dom0.
> We may focus on VT-i dom0 branch.
> While we still support para dom0, if there are bugs, we need to fix it, but
> we will not update xenolinux to new release version, we just try to make all
> functions work well.
>
> In the other side, It's impossible Redhat would like to maintain two modified
> linux version, one is for hybrid, the other is for para.
> Redhat may choose modified linux version for hybrid, it is more easier for
> maintain.
While I can't officially speak for Red Hat and exactly what route we may or
may not take in the future, I'd say its a pretty sure thing Red Hat would not
want to maintain two modified linux versions, particularly on an architecture
that makes up such a small percentage of the user base. At the same time, Red
Hat aims to maintain upgrade paths from one version of Red Hat Enterprise
Linux to another, so whatever lands in RHEL6, there will still have to be a
way to run fully virtualized and para-virtualized guests.
Again, not speaking in any official capacity, but note that the default
"Virtualization" software in Fedora right now is kvm, and Red Hat now employs
Gerd Hoffman (aka kraxel), who has been busy working on a project called xenner.
http://dl.bytesex.org/releases/xenner/
Summary from the README:
xenner is a utility which is able to boot xen paravirtualized kernels,
without the xen hypervisor, using kvm instead.
--
Jarod Wilson
jwilson@xxxxxxxxxx
signature.asc
Description: OpenPGP digital signature
_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel
|
Home