[Bug 1223288] [NEW] dom0 hangs after creating a new domU
nfhoge
nfhoge at gmail.com
Tue Sep 10 10:52:33 UTC 2013
Public bug reported:
release of Ubuntu : 13.04
package : xen-utils-common 4.2.1-0ubuntu3.1
Creating domU causes OOM and kills dom0 while physical memory is not
full.
-- Hardware Information --
Memory 24G
-- domU Resource Usage --
# xl list
Name ID Mem VCPUs State Time(s)
Domain-0 0 2048 2 r----- 47.9
domU1 1 3835 2 -b---- 9.0
domU2 2 3835 2 -b---- 32.5
domU3 3 3835 2 -b---- 1.4
-- new domU configuration --
# vim config
builder = "hvm"
name = "domU4"
memory = 8192
vcpus = 2
vif = ['bridge=xenbr***']
disk = ['phy:/dev/vg00/domU4_root,hda,w',
'phy:/dev/vg00/domU4_swap,hdb,w', ]
boot = "n"
vnc = 2
vnclisten = "0.0.0.0"
vncpasswd = "****"
-- /var/log/kernel after "xl create domU4.conf" --
Sep 5 11:10:05 dom0 kernel: [3087616.306594] qemu-dm invoked oom-killer: gfp_mask=0x201da, order=0, oom_score_adj=0
Sep 5 11:10:06 dom0 kernel: [3087616.306599] qemu-dm cpuset=/ mems_allowed=0
Sep 5 11:10:06 dom0 kernel: [3087616.306602] Pid: 3981, comm: qemu-dm Tainted: GF 3.8.0-26-generic #38-Ubuntu
Sep 5 11:10:06 dom0 kernel: [3087616.306604] Call Trace:
Sep 5 11:10:06 dom0 kernel: [3087616.306612] [<ffffffff816c0d04>] dump_header+0x80/0x1c3
Sep 5 11:10:06 dom0 kernel: [3087616.306617] [<ffffffff81132d67>] oom_kill_process+0x1b7/0x320
…
Sep 5 11:14:01 dom0 kernel: [3087833.452352] Out of memory: Kill process 32383 (puppet) score 0 or sacrifice child
Sep 5 11:14:01 dom0 kernel: [3087833.452428] Killed process 32383 (puppet) total-vm:173632kB, anon-rss:0kB, file-rss:0kB
Sep 5 11:16:17 dom0 kernel: imklog 5.8.11, log source = /proc/kmsg started.
Sep 5 11:16:17 dom0 kernel: [ 0.000000] Initializing cgroup subsys cpuset
Sep 5 11:16:17 dom0 kernel: [ 0.000000] Initializing cgroup subsys cpu
----------------------------------------------------
** Affects: xen (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
release of Ubuntu : 13.04
package : xen-utils-common 4.2.1-0ubuntu3.1
- Creating domU causes OOM and kills dom0 while physical memory is no
+ Creating domU causes OOM and kills dom0 while physical memory is not
full.
-- Hardware Information --
Memory 24G
-- domU Resource Usage --
# xl list
Name ID Mem VCPUs State Time(s)
Domain-0 0 2048 2 r----- 47.9
domU1 1 3835 2 -b---- 9.0
domU2 2 3835 2 -b---- 32.5
domU3 3 3835 2 -b---- 1.4
-- new domU configuration --
# vim config
builder = "hvm"
name = "domU4"
memory = 8192
vcpus = 2
vif = ['bridge=xenbr***']
disk = ['phy:/dev/vg00/domU4_root,hda,w',
- 'phy:/dev/vg00/domU4_swap,hdb,w', ]
+ 'phy:/dev/vg00/domU4_swap,hdb,w', ]
boot = "n"
vnc = 2
vnclisten = "0.0.0.0"
vncpasswd = "****"
-- /var/log/kernel after "xl create test.conf" --
Sep 5 11:10:05 dom0 kernel: [3087616.306594] qemu-dm invoked oom-killer: gfp_mask=0x201da, order=0, oom_score_adj=0
Sep 5 11:10:06 dom0 kernel: [3087616.306599] qemu-dm cpuset=/ mems_allowed=0
Sep 5 11:10:06 dom0 kernel: [3087616.306602] Pid: 3981, comm: qemu-dm Tainted: GF 3.8.0-26-generic #38-Ubuntu
Sep 5 11:10:06 dom0 kernel: [3087616.306604] Call Trace:
Sep 5 11:10:06 dom0 kernel: [3087616.306612] [<ffffffff816c0d04>] dump_header+0x80/0x1c3
Sep 5 11:10:06 dom0 kernel: [3087616.306617] [<ffffffff81132d67>] oom_kill_process+0x1b7/0x320
…
Sep 5 11:14:01 dom0 kernel: [3087833.452352] Out of memory: Kill process 32383 (puppet) score 0 or sacrifice child
Sep 5 11:14:01 dom0 kernel: [3087833.452428] Killed process 32383 (puppet) total-vm:173632kB, anon-rss:0kB, file-rss:0kB
Sep 5 11:16:17 dom0 kernel: imklog 5.8.11, log source = /proc/kmsg started.
Sep 5 11:16:17 dom0 kernel: [ 0.000000] Initializing cgroup subsys cpuset
Sep 5 11:16:17 dom0 kernel: [ 0.000000] Initializing cgroup subsys cpu
----------------------------------------------------
** Description changed:
release of Ubuntu : 13.04
package : xen-utils-common 4.2.1-0ubuntu3.1
Creating domU causes OOM and kills dom0 while physical memory is not
full.
-- Hardware Information --
Memory 24G
-- domU Resource Usage --
# xl list
Name ID Mem VCPUs State Time(s)
Domain-0 0 2048 2 r----- 47.9
domU1 1 3835 2 -b---- 9.0
domU2 2 3835 2 -b---- 32.5
domU3 3 3835 2 -b---- 1.4
-- new domU configuration --
# vim config
builder = "hvm"
name = "domU4"
memory = 8192
vcpus = 2
vif = ['bridge=xenbr***']
disk = ['phy:/dev/vg00/domU4_root,hda,w',
'phy:/dev/vg00/domU4_swap,hdb,w', ]
boot = "n"
vnc = 2
vnclisten = "0.0.0.0"
vncpasswd = "****"
- -- /var/log/kernel after "xl create test.conf" --
+ -- /var/log/kernel after "xl create domU4.conf" --
Sep 5 11:10:05 dom0 kernel: [3087616.306594] qemu-dm invoked oom-killer: gfp_mask=0x201da, order=0, oom_score_adj=0
Sep 5 11:10:06 dom0 kernel: [3087616.306599] qemu-dm cpuset=/ mems_allowed=0
Sep 5 11:10:06 dom0 kernel: [3087616.306602] Pid: 3981, comm: qemu-dm Tainted: GF 3.8.0-26-generic #38-Ubuntu
Sep 5 11:10:06 dom0 kernel: [3087616.306604] Call Trace:
Sep 5 11:10:06 dom0 kernel: [3087616.306612] [<ffffffff816c0d04>] dump_header+0x80/0x1c3
Sep 5 11:10:06 dom0 kernel: [3087616.306617] [<ffffffff81132d67>] oom_kill_process+0x1b7/0x320
…
Sep 5 11:14:01 dom0 kernel: [3087833.452352] Out of memory: Kill process 32383 (puppet) score 0 or sacrifice child
Sep 5 11:14:01 dom0 kernel: [3087833.452428] Killed process 32383 (puppet) total-vm:173632kB, anon-rss:0kB, file-rss:0kB
Sep 5 11:16:17 dom0 kernel: imklog 5.8.11, log source = /proc/kmsg started.
Sep 5 11:16:17 dom0 kernel: [ 0.000000] Initializing cgroup subsys cpuset
Sep 5 11:16:17 dom0 kernel: [ 0.000000] Initializing cgroup subsys cpu
----------------------------------------------------
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to xen in Ubuntu.
https://bugs.launchpad.net/bugs/1223288
Title:
dom0 hangs after creating a new domU
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xen/+bug/1223288/+subscriptions
More information about the Ubuntu-server-bugs
mailing list