All of lore.kernel.org
 help / color / mirror / Atom feed
From: Harald Dunkel <harald.dunkel@aixigo.de>
To: Avi Kivity <avi@redhat.com>
Cc: Harald Dunkel <harri@darkharri.de>,
	KVM Mailing List <kvm@vger.kernel.org>
Subject: Re: how to tweak kernel to get the best out of kvm?
Date: Thu, 11 Mar 2010 14:24:10 +0100	[thread overview]
Message-ID: <4B98EEFA.2090208@aixigo.de> (raw)
In-Reply-To: <4B979B81.5060508@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1990 bytes --]

Hi Avi,

I had missed to include some important syslog lines from the
host system. See attachment.

On 03/10/10 14:15, Avi Kivity wrote:
> 
> You have tons of iowait time, indicating an I/O bottleneck.
> 

Is this disk IO or network IO? The rsync session puts a
high load on both, but actually I do not see how a high
load on disk or block IO could make the virtual hosts
unresponsive, as shown by the hosts syslog?


> What filesystem are you using for the host?  Are you using qcow2 or raw
> access?  What's the qemu command line.
> 

It is ext3 and qcow2. Currently I am testing with reiserfs
on the host system. The system performance seems to be worse,
compared with ext3.

Here is the kvm command line (as generated by libvirt):

/usr/bin/kvm -S -M pc-0.11 -enable-kvm -m 1024 -smp 1 -name test0.0 \
	-uuid 74e71149-4baf-3af0-9c99-f4e50273296f \
	-monitor unix:/var/lib/libvirt/qemu/test0.0.monitor,server,nowait \
	-boot c -drive if=ide,media=cdrom,bus=1,unit=0 \
	-drive file=/export/storage/test0.0.img,if=virtio,boot=on \
	-net nic,macaddr=00:16:36:94:7e:f3,vlan=0,model=virtio,name=net0 \
	-net tap,fd=60,vlan=0,name=hostnet0 -serial pty -parallel none \
	-usb -vnc 127.0.0.1:0 -k en-us -vga cirrus -balloon virtio

>>>      
>> How many virtual machines would you assume I could run on a
>> host with 64 GByte RAM, 2 quad cores, a bonding NIC with
>> 4*1Gbit/sec and a hardware RAID? Each vhost is supposed to
>> get 4 GByte RAM and 1 CPU.
>>    
> 
> 15 guests should fit comfortably, more with ksm running if the workloads
> are similar, or if you use ballooning.
> 

15 vhosts would be nice. ksm is in the kernel, but not in my qemu-kvm
(yet).

> 
> Here the problem is likely the host filesystem and/or I/O scheduler.
> 
> The optimal layout is placing guest disks in LVM volumes, and accessing
> them with -drive file=...,cache=none.  However, file-based access should
> also work.
> 

I will try LVM tomorrow, when the test with reiserfs is completed.


Many thanx

Harri

[-- Attachment #2: syslog.gz --]
[-- Type: application/gzip, Size: 1164 bytes --]

  parent reply	other threads:[~2010-03-11 13:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-05 15:20 how to tweak kernel to get the best out of kvm? Harald Dunkel
2010-03-08 11:02 ` Avi Kivity
     [not found]   ` <4B979776.1000701@aixigo.de>
2010-03-10 13:15     ` Avi Kivity
2010-03-10 15:57       ` Javier Guerra Giraldez
2010-03-10 16:00         ` Avi Kivity
2010-03-11 13:24       ` Harald Dunkel [this message]
2010-03-13  8:54         ` Avi Kivity
2010-03-15 13:54           ` Harald Dunkel
  -- strict thread matches above, loose matches on Subject: below --
2010-04-23  8:47 Alec Istomin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B98EEFA.2090208@aixigo.de \
    --to=harald.dunkel@aixigo.de \
    --cc=avi@redhat.com \
    --cc=harri@darkharri.de \
    --cc=kvm@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.