Reading more on OVS, which I'm no means of any kind of expert, it would
appear that promox still has it in use even for standard default linux
interfaces and bridges.
And OVS stores its interfaces in /etc/openvswitch/conf.db
So guessing the db needs to be purged/flushed.
yea,nay?
On 10/29/2015 4:13 PM, David Lawley wrote:
Ok works for me. So with this logic I should be able to shut down said
machine, remove nics, migrate to other host. Then restart, replace
nics/drivers.
I think I have tried this, but just sounding off right now. Bit puzzled
why vmbr0 worked on both.. just affected vmbr1.
On 10/29/2015 4:04 PM, Michael Rasmussen wrote:
On Thu, 29 Oct 2015 15:51:29 -0400
David Lawley <[email protected]> wrote:
This behaviour is happening on all the nodes ( 1 2 and 4) that have
linux bridges..
I know there is a lot of reading between the lines here. I have kind
of glossed over the issue.
Just wondering if that last node with OVS is affecting the other 3?
If you have had some experience in this area your help would be
appreciated backing out of OVS.
The thing is that linux bridge and openvswitch is mutually exclusive
since both needs to load kernel modules which is supposed to hook into
the network stack the same place. What you discover is that when
migrating between a linux bridge and an openvswitch node the running vm
talks either language but not both at the same time (so to speak)
_______________________________________________
pve-user mailing list
[email protected]
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
_______________________________________________
pve-user mailing list
[email protected]
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
_______________________________________________
pve-user mailing list
[email protected]
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
