From: Magicboiz <magicboiz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Izik Eidus <izike-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: OpenBSD geometry disk problem
Date: Wed, 05 Sep 2007 13:07:22 +0200 [thread overview]
Message-ID: <1188990442.18424.7.camel@linux> (raw)
In-Reply-To: <46DDDE6E.70603-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1091 bytes --]
yes, it runs slowly.....
My config:
CPU: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz
Kernel: 2.6.22 (ubuntu 2.6.22-10-generic)
KVM: 36 and 35 tested.
I attach you two screenshots:
- In the first one, you can see at the bottom, how OpenBSD 4.2 kernel
detects an invalid disk geometry. In fact, the kernel does not detect
nothing, so it supposes that there is a ST506 disk.
- In the second screenshot, you have kernel messages of timeout while
accessing the disk.
Nothing of this happens with no-kvm flag enabled. I also tried with
no-acpi flag, but with the same results.
Regards,
Javier.
El mié, 05-09-2007 a las 01:38 +0300, Izik Eidus escribió:
> Magicboiz wrote:
> > it works!!!
> >
> > Great :)
> >
> > Regards.
> >
> ohh, wait it mean we have bug in kvm!
> and runing with --no-kvm mean your guest will run very slow.
> please tell us what is the cpu you use, and the exact message you get
> plus is it after installtion? in the middle? after boot? while booting?
> please give as much information as you can.
> thansk
>
[-- Attachment #2: Pantallazo-QEMU-KVM-02.png --]
[-- Type: image/png, Size: 21586 bytes --]
[-- Attachment #3: Pantallazo-QEMU-KVM-03.png --]
[-- Type: image/png, Size: 15871 bytes --]
[-- Attachment #4: Type: text/plain, Size: 315 bytes --]
-------------------------------------------------------------------------
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/
[-- Attachment #5: Type: text/plain, Size: 186 bytes --]
_______________________________________________
kvm-devel mailing list
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/kvm-devel
next prev parent reply other threads:[~2007-09-05 11:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-04 10:43 OpenBSD geometry disk problem Magicboiz
2007-09-04 2:23 ` Izik Eidus
[not found] ` <46DCC1BD.3000304-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-04 14:14 ` Magicboiz
2007-09-04 22:38 ` Izik Eidus
[not found] ` <46DDDE6E.70603-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-05 11:07 ` Magicboiz [this message]
2007-09-05 20:07 ` Avi Kivity
2007-09-19 1:15 ` Izik Eidus
[not found] ` <46F0783F.8040700-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-19 13:49 ` Laurent Vivier
[not found] ` <46F128DB.905-6ktuUTfB/bM@public.gmane.org>
2007-09-19 2:11 ` Izik Eidus
2007-09-20 0:05 ` Carlo Marcelo Arenas Belon
2007-09-20 9:17 ` [PATCH] REPN/REPNZ must set rep_prefix to 1 like REP/REPE/REPZ Laurent Vivier
[not found] ` <1190279844678-git-send-email-Laurent.Vivier-6ktuUTfB/bM@public.gmane.org>
2007-09-20 0:48 ` Izik Eidus
2007-09-20 9:20 ` Avi Kivity
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=1188990442.18424.7.camel@linux \
--to=magicboiz-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=izike-atKUWr5tajBWk0Htik3J/w@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