* [Qemu-devel] using scsi megasas causes Windows 8 bluescreen
@ 2015-04-21 7:49 Alex Fishman
2015-04-22 10:19 ` Stefan Hajnoczi
0 siblings, 1 reply; 4+ messages in thread
From: Alex Fishman @ 2015-04-21 7:49 UTC (permalink / raw)
To: qemu-devel
[-- Attachment #1: Type: text/plain, Size: 598 bytes --]
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.
My command line:
qemu-system-x86_64 -m 1G -device megasas,id=raid0 -device
scsi-hd,drive=disk.0,bus=raid0.0 -drive if=none,id=disk.0,file=win8test.img
-cdrom ~/Downloads/en-gb_windows_8.1_with_update_x64_dvd_6051481.iso -vnc
:1 -boot d
Any thoughts?
[-- Attachment #2: Type: text/html, Size: 717 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Qemu-devel] using scsi megasas causes Windows 8 bluescreen
2015-04-21 7:49 [Qemu-devel] using scsi megasas causes Windows 8 bluescreen Alex Fishman
@ 2015-04-22 10:19 ` Stefan Hajnoczi
2015-04-22 10:23 ` Hannes Reinecke
0 siblings, 1 reply; 4+ messages in thread
From: Stefan Hajnoczi @ 2015-04-22 10:19 UTC (permalink / raw)
To: Alex Fishman; +Cc: qemu-devel, Hannes Reinecke
[-- Attachment #1: Type: text/plain, Size: 749 bytes --]
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.
>
> My command line:
>
> qemu-system-x86_64 -m 1G -device megasas,id=raid0 -device
> scsi-hd,drive=disk.0,bus=raid0.0 -drive if=none,id=disk.0,file=win8test.img
> -cdrom ~/Downloads/en-gb_windows_8.1_with_update_x64_dvd_6051481.iso -vnc
> :1 -boot d
>
> Any thoughts?
CCing the author of the code.
Stefan
[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Qemu-devel] using scsi megasas causes Windows 8 bluescreen
2015-04-22 10:19 ` Stefan Hajnoczi
@ 2015-04-22 10:23 ` Hannes Reinecke
2015-04-22 16:48 ` Alex Fishman
0 siblings, 1 reply; 4+ messages in thread
From: Hannes Reinecke @ 2015-04-22 10:23 UTC (permalink / raw)
To: Stefan Hajnoczi, Alex Fishman; +Cc: qemu-devel
-----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.
>>
>> My command line:
>>
>> qemu-system-x86_64 -m 1G -device megasas,id=raid0 -device
>> scsi-hd,drive=disk.0,bus=raid0.0 -drive
>> if=none,id=disk.0,file=win8test.img -cdrom
>> ~/Downloads/en-gb_windows_8.1_with_update_x64_dvd_6051481.iso
>> -vnc :1 -boot d
>>
>> Any thoughts?
>
> CCing the author of the code.
>
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
- --
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton
HRB 21284 (AG Nürnberg)
-----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
=mGBA
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Qemu-devel] using scsi megasas causes Windows 8 bluescreen
2015-04-22 10:23 ` Hannes Reinecke
@ 2015-04-22 16:48 ` Alex Fishman
0 siblings, 0 replies; 4+ messages in thread
From: Alex Fishman @ 2015-04-22 16:48 UTC (permalink / raw)
To: Hannes Reinecke; +Cc: Stefan Hajnoczi, qemu-devel
[-- Attachment #1: Type: text/plain, Size: 2528 bytes --]
Hannes,
megasas-gen2 crashes as well
-Alex
On Wed, Apr 22, 2015 at 1:23 PM, Hannes Reinecke <hare@suse.de> wrote:
> -----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.
> >>
> >> My command line:
> >>
> >> qemu-system-x86_64 -m 1G -device megasas,id=raid0 -device
> >> scsi-hd,drive=disk.0,bus=raid0.0 -drive
> >> if=none,id=disk.0,file=win8test.img -cdrom
> >> ~/Downloads/en-gb_windows_8.1_with_update_x64_dvd_6051481.iso
> >> -vnc :1 -boot d
> >>
> >> Any thoughts?
> >
> > CCing the author of the code.
> >
> 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
> - --
> Dr. Hannes Reinecke zSeries & Storage
> hare@suse.de +49 911 74053 688
> SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
> GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton
> HRB 21284 (AG Nürnberg)
> -----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
> =mGBA
> -----END PGP SIGNATURE-----
>
[-- Attachment #2: Type: text/html, Size: 3286 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2015-04-22 16:48 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-04-21 7:49 [Qemu-devel] using scsi megasas causes Windows 8 bluescreen Alex Fishman
2015-04-22 10:19 ` Stefan Hajnoczi
2015-04-22 10:23 ` Hannes Reinecke
2015-04-22 16:48 ` Alex Fishman
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).