From: Riccardo Veraldi <Riccardo.Veraldi@cnaf.infn.it>
To: Andrew Cathrow <acathrow@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: live migration problems.
Date: Sat, 31 Mar 2012 14:35:17 +0200 [thread overview]
Message-ID: <4F76FA05.6010607@cnaf.infn.it> (raw)
In-Reply-To: <29021590.158.1333144756986.JavaMail.acathrow@0.0.0.0>
Thank you very much, this solved my problem, not even 1 ping is lost!
I did not find this hint in the documentation though.
Really thanks again
Riccardo
On 3/30/12 11:58 PM, Andrew Cathrow wrote:
>
> ----- Original Message -----
>> From: "Riccardo Veraldi"<Riccardo.Veraldi@cnaf.infn.it>
>> To: kvm@vger.kernel.org
>> Sent: Friday, March 30, 2012 5:45:47 PM
>> Subject: live migration problems.
>>
>> Hello,
>> I have problems with live migration.
>> I have several VMs in a CentOS 6.2 cluster environment.
>>
>> When I migrate one virtual machine from nodeA to nodeB the migration
>> goes smoothly but
>> in the same time the VM is migrated an external ping cannot reach the
>> VM.
>> I ping the VM before migration and after the migration is done ping
>> stops to work.
>> This happens for some VM and does not happen for other VM.
>> Apparently the VM are configured the same way so I can't understand
>> why
>> this is happening.
>> If I migrate the VM back to the original physical node the ping start
>> working again like if the switch did not
>> realize the VM mac address changed switch port.
>> To make things work always I Should make a ping from the VM console
>> to
>> whatever host and
>> in this case the arp table is updated on the switch.
>> The strange thing as I said is that some VM seems to always work
>> after
>> migration while other
>> seems never to work untl they are migrated back to original cluster
>> node.
>> Any hints or suggestions ?
> Make sure you have DELAY=0 set in the ifcfg file for the bridge on both hosts.
>
>
>> thank you very much
>>
>> Rick
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe kvm" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2012-03-31 12:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-30 21:45 live migration problems Riccardo Veraldi
2012-03-30 21:58 ` Andrew Cathrow
2012-03-31 12:25 ` Riccardo Veraldi
2012-03-31 12:35 ` Riccardo Veraldi [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=4F76FA05.6010607@cnaf.infn.it \
--to=riccardo.veraldi@cnaf.infn.it \
--cc=acathrow@redhat.com \
--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