From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:46617) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ykrow-000130-9R for qemu-devel@nongnu.org; Wed, 22 Apr 2015 06:23:55 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Ykroq-0006qY-FF for qemu-devel@nongnu.org; Wed, 22 Apr 2015 06:23:54 -0400 Received: from cantor2.suse.de ([195.135.220.15]:43075 helo=mx2.suse.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ykroq-0006px-9L for qemu-devel@nongnu.org; Wed, 22 Apr 2015 06:23:48 -0400 Message-ID: <553776B2.8070100@suse.de> Date: Wed, 22 Apr 2015 12:23:46 +0200 From: Hannes Reinecke MIME-Version: 1.0 References: <20150422101958.GG6581@stefanha-thinkpad.redhat.com> In-Reply-To: <20150422101958.GG6581@stefanha-thinkpad.redhat.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] using scsi megasas causes Windows 8 bluescreen List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Hajnoczi , Alex Fishman Cc: qemu-devel@nongnu.org -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 04/22/2015 12:19 PM, Stefan Hajnoczi wrote: > On Tue, Apr 21, 2015 at 10:49:48AM +0300, Alex Fishman wrote: >> I'm trying to install Windows 8 on megasas scsi device with >> master qemu branch. At the end of the installation I >> consistently get a blue screen and the image doesn't boot >> after that. I tried to bisect to older qemu versions, the >> oldest one that made Windows to recognize the disk was >> origin/stable-2.1. That version also gave me a blue screen. >>=20 >> My command line: >>=20 >> qemu-system-x86_64 -m 1G -device megasas,id=3Draid0 -device=20 >> scsi-hd,drive=3Ddisk.0,bus=3Draid0.0 -drive >> if=3Dnone,id=3Ddisk.0,file=3Dwin8test.img -cdrom >> ~/Downloads/en-gb_windows_8.1_with_update_x64_dvd_6051481.iso >> -vnc :1 -boot d >>=20 >> Any thoughts? >=20 > CCing the author of the code. >=20 Ah, good. So it's not a regression :-) I'll have to check what's going on there; the windows drivers are famous for having random assumptions on the driver behaviour... Can you try with 'megasas-gen2' instead of the original 'megasas' to see if it makes a difference? Cheers, Hannes - --=20 Dr. Hannes Reinecke zSeries & Storage hare@suse.de +49 911 74053 688 SUSE LINUX GmbH, Maxfeldstr. 5, 90409 N=FCrnberg GF: F. Imend=F6rffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton HRB 21284 (AG N=FCrnberg) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJVN3axAAoJEGz4yi9OyKjPOlIQAK1qjaOff6Pw0/V0CjYccHZo hAPMceol48nUKNxrUNlJ+elxAa3lhJ1UL17RmTtV8E+bcziVo1xbM9pfiY5MHBa0 64ReF4uMKF2d91+00HQtRZv1lywXLSE20+6VMOFeME6R2PYNg6rDfwAIxGLXvyMX eq/xI2bsq81jRXdLhaEHaCWR5BZrzx39qS0SwQs+l7tWisFEJm3ooZCwtVzW4hcp rumnGAeNd5W83UOME00G9Y8Qj7oHUCFUbg/rTdZRoNSqkzcmcy0MQAZAX8bgcvcs Uiy+H9MeRYbQdl3bB6GHrYZYIA3s9G7rSF85HSe3Yd/C8kBGx1aU7m+mYRVua3qm Jotw4u8PLWb8I6dc1pYukj8+jllLRYdzYfIh25NhjxHW8O3ThDQkz/TXn+mwv5rS 7tW/CvN6oRbkw3vpPG/5hN6XT+3ItZ9XxFLFaC6yvwHbJ7KuL1c+sXu3He/0rsOb uddxKridz83QjoE0AOwX/czrHgor4qr9hvc+9LEzcZslbbNxMdOFTte5j9uDzYKJ 5EVvSe7uHW8GTQrn7zTuZ8yzPrk0p+wrHrTEgwQOvdVhvSBNpe7W+LVFJpfvg6DU sauiQka4oRUO/XDqckU2XeUz7pYeGGxiZ7ODHVr3WBcvNah87nn86iBWc6B8PIA4 flLZgm4HLNUMlTIDnIgD =3DmGBA -----END PGP SIGNATURE-----