All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Alexander Graf <agraf@suse.de>
Cc: "kvm@vger.kernel.org list" <kvm@vger.kernel.org>
Subject: Re: 0.11.0-rc1 bugs
Date: Mon, 07 Sep 2009 12:22:03 +0200	[thread overview]
Message-ID: <4AA4DECB.2090809@siemens.com> (raw)
In-Reply-To: <4E3CA5E5-BB4E-4497-BB5B-747EB07C7310@suse.de>

Alexander Graf wrote:
> Hi list,
> 
> while trying out 0.11.0-rc1 I stumbled across several bugs and wanted to
> share them with you, so whoever feels bored knows what's left to do out
> there :-)

You may want to try the latest stable-0.11 branch which is close to
0.11.0-rc2. Should resolve at least some of your issues.

> 
> Unless I'm completely stupid, all of the following cases worked with
> 0.10.6 on the same machine (kernel, kvm-kmod).
> Linux with IDE as guest works great.
> 
> My kernel configuration:
> 
>   OpenSUSE 11.1 with 2.6.27 kernel and kvm-kmod-2.6.30.1.
> 
> Bugs:
> 
>   - Xen doesn't boot (fails with "..MP-BIOS bug: 8254 timer not
> connected to IO-APIC")

I've seen such issue with SLES10 2.6.16 and "notsc" kernel parameter.
Didn't dig deeper though.

> 
>   - Mac OS X boots for a bit, then qemu-kvm exit(1)'s with
> "hpet_disable_pit: kvm does not support pit_state2!"
>     It even breaks with -no-hpet! -no-kvm-pit works around it.
> 
>   - extboot doesn't get installed
> 
>   - extboot doesn't work (-drive ...,if=virtio,boot=on fails)
> 

The last two are solved in stable-0.11.

> 
> If you find additional problems in 0.11.0-rc1 or found that I only did
> something wrong, please reply to this thread.
> 
> Alex

Jan

-- 
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux

  reply	other threads:[~2009-09-07 10:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-07 10:03 0.11.0-rc1 bugs Alexander Graf
2009-09-07 10:22 ` Jan Kiszka [this message]
2009-09-07 12:06   ` Alexander Graf

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=4AA4DECB.2090809@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=agraf@suse.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.