From: John Clemens <jclemens-X2/pQFfLUrBl57MIdRCFDg@public.gmane.org>
To: Anthony Liguori <anthony-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: User feedback
Date: Fri, 05 Oct 2007 10:57:15 -0400 [thread overview]
Message-ID: <1191596235.24957.18.camel@beth> (raw)
In-Reply-To: <47063371.9060105-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
On Fri, 2007-10-05 at 07:52 -0500, Anthony Liguori wrote:
> http://hg.codemonkey.ws/qemu-nbd/
>
> This will let you expose a qcow file (or an individual partition within
> a qcow file) as an NBD server which you can then mount on your host. A
> bit round-about but it gets the job done.
You just made my day. I've been threatening to do the same thing for
weeks :) A couple of questions if you don't mind:
- I was a bit confused by the statement on the nbd homepage:
"Read-write nbd with client and server on same machine has a rather
fundamental problem: when the system is short of memory, it tries to
write back dirty pages. So the nbd client asks the nbd server to write
back data, but as nbd-server is a userland process, it may require
creating dirty pages to fullfill the request."
The above makes sense, and the README in the source says this is not a
problem on SMP systems since there's more than one kblockd flush
thread... which makes less sense (why can't both kblockd's be blocked in
this way?)
Does qemu-nbd address this, perhaps by opening the qcow file with O_SYNC
or something? or is this still a problem?
- There's no license file with the code, I'm assuming it's GPL since you
use qemu code directly?
Thanks for writing such a useful bit of software!
john.c
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
next prev parent reply other threads:[~2007-10-05 14:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-05 12:02 User feedback rob wilco
[not found] ` <84ad660e0710050502q3f4a3156g5451f7c70f2f7fdd-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-10-05 12:52 ` Anthony Liguori
[not found] ` <47063371.9060105-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
2007-10-05 14:57 ` John Clemens [this message]
2007-10-05 12:56 ` Avi Kivity
-- strict thread matches above, loose matches on Subject: below --
2007-10-07 12:11 Wolfram Gloger
[not found] ` <20071007121109.13666.qmail-apX3yWB0kgwDWtnaHct1IhJ8j3Mt6MsSG9Ur7JDdleE@public.gmane.org>
2007-10-07 14:34 ` Anthony Liguori
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=1191596235.24957.18.camel@beth \
--to=jclemens-x2/pqfflurbl57midrcfdg@public.gmane.org \
--cc=anthony-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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.