From: Paolo Bonzini <pbonzini@redhat.com>
To: Gerhard Wiesinger <lists@wiesinger.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Kernel Panic on Yum update
Date: Fri, 15 May 2015 08:51:20 +0200 [thread overview]
Message-ID: <55559768.4010104@redhat.com> (raw)
In-Reply-To: <5555937A.40109@wiesinger.com>
On 15/05/2015 08:34, Gerhard Wiesinger wrote:
> Helllo,
>
> I'm using latest qemu-kvm-2.3.0-3.fc21.x86_64 from libvirt repository
> (updated afterwards). Running yum regularly crashes the VM like below.
> VM is stripped down to minimum memory requirements (256MB) for owncloud.
> See below.
>
> Looks like a problem in virtio-net or a kernel bug with low memory
> situations.
You're simply running out of memory. Yum can be a memory hog.
Paolo
> Any ideas?
>
> Thank you.
>
> Ciao,
> Gerhard
>
> http://www.wiesinger.com/
>
> kernel: swapper/0: page allocation failure: order:0, mode:0x20
> kernel: CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.19.7-200.fc21.x86_64 #1
> kernel: Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS
> 1.8.1-20150414_141626-myhost.mydomain 04/01/2014
> kernel: 0000000000000000 c35c12d2c14e1ce8 ffff88000fc03ac8 ffffffff8176f1f7
> kernel: 0000000000000000 0000000000000020 ffff88000fc03b58 ffffffff811a1c9e
> kernel: 0000000000000000 0000000000000040 ffff880000000000 ffff88000ffcdb28
> kernel: Call Trace:
> kernel: <IRQ> [<ffffffff8176f1f7>] dump_stack+0x45/0x57
> kernel: [<ffffffff811a1c9e>] warn_alloc_failed+0xfe/0x170
> kernel: [<ffffffff811a607a>] __alloc_pages_nodemask+0x7ca/0xb10
> kernel: [<ffffffff81691854>] ? nf_hook_slow+0x84/0x130
> kernel: [<ffffffff816482df>] __alloc_page_frag+0x12f/0x150
> kernel: [<ffffffff8164832f>] __netdev_alloc_frag+0x2f/0x50
> kernel: [<ffffffff8164d446>] __alloc_rx_skb+0xe6/0x110
> kernel: [<ffffffff8164d48f>] __netdev_alloc_skb+0x1f/0x40
> kernel: [<ffffffffa008b125>] page_to_skb+0x65/0x370 [virtio_net]
> kernel: [<ffffffffa008d611>] virtnet_receive+0x2c1/0x980 [virtio_net]
> kernel: [<ffffffffa008dcf1>] virtnet_poll+0x21/0x90 [virtio_net]
> kernel: [<ffffffff8165b6aa>] net_rx_action+0x21a/0x350
> kernel: [<ffffffff810a01ab>] __do_softirq+0x10b/0x2b0
> kernel: [<ffffffff810a0565>] irq_exit+0x125/0x130
> kernel: [<ffffffff81778788>] do_IRQ+0x58/0xf0
> kernel: [<ffffffff8177656d>] common_interrupt+0x6d/0x6d
next prev parent reply other threads:[~2015-05-15 6:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-15 6:34 [Qemu-devel] Kernel Panic on Yum update Gerhard Wiesinger
2015-05-15 6:51 ` Paolo Bonzini [this message]
2015-05-15 7:37 ` Gerhard Wiesinger
2015-05-15 8:10 ` Paolo Bonzini
2015-05-15 14:31 ` Gerhard Wiesinger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55559768.4010104@redhat.com \
--to=pbonzini@redhat.com \
--cc=lists@wiesinger.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.