[ https://issues.apache.org/jira/browse/CLOUDSTACK-9362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Will Stevens resolved CLOUDSTACK-9362. -------------------------------------- Resolution: Fixed Fix Version/s: 4.9.0 > Migrating a VM using VXLANs and bridges fails > --------------------------------------------- > > Key: CLOUDSTACK-9362 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9362 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: KVM > Affects Versions: 4.6.2, 4.7.1, 4.8.0 > Environment: Using KVM with VXLANs in Linux bridge devices (not > OpenVSwitch) > Reporter: Aaron Brady > Fix For: 4.9.0 > > > https://github.com/apache/cloudstack/commit/bb8f7c652e42caacff5adce1ce60342603677605 > The above commit introduces rewriting of bridge device names when migrating a > virtual machine from one host to another. However, it also matches bridges > called "brvx-1234" and rewrites them to (in my case) "brem1-1234" - this > doesn't match the bridge name on the destination and causes the migration to > fail with the error: > error : virNetDevGetMTU:397 : Cannot get interface MTU on 'brem1-1234': No > such device > I have flagged this as major because it's not possible to migrate VMs using > VXLANs for maintenance, which seems important (it's certainly important to > me!). -- This message was sent by Atlassian JIRA (v6.3.4#6332)