From: Kevin Wolf <kwolf@redhat.com>
To: Juan Quintela <quintela@redhat.com>
Cc: kvm-devel <kvm@vger.kernel.org>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] KVM call minutes for 2019-06-18
Date: Tue, 18 Jun 2019 21:03:03 +0200 [thread overview]
Message-ID: <20190618190303.GF4296@localhost.localdomain> (raw)
In-Reply-To: <87d0jb9cex.fsf@trasno.org>
Am 18.06.2019 um 16:49 hat Juan Quintela geschrieben:
> * Kevin is experimenthing with an external qemu-storage daemon
> * qemu-storage daemon vs process for each image
> * compromise: less isolation but easier to do
> * i.e. just doing the full subsystem instead of each device
This is something that users can do then, but it's not a must.
The storage daemon is just a building block, and it's completely up to
the user whether they start a single daemon with many --blockdev options
and exports, or whether they start many daemons that serve only a single
image each.
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Wolf <kwolf@redhat.com>
To: Juan Quintela <quintela@redhat.com>
Cc: qemu-devel@nongnu.org, kvm-devel <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] KVM call minutes for 2019-06-18
Date: Tue, 18 Jun 2019 21:03:03 +0200 [thread overview]
Message-ID: <20190618190303.GF4296@localhost.localdomain> (raw)
In-Reply-To: <87d0jb9cex.fsf@trasno.org>
Am 18.06.2019 um 16:49 hat Juan Quintela geschrieben:
> * Kevin is experimenthing with an external qemu-storage daemon
> * qemu-storage daemon vs process for each image
> * compromise: less isolation but easier to do
> * i.e. just doing the full subsystem instead of each device
This is something that users can do then, but it's not a must.
The storage daemon is just a building block, and it's completely up to
the user whether they start a single daemon with many --blockdev options
and exports, or whether they start many daemons that serve only a single
image each.
Kevin
next prev parent reply other threads:[~2019-06-18 19:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-18 14:49 KVM call minutes for 2019-06-18 Juan Quintela
2019-06-18 14:49 ` [Qemu-devel] " Juan Quintela
2019-06-18 19:03 ` Kevin Wolf [this message]
2019-06-18 19:03 ` 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=20190618190303.GF4296@localhost.localdomain \
--to=kwolf@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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 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.