Re: [one-users] VM not pingable after Live migration

2011-07-04 Thread Jaime Melis
t; the developers could have an idea? Carlos & Co.? > > ** ** > > Regards. > > ** ** > > *Von:* Khoa Nguyen [mailto:vankhoa...@gmail.com] > *Gesendet:* Dienstag, 21. Juni 2011 16:31 > *An:* Adnan Pasic > > *Betreff:* Re: [one-users] VM not pingable a

Re: [one-users] VM not pingable after Live migration

2011-06-23 Thread Justin Cinkelj
esendet: Montag, 20. Juni 2011 08:44 > An: Adnan Pasic > Cc: users@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 phy

Re: [one-users] VM not pingable after Live migration

2011-06-21 Thread Adnan Pasic
Cc: users@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 th

Re: [one-users] VM not pingable after Live migration

2011-06-20 Thread Adnan Pasic
-Ursprüngliche Nachricht- Von: Justin Cinkelj [mailto:justin.cink...@xlab.si] Gesendet: Montag, 20. Juni 2011 08:44 An: Adnan Pasic Cc: users@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

Re: [one-users] VM not pingable after Live migration

2011-06-19 Thread Justin Cinkelj
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 ___ Users mailing list Users@lists.opennebula.or

[one-users] VM not pingable after Live migration

2011-06-15 Thread Adnan Pasic
Hello, I need a little help in understanding something. As far as I know, a live migration should migrate everything over to the other cluster, including the IP address, right? I have a front-end and two clusters, all three having an IP-address of this form: 192.168.0.1-3 My virtual machines rec