qemu-block
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [RFC PATCH 00/18] Add qemu-storage-daemon


From: Stefan Hajnoczi
Subject: Re: [RFC PATCH 00/18] Add qemu-storage-daemon
Date: Thu, 12 Dec 2019 11:16:32 +0000
User-agent: Mutt/1.12.1 (2019-06-15)

On Thu, Nov 21, 2019 at 12:08:16PM +0100, Kevin Wolf wrote:
> Am 21.11.2019 um 11:32 hat Stefan Hajnoczi geschrieben:
> > On Wed, Nov 06, 2019 at 03:58:00PM +0100, Kevin Wolf wrote:
> > > Am 06.11.2019 um 15:37 hat Max Reitz geschrieben:
> > > > On 17.10.19 15:01, Kevin Wolf wrote:
> > > > The only thing I don’t like is the name, but that’s what <Tab> is for.
> > > > :-)
> > > 
> > > I'm open for suggestions, but I thought 'qsd' was a bit too terse. :-)
> > > 
> > > (Actually, maybe we could even pick something that doesn't mention
> > > storage or block? After all, it can do all kinds of QEMU backends in
> > > theory. Not sure if there's any standalone use for them, but who
> > > knows...)
> > 
> > It's likely that non-storage use cases will want to a daemon too.  Maybe
> > just qemu-daemon?
> 
> Do you have specific use cases in mind? Most backends seem rather
> useless without a device to attach them to. In older QEMU versions,
> maybe you could put multiple network backends into a common vlan to
> forward between them, but even that vlan concept doesn't exist any more.

I was thinking about the model where device emulation happens in the
daemon.  We've since agreed that device emulation will continue to
happen in a more traditional QEMU process, so I can't think of
non-storage use cases at the moment.

Stefan

Attachment: signature.asc
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]