From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>,
"Pawel Moll" <pawel.moll@arm.com>,
"KONRAD Frédéric" <fred.konrad@greensocs.com>
Subject: Re: what should a virtio-mmio transport without a backend look like?
Date: Fri, 21 Jun 2013 22:13:36 +0200 [thread overview]
Message-ID: <51C4B3F0.60300@redhat.com> (raw)
In-Reply-To: <CAFEAcA9VjH7DhKnFTK-CjnQPOV8vqduLjuQgWMrOzuz2V1VgwQ@mail.gmail.com>
Il 21/06/2013 20:28, Peter Maydell ha scritto:
> On 21 June 2013 19:01, Christopher Covington <cov@codeaurora.org> wrote:
>> Anyhow, I just did a quick experiment with 0-size block devices, and they seem
>> to work for me, although trying to mount the device yields the confusing
>> message, "mount: mounting /dev/vda on mount failed: Invalid argument".
>
> I'm confused -- what's the significance of zero size
> block devices?
I wouldn't be sad if QEMU forbade creation of zero-sized block devices. :)
Paolo
next prev parent reply other threads:[~2013-06-21 20:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAFEAcA9qCUQLZho8wJvewYJ0AEhDBc37_LpZWs8XBV1U7RVZgA@mail.gmail.com>
2013-06-20 11:08 ` what should a virtio-mmio transport without a backend look like? Pawel Moll
2013-06-20 12:58 ` Christopher Covington
2013-06-21 15:23 ` Peter Maydell
2013-06-21 16:02 ` Christopher Covington
2013-06-21 16:41 ` Peter Maydell
2013-06-21 16:47 ` Pawel Moll
2013-06-21 17:01 ` Peter Maydell
2013-06-21 18:01 ` Christopher Covington
2013-06-21 18:28 ` Peter Maydell
2013-06-21 18:45 ` Christopher Covington
2013-06-22 10:51 ` Peter Maydell
2013-06-24 12:26 ` Christopher Covington
2013-06-24 12:57 ` Peter Maydell
2013-06-21 20:13 ` Paolo Bonzini [this message]
2013-07-01 0:07 ` Rusty Russell
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=51C4B3F0.60300@redhat.com \
--to=pbonzini@redhat.com \
--cc=fred.konrad@greensocs.com \
--cc=pawel.moll@arm.com \
--cc=peter.maydell@linaro.org \
--cc=virtualization@lists.linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.