From: Halim Sahin <halim.sahin@t-online.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] -kernel-kqemu option causes kernel-panic
Date: Thu, 15 Mar 2007 09:21:10 +0100 [thread overview]
Message-ID: <20070315082110.GA5487@halim.local> (raw)
In-Reply-To: <46d6db660703150114n7b012fcvd48718b756247968@mail.gmail.com>
Hello,
On Thu, Mar 15, 2007 at 09:14:46AM +0100, Christian MICHON wrote:
> is it on a freshly created qemu image, or one created with qemu
> <= 0.8.2 ?
0.8.2 was used to create the image
>
> what is the format of the qemu image ? raw, qcow, qcow2 ?
Raw
>
> right now (and I'm on windows hosts), latest qemu and 0.9.0
> work well. Most of the pb I see with kernel-kqemu are
> time out on hdc (cdrom) if I boot on hda with linux guests.
>
> what happens if you use a slax bootable iso, booting on
> it and accessing your data on hda ? this works for me
> and is very stable now since qemu 0.8.2.
>
Hmm I tested it now on my other host system.
There is a kernel 2.6.15 running under debian sarge.
All works fine. the described errors are not visible.
There runs a qemu 0.8.2 too but the kqemu module is an older version.
Perhaps the kqemu module causes these problems??
Thanks
Halim
next prev parent reply other threads:[~2007-03-15 8:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-15 6:34 [Qemu-devel] -kernel-kqemu option causes kernel-panic Halim Sahin
2007-03-15 7:12 ` Brad Campbell
2007-03-15 7:23 ` Halim Sahin
2007-03-15 8:14 ` Christian MICHON
2007-03-15 8:21 ` Halim Sahin [this message]
2007-03-15 8:33 ` Christian MICHON
2007-03-15 9:17 ` Halim Sahin
2007-03-15 9:21 ` Aurelien Jarno
2007-03-15 9:29 ` Halim Sahin
2007-03-15 9:32 ` Halim Sahin
2007-03-15 10:11 ` Halim Sahin
2007-03-15 11:58 ` Brad Campbell
2007-03-15 15:00 ` Halim Sahin
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=20070315082110.GA5487@halim.local \
--to=halim.sahin@t-online.de \
--cc=qemu-devel@nongnu.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.