From: Kevin Wolf <kwolf@redhat.com>
To: Peter Krempa <pkrempa@redhat.com>
Cc: Max Reitz <mreitz@redhat.com>,
Ciprian Barbu <Ciprian.Barbu@enea.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Eric Blake <eblake@redhat.com>,
Alexandru Avadanii <Alexandru.Avadanii@enea.com>,
Jeff Cody <jcody@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
svc-armband <armband@enea.com>
Subject: Re: [Qemu-devel] nbd: Possible regression in 2.9 RCs
Date: Tue, 4 Apr 2017 15:54:14 +0200 [thread overview]
Message-ID: <20170404135414.GC4536@noname.str.redhat.com> (raw)
In-Reply-To: <20170404132705.GE26598@andariel.pipo.sk>
[-- Attachment #1: Type: text/plain, Size: 1259 bytes --]
Am 04.04.2017 um 15:27 hat Peter Krempa geschrieben:
> On Tue, Apr 04, 2017 at 15:19:02 +0200, Kevin Wolf wrote:
> > Am 03.04.2017 um 14:51 hat Peter Krempa geschrieben:
> > > On Mon, Apr 03, 2017 at 10:15:42 +0200, Kevin Wolf wrote:
> > > > Am 31.03.2017 um 19:43 hat Max Reitz geschrieben:
> > > > > On 31.03.2017 18:03, Ciprian Barbu wrote:
>
> [...]
>
> > > > Peter, Eric, what is the status on the libvirt side here?
> > >
> > > Libvirt currently uses the NBD server only for non-shared storage
> > > migration. At that point the disk is not shared (while qemu may think
> > > so) since the other side is not actually running until the mirror
> > > reaches synchronized state.
> >
> > Yes, I misunderstood the situation at first.
> >
> > Anyway, is there already a libvirt patch for the cases where the image
> > is actually shared?
>
> As said, we use the nbd server only for migration. There's no other
> usage I know of and thus no patch.
I mean two VMs sharing the same image file, and both expose it as a
guest device. The situation for which we discussed before that libvirt
needs to pass share-rw=on. I understand that this isn't related to this
report, but I want to make sure that it's not forgotten.
Kevin
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2017-04-04 13:54 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-31 16:03 [Qemu-devel] nbd: Possible regression in 2.9 RCs Ciprian Barbu
2017-03-31 17:32 ` Ciprian Barbu
2017-03-31 17:36 ` Ciprian Barbu
2017-03-31 17:43 ` Max Reitz
2017-03-31 17:49 ` Ciprian Barbu
2017-03-31 17:57 ` Max Reitz
2017-03-31 19:07 ` Alexandru Avadanii
2017-04-03 18:52 ` Kashyap Chamarthy
2017-04-04 8:07 ` ciprian.barbu
2017-04-03 8:15 ` Kevin Wolf
2017-04-03 12:39 ` Max Reitz
2017-04-03 13:00 ` Kevin Wolf
2017-04-03 13:50 ` Peter Krempa
2017-04-04 12:16 ` Kevin Wolf
2017-04-04 13:51 ` Eric Blake
2017-04-04 14:04 ` Paolo Bonzini
2017-04-04 14:53 ` Kevin Wolf
2017-04-04 15:09 ` Paolo Bonzini
2017-04-05 11:01 ` Kevin Wolf
2017-04-05 21:13 ` Paolo Bonzini
2017-04-06 8:48 ` Kevin Wolf
2017-04-06 9:03 ` Kevin Wolf
2017-04-03 19:48 ` Eric Blake
2017-04-03 19:44 ` Eric Blake
2017-04-04 8:17 ` ciprian.barbu
2017-04-04 11:00 ` Paolo Bonzini
2017-04-04 11:14 ` Daniel P. Berrange
2017-04-03 12:51 ` Peter Krempa
2017-04-04 13:19 ` Kevin Wolf
2017-04-04 13:27 ` Peter Krempa
2017-04-04 13:54 ` Kevin Wolf [this message]
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=20170404135414.GC4536@noname.str.redhat.com \
--to=kwolf@redhat.com \
--cc=Alexandru.Avadanii@enea.com \
--cc=Ciprian.Barbu@enea.com \
--cc=armband@enea.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=jcody@redhat.com \
--cc=mreitz@redhat.com \
--cc=pkrempa@redhat.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).