Reading through comments again I am rather sure this should be in fixed
now.
** Changed in: linux (Ubuntu)
Status: Fix Committed = Fix Released
** Changed in: linux (Ubuntu)
Assignee: Stefan Bader (stefan-bader-canonical) = (unassigned)
--
You received this bug notification because
I have the same problem and kernel 2.6.38-9-server from natty-proposed
does not fix anything. Once I start any kvm guest, the whole machine
hangs after few seconds throwing kernel panic.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
@Adam,
Yours may be the same bug, but may not. Please open a new bug with the
information which Id asked of Sergei, in particular your /proc/cpuinfo,
uname -a, iptables -L, brctl show, and virsh dumpxml and release info
for an affected guest, and any relevant log info from both guest and
host.
Good news! kernel from proposed repositories works. It didn't crash
overnight in bridge mode.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/776936
Title:
Running KVM guest causes
Great, thanks for the info, Sergei.
** Changed in: qemu-kvm (Ubuntu)
Status: New = Invalid
** Changed in: linux (Ubuntu)
Status: New = Fix Committed
** Changed in: linux (Ubuntu)
Importance: Undecided = High
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Stefan
Today I noticed that although I removed the membaloon it didn't stick (possibly
due to panic not syncing the file).
I removed once again membaloon and started the guest with little bit better
results.
The system does not freeze immediately, but it leaves a lot of oopses in the
syslog/dmesg.
I
In nat mode it does not panic.
Having virtual machine in nat mode is piss poor, especially when the
network performance in nat mode is very unreliable (perhaps issue with
MTU? apt-get install gets stuck on 0% [Waiting for headers], wget
google.com also hangs, while I can ping everything fine),
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
Yes, membalooning is enabled right now:
domain type='kvm'
namedeluge/name
uuidde900b25-6dc3-cfd6-4fb1-55c6f9755b00/uuid
memory524288/memory
currentMemory524288/currentMemory
vcpu1/vcpu
os
type arch='i686' machine='pc-0.14'hvm/type
boot dev='hd'/
/os
This problem looks very similar to this: http://www.spinics.net/lists
/linux-net/msg17690.html
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/776936
Title:
Running KVM guest
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
Can you append whatever script you use to set up the iptables rules, so
I can as closely as possible emulate?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/776936
Title:
Running
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
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.
--
You received this bug notification because you are a member
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
I couldn't reproduce this with a simple kvm guest on i386 natty host
(64-bit hardware). I'll try mimicking your networking setup, as one of
you panics suggests a netfilter+bridge issue (though the other did not,
so I'm not optimistic).
--
You received this bug notification because you are a
** Attachment added: apport report
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/776936/+attachment/2113781/+files/apport.qemu-kvm.GeDpUE.apport
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
I ran it while I was watch 'dmesg | tail' and caught glimpse of this:
[91476.783713] [c142fdd0] ? __netif_receive_skb+0x180/0x4e0
[91476.785510] [c14301c2] ? process_backlog+0x92/0x160
[91476.787300] [c14319bd] ? net_rx_action+0x10d/0x200
[91476.789093] [c1056622] ? __do_softirq+0x82/0x170
Highlights of this panic is:
Kernel panic - not syncing: Fatal exception in interrupt
** Attachment added: another panic
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/776936/+attachment/2113916/+files/kvm_panic_002.jpg
--
You received this bug notification because you are a
** Changed in: qemu-kvm (Ubuntu)
Importance: Undecided = Critical
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
(installing an i386 natty desktop in order to try to reproduce)
Could you post your host network configuration? Results of 'brctl
show', 'ip link', 'ufw status' and 'iptables -L' and 'iptables -t nat
-L' (all done as root or under sudo).
--
You received this bug notification because you are a
brctl show
bridge name bridge id STP enabled interfaces
br0 8000.00270e160ec4 no eth1
ip link
1: lo: LOOPBACK,UP,LOWER_UP mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth1:
** Attachment added: dmesg (host)
https://bugs.launchpad.net/bugs/776936/+attachment/2111282/+files/dmesg.host.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/776936
Title:
** Attachment added: panic screen
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/776936/+attachment/2111283/+files/kvm_panic.jpg
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
Thanks for submitting this bug and helping to make Ubuntu better.
In order to give us some more info on your system, could you please run
'apport-collect 776936'?
I wonder whether disable KSM and memballoon might help. Could you
disable memballoon by doing
virsh edit deluge
and deleting
I am trying to apport-collect 776936 and I get the text mode browser in
terminal, I login and allow access, then what? Little bit confusing, and
I could not find the non-disruptive way to exit the apport-collect
except ctrl+z and kill. I am not sure if it even did anything.
--
You received this
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
27 matches
Mail list logo
