qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Wayne Xia <xiawenc@linux.vnet.ibm.com>
Cc: Michael Tokarev <mjt@tls.msk.ru>,
	qemu-devel@nongnu.org, anthony@codemonkey.ws,
	stefanha@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH] add text about how to use qemu-nbd with qemu
Date: Wed, 04 Jul 2012 09:35:55 +0200	[thread overview]
Message-ID: <4FF3F25B.8050608@redhat.com> (raw)
In-Reply-To: <4FF3A719.5040702@linux.vnet.ibm.com>

Il 04/07/2012 04:14, Wayne Xia ha scritto:
> 
>> of the internal structure inside - be it raw, or qcow, or anything else.
>> So, if you specify the format of the device explicitly, by using
>> format=raw, only single connection will be made.
>   thanks, that helped me. A bit more question: is there a way to let
> nbd client know the image format used by server? qemu-nbd exports
> simple_qcow2.img, and qemu saw it as raw block device, is it possible to
> get the information in qemu that server is using qcow2 image?

qemu-nbd takes care of the format translation itself, and always exposes
the image as raw.

Paolo

  reply	other threads:[~2012-07-04  7:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-03 11:05 [Qemu-devel] [PATCH] add text about how to use qemu-nbd with qemu xiawenc
2012-07-03 11:55 ` Paolo Bonzini
2012-07-04  2:21   ` Wayne Xia
2012-07-05  3:29   ` Wayne Xia
2012-07-05  6:42     ` Paolo Bonzini
2012-07-05  8:13       ` Michael Tokarev
2012-07-05  8:34         ` Paolo Bonzini
2012-07-06  8:01           ` Wayne Xia
2012-07-09  7:11             ` Wayne Xia
2012-07-09  7:15               ` Paolo Bonzini
2012-07-03 16:18 ` 陳韋任 (Wei-Ren Chen)
2012-07-04  2:26   ` Wayne Xia
2012-07-03 19:45 ` Michael Tokarev
2012-07-04  2:14   ` Wayne Xia
2012-07-04  7:35     ` Paolo Bonzini [this message]
2012-07-04  9:56   ` Kevin Wolf

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=4FF3F25B.8050608@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=mjt@tls.msk.ru \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@linux.vnet.ibm.com \
    --cc=xiawenc@linux.vnet.ibm.com \
    /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).