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
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),
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
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
** 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
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:
Public bug reported:
Binary package hint: qemu-kvm
as per http://ubuntuforums.org/showthread.php?p=10766552#post10766552
Host machine Ubuntu Natty server 2.6.38-8-generic i686
Guest machine Ubuntu Natty server 2.6.38-8-generic i686
Panic occurs in range of minutes to hours of uptime. It is
** 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.
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
15 matches
Mail list logo