qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: John Snow <jsnow@redhat.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	Gerd Hoffmann <kraxel@redhat.com>
Cc: Anthony.Perard@citrix.com, Fabio Fantoni <fabio.fantoni@m2r.biz>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [Qemu-devel] Question about xen disk unplug support for ahci missed in qemu
Date: Mon, 19 Oct 2015 12:54:30 -0400	[thread overview]
Message-ID: <56252046.7070508@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1510191238310.27957@kaball.uk.xensource.com>



On 10/19/2015 07:44 AM, Stefano Stabellini wrote:
> On Mon, 19 Oct 2015, Gerd Hoffmann wrote:
>>   Hi,
>>
>>>> I'm trying to follow this discussion as best as I am able, but my lack
>>>> of experience with Xen prevents me from really participating in a
>>>> meaningful way.
>>>>
>>>> (I see that Laszlo is still discussing some CD-ROM issues with Fabio
>>>> which may be of interest to me...)
>>>>
>>>> At any rate, I won't be authoring any Xen-specific hacks to the AHCI
>>>> device, but I do have plans to implement hot-plugging emulation as per
>>>> the AHCI spec. Perhaps this is sufficient for the Xen layer, but someone
>>>> else will need to author the appropriate glue code.
>>>>
>>>> If "real" hot-plugging is not sufficient, we'll need to discuss further,
>>>> preferably over some RFC patches.
>>>
>>> That's fine. AHCI hot-plugging would go a long way and once we have
>>> that, the rest is easy.
>>
>> Can we get some more background on this?
>>
>> IIRC the IDE bits are needed to boot hvm guests, which goes like this:
>>
>>   (1) boot disk is hooked up using both xenbus and ide.
>>   (2) seabios boots using ide.
>>   (3) linux kernel activates xenbus, at which point qemu zaps the ide
>>       disks to avoid the disk being present twice in the system.
>>
>> Correct?
>>
>> Do we really want repeat this exercise for AHCI?  Alot has changed since
>> this boot hack for ide was added ...
>>
>> As far I know OVMF has xenbus drivers, so OVMF should already boot xen
>> guests just fine without this, correct?
> 
> I agree with you that the current unplug in nasty. Also I don't care
> much about AHCI, in fact I don't think we should be spending efforts
> into making that scenario work better. I think we should be working on
> OVMF instead and fix the bug about empty cdrom drives reported by Fabio.
> 

OVMF and AHCI go hand in hand here from my viewpoint. I'm happy to debug
any OVMF+SATA/AHCI problems that are reported.

Last I saw, Laszlo asked Fabio for some more information on this
problem, so I am waiting for that information to start work on that issue.

Thanks,
--js

> 
>> Can we just have xenbus drivers for seabios too?  seabios can run disk
>> drivers in 32bit mode meanwhile, so this should not be as difficult any
>> more as it used to be.
> 
> Sure, I would be happy to see that happen, but I won't be working on it.
> 

  reply	other threads:[~2015-10-19 16:54 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-13 15:55 [Qemu-devel] Question about xen disk unplug support for ahci missed in qemu Fabio Fantoni
2015-10-13 16:45 ` John Snow
2015-10-13 17:10   ` Stefano Stabellini
2015-10-14  9:47     ` Kevin Wolf
2015-10-14 11:06       ` Stefano Stabellini
2015-10-14 11:27         ` [Qemu-devel] [Xen-devel] " Ian Campbell
2015-10-15 23:10           ` Laszlo Ersek
2015-10-16  2:38             ` Kevin O'Connor
2015-10-16  9:06               ` Stefano Stabellini
2015-10-16  9:21                 ` Laszlo Ersek
2015-10-16  9:33                   ` Stefano Stabellini
2015-10-16  9:34                 ` Ian Campbell
2015-10-16 13:03                 ` Kevin O'Connor
2015-10-16  9:13               ` Laszlo Ersek
2015-10-14 11:32         ` [Qemu-devel] " Kevin Wolf
2015-10-14 11:44           ` Stefano Stabellini
2015-10-15 16:27         ` Fabio Fantoni
2015-10-15 18:02           ` Anthony PERARD
2015-10-16  8:32             ` Fabio Fantoni
2015-10-16 10:13               ` Anthony PERARD
2015-10-16 10:23                 ` Fabio Fantoni
2015-10-16 10:47                   ` Stefano Stabellini
2015-10-16 11:34                     ` Fabio Fantoni
2015-10-16 19:09                       ` Laszlo Ersek
2015-10-19 20:32                         ` Laszlo Ersek
2015-10-20 11:59                           ` Stefano Stabellini
2015-10-20 12:45                             ` Laszlo Ersek
2015-10-20 14:52                               ` Stefano Stabellini
2015-10-14 11:11       ` Fabio Fantoni
2015-10-14 12:48         ` Paul Durrant
2015-10-15 23:35           ` Laszlo Ersek
2015-10-16 14:04           ` Kevin Wolf
2015-10-16 14:24             ` Paul Durrant
2015-10-16 15:02               ` Kevin Wolf
2015-10-16 15:10                 ` Paul Durrant
2015-10-16 16:11                   ` Kevin Wolf
2015-10-16 16:20                     ` Paul Durrant
2015-10-16 16:42                       ` Kevin Wolf
2015-10-16 16:53                         ` Paul Durrant
2015-10-16 17:03                           ` Kevin Wolf
2015-10-19 13:42                           ` Fabio Fantoni
2015-10-16 16:53                       ` Eric Blake
2015-10-16 20:40     ` John Snow
2015-10-19 10:18       ` Stefano Stabellini
2015-10-19 11:27         ` Gerd Hoffmann
2015-10-19 11:44           ` Stefano Stabellini
2015-10-19 16:54             ` John Snow [this message]
2015-10-19 16:57               ` Stefano Stabellini
2015-10-19 18:29                 ` Fabio Fantoni
2015-10-19 19:55                   ` Laszlo Ersek
2015-10-19 14:17         ` Fabio Fantoni
2015-10-19 14:57           ` Stefano Stabellini

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=56252046.7070508@redhat.com \
    --to=jsnow@redhat.com \
    --cc=Anthony.Perard@citrix.com \
    --cc=fabio.fantoni@m2r.biz \
    --cc=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xen.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).