public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: KVM list <kvm@vger.kernel.org>
Cc: Dominik Klein <dk@in-telegence.net>
Subject: FreeBSD boot hangs on qemu-kvm on AMD host
Date: Wed, 09 Mar 2011 15:06:28 +0300	[thread overview]
Message-ID: <4D776D44.9080302@msgid.tls.msk.ru> (raw)

Hello.

Dominik Klein (Cc'd) reported on irc that current
FreeBSD release hangs at boot in qemu-kvm.  It is
trivially verifiable by d/loading the bootonly
FreeBSD 8.2 CD image from ftp.freebsd.org and
running

  kvm -cdrom FreeBSD-8.2-RELEASE-amd64-bootonly.iso.

The guest unpacks kernel, draws a menu (apparently
in real kernel already, not in the boot loader) and
starts a 10-second countdown.  At this point it just
stops (either at 10 or 9, ie, right at the beginning
of the cycle) and kvm process starts using 100% of
the CPU core given to it.  With this typical kvm_stats
from qemu-kvm 0.14:

kvm statistics

 exits                                     43397783 1400960
 halt_exits                                42862622 1400769
 irq_exits                                     5487     172
 host_state_reload                           300074     101
 io_exits                                    292212      18
 irq_injections                                 768      18
 halt_wakeup                                    257       3
 mmu_pte_write                              7702163       0
 insn_emulation                              378273       0
 mmio_exits                                   15786       0
 pf_fixed                                      4817       0
 mmu_shadow_zapped                              170       0
 mmu_cache_miss                                 151       0
 remote_tlb_flush                                 2       0
 signal_exits                                     1       0
 fpu_reload                                       1       0


I tried i386 and amd64 guest images, and tried the same
thing with qemu-kvm 0.12.5 and 0.14.0 - the effect is
exactly the same.

So far the 3 affected systems where we tried this are all
AMD machines.  My home box is AthlonII, my work box is
PhenomI 9750, and Dominik tries it on Opteron 6174.

Running it with -no-kvm lets the guest to go (but obviously
very slow).  Using -no-kvm-irqchip helps too.

Any guess what it can be?

Thanks!

/mjt

             reply	other threads:[~2011-03-09 12:06 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-09 12:06 Michael Tokarev [this message]
2011-03-09 12:50 ` FreeBSD boot hangs on qemu-kvm on AMD host Avi Kivity
2011-03-09 12:59   ` Michael Tokarev
2011-03-09 13:03     ` Avi Kivity
2011-03-09 14:24       ` Gleb Natapov
2011-03-09 14:32         ` Michael Tokarev
2011-03-09 14:53       ` Dominik Klein
2011-03-09 15:38         ` Avi Kivity
2011-03-09 16:09           ` Michael Tokarev
2011-03-09 16:24             ` Avi Kivity
2011-03-09 16:26               ` Avi Kivity
2011-03-09 16:28                 ` Michael Tokarev
2011-03-09 16:32                   ` Avi Kivity
2011-03-09 16:34                     ` Avi Kivity
2011-03-09 17:11                       ` Michael Tokarev
2011-03-10  9:14                         ` Avi Kivity

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=4D776D44.9080302@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=dk@in-telegence.net \
    --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