Le Monday 02 Sep 2013 à 13:19:16 (-0300), Eduardo Habkost a écrit :
On Mon, Sep 02, 2013 at 05:06:37PM +0200, Benoît Canet wrote:
Some users running cpu intensive tasks checking the cache CPUID leaves at
startup and making decisions based on the result reported that the guest was
not
Il 02/09/2013 17:06, Benoît Canet ha scritto:
Some users running cpu intensive tasks checking the cache CPUID leaves at
startup and making decisions based on the result reported that the guest was
not reflecting the host CPUID leaves when -cpu host is used.
This patch fix this.
On Mon, Sep 02, 2013 at 07:09:47PM +0200, Benoît Canet wrote:
Signed-off-by: Benoit Canet ben...@irqsave.net
Reviewed-by: Eduardo Habkost ehabk...@redhat.com
Thanks.
Do you have an idea on how QEMU could reflect the real host clock frequency
to the guest when the host cpu
Some users running cpu intensive tasks checking the cache CPUID leaves at
startup and making decisions based on the result reported that the guest was
not reflecting the host CPUID leaves when -cpu host is used.
This patch fix this.
Signed-off-by: Benoit Canet ben...@irqsave.net
---
On Mon, Sep 02, 2013 at 05:06:37PM +0200, Benoît Canet wrote:
Some users running cpu intensive tasks checking the cache CPUID leaves at
startup and making decisions based on the result reported that the guest was
not reflecting the host CPUID leaves when -cpu host is used.
This patch fix
Signed-off-by: Benoit Canet ben...@irqsave.net
Reviewed-by: Eduardo Habkost ehabk...@redhat.com
Thanks.
Do you have an idea on how QEMU could reflect the real host clock frequency
to the guest when the host cpu scaling governor kicks in ?
Giving a false value to cloud customers is mildly
