Quoting SergeiFranco (776...@bugs.launchpad.net):
> This problem looks very similar to this: http://www.spinics.net/lists
> /linux-net/msg17690.html
Ah, thanks very much. That commit is in the natty-proposed kernel, but
not yet in the natty kernel. Can you test the natty-proposed kernel and
conf
Quoting SergeiFranco (776...@bugs.launchpad.net):
> In nat mode it does not panic.
Thanks for that info.
Is that true even with memballoon enabled?
...
> I need this box in bridge mode (it is a virtual server after all).
Absolutely. This just gives us a better chance of tracking down the
bug(
Hi, here is the iptables-save output:
*filter
:INPUT DROP [992:148145]
:FORWARD ACCEPT [24:1496]
:OUTPUT ACCEPT [215528:64537610]
-A INPUT -i lo -j ACCEPT
-A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
-A INPUT -s 192.168.1.0/24 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 22 -m state --stat
Quoting SergeiFranco (776...@bugs.launchpad.net):
> One thing I noticed that kernel panic comes much faster if there is network
> activity on the guest. Although I might be wrong...
> Anything else I could do? I will try to run guest without any network
> activity and see if it is panics.
If it
Sorry about that. Could you try doing
apport-cli qemu-kvm
Then when it asks
What would you like to do? Your options are:
S: Send report (813.3 KB)
V: View report
K: Keep report file for sending later or copying to somewhere else
C: Cancel
Please choose (S/V/K/C):
please choose K
