Hi Matt,
I looked into this and had to realize that I missed your bug.
I beg your pardon - I took over looking after qemu/libvirt a while ago and this
is an issue from the time this was not clear yet and we seemed to have missed
it for way too much time.
Especially since you made all the great effort to even test, bisect and
backport a fix.
I really beg your pardon!
OTOH (the good side of things) the issue you are referring to is already fixed
in bug 1620407.
We came to the same conclusion there as you did, we did look into backporting
but for the complexities you have found as well looked into alternatives.
It turned out we needed way less to get it working.
So since libvirt (1.3.1-1ubuntu10.8) your issue should be fixed.
If not for your specific kind of setup please report here, I'm subscribed now
and it should not be another year almsot :-/
** Tags removed: server-next
** Changed in: libvirt (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574957
Title:
Custom interface names with <interface type='ethernet'> does not start
qemu
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1574957/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
