qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Lieven <pl@kamp.de>
To: Paolo Bonzini <pbonzini@redhat.com>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: John Snow <jsnow@redhat.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-block] Migration sometimes fails with IDE and Qemu 2.2.1
Date: Tue, 07 Apr 2015 20:54:18 +0200	[thread overview]
Message-ID: <552427DA.3020609@kamp.de> (raw)
In-Reply-To: <5523F43B.2070707@redhat.com>

Am 07.04.2015 um 17:14 schrieb Paolo Bonzini:
>
> On 07/04/2015 17:11, Peter Lieven wrote:
>>> I'm not sure at what kernel version the switch is, but newer kernels use some
>>> code shared with the newer SATA world (libata?)  where as older kernels had
>>> separate IDE code, so the behaviour of the two can be quite different.
>> Thats a good point. I will check what the kernels have.
>> I remember that there was sth like a problem with error handling in
>> the old drivers? Paolo, you worked a lot on IDE lately. Do you remember?
> No, I don't know...  I didn't work a lot on IDE, those patches were all
> several years old and finally John shepherded them in. :)

Okay, I was thinking you just worked on that code and were the
new IDE expert ;-)

>
> Still, what David says is correct.  At least RHEL5's 2.6.18 defaulted to
> the old IDE drivers (/dev/hdXNN).

I can confirm that its /dev/hdX.

Peter

  reply	other threads:[~2015-04-07 18:54 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-06 18:47 [Qemu-devel] Migration sometimes fails with IDE and Qemu 2.2.1 Peter Lieven
2015-04-06 18:50 ` [Qemu-devel] [Qemu-block] " John Snow
2015-04-06 19:02   ` Peter Lieven
2015-04-06 19:10     ` Peter Lieven
2015-04-07  8:43       ` Dr. David Alan Gilbert
2015-04-07 15:11         ` Peter Lieven
2015-04-07 15:14           ` Paolo Bonzini
2015-04-07 18:54             ` Peter Lieven [this message]
2015-04-07 15:29           ` Dr. David Alan Gilbert
2015-04-07 18:44             ` Peter Lieven
2015-04-07 18:56               ` John Snow
2015-04-07 19:02                 ` Peter Lieven
2015-04-07 19:13                   ` John Snow
2015-04-09  6:34                     ` Peter Lieven
2015-04-09 12:46                     ` Peter Lieven
2015-04-09 12:50                       ` Paolo Bonzini
2015-04-07 19:01               ` Dr. David Alan Gilbert
2015-04-07 19:04                 ` Peter Lieven
2015-04-09 12:49                 ` Peter Lieven
2015-04-09 13:32                   ` Peter Lieven
2015-04-09 13:43                   ` Dr. David Alan Gilbert
2015-04-09 14:54                     ` Peter Lieven
2015-04-09 15:17                       ` Paolo Bonzini
2015-04-11 13:11                         ` Peter Lieven
2015-04-11 15:00                           ` Peter Lieven
2015-04-13  7:20                             ` Peter Lieven
2015-04-07 20:05               ` Paolo Bonzini
2015-04-09  6:43                 ` Peter Lieven

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=552427DA.3020609@kamp.de \
    --to=pl@kamp.de \
    --cc=dgilbert@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-block@nongnu.org \
    --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).