qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Salvador Fandino <sfandino@yahoo.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: NBD server for QEMU images
Date: Tue, 12 Dec 2006 18:00:49 +0100	[thread overview]
Message-ID: <elmmtp$ipr$1@sea.gmane.org> (raw)
In-Reply-To: <56d259a00612120537g5396ae0aif7bb3a84211f7975@mail.gmail.com>

Martin Guy wrote:
>> The patch available from http://qemu-forum.ipi.fi/viewtopic.php?t=2718
>> adds a new utility, qemu-nbds, that implements a NBD server
> 
> I have been using nbd volumes mounted from inside qemu for filestore
> and for swap, both read-write, served from files and from partitions,
> with the unmodified standard nbd-server (debian testing version) for
> intensive work and it has been faster and more reliable than NFS (not
> that that's saying much).
> 
> The only thing that doesn't work is the -swap option, which just
> hangs, but that proves not to be necessary when swapping onto nbd host
> volume from qemu-land, even when stress-testing it.
> 
> What problem is solved by a specially modified nbd server?

It serves disk images in any format QEMU can handle, for instance, qcow
images.

It's mostly intended to be used for accessing the files inside QEMU disk
images locally, without having to launch a virtual machine and accessing
then from there.

For instance, if you use QEMU to run Windows, and at some point you need
to get some file from your emulated windows disk, you can do it as follows:

 $ qemu-nbds windows.qcow -p 8001 -o 32256 &

 # modprobe nbd
 # nbd-client localhost 8001 /dev/nbd0
 # mount -o ro /dev/nbd0 /mnt/windows

 $ cp /mnt/windows/FOO.txt ~/


Cheers,

 - Salva



Cheers,

 - Salvador.

  reply	other threads:[~2006-12-12 16:55 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-12 12:48 [Qemu-devel] NBD server for QEMU images Salvador Fandiño
2006-12-12 13:37 ` Martin Guy
2006-12-12 17:00   ` Salvador Fandino [this message]
2006-12-12 16:58     ` [Qemu-devel] " Paul Brook
2006-12-12 17:13       ` Daniel Jacobowitz
2006-12-12 17:33         ` RE : " Sylvain Petreolle
2006-12-12 17:39           ` Paul Brook
2006-12-12 18:54             ` Anthony Liguori
2006-12-12 17:41           ` RE : " Johannes Schindelin
2006-12-12 17:42           ` Daniel Jacobowitz
2006-12-12 18:41             ` [Qemu-devel] Re: RE : " Salvador Fandino
2006-12-13 12:23               ` Jan Marten Simons
2006-12-13 19:03                 ` Salvador Fandino
2006-12-13 20:03                   ` Jim C. Brown
2006-12-13 22:07                     ` Salvador Fandino
2006-12-13 22:55                       ` Jim C. Brown
2006-12-14  8:37                         ` Salvador Fandino
2006-12-14 14:58                           ` Jim C. Brown
2006-12-12 19:00           ` Salvador Fandino
2006-12-12 17:45         ` [Qemu-devel] " Mark Williamson
2006-12-12 19:30         ` Christian MICHON
2006-12-12 15:09 ` Anthony Liguori
2006-12-12 17:32   ` Salvador Fandino
2006-12-12 20:13     ` Anthony Liguori
2006-12-13  2:14       ` Mark Williamson
2006-12-13 11:37       ` Avi Kivity
2006-12-13 13:19         ` Martin Guy
2006-12-13 13:29           ` Avi Kivity
2006-12-13 19:14             ` Salvador Fandino
2006-12-14  8:34               ` Avi Kivity
2006-12-13 16:58 ` [Qemu-devel] " Mulyadi Santosa

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='elmmtp$ipr$1@sea.gmane.org' \
    --to=sfandino@yahoo.com \
    --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).