From: Alex Fishman <alex.fishman@ravellosystems.com>
To: Hannes Reinecke <hare@suse.de>
Cc: Stefan Hajnoczi <stefanha@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] using scsi megasas causes Windows 8 bluescreen
Date: Wed, 22 Apr 2015 19:48:36 +0300 [thread overview]
Message-ID: <CAFNmCfRiXvh6eqH811g0cZ5qw=C268=w3qjoLBtDSizopw8fSw@mail.gmail.com> (raw)
In-Reply-To: <553776B2.8070100@suse.de>
[-- 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 --]
prev parent reply other threads:[~2015-04-22 16:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
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 message]
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='CAFNmCfRiXvh6eqH811g0cZ5qw=C268=w3qjoLBtDSizopw8fSw@mail.gmail.com' \
--to=alex.fishman@ravellosystems.com \
--cc=hare@suse.de \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
/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 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).