qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: John Snow <jsnow@redhat.com>,
	Bruno Alvisio <bruno.alvisio@gmail.com>,
	qemu-devel@nongnu.org, Qemu-block <qemu-block@nongnu.org>
Subject: Re: [Qemu-devel] [Qemu-block]  Behavior of QMP "query-block"
Date: Fri, 26 May 2017 16:06:30 -0400	[thread overview]
Message-ID: <20170526200630.GA3609@char.us.oracle.com> (raw)
In-Reply-To: <20170526200232.GA4340@noname.redhat.com>

On Fri, May 26, 2017 at 10:02:32PM +0200, Kevin Wolf wrote:
> Am 26.05.2017 um 18:55 hat John Snow geschrieben:
> > On 05/26/2017 07:40 AM, Kevin Wolf wrote:
> > > There is one completely crazy thing that Xen does with respect to disks.
> > > Instead of having support for their PV disks (i.e. virtio-blk, just
> > > different) in the BIOS, they add _both_ an IDE disk and a PV disk to the
> > > VM, so that the bootloader or non-PV-aware guest OSes can access the IDE
> > > disk, for which they most certainly do have drivers. As soon as a driver
> > > for the PV disk is loaded, however, that driver calls a hypervisor
> > > function that removes all the IDE disks from the VM and leaves only the

Not hypervisor. It calls the PCI device which is emulated in QEMU. That
"unplugs" the IDE.

> > > PV ones there, so that the PV-aware guest doesn't see two same disks.
> > > 
> > > I suspect that what you're seeing initially is the IDE disks, and when
> > > the PV driver is loaded, they disappear.
> > 
> > Sure, but does that mean that you'd see *no* block devices via a query
> > afterwards?
> 
> I believe xen_disk creates an anonymous BlockBackend, so it wouldn't
> appear in 'info block'. Though remembering that Xen does weird things is
> enough for me, I don't really want to know all the details that I am
> lucky enough to have forgotten. And trust me, neither do you.

Keep in mind that PV drivers are kernel drivers. Unless the qdisk driver
is used - and then you should see that as well.
> 
> Kevin
> 

      reply	other threads:[~2017-05-26 20:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-25  4:27 [Qemu-devel] Behavior of QMP "query-block" Bruno Alvisio
2017-05-25 18:18 ` John Snow
2017-05-25 18:44   ` Bruno Alvisio
2017-05-26 11:40     ` [Qemu-devel] [Qemu-block] " Kevin Wolf
2017-05-26 16:55       ` John Snow
2017-05-26 20:02         ` Kevin Wolf
2017-05-26 20:06           ` Konrad Rzeszutek Wilk [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=20170526200630.GA3609@char.us.oracle.com \
    --to=konrad.wilk@oracle.com \
    --cc=bruno.alvisio@gmail.com \
    --cc=jsnow@redhat.com \
    --cc=kwolf@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).