From: Avi Kivity <avi@redhat.com>
To: Gareth Bult <gareth@bult.co.uk>
Cc: kvm@vger.kernel.org
Subject: Re: SMP/DRBVD issues ...
Date: Sun, 13 Dec 2009 12:27:44 +0200 [thread overview]
Message-ID: <4B24C1A0.8030204@redhat.com> (raw)
In-Reply-To: <30898204.23101260095109812.JavaMail.root@zimbra>
On 12/06/2009 12:25 PM, Gareth Bult wrote:
>
> However, is there a flag that can be passed to qemu that will tell it whether the device is shared or not?
>
> On Xen, I think the migration code actually does a;
>
> "drbdadm secondary oldnode"
> "drbdadm primary newnode"
>
> As part of the migration process, thus forcing DRBD itself to provide the locking mechanism.
> (and this is part of Xen, i.e. it's "below" libvirt)
>
> .. is there somewhere more relevant I can post this?
>
>
The libvirt mailing lists.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-12-13 10:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <18980634.23081260094886486.JavaMail.root@zimbra>
2009-12-06 10:25 ` SMP/DRBVD issues Gareth Bult
2009-12-13 10:27 ` Avi Kivity [this message]
[not found] <13234756.23131260098867747.JavaMail.root@zimbra>
2009-12-06 11:28 ` Gareth Bult
2009-12-06 12:35 ` Avi Kivity
2009-12-06 2:43 Gareth Bult
2009-12-06 10:04 ` Avi Kivity
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=4B24C1A0.8030204@redhat.com \
--to=avi@redhat.com \
--cc=gareth@bult.co.uk \
--cc=kvm@vger.kernel.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