qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Bruno Alvisio <bruno.alvisio@gmail.com>
Cc: John Snow <jsnow@redhat.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 13:40:23 +0200	[thread overview]
Message-ID: <20170526114023.GI7211@noname.str.redhat.com> (raw)
In-Reply-To: <CADNMjECLPFyZp1Rm_M4KuSqnY1cp7k0T38=zmWidYvinrutFPQ@mail.gmail.com>

Am 25.05.2017 um 20:44 hat Bruno Alvisio geschrieben:
> Hello John,
> 
> Thanks. Yes, typo when I wrote the e-mail.
> 
> It might be possible that XEN does that (I will ask in the XEN forum). However,
> I have noticed that it is not the case for all of the VMs I have launched. In
> some of them I can query the block devices even after a long time the VM has
> been running.
> 
> I was wondering if the device is removed in case the disk is corrupted or
> something. When I mention it runs normally, I can log into ithe VM and perform
> read/write operations such creating files.
> 
> Also, is there an easy way to log all qemu events so that I can see what might
> be going on with the 'ide' device?

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
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.

Kevin

  reply	other threads:[~2017-05-26 11:40 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     ` Kevin Wolf [this message]
2017-05-26 16:55       ` [Qemu-devel] [Qemu-block] " John Snow
2017-05-26 20:02         ` Kevin Wolf
2017-05-26 20:06           ` Konrad Rzeszutek Wilk

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=20170526114023.GI7211@noname.str.redhat.com \
    --to=kwolf@redhat.com \
    --cc=bruno.alvisio@gmail.com \
    --cc=jsnow@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).