This bug was fixed in the package libvirt - 0.6.1-0ubuntu5
---
libvirt (0.6.1-0ubuntu5) jaunty; urgency=low
* Fix logic error when applying %d bridge name rewriting. (LP:
#350780)
-- Soren HansenThu, 16 Apr 2009 20:48:49 +0200
** Changed in: libvirt (Ubuntu Jaunty)
Sta
I'm uploading the fixed package now. We'll see if it makes it ...
:-Dustin
** Also affects: libvirt (Ubuntu Jaunty)
Importance: High
Assignee: Soren Hansen (soren)
Status: In Progress
** Also affects: virt-manager (Ubuntu Jaunty)
Importance: Undecided
Status: Invalid
-
Soren submitted this patch, which I have tested and verified that it
solves the problem.
:-Dustin
** Changed in: libvirt (Ubuntu)
Status: Triaged => In Progress
--
Internal error starting virtual network 'default': virbr%d syntax not working
https://bugs.launchpad.net/bugs/350780
You rec
Marking invalid against virt-manager. Virt-manager is definitely
affected, but the bug is actually in libvirt.
:-Dustin
** Changed in: virt-manager (Ubuntu)
Status: New => Invalid
--
Internal error starting virtual network 'default': virbr%d syntax not working
https://bugs.launchpad.net
Soren submitted this patch, which I have tested and verified that it
solves the problem.
:-Dustin
** Attachment added: "libvirt_0.6.1-0ubuntu5.debdiff"
http://launchpadlibrarian.net/25634630/libvirt_0.6.1-0ubuntu5.debdiff
--
Internal error starting virtual network 'default': virbr%d syntax n
If /etc/libvirt/network/default.xml exists, in update progress, this
file doesn't get patched via normal dpkg post-inst scripts.
>
Manually all I had to do to fix it:
> /etc/init.f/stop
> ifconfig vnet0 down
> brctl delif virbr0
> /etc/init.d/libvirt-bin start
results in changed /etc/libvirt/n
>
> 'brctl setfd virbr%d 0' exited with non-zero status 1
It sounds like you didn’t restart libvirt after making the config
change, because it is still trying to bring up a bridge named “virbr%d”.
Maybe try `/etc/init.d/libvirt-bin restart`, or reboot.
--
Internal error starting virtual network
** Changed in: libvirt (Ubuntu)
Assignee: (unassigned) => Soren Hansen (soren)
--
Internal error starting virtual network 'default': virbr%d syntax not working
https://bugs.launchpad.net/bugs/350780
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
The Anders workaround does NOT works for me. My
/etc/libvirt/qemu/networks/default.xml has the following:
default
But the default network connection is always in Inactive state. When I
try to active it using the "Play" button at the bottom left of the
dialog, I ge
Confirming. The default configuration shipped with libvirt doesn't work.
Anders workaround works:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/350780/comments/1
** Changed in: libvirt (Ubuntu)
Importance: Undecided => High
** Changed in: libvirt (Ubuntu)
Status: New => Triag
Is the bug being assigned or worked? Just happens on Jaunty Beta as
well. Really hate tweaking the default.xml manually.
--
Internal error starting virtual network 'default'
https://bugs.launchpad.net/bugs/350780
You received this bug notification because you are a member of Ubuntu
Bugs, which
The problem goes away if I replace virbr%d with virbr0 in
/etc/libvirt/qemu/networks/default.xml. That lets the “default” network
start up as active rather than inactive.
** Also affects: libvirt (Ubuntu)
Importance: Undecided
Status: New
--
Internal error starting virtual network 'de
12 matches
Mail list logo
