On Friday 07 September 2007, Natalia Portillo wrote:
> and remember, please, x86_64 only composes from pentium4 upwards and
> athlon64 upwards, no sense to behave like 386 in x86-64 emulator lol)
Actually, there is. Isn't the x86_64 emulator required to use kqemu on x86_64?
Or does the -cpu 486 o
Dan Kenigsberg wrote:
> On Mon, Sep 10, 2007 at 12:47:51PM +0100, Natalia Portillo wrote:
> > I don't see in what is it useful without KVM/KQEMU.
>
> It is not. I tried to be clear about it in my post. Sorry for not being
> clearer.
Some day it may be useful without KVM/KQEMU, but not for a long
Hi,
On Mon, Sep 10, 2007 at 12:47:51PM +0100, Natalia Portillo wrote:
I don't see in what is it useful without KVM/KQEMU.
It is not. I tried to be clear about it in my post. Sorry for not being
clearer.
Ok now understood.
And even with them there are some instructions that can't be accesib
On Mon, Sep 10, 2007 at 12:47:51PM +0100, Natalia Portillo wrote:
> I don't see in what is it useful without KVM/KQEMU.
It is not. I tried to be clear about it in my post. Sorry for not being
clearer.
> And even with them there are some instructions that can't be accesible
> without KQEMU/KVM p
I don't see in what is it useful without KVM/KQEMU.
And even with them there are some instructions that can't be accesible
without KQEMU/KVM prepared for them.
And, the -cpu option, should be enabled in x86 and x86_64 to
enable/disable emulation of instructions (and them cpuid adjusted to
As with Take 1 of this patch, its purpose is to expose host CPU features to
guests. It proved rather helpful to KVM in various benchmarks, and it should
similarly speed kqemu up. Note that it does not extend the set of emulated
opcodes, only exposes what's supported by the host CPU.
I changed the
