qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: qemu-devel <qemu-devel@nongnu.org>, Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] strange failures with SATA drive but not with IDE drive
Date: Tue, 17 Dec 2013 11:13:45 +0100	[thread overview]
Message-ID: <52B023D9.2030405@redhat.com> (raw)
In-Reply-To: <52AFCF2B.2090407@msgid.tls.msk.ru>

Il 17/12/2013 05:12, Michael Tokarev ha scritto:
> 
> When you switch from bus=ahci.0 to bus=ide.0 on the qemu command line
> above, it all works fine and does not spew any warnings like that
> about emulation failure.
> 
> It looks like we have some uninitialized data on sata emulation
> (in addition to the altmbr issue which I'm investigating further).

Next year, I plan to update my patches to improve SATA emulation.

      reply	other threads:[~2013-12-17 10:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-17  4:12 [Qemu-devel] strange failures with SATA drive but not with IDE drive Michael Tokarev
2013-12-17 10:13 ` Paolo Bonzini [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=52B023D9.2030405@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=mjt@tls.msk.ru \
    --cc=qemu-devel@nongnu.org \
    /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).