From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Oliver Kowalke <oliver.kowalke-Mmb7MZpHnFY@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: OpenBSD 4.1 failes with kvm-45
Date: Wed, 10 Oct 2007 17:39:00 +0200 [thread overview]
Message-ID: <470CF214.8060604@qumranet.com> (raw)
In-Reply-To: <200710101936.10007.oliver.kowalke-Mmb7MZpHnFY@public.gmane.org>
Oliver Kowalke wrote:
> Am Mittwoch, 10. Oktober 2007 14:17:56 schrieb Alexey Eremenko:
>
>> On 10/10/07, Izik Eidus <izike-atKUWr5tajBWk0Htik3J/w@public.gmane.org> wrote:
>>
>>> Oliver Kowalke wrote:
>>>
>>>> Hi,
>>>> I've Debian/Lenny (amd64) with kernel 2.6.22-9 (kvm-support build in)
>>>> with kvm-45 running.
>>>> WinXP, FreeBSD-6.2 (i386) and NetBSD-3.1 (i386) are working.
>>>> I've only a problem running OpenBSD-4.1 (i386). The installation
>>>> succeeded, but if I start OpenBSD I get following error:
>>>>
>>>> cpu0: QEMU Virtual CPU version 0.9.0
>>>> cpu0: unknown i686 model 2, can't get bus clockkernel: protection fault
>>>> trap, code=0
>>>>
>> This is strange, because I have OpenBSD running fine on KVM-45.
>>
>> Which CPU ? Intel or AMD?
>>
>> please do:
>> modinfo kvm_intel
>> modinfo kvm_amd
>>
>
> Hi,
> I'm using Intel c2d 6600 and I've compiled the kvm spport into the kernel (so
> no modules).
>
That means you're using a fairly old version of the kvm kernel
components. Perhaps a bug that openbsd hit was fixed later on.
I suggest you try with the kvm-45 modules to be sure.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
next prev parent reply other threads:[~2007-10-10 15:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200710102211.03162.oliver.kowalke@gmx.de>
2007-10-10 13:00 ` OpenBSD 4.1 failes with kvm-45 Oliver Kowalke
[not found] ` <200710101500.27733.oliver.kowalke-Mmb7MZpHnFY@public.gmane.org>
2007-10-10 10:56 ` Izik Eidus
[not found] ` <470CAFD2.80803-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-10 12:17 ` Alexey Eremenko
[not found] ` <7fac565a0710100517x68f4149av8d6a63741cda07bd-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-10-10 17:36 ` Oliver Kowalke
[not found] ` <200710101936.10007.oliver.kowalke-Mmb7MZpHnFY@public.gmane.org>
2007-10-10 15:39 ` Avi Kivity [this message]
2007-10-10 12:34 ` Dan Kenigsberg
[not found] ` <200710101938.55042.oliver.kowalke@gmx.de>
[not found] ` <200710102211.03162.oliver.kowalke-Mmb7MZpHnFY@public.gmane.org>
[not found] ` <200710101938.55042.oliver.kowalke-Mmb7MZpHnFY@public.gmane.org>
2007-10-11 7:57 ` Dan Kenigsberg
[not found] ` <20071011075719.GA7547-RO/WWmT55CHJJbofclyLPCHBx9XpghdU@public.gmane.org>
2007-10-12 23:36 ` Oliver Kowalke
[not found] ` <200710130136.57068.oliver.kowalke-Mmb7MZpHnFY@public.gmane.org>
2007-10-13 20:56 ` Carlo Marcelo Arenas Belon
2007-10-14 8:15 ` Oliver Kowalke
2007-10-14 7:41 ` Dan Kenigsberg
[not found] ` <20071014074144.GA32540-iWbx9bcAnq+Hk9JtIoIkgNBPR1lH4CV8@public.gmane.org>
2007-10-17 11:15 ` Oliver Kowalke
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=470CF214.8060604@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=oliver.kowalke-Mmb7MZpHnFY@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