From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1H2uax-0008BI-35 for qemu-devel@nongnu.org; Fri, 05 Jan 2007 14:19:15 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1H2uav-00089x-CN for qemu-devel@nongnu.org; Fri, 05 Jan 2007 14:19:14 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1H2uav-00089q-6L for qemu-devel@nongnu.org; Fri, 05 Jan 2007 14:19:13 -0500 Received: from [193.7.176.60] (helo=mail.bawue.net) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1H2uat-0005eA-92 for qemu-devel@nongnu.org; Fri, 05 Jan 2007 14:19:12 -0500 Date: Fri, 5 Jan 2007 19:20:05 +0000 Subject: Re: [Qemu-devel] cvs regression - blue screen INACCESSIBLE_BOOT_DEVICE Message-ID: <20070105192005.GB15486@networkno.de> References: <20070103074830.CC69B1DCC5B@ravel.n2.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070103074830.CC69B1DCC5B@ravel.n2.net> From: Thiemo Seufer Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Don Kitchen Cc: qemu-devel@nongnu.org Don Kitchen wrote: > I just compiled CVS and have experienced a regression with some windows > qcow images (2000 pro and server). The images work with cvs I compiled back > in July, but current cvs produces blue screen with INACCESSIBLE_BOOT_DEVICE. Could you try to find out which change in qemu triggers this behaviour? I don't have a windows to test, and given there weren't (yet :-) loud complaints I figure the problem might be connected to you local setup. Thiemo