>> Timing with the rotational stuff set to 1...
>>
>> real14m13.015s
>> user29m42.162s
>> sys 8m37.416s
>
> (user + sys) / real = 2.7
>
>> And finally, to confirm the numbers on the host with no guest running...
>> The same disk/filesystem, now mounted on the host instead of the guest,
> Haven't followed the thread in great detail, but has anyone tried
> putting the virtio disk back into rotational mode?
Hello. I haven't had a chance to try all the suggestions in the thread
so far. However, I did just run some tests with block queue rotation
settings tonight.
For the problem
ot; in
> the body of a message to majord...@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Erik Jacobson - Linux System Software - SGI - Eagan, Minnesota
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
I wanted to post in to the thread the lastest test run.
Avi Kivity provided some ideas to try. I had mixed luck. I'd like to try
this again if we have any thoughts on the vpid/ept issue, or any other
ideas for drilling down on this. Avi Kivity mentioned LVM in the thread.
I continued to just ex
>> * In some of the timing runs on this system, the "real time" reported by
>> the time command was off by 10 to 11 times. Issues were found in
>> the messages file that seemed to relate to this including HUGE time
>> adjustments by NTP and kernel hrtimer 'interrupt too slow' message
_alignment : 64
address sizes : 40 bits physical, 48 bits virtual
power management:
On Sun, Jun 14, 2009 at 12:33:06PM +0300, Avi Kivity wrote:
> Erik Jacobson wrote:
>> We have been trying to test qemu-kvm virtual machines under an IO load.
>> The IO load is quite simple: A time
> What is the host cpu type? On pre-Nehalem/Barcelona processors kvm has
> poor scalability in mmu intensive workloads like kernel builds.
Thanks for getting back to me.
Today is pretty booked but I'm going to go find a Nehalem system and try to
run similar tests to compare. I'll post my resu
We have been trying to test qemu-kvm virtual machines under an IO load.
The IO load is quite simple: A timed build of the linux kernel and modules.
I have found that virtual machines take more than twice as long to do this
build as the host. It doesn't seem to matter if I use virtio or not, Using
