On Wed, Apr 1, 2009 at 11:31 AM, Christian Limpach
<christian.limpach@xxxxxxxxx> wrote:
> On Tue, Mar 31, 2009 at 7:25 PM, Jun Koi <junkoi2004@xxxxxxxxx> wrote:
>> On Wed, Apr 1, 2009 at 11:04 AM, Christian Limpach
>> <christian.limpach@xxxxxxxxx> wrote:
>>> On Tue, Mar 31, 2009 at 6:27 PM, Jun Koi <junkoi2004@xxxxxxxxx> wrote:
>>>> One more question: is it true that this requires virtualization
>>>> hardware (VT-X/Pacifica)? Or it can also do binary translation (using
>>>> Qemu), so it can even work with very old hardware?
>>>
>>> It requires hardware virtualization and we've only added the vmx side
>>> of that so far.
>>
>> So only Intel hardware is supported now?
>
> Correct. Should be fairly straightforward to add the svm code and
> make corresponding changes, seems easier to do this once later rather
> than having to change two places all the time...
>
>> I see some SVM code in the source, but it is not activated yet?
>
> Yeah, code which is in common files is there but the svm directory
> corresponding to the vmx directory is missing.
Another question: what is the plan for Linux support for KXen? Will
that target Linux upstream and use virtops?
Thanks,
J
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|