I think it is an unsync tsc problem.
First, make sure you pin all of the process threads. There is thread
per
vcpu + io thread +more non relevant.
You can do it by adding the taskset before the cmdline.
Second, you said that you use smp guest. So windows also sees unsync
tsc.
So, either
On Wed, Dec 03, 2008 at 11:20:08AM -0800, Chris Wedgwood wrote:
TSC instability? Is this an SMP guest?
Ok, I tried pinning the kvm process to two cores (0,2) on a single
socket, but that didn't seem to make any difference for my virtio
network performance. I also tried pinning the process
Adrian Schmitz wrote:
On Wed, Dec 03, 2008 at 11:20:08AM -0800, Chris Wedgwood wrote:
TSC instability? Is this an SMP guest?
Ok, I tried pinning the kvm process to two cores (0,2) on a single
socket, but that didn't seem to make any difference for my virtio
network
I'm having a problem with virtio networking. I mentioned this in a
previous thread, but I'm starting a new one since Dor solved the problem
I reported in the original thread. This appears to be a new problem.
Iperf shows throughput of ~120 Mb/s between a Windows Server 2003 x64
guest and the br0
On Wed, Dec 03, 2008 at 11:20:08AM -0800, Chris Wedgwood wrote:
TSC instability? Is this an SMP guest?
Actually, worded badly.
A UP guest on an SMP host with unsync'ed TSCs would show this too
obviously. As would changes in the TSC speed. The first I guess we
can avoid by pinning
On Wed, Dec 03, 2008 at 02:11:45PM -0500, Adrian Schmitz wrote:
Iperf shows throughput of ~120 Mb/s between a Windows Server 2003 x64
guest and the br0 interface on the host. Also, a ping between the same
two interfaces looks pretty bad:
Pinging 10.10.10.128 with 32 bytes of data:
Reply
On Wed, Dec 03, 2008 at 11:20:08AM -0800, Chris Wedgwood wrote:
TSC instability? Is this an SMP guest?
Actually, worded badly.
A UP guest on an SMP host with unsync'ed TSCs would show this too
obviously. As would changes in the TSC speed. The first I guess we
can avoid by pinning that
Adrian Schmitz wrote:
I'm having a problem with virtio networking. I mentioned this in a
previous thread, but I'm starting a new one since Dor solved the problem
I reported in the original thread. This appears to be a new problem.
On an older kernel, you'll likely see packet corruption with
