From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HRlPj-00074y-HU for qemu-devel@nongnu.org; Thu, 15 Mar 2007 04:34:23 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HRlPh-00074e-UN for qemu-devel@nongnu.org; Thu, 15 Mar 2007 04:34:23 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HRlPh-00074b-Qh for qemu-devel@nongnu.org; Thu, 15 Mar 2007 03:34:21 -0500 Received: from wr-out-0506.google.com ([64.233.184.233]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1HRlOh-0000WW-HU for qemu-devel@nongnu.org; Thu, 15 Mar 2007 04:33:20 -0400 Received: by wr-out-0506.google.com with SMTP id 41so6601wry for ; Thu, 15 Mar 2007 01:33:13 -0700 (PDT) Message-ID: <46d6db660703150133q4d1c4b7cv4974f47fc48de39b@mail.gmail.com> Date: Thu, 15 Mar 2007 09:33:12 +0100 From: "Christian MICHON" Subject: Re: [Qemu-devel] -kernel-kqemu option causes kernel-panic In-Reply-To: <20070315082110.GA5487@halim.local> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20070315063448.GA15229@halim.local> <45F8F1E9.9070607@wasp.net.au> <20070315072332.GA22667@halim.local> <46d6db660703150114n7b012fcvd48718b756247968@mail.gmail.com> <20070315082110.GA5487@halim.local> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org On 3/15/07, Halim Sahin wrote: > 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 I wanted to discard any change of behaviour between formats and releases of qemu-img. You could have had a compressed encrypted qcow(2) for example... > > > > 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 > I'm using the latest kqemu each time, and it works... -- Christian