public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Riepe <michael-0QoEqw4nQxo@public.gmane.org>
To: Uri Lublin <uri.lublin-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Talking about regressions...
Date: Mon, 15 Jan 2007 19:38:02 +0100	[thread overview]
Message-ID: <45ABCA0A.7040905@mr511.de> (raw)
In-Reply-To: <64F9B87B6B770947A9F8391472E0321603496B00-yEcIvxbTEBqsx+V+t5oei8rau4O3wl8o3fe8/T/H7NteoWH0uzbU5w@public.gmane.org>

Hi!

Uri Lublin wrote:
> 
> Thanks for running those tests.
> Does kvm complains ( dmesg ) ?

Not in the cases I listed. The host just becomes very busy, for a long
time. After ~30 minutes I lost patience and killed qemu.

I see a single "kvm: emulating exchange as write" when I try to boot
FreeBSD 6.1, and with Knoppix 5.1.1 the kernel reports "kvm: unhandled
wrmsr: 0xc1" once. Neither of these worked with earlier kvm versions,
though.

Interestingly, Knoppix 5.1.1 *does* work on an AMD Quad Dual-Core
Opteron we have at work (running Suse Linux Enterprise Server 10, as far
as I remember). Knoppix 5.0, on the other hand, which works fine on the
Core Duo, needs "acpi=off" as a boot parameter on the AMD.

More AMD results: FreeBSD, NetBSD and OpenSolaris (32-bit versions) all
fail with exceptions, usually page faults. OpenSolaris catches lots of
SIGILL's. OpenSuse 10.2 (32 bit as well) works, even with gfxmenu
enabled. Qemu-puppy behaves the same as on the Intel CPU - the old
version works, the new one sometimes hangs (and at the same point).

The next thing I'm going to try is the Dual Quad-Core Xeon... as soon as
I can get my hands on it. :-)

> -----Original Message-----
> From: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org on behalf of Michael Riepe
> Sent: Sun 14/01/2007 19:09
> To: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> Subject: [kvm-devel] Talking about regressions...
> 
> 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
> <http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV>
> _______________________________________________
> kvm-devel mailing list
> kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/kvm-devel
> 
> 

-- 
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

  parent reply	other threads:[~2007-01-15 18:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-14 17:09 Talking about regressions Michael Riepe
2007-01-15 11:18 ` Uri Lublin
     [not found]   ` <64F9B87B6B770947A9F8391472E0321603496B00-yEcIvxbTEBqsx+V+t5oei8rau4O3wl8o3fe8/T/H7NteoWH0uzbU5w@public.gmane.org>
2007-01-15 18:38     ` Michael Riepe [this message]
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=45ABCA0A.7040905@mr511.de \
    --to=michael-0qoeqw4nqxo@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=uri.lublin-atKUWr5tajBWk0Htik3J/w@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