public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Riepe <michael-0QoEqw4nQxo@public.gmane.org>
To: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Talking about regressions...
Date: Sun, 14 Jan 2007 18:09:06 +0100	[thread overview]
Message-ID: <45AA63B2.5060900@mr511.de> (raw)

When I did a couple of tests the other day, I noticed that one or more
bugs must have been introduced at least into the vmx part in kvm-10:

- netbsd 3.1 used to work with kvm-9. In kvm-10, the system hangs during
boot. One of the last things I can see is that a shell process dies with
a SIGSEGV. Then the load rises to 100% (sys) on the host and stays there
until I kill qemu (yes I've waited several minutes).

- opensolaris displays a "Time of Day clock error" during boot, claiming
the clock has jumped by 0x5 (no unit given, I suppose that means
seconds). Everything else seems to work.

- qemu-puppy-2.13-1 sometimes works and sometimes hangs somewhere inside
the initial ramdisk. The exact place seems to differ, but usually it
happens while the kernel modules are loaded. Again, host load rises to
100%. An older version (2.01-3) still works fine. kvm-9 works, too.

(Core Duo T2400, 32-bit SMP host, 32-bit guest, Linux 2.6.19 + kvm trunk
revision 4290)

Any idea what to look for? The SIGSEGV on netbsd makes me suspect that
there's a problem with the page tables, but I couldn't narrow down the
cause yet.

-- 
Michael "Tired" Riepe <michael-0QoEqw4nQxo@public.gmane.org>
X-Tired: Each morning I get up I die a little

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

             reply	other threads:[~2007-01-14 17:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-14 17:09 Michael Riepe [this message]
2007-01-15 11:18 ` Talking about regressions Uri Lublin
     [not found]   ` <64F9B87B6B770947A9F8391472E0321603496B00-yEcIvxbTEBqsx+V+t5oei8rau4O3wl8o3fe8/T/H7NteoWH0uzbU5w@public.gmane.org>
2007-01-15 18:38     ` Michael Riepe
2007-01-15 21:16       ` Uri Lublin
     [not found]         ` <64F9B87B6B770947A9F8391472E0321603496B02-yEcIvxbTEBqsx+V+t5oei8rau4O3wl8o3fe8/T/H7NteoWH0uzbU5w@public.gmane.org>
2007-01-16 13:23           ` Michael Riepe
2007-01-16 14:03             ` Uri Lublin
     [not found]             ` <45ACD1D3.30406-0QoEqw4nQxo@public.gmane.org>
2007-01-21 12:03               ` Avi Kivity
     [not found] ` <45AA63B2.5060900-0QoEqw4nQxo@public.gmane.org>
2007-01-17  4:17   ` Bill Davidsen

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=45AA63B2.5060900@mr511.de \
    --to=michael-0qoeqw4nqxo@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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