From: William Boughton <bill@boughton.de>
To: kvm@vger.kernel.org
Subject: Re: guests locking up issue
Date: Wed, 18 Jun 2008 11:34:37 +0200 [thread overview]
Message-ID: <20080618093437.GA13133@yuri.org.uk> (raw)
In-Reply-To: <20080617224210.GA24642@yuri.org.uk>
> with KVM-70
>
> my host:
> dual quad core Intel E5320
> 4G ram
> Debian Etch
> 2.6.26-rc6 x86_64
>
> my guest:
> debian etch
> 2.6.26-rc6 x86_64
> 512 Mb ram
I rebuild my guest kernels without CONFIG_KVM_CLOCK, just with
CONFIG_HAVE_KVM=y
It now seems far more stable with -smp 4
> started with:
>
> qemu-system-x86_64 -drive \
> file=/mnt/kvms/images/guitest.img,if=ide,boot=on -m 512 \
> -vnc localhost:2 -name guitest -monitor stdio -net \
> nic,model=e1000,macaddr=00:12:8E:BA:AC:22 -net \
> tap,script=/etc/qemu-ifup,ifname=tapguitest -k en-gb -smp 4
>
> further details of my setup including .configs are at
> http://www.yuri.org.uk/~murble/kvm/
>
> I'm also able to reproduce this with the same image on a
> dual Quad-Core AMD Opteron(tm) Processor 2354 with 16Gb of RAM.
I left two guest running all night building kernels in a loop
with -j3 and -smp 4 using both virtio-blk and net. One running
on the Intel quad core machine the other on the AMD quadcore machine
running the same guest image file, kvm version and guest kernel
version.
Some time in the night the Intel guest froze the AMD hosted one
is still going strong. The Intel host is hosting some other KVM
guests without virtio / smp which had bad been running several
days until I upgraded to 2.6.26-rc6 yesterday evening without any
crashes.
The guest running on Intel qemu monitor is still responsive but
the qemu-system-x86 was using 200% CPU constantly.
both guests were started with:
qemu-system-x86_64 -drive \
file=/mnt/kvms/images/guitest.img,if=virtio,boot=on -m 512 -vnc \
localhost:2 -name guitest -monitor stdio -net \
nic,model=virtio,macaddr=00:12:8E:BA:AC:22 -net \
tap,script=/etc/qemu-ifup,ifname=tapguitest -k en-gb -smp 4
Details of the amd host configuration are at
http://www.yuri.org.uk/~murble/kvm/amd/
When I quit from the qemu monitor on the intel host i got
a softlockup on the host
http://www.yuri.org.uk/~murble/kvm/intel-host-softlockup.txt
my new guest .config
http://www.yuri.org.uk/~murble/kvm/new.guest.config.txt
used on both guests.
regards
bill
--
Bill Boughton
next prev parent reply other threads:[~2008-06-18 9:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-17 19:29 guests locking up issue Brian Jackson
2008-06-17 20:26 ` Marcelo Tosatti
2008-06-17 22:42 ` William Boughton
2008-06-18 9:34 ` William Boughton [this message]
2008-06-18 2:58 ` Brian Jackson
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=20080618093437.GA13133@yuri.org.uk \
--to=bill@boughton.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox