Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#35459 - [libvirt] fails to launch networks
Attached to Project:
Community Packages
Opened by Loïc BLOT (Nerzhul) - Friday, 24 May 2013, 16:20 GMT
Last edited by Sergej Pupykin (sergej) - Monday, 27 May 2013, 14:22 GMT
Opened by Loïc BLOT (Nerzhul) - Friday, 24 May 2013, 16:20 GMT
Last edited by Sergej Pupykin (sergej) - Monday, 27 May 2013, 14:22 GMT
|
DetailsDescription:
Since recent iptables update, libvirt cannot launch networks, and then we cannot virtualize. Additional info: * package version(s) community/libvirt 1.0.5-4 core/iptables 1.4.18-1 Steps to reproduce: Upgrade to this libvirt and iptables version, launch libvirt process and try to start a network. |
This task depends upon
Closed by Sergej Pupykin (sergej)
Monday, 27 May 2013, 14:22 GMT
Reason for closing: Duplicate
Additional comments about closing: FS#35443
Monday, 27 May 2013, 14:22 GMT
Reason for closing: Duplicate
Additional comments about closing:
Comment by Evan Callicoat (Apsu) -
Friday, 24 May 2013, 21:25 GMT
This is a duplicate of #35443; the hardcoded path to iptables in libvirt is incorrect now that the iptables package has moved the binary to /usr/bin