Oh, actually, if you don't object, I'd like to re-title this bug to be a
feature request for virt-manager to support an ovs bridge for VM
connections.
** No longer affects: libvirt (Ubuntu)
** Changed in: virt-manager (Ubuntu)
Importance: High => Wishlist
--
You received this bug notificatio
Hi,
Laine straightened me out on irc. the means
that it will create a macvtap interface. It is not meant to be used
with a bridge, but with a real nic. Since you are using a bridge, you
want to use . The fact that type='direct'
sometimes works appears to be an accident.
You mentioned in comm
I can no longer get that to fail, so either my first configuration was
invalid, or the bug is very intermittent.
I'm using the 2.0 qemu candidate from ppa:ubuntu-virt/ppa, and
1.2.2-0ubuntu3 libvirt.
If you switch to that ppa and update libvirt, does that help?
--
You received this bug notifica
I tested this 4 ways:
Using a linux bridge, using
Using a linux bridge, using
Using an ovs bridge, using
Using an ovs bridge, using
Only the ovs bridge with type='direct' failed to ping its ipv6 gateway
(fc00::1 for me).
The fact that type='direct' works
Interestingly, a subsequent attempt using ovsbr1 and type='direct'
succeeded.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1279176
Title:
IPv6 fails when "", on top of OVS
To manage notifications
importance: high
** Changed in: libvirt (Ubuntu)
Importance: Medium => High
** Changed in: virt-manager (Ubuntu)
Importance: Medium => High
** Changed in: virt-manager (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubunt
Thanks, so it sounds like there are several bugs here, if I'm
understanding things right. It's possible that virtinst should
be using type=bridge, I need to figure that out. In either case,
as you say, if ipv4 works then you'd think ipv6 should work - that
would be a libvirt bug.
And it sounds l
** Also affects: libvirt (Ubuntu)
Importance: Undecided
Status: New
** Changed in: virt-manager (Ubuntu)
Importance: Wishlist => Medium
** Changed in: libvirt (Ubuntu)
Importance: Undecided => Medium
** Changed in: libvirt (Ubuntu)
Status: New => Confirmed
--
You receive
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 d
Quoting Thiago Martins (thiagocmarti...@gmail.com):
> Hello Serge!
>
> I think that this is, in fact, a bug.
>
> Even using "vepa", the problem is the same.
>
> My XML looks like this now:
>
> ---
>
>
>
>
>function='0x0'/>
>
> ---
>
> Same problem, guest
BTW, I'm seeing that, with your example, you're using:
---
---
...so, your example points directly to eth0 but, I'm using OpenVSwitch,
is that valid even for when using it?!
I'm reading http://libvirt.org/formatdomain.html now, thanks for
pointing it out!
Best,
Thiago
--
You receiv
Hello Serge!
I think that this is, in fact, a bug.
Even using "vepa", the problem is the same.
My XML looks like this now:
---
---
Same problem, guest IPv4 works, IPv6 does not!
The weird is that, if I start a Router Advertisement in my network, the
guest
Thanks for submitting this bug.
It appears to me that 'interface type='direct'' works only for macvlan
devices. This would require you to use a real physical NIC, as in:
For instance see http://libvirt.org/formatdomain.html.
So if there is a bug it would seem to me to be in virt-man
** Description changed:
Hello!
* Hypervisor is daily / latest Ubuntu 14.04 and guest is Ubuntu 12.04
and 14.04
-
KVM1.7.0+dfsg-3ubuntu1
openvswitch-switch 2.0.1+git20140120-0ubuntu1
libvirt0
14 matches
Mail list logo
