* [BUG] invocation of xl create with insufficient memory for new domU causes system reboot
@ 2014-04-01 9:35 Georgy V. Repin
2014-04-01 9:52 ` Ian Campbell
0 siblings, 1 reply; 9+ messages in thread
From: Georgy V. Repin @ 2014-04-01 9:35 UTC (permalink / raw)
To: xen-devel
Hello!
1. Problem: invocation of xl create when there is not enough memory to
create new domU causes oom to select process to kiill; when oom selects
to kill quemu-system-* process, this causes kernel panic (it's my
suppose, because i see no message "kernel panic" in log, but i do see
"CPU: 0 PID: 7899 Comm: qemu-system-i38 Not tainted 3.10.17-gentoo #1" +
failed call trace), and, therefore (assuming default settings) kernel
reboot (see log at "4.")
Couple of remarks:
- fix checking of available memory for new domU in xl toolstack could
serve as workaround
- real cause is not clear to me, maybe it's not even a xen bug (quemu ?
kernel ?)
2. system information (kernel, glibc, etc.; unneccessary information
omiitted):
informika-xen-3 ~ # emerge --info
Portage 2.2.7 (default/linux/amd64/13.0, gcc-4.7.3, glibc-2.16.0,
3.10.17-gentoo x86_64)
=================================================================
System uname:
Linux-3.10.17-gentoo-x86_64-Intel-R-_Xeon-R-_CPU_E5620_@_2.40GHz-with-gentoo-2.2
KiB Mem: 11274196 total, 10784164 free
KiB Swap: 976892 total, 976892 free
ld GNU ld (GNU Binutils) 2.23.1
app-shells/bash: 4.2_p45
dev-lang/python: 2.7.5-r3, 3.2.5-r3, 3.3.2-r2
dev-util/cmake: 2.8.11.2
dev-util/pkgconfig: 0.28
sys-apps/baselayout: 2.2
sys-apps/openrc: 0.12.4
sys-apps/sandbox: 2.6-r1
sys-devel/autoconf: 2.69
sys-devel/automake: 1.13.4
sys-devel/binutils: 2.23.1
sys-devel/gcc: 4.7.3-r1
sys-devel/gcc-config: 1.7.3
sys-devel/libtool: 2.4.2
sys-devel/make: 3.82-r4
sys-kernel/linux-headers: 3.9 (virtual/os-headers)
sys-libs/glibc: 2.16.0
Repositories: gentoo
ACCEPT_KEYWORDS="amd64"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-O2 -march=core2 -pipe -fomit-frame-pointer
-mno-tls-direct-seg-refs"
CHOST="x86_64-pc-linux-gnu"
CXXFLAGS="-O2 -march=core2 -pipe -fomit-frame-pointer
-mno-tls-direct-seg-refs"
FCFLAGS="-O2 -pipe"
FFLAGS="-O2 -pipe"
LANG="ru_RU.utf8"
LC_ALL="ru_RU.utf8"
LDFLAGS="-Wl,-O1 -Wl,--as-needed"
MAKEOPTS="-j1"
3. xen information:
informika-xen-3 ~ # emerge -pv xen xen-tools
[ebuild R ] app-emulation/xen-tools-4.3.1-r3 USE="hvm pam pygrub
python qemu -api -custom-cflags -debug -doc -flask -ocaml -screen
-static-libs -xend" PYTHON_SINGLE_TARGET="python2_7 -python2_6"
PYTHON_TARGETS="python2_7 -python2_6" 0 kB
[ebuild R ~] app-emulation/xen-4.3.1-r2 USE="-custom-cflags -debug
-efi -flask -xsm" 0 kB
4. part of /var/log/messages
Apr 1 11:07:55 informika-xen-3 kernel: [1093415.268719] Node 0
hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=2048kB
Apr 1 11:07:55 informika-xen-3 kernel: [1093415.268720] 2830 total
pagecache pages
Apr 1 11:07:55 informika-xen-3 kernel: [1093415.268722] 2499 pages in
swap cache
Apr 1 11:07:55 informika-xen-3 kernel: [1093415.268723] Swap cache
stats: add 3364, delete 865, find 0/0
Apr 1 11:07:55 informika-xen-3 kernel: [1093415.268725] Free swap =
963436kB
Apr 1 11:07:55 informika-xen-3 kernel: [1093415.268726] Total swap =
976892kB
Apr 1 11:07:55 informika-xen-3 kernel: [1093415.331703] 6291455 pages RAM
Apr 1 11:07:55 informika-xen-3 kernel: [1093415.331707] 248055 pages
reserved
Apr 1 11:07:55 informika-xen-3 kernel: [1093415.331709] 262298 pages shared
Apr 1 11:07:55 informika-xen-3 kernel: [1093415.331710] 6011909 pages
non-shared
Apr 1 11:07:55 informika-xen-3 kernel: [1093415.331712] [ pid ] uid
tgid total_vm rss nr_ptes swapents oom_score_adj name
Apr 1 11:07:55 informika-xen-3 kernel: [1093415.331738] [ 1774] 0
1774 8990 39 20 82 -1000 udevd
Apr 1 11:07:55 informika-xen-3 kernel: [1093415.331743] [ 2697] 0
2697 6270 13 16 46 0 syslog-ng
Apr 1 11:07:55 informika-xen-3 kernel: [1093415.331746] [ 2698] 0
2698 86549 72 36 306 0 syslog-ng
Apr 1 11:07:55 informika-xen-3 kernel: [1093415.331749] [ 5870] 0
5870 2735 17 11 114 0 xenstored
Apr 1 11:07:55 informika-xen-3 kernel: [1093415.331752] [ 5954] 0
5954 5489 0 16 48 0 fcron
Apr 1 11:07:55 informika-xen-3 kernel: [1093415.331755] [ 5998] 0
5998 8010 13 20 106 -1000 sshd
Apr 1 11:07:55 informika-xen-3 kernel: [1093415.331757] [ 6019] 0
6019 22721 2 19 58 0 xenconsoled
Apr 1 11:07:55 informika-xen-3 kernel: [1093415.331760] [ 6194] 101
6194 2956 2 11 41 0 zabbix_agentd
Apr 1 11:07:55 informika-xen-3 kernel: [1093415.331763] [ 6199] 101
6199 2956 245 11 41 0 zabbix_agentd
Apr 1 11:07:55 informika-xen-3 kernel: [1093415.331765] [ 6200] 101
6200 2956 21 11 47 0 zabbix_agentd
Apr 1 11:07:55 informika-xen-3 kernel: [1093415.331767] [ 6201] 101
6201 2956 21 11 47 0 zabbix_agentd
Apr 1 11:07:55 informika-xen-3 kernel: [1093415.331770] [ 6202] 101
6202 2956 21 11 47 0 zabbix_agentd
Apr 1 11:07:55 informika-xen-3 kernel: [1093415.331772] [ 6203] 101
6203 2956 22 11 46 0 zabbix_agentd
Apr 1 11:07:55 informika-xen-3 kernel: [1093415.331774] [ 6204] 101
6204 2956 21 11 47 0 zabbix_agentd
Apr 1 11:07:55 informika-xen-3 kernel: [1093415.331777] [ 6246] 0
6246 3864 1 13 39 0 agetty
Apr 1 11:07:55 informika-xen-3 kernel: [1093415.331780] [ 6247] 0
6247 3864 1 13 39 0 agetty
Apr 1 11:07:55 informika-xen-3 kernel: [1093415.331782] [ 6248] 0
6248 3864 1 13 39 0 agetty
Apr 1 11:07:55 informika-xen-3 kernel: [1093415.331784] [ 6249] 0
6249 3864 1 13 39 0 agetty
Apr 1 11:07:55 informika-xen-3 kernel: [1093415.331786] [ 6251] 0
6251 3864 1 13 40 0 agetty
Apr 1 11:07:55 informika-xen-3 kernel: [1093415.331791] [13742] 0
13742 25534 0 25 127 0 xl
Apr 1 11:07:55 informika-xen-3 kernel: [1093415.331795] [13945] 0
13945 32183 4788 36 1986 0 xl
Apr 1 11:07:55 informika-xen-3 kernel: [1093415.331799] [ 7899] 0
7899 59868 2136 53 529 0 qemu-system-i38
Apr 1 11:07:55 informika-xen-3 kernel: [1093415.331802] [ 7989] 0
7989 25534 16 23 112 0 xl
Apr 1 11:07:55 informika-xen-3 kernel: [1093415.331807] [10154] 0
10154 30647 5233 34 0 0 xl
Apr 1 11:07:55 informika-xen-3 kernel: [1093415.331810] [22644] 0
22644 73518 1867 63 0 0 qemu-system-i38
Apr 1 11:07:55 informika-xen-3 kernel: [1093415.331827] [22807] 0
22807 25538 127 23 0 0 xl
Apr 1 11:07:55 informika-xen-3 kernel: [1093415.331831] [10075] 0
10075 18016 190 40 0 0 sshd
Apr 1 11:07:55 informika-xen-3 kernel: [1093415.331834] [10079] 0
10079 5811 138 16 0 0 bash
Apr 1 11:07:55 informika-xen-3 kernel: [1093415.331838] [10822] 0
10822 3864 40 13 0 0 agetty
Apr 1 11:07:55 informika-xen-3 kernel: [1093415.331842] [12178] 0
12178 9142 71 24 0 0 xl
Apr 1 11:07:55 informika-xen-3 kernel: [1093415.331845] Out of memory:
Kill process 6199 (zabbix_agentd) score 0 or sacrifice child
Apr 1 11:07:55 informika-xen-3 kernel: [1093415.331847] Killed process
6199 (zabbix_agentd) total-vm:11824kB, anon-rss:0kB, file-rss:980kB
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346289] qemu-system-i38
invoked oom-killer: gfp_mask=0x201da, order=0, oom_score_adj=0
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346294] qemu-system-i38
cpuset=/ mems_allowed=0
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346297] CPU: 0 PID:
7899 Comm: qemu-system-i38 Not tainted 3.10.17-gentoo #1
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346299] Hardware name:
FUJITSU PRIMERGY RX300 S6 /D2619,
BIOS 6.00 Rev. 1.13.2619.N1 01/19/2012
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346301]
0000000000000000 ffff8801c6f6b748 ffffffff81969d9b ffff8801c6f6b7c8
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346304]
ffffffff81964922 ffff8801c6f6b768 ffffffff810081f9 0000000000000200
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346307]
ffff8806010404c8 ffffffff81971cc9 0000000081c67ce0 ffff8801c6f6b7c8
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346310] Call Trace:
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346317]
[<ffffffff81969d9b>] dump_stack+0x19/0x1b
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346321]
[<ffffffff81964922>] dump_header.isra.7+0x76/0x1aa
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346327]
[<ffffffff810081f9>] ? xen_clocksource_get_cycles+0x9/0x10
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346331]
[<ffffffff81971cc9>] ? _raw_spin_unlock_irqrestore+0x19/0x20
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346335]
[<ffffffff81478123>] ? ___ratelimit+0xa3/0x120
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346339]
[<ffffffff810ca377>] oom_kill_process+0x1b7/0x320
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346343]
[<ffffffff81438780>] ? security_capable_noaudit+0x10/0x20
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346347]
[<ffffffff8105e450>] ? has_ns_capability_noaudit+0x10/0x20
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346350]
[<ffffffff8105e472>] ? has_capability_noaudit+0x12/0x20
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346352]
[<ffffffff810caaa5>] out_of_memory+0x415/0x450
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346356]
[<ffffffff810cfa15>] __alloc_pages_nodemask+0x955/0x970
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346361]
[<ffffffff81102da7>] alloc_pages_current+0xb7/0x180
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346363]
[<ffffffff810c7587>] __page_cache_alloc+0xa7/0xc0
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346366]
[<ffffffff810c952a>] filemap_fault+0x27a/0x430
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346369]
[<ffffffff810e5c3c>] __do_fault+0x6c/0x490
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346373]
[<ffffffff81121b10>] ? __pollwait+0xf0/0xf0
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346375]
[<ffffffff810e8a5f>] handle_pte_fault+0x8f/0x860
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346378]
[<ffffffff810074e0>] ? pte_mfn_to_pfn+0x70/0x100
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346380]
[<ffffffff81007589>] ? xen_pmd_val+0x9/0x10
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346383]
[<ffffffff81004859>] ? __raw_callee_save_xen_pmd_val+0x11/0x1e
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346386]
[<ffffffff810e9574>] handle_mm_fault+0x144/0x210
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346389]
[<ffffffff8103d499>] __do_page_fault+0x159/0x4c0
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346392]
[<ffffffff810e8a5f>] ? handle_pte_fault+0x8f/0x860
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346394]
[<ffffffff810074e0>] ? pte_mfn_to_pfn+0x70/0x100
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346397]
[<ffffffff81061f4a>] ? recalc_sigpending+0x1a/0x60
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346400]
[<ffffffff8103d829>] do_page_fault+0x9/0x10
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346403]
[<ffffffff81972558>] page_fault+0x28/0x30
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346406]
[<ffffffff8147d9a0>] ? copy_user_generic_string+0x30/0x40
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346410]
[<ffffffff811518c0>] ? eventfd_write+0x60/0x210
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346413]
[<ffffffff8107f720>] ? try_to_wake_up+0x290/0x290
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346417]
[<ffffffff8110ff60>] vfs_write+0xc0/0x1e0
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346420]
[<ffffffff8111042d>] SyS_write+0x4d/0x90
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346422]
[<ffffffff8103d829>] ? do_page_fault+0x9/0x10
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346425]
[<ffffffff81972b2d>] system_call_fastpath+0x1a/0x1f
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346427] Mem-Info:
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346428] Node 0 DMA per-cpu:
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346430] CPU 0: hi:
0, btch: 1 usd: 0
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346432] CPU 1: hi:
0, btch: 1 usd: 0
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346433] CPU 2: hi:
0, btch: 1 usd: 0
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346435] CPU 3: hi:
0, btch: 1 usd: 0
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346436] CPU 4: hi:
0, btch: 1 usd: 0
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346438] CPU 5: hi:
0, btch: 1 usd: 0
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346439] CPU 6: hi:
0, btch: 1 usd: 0
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346440] CPU 7: hi:
0, btch: 1 usd: 0
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346442] CPU 8: hi:
0, btch: 1 usd: 0
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346443] CPU 9: hi:
0, btch: 1 usd: 0
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346445] CPU 10: hi:
0, btch: 1 usd: 0
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346446] CPU 11: hi:
0, btch: 1 usd: 0
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346448] CPU 12: hi:
0, btch: 1 usd: 0
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346449] CPU 13: hi:
0, btch: 1 usd: 0
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346451] CPU 14: hi:
0, btch: 1 usd: 0
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346452] CPU 15: hi:
0, btch: 1 usd: 0
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346453] Node 0 DMA32
per-cpu:
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346455] CPU 0: hi:
186, btch: 31 usd: 0
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346457] CPU 1: hi:
186, btch: 31 usd: 0
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346458] CPU 2: hi:
186, btch: 31 usd: 31
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346460] CPU 3: hi:
186, btch: 31 usd: 0
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346461] CPU 4: hi:
186, btch: 31 usd: 0
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346463] CPU 5: hi:
186, btch: 31 usd: 0
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346464] CPU 6: hi:
186, btch: 31 usd: 0
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346466] CPU 7: hi:
186, btch: 31 usd: 0
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346467] CPU 8: hi:
186, btch: 31 usd: 0
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346468] CPU 9: hi:
186, btch: 31 usd: 0
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346470] CPU 10: hi:
186, btch: 31 usd: 0
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346471] CPU 11: hi:
186, btch: 31 usd: 0
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346473] CPU 12: hi:
186, btch: 31 usd: 0
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346474] CPU 13: hi:
186, btch: 31 usd: 0
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346476] CPU 14: hi:
186, btch: 31 usd: 0
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346477] CPU 15: hi:
186, btch: 31 usd: 0
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346478] Node 0 Normal
per-cpu:
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346480] CPU 0: hi:
186, btch: 31 usd: 1
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346482] CPU 1: hi:
186, btch: 31 usd: 0
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346483] CPU 2: hi:
186, btch: 31 usd: 32
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346485] CPU 3: hi:
186, btch: 31 usd: 0
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346486] CPU 4: hi:
186, btch: 31 usd: 0
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346487] CPU 5: hi:
186, btch: 31 usd: 0
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346489] CPU 6: hi:
186, btch: 31 usd: 0
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346490] CPU 7: hi:
186, btch: 31 usd: 0
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346492] CPU 8: hi:
186, btch: 31 usd: 0
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346493] CPU 9: hi:
186, btch: 31 usd: 0
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346495] CPU 10: hi:
186, btch: 31 usd: 0
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346496] CPU 11: hi:
186, btch: 31 usd: 0
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346497] CPU 12: hi:
186, btch: 31 usd: 0
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346499] CPU 13: hi:
186, btch: 31 usd: 0
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346500] CPU 14: hi:
186, btch: 31 usd: 0
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346502] CPU 15: hi:
186, btch: 31 usd: 0
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346506]
active_anon:11736 inactive_anon:1457 isolated_anon:0
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346506] active_file:26
inactive_file:0 isolated_file:0
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346506] unevictable:20
dirty:6 writeback:32 unstable:0
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346506] free:29431
slab_reclaimable:3545 slab_unreclaimable:7726
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346506] mapped:153
shmem:255 pagetables:583 bounce:0
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346506] free_cma:0
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346509] Node 0 DMA
free:15880kB min:12kB low:12kB high:16kB active_anon:0kB
inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB
isolated(anon):0kB isolated(file):0kB present:15980kB managed:15896kB
mlocked:0kB dirty:0kB writeback:0kB mapped:0kB shmem:0kB
slab_reclaimable:0kB slab_unreclaimable:16kB kernel_stack:0kB
pagetables:0kB unstable:0kB bounce:0kB free_cma:0kB writeback_tmp:0kB
pages_scanned:0 all_unreclaimable? yes
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346514]
lowmem_reserve[]: 0 3031 23590 23590
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346517] Node 0 DMA32
free:84760kB min:2524kB low:3152kB high:3784kB active_anon:11888kB
inactive_anon:3052kB active_file:4kB inactive_file:0kB unevictable:0kB
isolated(anon):0kB isolated(file):0kB present:3119808kB
managed:3104116kB mlocked:0kB dirty:4kB writeback:20kB mapped:256kB
shmem:0kB slab_reclaimable:1100kB slab_unreclaimable:2096kB
kernel_stack:40kB pagetables:44kB unstable:0kB bounce:0kB free_cma:0kB
writeback_tmp:0kB pages_scanned:23661 all_unreclaimable? yes
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346522]
lowmem_reserve[]: 0 0 20559 20559
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346525] Node 0 Normal
free:17084kB min:17124kB low:21404kB high:25684kB active_anon:35056kB
inactive_anon:2776kB active_file:100kB inactive_file:0kB
unevictable:80kB isolated(anon):0kB isolated(file):0kB
present:22020096kB managed:21052500kB mlocked:80kB dirty:20kB
writeback:108kB mapped:356kB shmem:1020kB slab_reclaimable:13080kB
slab_unreclaimable:28792kB kernel_stack:2160kB pagetables:2288kB
unstable:0kB bounce:0kB free_cma:0kB writeback_tmp:0kB
pages_scanned:57027 all_unreclaimable? yes
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346530]
lowmem_reserve[]: 0 0 0 0
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346533] Node 0 DMA:
0*4kB 1*8kB (U) 0*16kB 0*32kB 2*64kB (U) 1*128kB (U) 1*256kB (U) 0*512kB
1*1024kB (U) 1*2048kB (R) 3*4096kB (M) = 15880kB
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346544] Node 0 DMA32:
103*4kB (UEM) 83*8kB (UEM) 64*16kB (UEM) 80*32kB (EM) 64*64kB (M)
48*128kB (M) 30*256kB (M) 20*512kB (M) 15*1024kB (M) 16*2048kB (UM)
1*4096kB (R) = 85044kB
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346557] Node 0 Normal:
3459*4kB (UM) 29*8kB (UM) 8*16kB (UM) 1*32kB (R) 1*64kB (R) 1*128kB (R)
1*256kB (R) 1*512kB (R) 1*1024kB (R) 1*2048kB (R) 0*4096kB = 18260kB
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346570] Node 0
hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=2048kB
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346571] 1832 total
pagecache pages
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346572] 1514 pages in
swap cache
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346574] Swap cache
stats: add 7822, delete 6308, find 220/245
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346575] Free swap =
947036kB
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.346576] Total swap =
976892kB
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.398205] 6291455 pages RAM
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.398209] 248055 pages
reserved
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.398210] 262437 pages shared
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.398211] 6012368 pages
non-shared
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.398212] [ pid ] uid
tgid total_vm rss nr_ptes swapents oom_score_adj name
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.398229] [ 1774] 0
1774 8990 37 20 84 -1000 udevd
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.398233] [ 2697] 0
2697 6270 13 16 46 0 syslog-ng
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.398236] [ 2698] 0
2698 86549 132 36 299 0 syslog-ng
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.398239] [ 5870] 0
5870 2735 2 11 129 0 xenstored
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.398241] [ 5954] 0
5954 5489 0 16 48 0 fcron
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.398244] [ 5998] 0
5998 8010 13 20 106 -1000 sshd
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.398246] [ 6019] 0
6019 22721 2 19 58 0 xenconsoled
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.398248] [ 6194] 101
6194 2956 19 11 22 0 zabbix_agentd
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.398252] [ 6246] 0
6246 3864 1 13 39 0 agetty
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.398254] [ 6247] 0
6247 3864 1 13 39 0 agetty
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.398256] [ 6248] 0
6248 3864 1 13 39 0 agetty
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.398259] [ 6249] 0
6249 3864 1 13 39 0 agetty
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.398261] [ 6251] 0
6251 3864 1 13 40 0 agetty
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.398264] [13742] 0
13742 25534 0 25 127 0 xl
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.398267] [13945] 0
13945 32183 2331 36 4443 0 xl
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.398270] [ 7899] 0
7899 59868 15 53 2666 0 qemu-system-i38
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.398273] [ 7989] 0
7989 25534 0 23 128 0 xl
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.398277] [10154] 0
10154 30647 5200 34 33 0 xl
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.398279] [22644] 0
22644 73518 1866 63 0 0 qemu-system-i38
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.398282] [22807] 0
22807 25538 127 23 0 0 xl
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.398284] [10075] 0
10075 18016 190 40 0 0 sshd
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.398287] [10079] 0
10079 5811 138 16 0 0 bash
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.398290] [10822] 0
10822 3864 40 13 0 0 agetty
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.398292] [12178] 0
12178 9142 74 24 0 0 xl
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.398295] Out of memory:
Kill process 6194 (zabbix_agentd) score 0 or sacrifice child
Apr 1 11:07:57 informika-xen-3 kernel: [1093417.398297] Killed process
6194 (zabbix_agentd) total-vm:11824kB, anon-rss:76kB, file-rss:0kB
Apr 1 11:10:48 informika-xen-3 syslog-ng[2689]: syslog-ng starting up;
version='3.4.2'
Apr 1 11:10:48 kernel: [ 0.000000] Initializing cgroup subsys cpuset
--
Georgy V. Repin
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [BUG] invocation of xl create with insufficient memory for new domU causes system reboot
2014-04-01 9:35 [BUG] invocation of xl create with insufficient memory for new domU causes system reboot Georgy V. Repin
@ 2014-04-01 9:52 ` Ian Campbell
2014-04-01 10:17 ` Georgy V. Repin
0 siblings, 1 reply; 9+ messages in thread
From: Ian Campbell @ 2014-04-01 9:52 UTC (permalink / raw)
To: Georgy V. Repin; +Cc: xen-devel
On Tue, 2014-04-01 at 13:35 +0400, Georgy V. Repin wrote:
> Hello!
>
> 1. Problem: invocation of xl create when there is not enough memory to
> create new domU causes oom to select process to kiill; when oom selects
> to kill quemu-system-* process, this causes kernel panic (it's my
> suppose, because i see no message "kernel panic" in log, but i do see
> "CPU: 0 PID: 7899 Comm: qemu-system-i38 Not tainted 3.10.17-gentoo #1" +
> failed call trace), and, therefore (assuming default settings) kernel
> reboot (see log at "4.")
> Couple of remarks:
> - fix checking of available memory for new domU in xl toolstack could
> serve as workaround
> - real cause is not clear to me, maybe it's not even a xen bug (quemu ?
> kernel ?)
Are you using dom0_mem= together with auto ballooning enabled in the
toolstack?
I think it was Xen 4.4 which gained the ability to detect dom0_mem= and
disable ballooning automatically in that case, but I might be
misremembering.
Ian.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [BUG] invocation of xl create with insufficient memory for new domU causes system reboot
2014-04-01 9:52 ` Ian Campbell
@ 2014-04-01 10:17 ` Georgy V. Repin
2014-04-02 5:47 ` Georgy V. Repin
2014-04-02 9:30 ` Ian Campbell
0 siblings, 2 replies; 9+ messages in thread
From: Georgy V. Repin @ 2014-04-01 10:17 UTC (permalink / raw)
To: Ian Campbell; +Cc: xen-devel
01.04.2014 13:52, Ian Campbell пишет:
> On Tue, 2014-04-01 at 13:35 +0400, Georgy V. Repin wrote:
>> Hello!
>>
>> 1. Problem: invocation of xl create when there is not enough memory to
>> create new domU causes oom to select process to kiill; when oom selects
>> to kill quemu-system-* process, this causes kernel panic (it's my
>> suppose, because i see no message "kernel panic" in log, but i do see
>> "CPU: 0 PID: 7899 Comm: qemu-system-i38 Not tainted 3.10.17-gentoo #1" +
>> failed call trace), and, therefore (assuming default settings) kernel
>> reboot (see log at "4.")
>> Couple of remarks:
>> - fix checking of available memory for new domU in xl toolstack could
>> serve as workaround
>> - real cause is not clear to me, maybe it's not even a xen bug (quemu ?
>> kernel ?)
>
> Are you using dom0_mem= together with auto ballooning enabled in the
> toolstack?
informika-xen-3 ~ # cat /proc/cmdline
placeholder root=/dev/sda1 ro
part of grub.cfg
if [ "$grub_platform" = "pc" -o "$grub_platform" = "" ]; then
xen_rm_opts=
else
xen_rm_opts="no-real-mode edd=off"
fi
multiboot /boot/xen-4.gz placeholder ${xen_rm_opts}
echo 'Loading Linux 3.10.17-gentoo ...'
module /boot/vmlinuz-3.10.17-gentoo placeholder root=/dev/sda1 ro
xl.conf:
# Control whether dom0 is ballooned down when xen doesn't have enough
# free memory to create a domain. "auto" means only balloon if dom0
# starts with all the host's memory.
#autoballoon="auto"
So:
- no dom0_mem= as boot param
- autobaloon is set to default ("auto", i suppose)
>
> I think it was Xen 4.4 which gained the ability to detect dom0_mem= and
> disable ballooning automatically in that case, but I might be
> misremembering.
>
> Ian.
>
--
С уважением,
Георгий Репин
ФГАУ ГНИИ ИТТ "Информика"
http://www.informika.ru
http://www.runnet.ru
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [BUG] invocation of xl create with insufficient memory for new domU causes system reboot
2014-04-01 10:17 ` Georgy V. Repin
@ 2014-04-02 5:47 ` Georgy V. Repin
2014-04-02 9:31 ` Ian Campbell
2014-04-02 9:30 ` Ian Campbell
1 sibling, 1 reply; 9+ messages in thread
From: Georgy V. Repin @ 2014-04-02 5:47 UTC (permalink / raw)
To: xen-devel
01.04.2014 14:17, Georgy V. Repin пишет:
>
> 01.04.2014 13:52, Ian Campbell пишет:
>> On Tue, 2014-04-01 at 13:35 +0400, Georgy V. Repin wrote:
>>> Hello!
>>>
>>> 1. Problem: invocation of xl create when there is not enough memory to
>>> create new domU causes oom to select process to kiill; when oom selects
>>> to kill quemu-system-* process, this causes kernel panic (it's my
>>> suppose, because i see no message "kernel panic" in log, but i do see
>>> "CPU: 0 PID: 7899 Comm: qemu-system-i38 Not tainted 3.10.17-gentoo #1" +
>>> failed call trace), and, therefore (assuming default settings) kernel
>>> reboot (see log at "4.")
>>> Couple of remarks:
>>> - fix checking of available memory for new domU in xl toolstack could
>>> serve as workaround
>>> - real cause is not clear to me, maybe it's not even a xen bug (quemu ?
>>> kernel ?)
>>
>> Are you using dom0_mem= together with auto ballooning enabled in the
>> toolstack?
>
> informika-xen-3 ~ # cat /proc/cmdline
> placeholder root=/dev/sda1 ro
>
> part of grub.cfg
>
> if [ "$grub_platform" = "pc" -o "$grub_platform" = ""
> ]; then
> xen_rm_opts=
> else
> xen_rm_opts="no-real-mode edd=off"
> fi
> multiboot /boot/xen-4.gz placeholder ${xen_rm_opts}
> echo 'Loading Linux 3.10.17-gentoo ...'
> module /boot/vmlinuz-3.10.17-gentoo placeholder
> root=/dev/sda1 ro
>
> xl.conf:
> # Control whether dom0 is ballooned down when xen doesn't have enough
> # free memory to create a domain. "auto" means only balloon if dom0
> # starts with all the host's memory.
> #autoballoon="auto"
>
> So:
> - no dom0_mem= as boot param
> - autobaloon is set to default ("auto", i suppose)
Any other suggestions what to "do" with this "bug" ?
(Captain Obvious definetly says "you should not start new domU when you
don't have enough memory")
>
>>
>> I think it was Xen 4.4 which gained the ability to detect dom0_mem= and
>> disable ballooning automatically in that case, but I might be
>> misremembering.
>>
>> Ian.
>>
>
--
С уважением,
Георгий Репин
ФГАУ ГНИИ ИТТ "Информика"
http://www.informika.ru
http://www.runnet.ru
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [BUG] invocation of xl create with insufficient memory for new domU causes system reboot
2014-04-01 10:17 ` Georgy V. Repin
2014-04-02 5:47 ` Georgy V. Repin
@ 2014-04-02 9:30 ` Ian Campbell
2014-04-02 10:25 ` Georgy V. Repin
1 sibling, 1 reply; 9+ messages in thread
From: Ian Campbell @ 2014-04-02 9:30 UTC (permalink / raw)
To: Georgy V. Repin; +Cc: xen-devel
On Tue, 2014-04-01 at 14:17 +0400, Georgy V. Repin wrote:
> 01.04.2014 13:52, Ian Campbell пишет:
> > On Tue, 2014-04-01 at 13:35 +0400, Georgy V. Repin wrote:
> >> Hello!
> >>
> >> 1. Problem: invocation of xl create when there is not enough memory to
> >> create new domU causes oom to select process to kiill; when oom selects
> >> to kill quemu-system-* process, this causes kernel panic (it's my
> >> suppose, because i see no message "kernel panic" in log, but i do see
> >> "CPU: 0 PID: 7899 Comm: qemu-system-i38 Not tainted 3.10.17-gentoo #1" +
> >> failed call trace), and, therefore (assuming default settings) kernel
> >> reboot (see log at "4.")
> >> Couple of remarks:
> >> - fix checking of available memory for new domU in xl toolstack could
> >> serve as workaround
> >> - real cause is not clear to me, maybe it's not even a xen bug (quemu ?
> >> kernel ?)
> >
> > Are you using dom0_mem= together with auto ballooning enabled in the
> > toolstack?
>
> informika-xen-3 ~ # cat /proc/cmdline
> placeholder root=/dev/sda1 ro
dom0_mem is a hypervisor command line option, not a Linux one. Although
given that you have show autobaloon=auto that is moot since it implies
the automatic functionality was indeed added in the version you have.
>
> part of grub.cfg
>
> if [ "$grub_platform" = "pc" -o "$grub_platform" = "" ]; then
> xen_rm_opts=
> else
> xen_rm_opts="no-real-mode edd=off"
> fi
> multiboot /boot/xen-4.gz placeholder ${xen_rm_opts}
> echo 'Loading Linux 3.10.17-gentoo ...'
> module /boot/vmlinuz-3.10.17-gentoo placeholder root=/dev/sda1 ro
>
> xl.conf:
> # Control whether dom0 is ballooned down when xen doesn't have enough
> # free memory to create a domain. "auto" means only balloon if dom0
> # starts with all the host's memory.
> #autoballoon="auto"
>
> So:
> - no dom0_mem= as boot param
> - autobaloon is set to default ("auto", i suppose)
Correct, the default is auto.
Please can you show us the output of "xl info" and your guest cfg file
as well as the full output of "xl -vvv create $cfg".
Thanks,
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [BUG] invocation of xl create with insufficient memory for new domU causes system reboot
2014-04-02 5:47 ` Georgy V. Repin
@ 2014-04-02 9:31 ` Ian Campbell
0 siblings, 0 replies; 9+ messages in thread
From: Ian Campbell @ 2014-04-02 9:31 UTC (permalink / raw)
To: Georgy V. Repin; +Cc: xen-devel
On Wed, 2014-04-02 at 09:47 +0400, Georgy V. Repin wrote:
> Any other suggestions what to "do" with this "bug" ?
Did you see my reply in
<1396349690.8667.104.camel@kazak.uk.xensource.com> ?
It seems not to have made it to the list for some reason, but you were
explicitly copied too. I guess that copy also didn't arise, something is
really funky with my email at the moment...
Ian/
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [BUG] invocation of xl create with insufficient memory for new domU causes system reboot
2014-04-02 9:30 ` Ian Campbell
@ 2014-04-02 10:25 ` Georgy V. Repin
2014-04-02 10:39 ` Georgy V. Repin
2014-04-02 10:52 ` Ian Campbell
0 siblings, 2 replies; 9+ messages in thread
From: Georgy V. Repin @ 2014-04-02 10:25 UTC (permalink / raw)
To: Ian Campbell; +Cc: xen-devel
02.04.2014 13:30, Ian Campbell пишет:
>
> On Tue, 2014-04-01 at 14:17 +0400, Georgy V. Repin wrote:
>> 01.04.2014 13:52, Ian Campbell пишет:
>>> On Tue, 2014-04-01 at 13:35 +0400, Georgy V. Repin wrote:
>>>> Hello!
>>>>
>>>> 1. Problem: invocation of xl create when there is not enough memory to
>>>> create new domU causes oom to select process to kiill; when oom selects
>>>> to kill quemu-system-* process, this causes kernel panic (it's my
>>>> suppose, because i see no message "kernel panic" in log, but i do see
>>>> "CPU: 0 PID: 7899 Comm: qemu-system-i38 Not tainted 3.10.17-gentoo #1" +
>>>> failed call trace), and, therefore (assuming default settings) kernel
>>>> reboot (see log at "4.")
>>>> Couple of remarks:
>>>> - fix checking of available memory for new domU in xl toolstack could
>>>> serve as workaround
>>>> - real cause is not clear to me, maybe it's not even a xen bug (quemu ?
>>>> kernel ?)
>>>
>>> Are you using dom0_mem= together with auto ballooning enabled in the
>>> toolstack?
>>
>> informika-xen-3 ~ # cat /proc/cmdline
>> placeholder root=/dev/sda1 ro
>
> dom0_mem is a hypervisor command line option, not a Linux one. Although
> given that you have show autobaloon=auto that is moot since it implies
> the automatic functionality was indeed added in the version you have.
>
>>
>> part of grub.cfg
>>
>> if [ "$grub_platform" = "pc" -o "$grub_platform" = "" ]; then
>> xen_rm_opts=
>> else
>> xen_rm_opts="no-real-mode edd=off"
>> fi
>> multiboot /boot/xen-4.gz placeholder ${xen_rm_opts}
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
this code from grub.cfg shows that there is no dom0_mem= parameter for
/boot/xen-4.gz
>> echo 'Loading Linux 3.10.17-gentoo ...'
>> module /boot/vmlinuz-3.10.17-gentoo placeholder root=/dev/sda1 ro
>>
>> xl.conf:
>> # Control whether dom0 is ballooned down when xen doesn't have enough
>> # free memory to create a domain. "auto" means only balloon if dom0
>> # starts with all the host's memory.
>> #autoballoon="auto"
>>
>> So:
>> - no dom0_mem= as boot param
>> - autobaloon is set to default ("auto", i suppose)
>
> Correct, the default is auto.
>
> Please can you show us the output of "xl info" and your guest cfg file
> as well as the full output of "xl -vvv create $cfg".
informika-xen-3 ~ # xl info
host : informika-xen-3
release : 3.10.17-gentoo
version : #1 SMP Sun Dec 8 13:22:31 MSK 2013
machine : x86_64
nr_cpus : 16
max_cpu_id : 15
nr_nodes : 2
cores_per_socket : 4
threads_per_core : 2
cpu_mhz : 2400
hw_caps :
bfebfbff:2c100800:00000000:00003f00:029ee3ff:00000000:00000001:00000000
virt_caps : hvm
total_memory : 24566
free_memory : 418
sharing_freed_memory : 0
sharing_used_memory : 0
outstanding_claims : 0
free_cpus : 0
xen_major : 4
xen_minor : 3
xen_extra : .1
xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler : credit
xen_pagesize : 4096
platform_params : virt_start=0xffff800000000000
xen_changeset :
xen_commandline : placeholder
cc_compiler : x86_64-pc-linux-gnu-gcc (Gentoo 4.7.3-r1 p1.3,
pie-0.5.5) 4.7.3
cc_compile_by :
cc_compile_domain : internal
cc_compile_date : Sun Jan 5 22:39:16 MSK 2014
xend_config_format : 4
remark:
- now there is no oom reaction, because i have reduced memory amount
for one of other domU's (now it's enough memory for all domU's)
- it seems that "xen_commandline" states that there is no "dom0_mem="
option.
informika-xen-3 ~ # xl -vvv create /etc/xen/vm/www.icsit.ru
Parsing config from /etc/xen/vm/www.icsit.ru
libxl: debug: libxl_create.c:1230:do_domain_create: ao 0x24915a0:
create: how=(nil) callback=(nil) poller=0x24903a0
libxl: debug: libxl_device.c:257:libxl__device_disk_set_backend: Disk
vdev=xvda spec.backend=unknown
libxl: debug: libxl_device.c:296:libxl__device_disk_set_backend: Disk
vdev=xvda, using backend phy
libxl: debug: libxl_create.c:675:initiate_domain_create: running bootloader
libxl: debug: libxl_device.c:257:libxl__device_disk_set_backend: Disk
vdev=(null) spec.backend=phy
libxl: debug: libxl.c:2604:libxl__device_disk_local_initiate_attach:
locally attaching PHY disk /dev/storage-a/www.icsit.ru
libxl: debug: libxl_bootloader.c:409:bootloader_disk_attached_cb: Config
bootloader value: pygrub
libxl: debug: libxl_bootloader.c:425:bootloader_disk_attached_cb:
Checking for bootloader in libexec path: /usr/lib64/xen/bin/pygrub
libxl: debug: libxl_create.c:1243:do_domain_create: ao 0x24915a0:
inprogress: poller=0x24903a0, flags=i
libxl: debug: libxl_event.c:559:libxl__ev_xswatch_register: watch
w=0x248f798 wpath=/local/domain/8 token=3/0: register slotnum=3
libxl: debug: libxl_event.c:1737:libxl__ao_progress_report: ao
0x24915a0: progress report: ignored
libxl: debug: libxl_bootloader.c:535:bootloader_gotptys: executing
bootloader: /usr/lib64/xen/bin/pygrub
libxl: debug: libxl_bootloader.c:539:bootloader_gotptys: bootloader
arg: /usr/lib64/xen/bin/pygrub
libxl: debug: libxl_bootloader.c:539:bootloader_gotptys: bootloader
arg: --args=root=/dev/xvda fastboot
libxl: debug: libxl_bootloader.c:539:bootloader_gotptys: bootloader
arg: --output=/var/run/xen/bootloader.8.out
libxl: debug: libxl_bootloader.c:539:bootloader_gotptys: bootloader
arg: --output-format=simple0
libxl: debug: libxl_bootloader.c:539:bootloader_gotptys: bootloader
arg: --output-directory=/var/run/xen/bootloader.8.d
libxl: debug: libxl_bootloader.c:539:bootloader_gotptys: bootloader
arg: /dev/storage-a/www.icsit.ru
libxl: debug: libxl_event.c:503:watchfd_callback: watch w=0x248f798
wpath=/local/domain/8 token=3/0: event epath=/local/domain/8
libxl: debug: libxl_bootloader.c:634:bootloader_finished: bootloader
completed
libxl: debug: libxl_bootloader.c:136:bootloader_result_command:
bootloader output contained kernel
/var/run/xen/bootloader.8.d/boot_kernel.VfLJyd
libxl: debug: libxl_bootloader.c:136:bootloader_result_command:
bootloader output contained ramdisk
/var/run/xen/bootloader.8.d/boot_ramdisk.HBHXnw
libxl: debug: libxl_bootloader.c:136:bootloader_result_command:
bootloader output contained args root=/dev/xvda console=hvc0 ro
root=/dev/xvda fastboot
libxl: debug: libxl_bootloader.c:647:bootloader_finished: bootloader
execution successful
libxl: debug: libxl_event.c:596:libxl__ev_xswatch_deregister: watch
w=0x248f798 wpath=/local/domain/8 token=3/0: deregister slotnum=3
libxl: debug: libxl_numa.c:475:libxl__get_numa_candidate: New best NUMA
placement candidate found: nr_nodes=2, nr_cpus=16, nr_vcpus=65,
free_memkb=2466
libxl: detail: libxl_dom.c:195:numa_place_domain: NUMA placement
candidate with 2 nodes, 16 cpus and 2466 KB free selected
domainbuilder: detail: xc_dom_allocate: cmdline="root=/dev/xvda
console=hvc0 ro root=/dev/xvda fastboot", features="(null)"
libxl: debug: libxl_dom.c:341:libxl__build_pv: pv kernel mapped 1 path
/var/run/xen/bootloader.8.d/boot_kernel.VfLJyd
domainbuilder: detail: xc_dom_kernel_mem: called
domainbuilder: detail: xc_dom_ramdisk_mem: called
domainbuilder: detail: xc_dom_boot_xen_init: ver 4.3, caps
xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p
hvm-3.0-x86_64
domainbuilder: detail: xc_dom_parse_image: called
domainbuilder: detail: xc_dom_find_loader: trying multiboot-binary
loader ...
domainbuilder: detail: loader probe failed
domainbuilder: detail: xc_dom_find_loader: trying Linux bzImage loader ...
domainbuilder: detail: xc_dom_malloc : 18250 kB
domainbuilder: detail: xc_dom_do_gunzip: unzip ok, 0x4b30aa -> 0x11d2aa0
domainbuilder: detail: loader probe OK
xc: detail: elf_parse_binary: phdr: paddr=0x1000000 memsz=0xad6000
xc: detail: elf_parse_binary: phdr: paddr=0x1c00000 memsz=0xe30e0
xc: detail: elf_parse_binary: phdr: paddr=0x1ce4000 memsz=0x143c0
xc: detail: elf_parse_binary: phdr: paddr=0x1cf9000 memsz=0x35f000
xc: detail: elf_parse_binary: memory: 0x1000000 -> 0x2058000
xc: detail: elf_xen_parse_note: GUEST_OS = "linux"
xc: detail: elf_xen_parse_note: GUEST_VERSION = "2.6"
xc: detail: elf_xen_parse_note: XEN_VERSION = "xen-3.0"
xc: detail: elf_xen_parse_note: VIRT_BASE = 0xffffffff80000000
xc: detail: elf_xen_parse_note: ENTRY = 0xffffffff81cf9200
xc: detail: elf_xen_parse_note: HYPERCALL_PAGE = 0xffffffff81001000
xc: detail: elf_xen_parse_note: FEATURES =
"!writable_page_tables|pae_pgdir_above_4gb"
xc: detail: elf_xen_parse_note: PAE_MODE = "yes"
xc: detail: elf_xen_parse_note: LOADER = "generic"
xc: detail: elf_xen_parse_note: unknown xen elf note (0xd)
xc: detail: elf_xen_parse_note: SUSPEND_CANCEL = 0x1
xc: detail: elf_xen_parse_note: HV_START_LOW = 0xffff800000000000
xc: detail: elf_xen_parse_note: PADDR_OFFSET = 0x0
xc: detail: elf_xen_addr_calc_check: addresses:
xc: detail: virt_base = 0xffffffff80000000
xc: detail: elf_paddr_offset = 0x0
xc: detail: virt_offset = 0xffffffff80000000
xc: detail: virt_kstart = 0xffffffff81000000
xc: detail: virt_kend = 0xffffffff82058000
xc: detail: virt_entry = 0xffffffff81cf9200
xc: detail: p2m_base = 0xffffffffffffffff
domainbuilder: detail: xc_dom_parse_elf_kernel: xen-3.0-x86_64:
0xffffffff81000000 -> 0xffffffff82058000
domainbuilder: detail: xc_dom_mem_init: mem 2048 MB, pages 0x80000
pages, 4k each
domainbuilder: detail: xc_dom_mem_init: 0x80000 pages
domainbuilder: detail: xc_dom_boot_mem_init: called
domainbuilder: detail: x86_compat: guest xen-3.0-x86_64, address size 64
domainbuilder: detail: xc_dom_malloc : 4096 kB
domainbuilder: detail: xc_dom_build_image: called
domainbuilder: detail: xc_dom_alloc_segment: kernel :
0xffffffff81000000 -> 0xffffffff82058000 (pfn 0x1000 + 0x1058 pages)
domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn
0x1000+0x1058 at 0x7f9aa40e4000
xc: detail: elf_load_binary: phdr 0 at 0x7f9aa40e4000 -> 0x7f9aa4bba000
xc: detail: elf_load_binary: phdr 1 at 0x7f9aa4ce4000 -> 0x7f9aa4dc70e0
xc: detail: elf_load_binary: phdr 2 at 0x7f9aa4dc8000 -> 0x7f9aa4ddc3c0
xc: detail: elf_load_binary: phdr 3 at 0x7f9aa4ddd000 -> 0x7f9aa4eb6000
domainbuilder: detail: xc_dom_alloc_segment: ramdisk :
0xffffffff82058000 -> 0xffffffff82fa8000 (pfn 0x2058 + 0xf50 pages)
domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn
0x2058+0xf50 at 0x7f9a9f0b0000
domainbuilder: detail: xc_dom_do_gunzip: unzip ok, 0x5c1479 -> 0xf4fa10
domainbuilder: detail: xc_dom_alloc_segment: phys2mach :
0xffffffff82fa8000 -> 0xffffffff833a8000 (pfn 0x2fa8 + 0x400 pages)
domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn
0x2fa8+0x400 at 0x7f9a9ecb0000
domainbuilder: detail: xc_dom_alloc_page : start info :
0xffffffff833a8000 (pfn 0x33a8)
domainbuilder: detail: xc_dom_alloc_page : xenstore :
0xffffffff833a9000 (pfn 0x33a9)
domainbuilder: detail: xc_dom_alloc_page : console :
0xffffffff833aa000 (pfn 0x33aa)
domainbuilder: detail: nr_page_tables: 0x0000ffffffffffff/48:
0xffff000000000000 -> 0xffffffffffffffff, 1 table(s)
domainbuilder: detail: nr_page_tables: 0x0000007fffffffff/39:
0xffffff8000000000 -> 0xffffffffffffffff, 1 table(s)
domainbuilder: detail: nr_page_tables: 0x000000003fffffff/30:
0xffffffff80000000 -> 0xffffffffbfffffff, 1 table(s)
domainbuilder: detail: nr_page_tables: 0x00000000001fffff/21:
0xffffffff80000000 -> 0xffffffff837fffff, 28 table(s)
domainbuilder: detail: xc_dom_alloc_segment: page tables :
0xffffffff833ab000 -> 0xffffffff833ca000 (pfn 0x33ab + 0x1f pages)
domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn
0x33ab+0x1f at 0x7f9aa9696000
domainbuilder: detail: xc_dom_alloc_page : boot stack :
0xffffffff833ca000 (pfn 0x33ca)
domainbuilder: detail: xc_dom_build_image : virt_alloc_end :
0xffffffff833cb000
domainbuilder: detail: xc_dom_build_image : virt_pgtab_end :
0xffffffff83800000
domainbuilder: detail: xc_dom_boot_image: called
domainbuilder: detail: arch_setup_bootearly: doing nothing
domainbuilder: detail: xc_dom_compat_check: supported guest type:
xen-3.0-x86_64 <= matches
domainbuilder: detail: xc_dom_compat_check: supported guest type:
xen-3.0-x86_32p
domainbuilder: detail: xc_dom_compat_check: supported guest type:
hvm-3.0-x86_32
domainbuilder: detail: xc_dom_compat_check: supported guest type:
hvm-3.0-x86_32p
domainbuilder: detail: xc_dom_compat_check: supported guest type:
hvm-3.0-x86_64
domainbuilder: detail: xc_dom_update_guest_p2m: dst 64bit, pages 0x80000
domainbuilder: detail: clear_page: pfn 0x33aa, mfn 0x5d4935
domainbuilder: detail: clear_page: pfn 0x33a9, mfn 0x21c2da
domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn
0x33a8+0x1 at 0x7f9aa9693000
domainbuilder: detail: start_info_x86_64: called
domainbuilder: detail: setup_hypercall_page: vaddr=0xffffffff81001000
pfn=0x1001
domainbuilder: detail: domain builder memory footprint
domainbuilder: detail: allocated
domainbuilder: detail: malloc : 22564 kB
domainbuilder: detail: anon mmap : 0 bytes
domainbuilder: detail: mapped
domainbuilder: detail: file mmap : 0 bytes
domainbuilder: detail: domU mmap : 35 MB
domainbuilder: detail: arch_setup_bootlate: shared_info: pfn 0x0, mfn
0x1f6b9
domainbuilder: detail: shared_info_x86_64: called
domainbuilder: detail: vcpu_x86_64: called
domainbuilder: detail: vcpu_x86_64: cr3: pfn 0x33ab mfn 0x21c2d9
domainbuilder: detail: launch_vm: called, ctxt=0x7fff07610e70
domainbuilder: detail: xc_dom_release: called
libxl: debug: libxl_device.c:257:libxl__device_disk_set_backend: Disk
vdev=xvda spec.backend=phy
libxl: debug: libxl_event.c:559:libxl__ev_xswatch_register: watch
w=0x248dd08 wpath=/local/domain/0/backend/vbd/8/51712/state token=3/1:
register slotnum=3
libxl: debug: libxl_event.c:503:watchfd_callback: watch w=0x248dd08
wpath=/local/domain/0/backend/vbd/8/51712/state token=3/1: event
epath=/local/domain/0/backend/vbd/8/51712/state
libxl: debug: libxl_event.c:647:devstate_watch_callback: backend
/local/domain/0/backend/vbd/8/51712/state wanted state 2 still waiting
state 1
libxl: debug: libxl_event.c:503:watchfd_callback: watch w=0x248dd08
wpath=/local/domain/0/backend/vbd/8/51712/state token=3/1: event
epath=/local/domain/0/backend/vbd/8/51712/state
libxl: debug: libxl_event.c:643:devstate_watch_callback: backend
/local/domain/0/backend/vbd/8/51712/state wanted state 2 ok
libxl: debug: libxl_event.c:596:libxl__ev_xswatch_deregister: watch
w=0x248dd08 wpath=/local/domain/0/backend/vbd/8/51712/state token=3/1:
deregister slotnum=3
libxl: debug: libxl_event.c:608:libxl__ev_xswatch_deregister: watch
w=0x248dd08: deregister unregistered
libxl: debug: libxl_device.c:959:device_hotplug: calling hotplug script:
/etc/xen/scripts/block add
libxl: debug: libxl_event.c:559:libxl__ev_xswatch_register: watch
w=0x248de18 wpath=/local/domain/0/backend/vif/8/0/state token=3/2:
register slotnum=3
libxl: debug: libxl_event.c:503:watchfd_callback: watch w=0x248de18
wpath=/local/domain/0/backend/vif/8/0/state token=3/2: event
epath=/local/domain/0/backend/vif/8/0/state
libxl: debug: libxl_event.c:647:devstate_watch_callback: backend
/local/domain/0/backend/vif/8/0/state wanted state 2 still waiting state 1
libxl: debug: libxl_event.c:503:watchfd_callback: watch w=0x248de18
wpath=/local/domain/0/backend/vif/8/0/state token=3/2: event
epath=/local/domain/0/backend/vif/8/0/state
libxl: debug: libxl_event.c:643:devstate_watch_callback: backend
/local/domain/0/backend/vif/8/0/state wanted state 2 ok
libxl: debug: libxl_event.c:596:libxl__ev_xswatch_deregister: watch
w=0x248de18 wpath=/local/domain/0/backend/vif/8/0/state token=3/2:
deregister slotnum=3
libxl: debug: libxl_event.c:608:libxl__ev_xswatch_deregister: watch
w=0x248de18: deregister unregistered
libxl: debug: libxl_device.c:959:device_hotplug: calling hotplug script:
/etc/xen/scripts/vif-bridge online
libxl: debug: libxl_event.c:1737:libxl__ao_progress_report: ao
0x24915a0: progress report: ignored
libxl: debug: libxl_event.c:1569:libxl__ao_complete: ao 0x24915a0:
complete, rc=0
libxl: debug: libxl_event.c:1541:libxl__ao__destroy: ao 0x24915a0: destroy
Daemon running with PID 6087
xc: debug: hypercall buffer: total allocations:346 total releases:346
xc: debug: hypercall buffer: current allocations:0 maximum allocations:4
xc: debug: hypercall buffer: cache current size:4
xc: debug: hypercall buffer: cache hits:336 misses:4 toobig:6
informika-xen-3 ~ # cat /etc/xen/vm/www.icsit.ru
bootloader = "pygrub"
memory = 2048
vcpus = 2
name = "www.icsit.ru"
vif = [ 'mac=00:16:3E:5A:04:01, bridge=v119, model=e1000' ]
disk = ['phy:/dev/storage-a/www.icsit.ru,xvda,w']
root = "/dev/xvda"
extra = "fastboot"
>
> Thanks,
> Ian.
>
>
>
>
--
Georgy V. Repin
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [BUG] invocation of xl create with insufficient memory for new domU causes system reboot
2014-04-02 10:25 ` Georgy V. Repin
@ 2014-04-02 10:39 ` Georgy V. Repin
2014-04-02 10:52 ` Ian Campbell
1 sibling, 0 replies; 9+ messages in thread
From: Georgy V. Repin @ 2014-04-02 10:39 UTC (permalink / raw)
To: Ian Campbell; +Cc: xen-devel
02.04.2014 14:25, Georgy V. Repin пишет:
> 02.04.2014 13:30, Ian Campbell пишет:
>>
>> On Tue, 2014-04-01 at 14:17 +0400, Georgy V. Repin wrote:
>>> 01.04.2014 13:52, Ian Campbell пишет:
>>>> On Tue, 2014-04-01 at 13:35 +0400, Georgy V. Repin wrote:
>>>>> Hello!
>>>>>
>>>>> 1. Problem: invocation of xl create when there is not enough memory to
>>>>> create new domU causes oom to select process to kiill; when oom
>>>>> selects
>>>>> to kill quemu-system-* process, this causes kernel panic (it's my
>>>>> suppose, because i see no message "kernel panic" in log, but i do see
>>>>> "CPU: 0 PID: 7899 Comm: qemu-system-i38 Not tainted 3.10.17-gentoo
>>>>> #1" +
>>>>> failed call trace), and, therefore (assuming default settings) kernel
>>>>> reboot (see log at "4.")
>>>>> Couple of remarks:
>>>>> - fix checking of available memory for new domU in xl toolstack could
>>>>> serve as workaround
>>>>> - real cause is not clear to me, maybe it's not even a xen bug
>>>>> (quemu ?
>>>>> kernel ?)
>>>>
>>>> Are you using dom0_mem= together with auto ballooning enabled in the
>>>> toolstack?
>>>
>>> informika-xen-3 ~ # cat /proc/cmdline
>>> placeholder root=/dev/sda1 ro
>>
>> dom0_mem is a hypervisor command line option, not a Linux one. Although
>> given that you have show autobaloon=auto that is moot since it implies
>> the automatic functionality was indeed added in the version you have.
>>
>>>
>>> part of grub.cfg
>>>
>>> if [ "$grub_platform" = "pc" -o "$grub_platform" = ""
>>> ]; then
>>> xen_rm_opts=
>>> else
>>> xen_rm_opts="no-real-mode edd=off"
>>> fi
>>> multiboot /boot/xen-4.gz placeholder ${xen_rm_opts}
>
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> this code from grub.cfg shows that there is no dom0_mem= parameter for
> /boot/xen-4.gz
>
>
>>> echo 'Loading Linux 3.10.17-gentoo ...'
>>> module /boot/vmlinuz-3.10.17-gentoo placeholder
>>> root=/dev/sda1 ro
>>>
>>> xl.conf:
>>> # Control whether dom0 is ballooned down when xen doesn't have enough
>>> # free memory to create a domain. "auto" means only balloon if dom0
>>> # starts with all the host's memory.
>>> #autoballoon="auto"
>>>
>>> So:
>>> - no dom0_mem= as boot param
>>> - autobaloon is set to default ("auto", i suppose)
>>
>> Correct, the default is auto.
>>
>> Please can you show us the output of "xl info" and your guest cfg file
>> as well as the full output of "xl -vvv create $cfg".
>
> informika-xen-3 ~ # xl info
> host : informika-xen-3
> release : 3.10.17-gentoo
> version : #1 SMP Sun Dec 8 13:22:31 MSK 2013
> machine : x86_64
> nr_cpus : 16
> max_cpu_id : 15
> nr_nodes : 2
> cores_per_socket : 4
> threads_per_core : 2
> cpu_mhz : 2400
> hw_caps :
> bfebfbff:2c100800:00000000:00003f00:029ee3ff:00000000:00000001:00000000
> virt_caps : hvm
> total_memory : 24566
> free_memory : 418
> sharing_freed_memory : 0
> sharing_used_memory : 0
> outstanding_claims : 0
> free_cpus : 0
> xen_major : 4
> xen_minor : 3
> xen_extra : .1
> xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
> hvm-3.0-x86_32p hvm-3.0-x86_64
> xen_scheduler : credit
> xen_pagesize : 4096
> platform_params : virt_start=0xffff800000000000
> xen_changeset :
> xen_commandline : placeholder
> cc_compiler : x86_64-pc-linux-gnu-gcc (Gentoo 4.7.3-r1 p1.3,
> pie-0.5.5) 4.7.3
> cc_compile_by :
> cc_compile_domain : internal
> cc_compile_date : Sun Jan 5 22:39:16 MSK 2014
> xend_config_format : 4
>
>
> remark:
> - now there is no oom reaction, because i have reduced memory
> amount for one of other domU's (now it's enough memory for all domU's)
> - it seems that "xen_commandline" states that there is no
> "dom0_mem=" option.
>
sorry, now something wrong with my email, i see just part of email i was
intended to send in my "sent" box.
informika-xen-3 ~ # xl -vvv create /etc/xen/vm/www.icsit.ru
Parsing config from /etc/xen/vm/www.icsit.ru
libxl: debug: libxl_create.c:1230:do_domain_create: ao 0x24915a0:
create: how=(nil) callback=(nil) poller=0x24903a0
libxl: debug: libxl_device.c:257:libxl__device_disk_set_backend: Disk
vdev=xvda spec.backend=unknown
libxl: debug: libxl_device.c:296:libxl__device_disk_set_backend: Disk
vdev=xvda, using backend phy
libxl: debug: libxl_create.c:675:initiate_domain_create: running bootloader
libxl: debug: libxl_device.c:257:libxl__device_disk_set_backend: Disk
vdev=(null) spec.backend=phy
libxl: debug: libxl.c:2604:libxl__device_disk_local_initiate_attach:
locally attaching PHY disk /dev/storage-a/www.icsit.ru
libxl: debug: libxl_bootloader.c:409:bootloader_disk_attached_cb: Config
bootloader value: pygrub
libxl: debug: libxl_bootloader.c:425:bootloader_disk_attached_cb:
Checking for bootloader in libexec path: /usr/lib64/xen/bin/pygrub
libxl: debug: libxl_create.c:1243:do_domain_create: ao 0x24915a0:
inprogress: poller=0x24903a0, flags=i
libxl: debug: libxl_event.c:559:libxl__ev_xswatch_register: watch
w=0x248f798 wpath=/local/domain/8 token=3/0: register slotnum=3
libxl: debug: libxl_event.c:1737:libxl__ao_progress_report: ao
0x24915a0: progress report: ignored
libxl: debug: libxl_bootloader.c:535:bootloader_gotptys: executing
bootloader: /usr/lib64/xen/bin/pygrub
libxl: debug: libxl_bootloader.c:539:bootloader_gotptys: bootloader
arg: /usr/lib64/xen/bin/pygrub
libxl: debug: libxl_bootloader.c:539:bootloader_gotptys: bootloader
arg: --args=root=/dev/xvda fastboot
libxl: debug: libxl_bootloader.c:539:bootloader_gotptys: bootloader
arg: --output=/var/run/xen/bootloader.8.out
libxl: debug: libxl_bootloader.c:539:bootloader_gotptys: bootloader
arg: --output-format=simple0
libxl: debug: libxl_bootloader.c:539:bootloader_gotptys: bootloader
arg: --output-directory=/var/run/xen/bootloader.8.d
libxl: debug: libxl_bootloader.c:539:bootloader_gotptys: bootloader
arg: /dev/storage-a/www.icsit.ru
libxl: debug: libxl_event.c:503:watchfd_callback: watch w=0x248f798
wpath=/local/domain/8 token=3/0: event epath=/local/domain/8
libxl: debug: libxl_bootloader.c:634:bootloader_finished: bootloader
completed
libxl: debug: libxl_bootloader.c:136:bootloader_result_command:
bootloader output contained kernel
/var/run/xen/bootloader.8.d/boot_kernel.VfLJyd
libxl: debug: libxl_bootloader.c:136:bootloader_result_command:
bootloader output contained ramdisk
/var/run/xen/bootloader.8.d/boot_ramdisk.HBHXnw
libxl: debug: libxl_bootloader.c:136:bootloader_result_command:
bootloader output contained args root=/dev/xvda console=hvc0 ro
root=/dev/xvda fastboot
libxl: debug: libxl_bootloader.c:647:bootloader_finished: bootloader
execution successful
libxl: debug: libxl_event.c:596:libxl__ev_xswatch_deregister: watch
w=0x248f798 wpath=/local/domain/8 token=3/0: deregister slotnum=3
libxl: debug: libxl_numa.c:475:libxl__get_numa_candidate: New best NUMA
placement candidate found: nr_nodes=2, nr_cpus=16, nr_vcpus=65,
free_memkb=2466
libxl: detail: libxl_dom.c:195:numa_place_domain: NUMA placement
candidate with 2 nodes, 16 cpus and 2466 KB free selected
domainbuilder: detail: xc_dom_allocate: cmdline="root=/dev/xvda
console=hvc0 ro root=/dev/xvda fastboot", features="(null)"
libxl: debug: libxl_dom.c:341:libxl__build_pv: pv kernel mapped 1 path
/var/run/xen/bootloader.8.d/boot_kernel.VfLJyd
domainbuilder: detail: xc_dom_kernel_mem: called
domainbuilder: detail: xc_dom_ramdisk_mem: called
domainbuilder: detail: xc_dom_boot_xen_init: ver 4.3, caps
xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p
hvm-3.0-x86_64
domainbuilder: detail: xc_dom_parse_image: called
domainbuilder: detail: xc_dom_find_loader: trying multiboot-binary
loader ...
domainbuilder: detail: loader probe failed
domainbuilder: detail: xc_dom_find_loader: trying Linux bzImage loader ...
domainbuilder: detail: xc_dom_malloc : 18250 kB
domainbuilder: detail: xc_dom_do_gunzip: unzip ok, 0x4b30aa -> 0x11d2aa0
domainbuilder: detail: loader probe OK
xc: detail: elf_parse_binary: phdr: paddr=0x1000000 memsz=0xad6000
xc: detail: elf_parse_binary: phdr: paddr=0x1c00000 memsz=0xe30e0
xc: detail: elf_parse_binary: phdr: paddr=0x1ce4000 memsz=0x143c0
xc: detail: elf_parse_binary: phdr: paddr=0x1cf9000 memsz=0x35f000
xc: detail: elf_parse_binary: memory: 0x1000000 -> 0x2058000
xc: detail: elf_xen_parse_note: GUEST_OS = "linux"
xc: detail: elf_xen_parse_note: GUEST_VERSION = "2.6"
xc: detail: elf_xen_parse_note: XEN_VERSION = "xen-3.0"
xc: detail: elf_xen_parse_note: VIRT_BASE = 0xffffffff80000000
xc: detail: elf_xen_parse_note: ENTRY = 0xffffffff81cf9200
xc: detail: elf_xen_parse_note: HYPERCALL_PAGE = 0xffffffff81001000
xc: detail: elf_xen_parse_note: FEATURES =
"!writable_page_tables|pae_pgdir_above_4gb"
xc: detail: elf_xen_parse_note: PAE_MODE = "yes"
xc: detail: elf_xen_parse_note: LOADER = "generic"
xc: detail: elf_xen_parse_note: unknown xen elf note (0xd)
xc: detail: elf_xen_parse_note: SUSPEND_CANCEL = 0x1
xc: detail: elf_xen_parse_note: HV_START_LOW = 0xffff800000000000
xc: detail: elf_xen_parse_note: PADDR_OFFSET = 0x0
xc: detail: elf_xen_addr_calc_check: addresses:
xc: detail: virt_base = 0xffffffff80000000
xc: detail: elf_paddr_offset = 0x0
xc: detail: virt_offset = 0xffffffff80000000
xc: detail: virt_kstart = 0xffffffff81000000
xc: detail: virt_kend = 0xffffffff82058000
xc: detail: virt_entry = 0xffffffff81cf9200
xc: detail: p2m_base = 0xffffffffffffffff
domainbuilder: detail: xc_dom_parse_elf_kernel: xen-3.0-x86_64:
0xffffffff81000000 -> 0xffffffff82058000
domainbuilder: detail: xc_dom_mem_init: mem 2048 MB, pages 0x80000
pages, 4k each
domainbuilder: detail: xc_dom_mem_init: 0x80000 pages
domainbuilder: detail: xc_dom_boot_mem_init: called
domainbuilder: detail: x86_compat: guest xen-3.0-x86_64, address size 64
domainbuilder: detail: xc_dom_malloc : 4096 kB
domainbuilder: detail: xc_dom_build_image: called
domainbuilder: detail: xc_dom_alloc_segment: kernel :
0xffffffff81000000 -> 0xffffffff82058000 (pfn 0x1000 + 0x1058 pages)
domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn
0x1000+0x1058 at 0x7f9aa40e4000
xc: detail: elf_load_binary: phdr 0 at 0x7f9aa40e4000 -> 0x7f9aa4bba000
xc: detail: elf_load_binary: phdr 1 at 0x7f9aa4ce4000 -> 0x7f9aa4dc70e0
xc: detail: elf_load_binary: phdr 2 at 0x7f9aa4dc8000 -> 0x7f9aa4ddc3c0
xc: detail: elf_load_binary: phdr 3 at 0x7f9aa4ddd000 -> 0x7f9aa4eb6000
domainbuilder: detail: xc_dom_alloc_segment: ramdisk :
0xffffffff82058000 -> 0xffffffff82fa8000 (pfn 0x2058 + 0xf50 pages)
domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn
0x2058+0xf50 at 0x7f9a9f0b0000
domainbuilder: detail: xc_dom_do_gunzip: unzip ok, 0x5c1479 -> 0xf4fa10
domainbuilder: detail: xc_dom_alloc_segment: phys2mach :
0xffffffff82fa8000 -> 0xffffffff833a8000 (pfn 0x2fa8 + 0x400 pages)
domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn
0x2fa8+0x400 at 0x7f9a9ecb0000
domainbuilder: detail: xc_dom_alloc_page : start info :
0xffffffff833a8000 (pfn 0x33a8)
domainbuilder: detail: xc_dom_alloc_page : xenstore :
0xffffffff833a9000 (pfn 0x33a9)
domainbuilder: detail: xc_dom_alloc_page : console :
0xffffffff833aa000 (pfn 0x33aa)
domainbuilder: detail: nr_page_tables: 0x0000ffffffffffff/48:
0xffff000000000000 -> 0xffffffffffffffff, 1 table(s)
domainbuilder: detail: nr_page_tables: 0x0000007fffffffff/39:
0xffffff8000000000 -> 0xffffffffffffffff, 1 table(s)
domainbuilder: detail: nr_page_tables: 0x000000003fffffff/30:
0xffffffff80000000 -> 0xffffffffbfffffff, 1 table(s)
domainbuilder: detail: nr_page_tables: 0x00000000001fffff/21:
0xffffffff80000000 -> 0xffffffff837fffff, 28 table(s)
domainbuilder: detail: xc_dom_alloc_segment: page tables :
0xffffffff833ab000 -> 0xffffffff833ca000 (pfn 0x33ab + 0x1f pages)
domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn
0x33ab+0x1f at 0x7f9aa9696000
domainbuilder: detail: xc_dom_alloc_page : boot stack :
0xffffffff833ca000 (pfn 0x33ca)
domainbuilder: detail: xc_dom_build_image : virt_alloc_end :
0xffffffff833cb000
domainbuilder: detail: xc_dom_build_image : virt_pgtab_end :
0xffffffff83800000
domainbuilder: detail: xc_dom_boot_image: called
domainbuilder: detail: arch_setup_bootearly: doing nothing
domainbuilder: detail: xc_dom_compat_check: supported guest type:
xen-3.0-x86_64 <= matches
domainbuilder: detail: xc_dom_compat_check: supported guest type:
xen-3.0-x86_32p
domainbuilder: detail: xc_dom_compat_check: supported guest type:
hvm-3.0-x86_32
domainbuilder: detail: xc_dom_compat_check: supported guest type:
hvm-3.0-x86_32p
domainbuilder: detail: xc_dom_compat_check: supported guest type:
hvm-3.0-x86_64
domainbuilder: detail: xc_dom_update_guest_p2m: dst 64bit, pages 0x80000
domainbuilder: detail: clear_page: pfn 0x33aa, mfn 0x5d4935
domainbuilder: detail: clear_page: pfn 0x33a9, mfn 0x21c2da
domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn
0x33a8+0x1 at 0x7f9aa9693000
domainbuilder: detail: start_info_x86_64: called
domainbuilder: detail: setup_hypercall_page: vaddr=0xffffffff81001000
pfn=0x1001
domainbuilder: detail: domain builder memory footprint
domainbuilder: detail: allocated
domainbuilder: detail: malloc : 22564 kB
domainbuilder: detail: anon mmap : 0 bytes
domainbuilder: detail: mapped
domainbuilder: detail: file mmap : 0 bytes
domainbuilder: detail: domU mmap : 35 MB
domainbuilder: detail: arch_setup_bootlate: shared_info: pfn 0x0, mfn
0x1f6b9
domainbuilder: detail: shared_info_x86_64: called
domainbuilder: detail: vcpu_x86_64: called
domainbuilder: detail: vcpu_x86_64: cr3: pfn 0x33ab mfn 0x21c2d9
domainbuilder: detail: launch_vm: called, ctxt=0x7fff07610e70
domainbuilder: detail: xc_dom_release: called
libxl: debug: libxl_device.c:257:libxl__device_disk_set_backend: Disk
vdev=xvda spec.backend=phy
libxl: debug: libxl_event.c:559:libxl__ev_xswatch_register: watch
w=0x248dd08 wpath=/local/domain/0/backend/vbd/8/51712/state token=3/1:
register slotnum=3
libxl: debug: libxl_event.c:503:watchfd_callback: watch w=0x248dd08
wpath=/local/domain/0/backend/vbd/8/51712/state token=3/1: event
epath=/local/domain/0/backend/vbd/8/51712/state
libxl: debug: libxl_event.c:647:devstate_watch_callback: backend
/local/domain/0/backend/vbd/8/51712/state wanted state 2 still waiting
state 1
libxl: debug: libxl_event.c:503:watchfd_callback: watch w=0x248dd08
wpath=/local/domain/0/backend/vbd/8/51712/state token=3/1: event
epath=/local/domain/0/backend/vbd/8/51712/state
libxl: debug: libxl_event.c:643:devstate_watch_callback: backend
/local/domain/0/backend/vbd/8/51712/state wanted state 2 ok
libxl: debug: libxl_event.c:596:libxl__ev_xswatch_deregister: watch
w=0x248dd08 wpath=/local/domain/0/backend/vbd/8/51712/state token=3/1:
deregister slotnum=3
libxl: debug: libxl_event.c:608:libxl__ev_xswatch_deregister: watch
w=0x248dd08: deregister unregistered
libxl: debug: libxl_device.c:959:device_hotplug: calling hotplug script:
/etc/xen/scripts/block add
libxl: debug: libxl_event.c:559:libxl__ev_xswatch_register: watch
w=0x248de18 wpath=/local/domain/0/backend/vif/8/0/state token=3/2:
register slotnum=3
libxl: debug: libxl_event.c:503:watchfd_callback: watch w=0x248de18
wpath=/local/domain/0/backend/vif/8/0/state token=3/2: event
epath=/local/domain/0/backend/vif/8/0/state
libxl: debug: libxl_event.c:647:devstate_watch_callback: backend
/local/domain/0/backend/vif/8/0/state wanted state 2 still waiting state 1
libxl: debug: libxl_event.c:503:watchfd_callback: watch w=0x248de18
wpath=/local/domain/0/backend/vif/8/0/state token=3/2: event
epath=/local/domain/0/backend/vif/8/0/state
libxl: debug: libxl_event.c:643:devstate_watch_callback: backend
/local/domain/0/backend/vif/8/0/state wanted state 2 ok
libxl: debug: libxl_event.c:596:libxl__ev_xswatch_deregister: watch
w=0x248de18 wpath=/local/domain/0/backend/vif/8/0/state token=3/2:
deregister slotnum=3
libxl: debug: libxl_event.c:608:libxl__ev_xswatch_deregister: watch
w=0x248de18: deregister unregistered
libxl: debug: libxl_device.c:959:device_hotplug: calling hotplug script:
/etc/xen/scripts/vif-bridge online
libxl: debug: libxl_event.c:1737:libxl__ao_progress_report: ao
0x24915a0: progress report: ignored
libxl: debug: libxl_event.c:1569:libxl__ao_complete: ao 0x24915a0:
complete, rc=0
libxl: debug: libxl_event.c:1541:libxl__ao__destroy: ao 0x24915a0: destroy
Daemon running with PID 6087
xc: debug: hypercall buffer: total allocations:346 total releases:346
xc: debug: hypercall buffer: current allocations:0 maximum allocations:4
xc: debug: hypercall buffer: cache current size:4
xc: debug: hypercall buffer: cache hits:336 misses:4 toobig:6
informika-xen-3 ~ #
informika-xen-3 ~ # cat /etc/xen/vm/www.icsit.ru
bootloader = "pygrub"
memory = 2048
vcpus = 2
name = "www.icsit.ru"
vif = [ 'mac=00:16:3E:5A:04:01, bridge=v119, model=e1000' ]
disk = ['phy:/dev/storage-a/www.icsit.ru,xvda,w']
root = "/dev/xvda"
extra = "fastboot"
--
С уважением,
Георгий Репин
ФГАУ ГНИИ ИТТ "Информика"
http://www.informika.ru
http://www.runnet.ru
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [BUG] invocation of xl create with insufficient memory for new domU causes system reboot
2014-04-02 10:25 ` Georgy V. Repin
2014-04-02 10:39 ` Georgy V. Repin
@ 2014-04-02 10:52 ` Ian Campbell
1 sibling, 0 replies; 9+ messages in thread
From: Ian Campbell @ 2014-04-02 10:52 UTC (permalink / raw)
To: Georgy V. Repin; +Cc: xen-devel
On Wed, 2014-04-02 at 14:25 +0400, Georgy V. Repin wrote:
> - now there is no oom reaction, because i have reduced memory amount
> for one of other domU's (now it's enough memory for all domU's)
Thanks, but I was hoping to see the logs for the failure case so I could
try and diagnose it. Logs of things working don't tell me very much.
Ian.
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2014-04-02 10:52 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-04-01 9:35 [BUG] invocation of xl create with insufficient memory for new domU causes system reboot Georgy V. Repin
2014-04-01 9:52 ` Ian Campbell
2014-04-01 10:17 ` Georgy V. Repin
2014-04-02 5:47 ` Georgy V. Repin
2014-04-02 9:31 ` Ian Campbell
2014-04-02 9:30 ` Ian Campbell
2014-04-02 10:25 ` Georgy V. Repin
2014-04-02 10:39 ` Georgy V. Repin
2014-04-02 10:52 ` Ian Campbell
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.