ping we had better options ;-)
>
>
>
> - Original Message -
>
> From: "Marcus Sorensen"
> To: dev@cloudstack.apache.org
> Cc: cloudstack-...@incubator.apache.org
> Sent: Monday, August 5, 2013 5:42:38 PM
> Subject: Re: 4.1.x KVM cloudVirBr to br-
>
> Yes, th
t: Re: 4.1.x KVM cloudVirBr to br-
Yes, the vm definition already has the bridge name chosen (on initial
startup), and that definition is migrated between hosts. This is
further exacerbated by the fact that the bridges are created on the
destination host prior to migration (so they'll be
Yes, the vm definition already has the bridge name chosen (on initial
startup), and that definition is migrated between hosts. This is
further exacerbated by the fact that the bridges are created on the
destination host prior to migration (so they'll be ready), rather than
somehow being able to see
All,
As most know, the upgrade from 4.0 to 4.1 changed the interface naming schema.
When a host in a cluster is rebooted, the interface naming changes. When this
occurs, live migration breaks to that host.
Example config:
All Management and hosts running CS 4.1.1
Hypervisor: KVM on RHEL 6.3
