From: Avi Kivity <avi@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: Nils Cant <nils.cant@kangaroot.net>,
Gleb Natapov <gleb@redhat.com>,
kvm@vger.kernel.org, libvir-list@redhat.com
Subject: Re: KVM doesn't send an arp announce after live migrating a domain
Date: Wed, 25 Aug 2010 14:59:55 +0300 [thread overview]
Message-ID: <4C7505BB.101@redhat.com> (raw)
In-Reply-To: <20100825114237.GH13337@redhat.com>
On 08/25/2010 02:42 PM, Daniel P. Berrange wrote:
>
>> Is virt-manager able to drive this? it would be great if you could
>> drive everything from there.
> Yes, it does now, under the menu Edit -> Host Details -> Network Interfaces
> NetworkManager has also finally learnt to ignore ifcfg-XXX files which
> have a BRIDGE= setting in them, so it shouldn't totally trash your guest
> bridge networking if you leave NM running.
Cool. I guess what remains is to get people to unlearn all the previous
hacks.
(also would be nice to have libvirt talk to NetworkManager instead of
/etc/sysconfig)
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
prev parent reply other threads:[~2010-08-25 12:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-25 7:52 KVM doesn't send an arp announce after live migrating a domain Nils Cant
2010-08-25 8:37 ` Michael Tokarev
2010-08-25 8:43 ` Gleb Natapov
2010-08-25 10:51 ` Michael Tokarev
2010-08-25 10:59 ` Gleb Natapov
2010-08-25 11:07 ` Gleb Natapov
2010-08-25 11:36 ` Michael Tokarev
2010-08-25 12:15 ` Gleb Natapov
2010-08-25 8:38 ` Gleb Natapov
2010-08-25 9:21 ` Nils Cant
2010-08-25 10:40 ` Avi Kivity
2010-08-25 10:52 ` Daniel P. Berrange
2010-08-25 11:05 ` Avi Kivity
2010-08-25 11:15 ` Daniel P. Berrange
2010-08-25 11:30 ` Avi Kivity
2010-08-25 11:36 ` Daniel P. Berrange
2010-08-25 11:38 ` Avi Kivity
2010-08-25 11:42 ` Daniel P. Berrange
2010-08-25 11:59 ` Avi Kivity [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=4C7505BB.101@redhat.com \
--to=avi@redhat.com \
--cc=berrange@redhat.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=libvir-list@redhat.com \
--cc=nils.cant@kangaroot.net \
/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