Ubuntu
virt-manager package

  1. Bug #1279176
  2. Comment #5

Comment 5 for bug 1279176

Revision history for this message
Thiago Martins (martinx) wrote : Re: IPv6 fails when "<interface type='direct'>", on top of OVS

Hi Serge,

Why this BUG is marked as "Incomplete"?

Do I need to post more info about it?!

Nevertheless, do you think that this is a problem with virt-manager itself? I mean, it is the "guy" who is writing the guest XML, right?! I'm used to use it with "type=directly" mostly because virt-manager does that for me automatically, but, now, that I have my IPv6 blocks, this problem appeared and I'm seeing myself "obligated" to move to "type=bridge"...

Sometimes, "type=bridge" triggers errors, telling me that some vnetX OVS ports are already in use but, it is not, then, I need to manually delete the "conflicting" ports on host with "ovs-vsctl del-port ovsbr1 vnet13", for example, otherwise, some random guests doesn't even start.

Listen, I'm a bit worried about this because it works for IPv4 and not for IPv6, but why?! Something is wrong. This BUG is "Confirmed", don't you think?!

NOTE: About the conflicts with "vnetX" when "type=bridge", I'm seeing that, with the latest Ubuntu 14.04 packages, there is no "vnetX" interfaces anymore, they are now called "vifX.Y", maybe it will not conflict anymore... Time will tell.

Regards,
Thiago