[one-users] VM not pingable after Live migration

[Justin Cinkelj]

(sorry for late answer, I missed the mail)

One example is
root at n0007:~# brctl show | expand -
bridge name     bridge id               STP enabled     interfaces
br100           8000.1c6f65d1a37d       yes             eth0.200
#
root at n0008:~# brctl show | expand -         
bridge name     bridge id               STP enabled     interfaces
br100           8000.1c6f65d1a5b2       yes             eth0.200
                                                        vnet0
n0007 is head node, and n0008 is compute node.
eth0.200 could be replaced with eth0 (eg no VLAN would be used)

Try to create some bridge, and use it in our network template file, or
move existing vnet? and eth0 to this bridge.

regards, justin

On Mon, 2011-06-20 at 19:04 +0200, Adnan Pasic wrote:
> Hello,
> well, actually this command gives me as result that the virbr0-bridge is connected to the vnet0-interface. Is this what you meant? How could I change this to eth0?
> And would the VM then be pingable after the migration as well??
> 
> Thanks for your help!
> Best regards, Adnan
> 
> -----Ursprüngliche Nachricht-----
> Von: Justin Cinkelj [mailto:justin.cinkelj at xlab.si] 
> Gesendet: Montag, 20. Juni 2011 08:44
> An: Adnan Pasic
> Cc: users at lists.opennebula.org
> Betreff: Re: [one-users] VM not pingable after Live migration
> 
> I assume this would occur if VM's network interface is connected to a
> bridge, and bridge is not connected to to a physical network interface.
> 'brctl show' should show if this is the case.
> 
> Regards, justin
> 
>