[
https://issues.apache.org/jira/browse/CLOUDSTACK-4550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13813859#comment-13813859
]
hayou edited comment on CLOUDSTACK-4550 at 11/5/13 11:26 AM:
-------------------------------------------------------------
I use Edison's procedure but it fails.
When you launch a Vm, '/etc/libvirt/hooks/qemu' script will automatically
connect the vnet to the right bridge :
{quote}
*cloudVirBr100 8000.0017a4770064 no bond0.100*
*+vnet0+*
cloudVirBr200 8000.0017a4770066 no bond1.200
cloudVirBrPriv 8000.0017a4770067 no bond2
cloudVirBrPub 8000.0017a477006b no bond3
{quote}
on CS 4.2.1 I have this error when I wanna to use live migration :
+on management+ :
{quote}
2013-11-01 14:39:34,911 ERROR [cloud.vm.VirtualMachineManagerImpl]
(Job-Executor-3:job-144 = [ 78724381-e9e3-4fb7-aeb7-b366193876ba ]) Unable to
migrate due to Cannot get interface MTU on 'brbond0.100-100': No such device
{quote}
To use live migration I have to add I bridge on each KVM host ( *brctl addbr
brbond0.100-100* )
after the live migration on my KVM hosts I have this :
{quote}
# brctl show
bridge name bridge id STP enabled interfaces
brbond0-100 8000.000000000000 no
*brbond0.100-100 8000.fe31f4000139 no +vnet0+*
cloud0 8000.000000000000 no
cloudVirBr100 8000.0017a4770064 no bond0.100
cloudVirBr200 8000.0017a4770066 no bond1.200
cloudVirBrPriv 8000.0017a4770067 no bond2
cloudVirBrPub 8000.0017a477006b no bond3
{quote}
It's ok for live migration but my vnet is not on the right bridge
was (Author: hayou):
I use Edison's procedure but it fails.
When you launch a Vm, '/etc/libvirt/hooks/qemu' script will automatically
connect the vnet to the right bridge :
{quote}
*cloudVirBr100 8000.0017a4770064 no bond0.100*
*+vnet0+*
cloudVirBr200 8000.0017a4770066 no bond1.200
cloudVirBrPriv 8000.0017a4770067 no bond2
cloudVirBrPub 8000.0017a477006b no bond3
{quote}
on CS 4.2.1 I have this error when I wanna to use live migration :
+on management+ :
{quote}
2013-11-01 14:39:34,911 ERROR [cloud.vm.VirtualMachineManagerImpl]
(Job-Executor-3:job-144 = [ 78724381-e9e3-4fb7-aeb7-b366193876ba ]) Unable to
migrate due to Cannot get interface MTU on 'brbond0.100-100': No such device
{quote}
To use live migration I have to add I bridge on each KVM host ( *brctl addbr
brbond0.100-100* )
after the live migration on my KVM hosts I have this :
{quote}
# brctl show
bridge name bridge id STP enabled interfaces
brbond0-100 8000.000000000000 no
*brbond0.100-100 8000.fe31f4000139 no +vnet0+*
cloud0 8000.000000000000 no
cloudVirBr100 8000.0017a4770064 no bond0.100
cloudVirBr200 8000.0017a4770066 no bond1.200
cloudVirBrPriv 8000.0017a4770067 no bond2
cloudVirBrPub 8000.0017a477006b no bond3
{quote}
It's ok for live migration but my vnet is not on the right
> [DOC] When upgrading KVM agents to 4.2(.1?) perform bridge renaming to have
> migration work
> ------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-4550
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4550
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Doc, KVM, Upgrade
> Affects Versions: 4.2.0
> Reporter: Prasanna Santhanam
> Priority: Critical
>
> See CLOUDSTACK-4405 for the original bug. This is the doc to be prepared as
> part of upgrade in release notes once the fix for the bug is verified to work
> After network bridges being renamed from cloudVirBrVLAN to brem1-VLAN to
> support the same VLAN on multiple physical networks the migration of VMs from
> hosts prior the upgrade to the ones added after the upgrade will fail.
> In order to fix this rename the bridges is required to allow migration to
> work.
> This can be done by running the cloudstack-agent-upgrade script. The original
> bug is still undergoing testing, but these are the initial instructions
--
This message was sent by Atlassian JIRA
(v6.1#6144)
