Karmic has long since stopped to receive any updates. Marking the Karmic
task for this ticket as "Won't Fix".
** Changed in: libvirt (Ubuntu Maverick)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
As pointed out by Alex, starting the dnsmasq service makes the libvirt
network to crash and not start.
So I found a work-around for this: you must set the option "bind-
interfaces" in the "/etc/dnsmasq.conf" file to tell the dnsmasq daemon
to bind itself to the interface specified in the config fi
** Changed in: libvirt (Debian)
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/668043
Title:
libvirt default network doesn't start, iptables errors, bad rules
To m
@Alex
thank you.
service dnsmasq stop
has helped to me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/668043
Title:
libvirt default network doesn't start, iptables errors, bad rules
To manage no
** Changed in: libvirt (Ubuntu Maverick)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/668043
Title:
libvirt default network doesn't start, iptables errors,
@Charles,
what release are you on? Are you using a backported libvirt 0.8.8 on
maverick?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/668043
Title:
libvirt default network doesn't start, iptables
I'm using libvirt version: 0.8.8, this bug stille xists
12:29:45.910: 27562: info : libvirt version: 0.8.8
12:29:45.910: 27562: error : virCommandWait:1229 : internal error Child process
(/sbin/iptables --table mangle --delete POSTROUTING --out-interface virbr0
--protocol udp --destination-port
@Serge
While reporting the new bug as suggested Launchpad found it previously
reported in bug #231060.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/668043
Title:
libvirt default network doesn't st
Quoting Alex Muntada (al...@alexm.org):
> @Serge
>
> i actually experienced the problem on my laptop but never tried the
> proposed packages. After removing dnsmasq package i had manually added,
> the problem disappeared.
I see, thanks.
> Would you like me to reinstall dnsmasq again and try the
@Serge
i actually experienced the problem on my laptop but never tried the
proposed packages. After removing dnsmasq package i had manually added,
the problem disappeared.
Would you like me to reinstall dnsmasq again and try the proposed
packages?
--
You received this bug notification because y
@Alex- in comment #20, is 'and now libvirt network starts fine' a
confirmation of the proposed packages fixing the problem, or did you
never actually experience this particular bug to begin with?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: libvirt (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/668043
Title:
libvirt default network doesn't start, iptables errors, bad rules
--
ubunt
According to debian bug I just added in this one, the problem is
actually in dnsmasq being already running before starting libvirt
network.
I just purged dnsmasq package on my maverick destop and now libvirt
network starts fine.
HTH
** Bug watch added: Debian Bug tracker #592177
http://bugs.
@Mark,
The ppa at https://launchpad.net/~serge-hallyn/+archive/libvirt-mav has
64-bit versions as well. You should be able to just
sudo add-apt-repository ppa:serge-hallyn/libvirt-mav
sudo apt-get update
sudo apt-get -y dist-upgrade
to install them
--
You received this bug notification becaus
Serge, I tried installing your packages, but they're for 32 bit systems
only. Can you make the 64 bit versions?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/668043
Title:
libvirt default network do
I installed this patch late last night, and got the error
error: internal error '/sbin/iptables --table mangle --delete
POSTROUTING --out-interface virbr0 --protocol udp --destination-port 68
--jump CHECKSUM --checksum-fill' exited with non-zero status 2 and
signal 0: iptables v1.4.4: unknown opti
A package is building at ppa:serge-hallyn/libvirt-mav, with source at
https://code.launchpad.net/~serge-
hallyn/ubuntu/maverick/libvirt/bugall/, with fixes for this bug (and for
bug 713071). Please test when it is finished building, and let us know
if it fixes the bug for you.
** Branch linked: l
@Brian:
> At this point, seeing as there are two different issues in this one
> ticket, I would suggest that Alle open a new ticket covering the second
> issue.
Yes, that would be ideal. The problem is that I can't ask for this
patch to be merged into maverick without confirmation that it fixes
On Thu, 2011-02-03 at 13:39 +, Serge Hallyn wrote:
> Please test the packages from the attachment in comment #6.
I would if I could but I can't because my libvirt has other patches
(i.e. bug 713071) for bugs which I have run into and filed reports
upstream in my libvirt. Running your above p
On Thu, 2011-02-03 at 21:04 +, Serge Hallyn wrote:
> (If it did in fact fail, then I'll revert the offending patch
> http://libvirt.org/git/?p=libvirt.git;a=commitdiff;h=fd5b15ff1a2ec37e75609c091522ae1e2c74c811
> as per http://bugs.gentoo.org/334921.
Please take note that the fix that I suppl
Hi Serge,
Yes I confirm it did fail. I am using the "Virtual Machine Manager" and
when I enable the network it gives me the message I posted earlier.
When I sun it at the command line, (after updating my libvirt deb today
from your ppa) I get:
ademaria@ademaria-laptop:~$ sudo virsh net-start def
(If it did in fact fail, then I'll revert the offending patch
http://libvirt.org/git/?p=libvirt.git;a=commitdiff;h=fd5b15ff1a2ec37e75609c091522ae1e2c74c811
as per http://bugs.gentoo.org/334921.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Fascinating - I'm looking at
https://bugzilla.redhat.com/show_bug.cgi?id=642355.
** Bug watch added: Red Hat Bugzilla #642355
https://bugzilla.redhat.com/show_bug.cgi?id=642355
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
Alessandro,
All references to this that I find online suggest that while you should
see that message, it should only be a warning. Did things proceed after
you saw that warning?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
I get:
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/host.py", line 401, in start_network
net.start()
File "/usr/share/virt-manager/virtManager/network.py", line 97, in start
self.net.create()
File "/usr/lib/python2.6/dist-packages/libvirt.py", line 866
Please test the packages from the attachment in comment #6. (You can
also get them from ppa:serge-hallyn/virt) If these do indeed fix the
issue for you, then I'll issue a SRU to get this fix into maverick.
I've marked the main bug 'fix released' since natty has the fix from
upstream (and since t
libvirt0 and libvirt-bin packages with the proposed fix.
** Attachment added: "libvirt-test.tgz"
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/668043/+attachment/1827071/+files/libvirt-test.tgz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
** Changed in: libvirt (Ubuntu)
Assignee: (unassigned) => Serge Hallyn (serge-hallyn)
** Changed in: libvirt (Ubuntu Maverick)
Status: Triaged => In Progress
** Changed in: libvirt (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: libvirt (Ubuntu Maverick)
Assigne
** Branch linked: lp:~serge-hallyn/ubuntu/maverick/libvirt/fixfw
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/668043
Title:
libvirt default network doesn't start, iptables errors, bad rules
--
ub
** Also affects: libvirt (Ubuntu Maverick)
Importance: Undecided
Status: New
** Changed in: libvirt (Ubuntu Maverick)
Status: New => Triaged
** Changed in: libvirt (Ubuntu Maverick)
Importance: Undecided => Medium
--
You received this bug notification because you are a membe
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/668043
Title:
libvirt default network doesn't start, iptables errors, bad rules
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubu
This patch fixes the problem.
** Patch added: "the fix"
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/668043/+attachment/1822422/+files/9030-Only-attempt-removal-of-the-rule-allowing-tftp-if-it-was-added.patch
--
You received this bug notification because you are a member of Ubuntu
Brian, I'm sorry that you haven't received any direct response on this
issue. This bug actually wasn't triaged fully, it was just set to medium
importance. Since there are multiple users showing as affected, I'll
mark the issue as Confirmed.
Can you please clarify something, is the git link from t
3 months ago this bug was filed and triaged and yet nothing has been
done about it. You do realize that this prevents us from being able to
configure networks in virt-manager, right? You know that this means
that nothing except basic virtual guests can be created right?
Fixing this is simply a m
** Changed in: libvirt (Ubuntu)
Importance: Undecided => Medium
--
libvirt default network doesn't start, iptables errors, bad rules
https://bugs.launchpad.net/bugs/668043
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bug
Hi there,
I'm hitting the same bug with an explanation there :
http://www.spinics.net/lists/kvm/msg42207.html
libvirt "faulty" change :
http://libvirt.org/git/?p=libvirt.git;a=commitdiff;h=fd5b15ff1a2ec37e75609c091522ae1e2c74c811
and a quick way to test issue:
# /sbin/iptables --table mangle -A
I have the same error after install KVM and use virtual-manager.
I try to add some iptables rules but nothing change.
We wait somebody help us to resolve this problem
thanks andrea
--
libvirt default network doesn't start, iptables errors, bad rules
https://bugs.launchpad.net/bugs/668043
You rece
37 matches
Mail list logo
