public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Tobias Brink <tobias.brink-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: KVM behaves weird on AMD64
Date: Fri, 14 Sep 2007 00:55:32 +0200	[thread overview]
Message-ID: <87k5quyy3f.fsf@tobe.homeunix.org> (raw)
In-Reply-To: 46E7BEE3.8090203@Nosys.net

Miguel Araujo <maraujo-l9cVusCFpiBeoWH0uzbU5w@public.gmane.org>
writes:

[snip]
> The issue started when I tried to install OpenBSD 4.1 on a Virtual
> Machine and It could not manage to write the MBR on disk. That
> should not happen.

I have a probably similar problem with OpenBSD 4.1 and kvm-37 and
kvm-39 (didn't have time to test any further versions).  Kernel is
2.6.22-gentoo-r5 and processor is Intel Core2 Quad.  I use the modules
from the unpatched (Gentoo) kernel.

I installed OpenBSD with vanilla qemu and it works perfectly but as
soon as I use kvm the OpenBSD kernel panics on boot with

  root on wd0a
  rootdev=0x0 rrootdev=0x300 rawdev=0x302
  panic: root filesystem has size 0

and then enters the debugger.  With -no-kvm it works as flawlessly as
in vanilla qemu.

I don't have much time at the moment but I'll try to find a working
kvm version.  If you need further information I'll see if I can
provide it as I'd really like to see OpenBSD working with kvm.

Greetings,
Tobias


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

  parent reply	other threads:[~2007-09-13 22:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-12 10:26 KVM behaves weird on AMD64 Miguel Araujo
     [not found] ` <46E7BEE3.8090203-l9cVusCFpiBeoWH0uzbU5w@public.gmane.org>
2007-09-12 10:47   ` Avi Kivity
     [not found]     ` <46E7C3DD.8020003-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-12 11:03       ` Miguel Araujo
     [not found]         ` <46E7C79E.9070409-l9cVusCFpiBeoWH0uzbU5w@public.gmane.org>
2007-09-12 11:14           ` Avi Kivity
     [not found]             ` <46E7CA21.9000201-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-12 12:27               ` Miguel Araujo
2007-09-13 22:55 ` Tobias Brink [this message]
     [not found]   ` <87k5quyy3f.fsf-eMrnMapibgNxJOgadfisgdi2O/JbrIOy@public.gmane.org>
2007-09-30 10:59     ` Avi Kivity
2007-09-30 11:41       ` Tobias Brink
     [not found]         ` <87myv4tm6j.fsf-eMrnMapibgNxJOgadfisgdi2O/JbrIOy@public.gmane.org>
2007-10-01 11:48           ` Miguel Araujo

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=87k5quyy3f.fsf@tobe.homeunix.org \
    --to=tobias.brink-re5jqeeqqe8avxtiumwx3w@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