On Fri, 20 Mar 2015 12:21:37 +
Igor Mammedov imamm...@redhat.com wrote:
KVM guest can fail to startup with following trace on host:
qemu-system-x86: page allocation failure: order:4, mode:0x40d0
Call Trace:
dump_stack+0x47/0x67
warn_alloc_failed+0xee/0x150
KVM guest can fail to startup with following trace on host:
qemu-system-x86: page allocation failure: order:4, mode:0x40d0
Call Trace:
dump_stack+0x47/0x67
warn_alloc_failed+0xee/0x150
__alloc_pages_direct_compact+0x14a/0x150
__alloc_pages_nodemask+0x776/0xb80
alloc_kmem_pages+0x3a
KVM guest can fail to startup with following trace on host:
qemu-system-x86: page allocation failure: order:4, mode:0x40d0
Call Trace:
dump_stack+0x47/0x67
warn_alloc_failed+0xee/0x150
__alloc_pages_direct_compact+0x14a/0x150
__alloc_pages_nodemask+0x776/0xb80
alloc_kmem_pages+0x3a
On Fri, Mar 20, 2015 at 09:51:26AM +, Igor Mammedov wrote:
KVM guest can fail to startup with following trace on host:
qemu-system-x86: page allocation failure: order:4, mode:0x40d0
Call Trace:
dump_stack+0x47/0x67
warn_alloc_failed+0xee/0x150
__alloc_pages_direct_compact+0x14a
On Fri, 20 Mar 2015 08:59:03 -0300
Marcelo Tosatti mtosa...@redhat.com wrote:
On Fri, Mar 20, 2015 at 09:51:26AM +, Igor Mammedov wrote:
KVM guest can fail to startup with following trace on host:
qemu-system-x86: page allocation failure: order:4, mode:0x40d0
Call Trace
https://bugzilla.kernel.org/show_bug.cgi?id=30042
Alan a...@lxorguk.ukuu.org.uk changed:
What|Removed |Added
Status|NEW |RESOLVED
https://bugzilla.kernel.org/show_bug.cgi?id=30042
Avi Kivity a...@redhat.com changed:
What|Removed |Added
CC||a...@redhat.com
---
https://bugzilla.kernel.org/show_bug.cgi?id=30042
--- Comment #2 from Peter Merhaut kernelbug_...@russenmafia.at 2011-02-28
11:47:51 ---
uh i should add that the file rtorrent hashes is on a nfs filesystem. so this
generates a lot of network traffic. between the host (which also serves as
https://bugzilla.kernel.org/show_bug.cgi?id=30042
Summary: page allocation failure when using jumbo frames with
kvm guests
Product: Virtualization
Version: unspecified
Kernel Version: 2.6.35
Platform: All
OS/Version: Linux
allocation failure. order:0, mode:0x20
[ 1392.030910] Pid: 407, comm: rpciod/0 Not tainted 2.6.32-gentoo-r5 #1
[ 1392.030912] Call Trace:
[ 1392.030915] IRQ [8109cf2f]
__alloc_pages_nodemask+0x5ad/0x5fa
[ 1392.030986] [81028fdc] ? default_spin_lock_flags+0x9/0xd
[ 1392.031008
Am Tue, 06 Apr 2010 14:15:10 +0200 schrieb kvm:
Hi,
running kernel 2.6.32 (kvm 0.12.3) in host and 2.6.30 in guest (using
Gentoo) works fine. Now I've upgraded several guests to 2.6.32 too and
have had no problems so far. But with one guest after 2-3 hours the
guest hangs and I always get
Thanks! I'll try a new kernel. Interestingly two guests with 2.6.32-r3
(Gentoo naming not rc3) with much more NFS traffic don't show
this behavior of 2.6.32-r5. So I'll try 2.6.32-r8. I've found
some threads with NFS and kernel 2.6.32.x related problems
which seems to be fixed in later versions.
Avi Kivity schrieb:
Tomasz Chmielewski wrote:
I'm trying to use ballooning with kvm-83.
Although I'm able to limit the guest's memory, when I try to increase
it right after that, I get vballoon: page allocation failure.
order:0 followed by a kernel panic.
Is it expected?
The guest
Tomasz Chmielewski wrote:
BTW, is it possible to balloon to a bigger amount of memory that
what was available when the guest started?
No. The guest won't have its data structures set up to handle the extra
memory.
Or is it only possible to shrink and grow within initial memory
I'm trying to use ballooning with kvm-83.
Although I'm able to limit the guest's memory, when I try to increase it right after
that, I get vballoon: page allocation failure. order:0 followed by a kernel
panic.
Is it expected?
The guest is running Debian Lenny with 2.6.26 kernel. It had
Tomasz Chmielewski wrote:
I'm trying to use ballooning with kvm-83.
Although I'm able to limit the guest's memory, when I try to increase
it right after that, I get vballoon: page allocation failure.
order:0 followed by a kernel panic.
Is it expected?
The guest is running Debian Lenny
16 matches
Mail list logo