Bug 1195945 - high cpu useage on LXCs caused by /dev/kmsg symlinked to /dev/console
Summary: high cpu useage on LXCs caused by /dev/kmsg symlinked to /dev/console
Keywords:
Status: CLOSED DUPLICATE of bug 1141456
Alias: None
Product: Fedora
Classification: Fedora
Component: lxc
Version: 21
Hardware: Unspecified
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Thomas Moschny
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-02-24 21:30 UTC by Ayman Khamouma
Modified: 2015-03-03 20:24 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-03-03 20:24:34 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Ayman Khamouma 2015-02-24 21:30:18 UTC
Description of problem:

systemd-journald from an lxc consuming 100% cpu.
this is caused by the fact that /dev/kmsg is a symlink to /dev/console

As this is the default fedora 22 configuration, I guess it is a bug in the lxc / lxc-template packages.

Version-Release number of selected component (if applicable):

lxc: 
 Version 1.0.7
 Release 1.fc21

lxc-templates: 
 Version 1.0.7
 Release 1.fc21 

How reproducible:

systematic

Steps to Reproduce:
1. sudo su
2. lxc-create -n fed21 -t fedora
3. lxc-start -n fed21

Actual results:

systemd-journald from the lxc consumes 100% cpu because /dev/kmsg is a symlink to /dev/console

Expected results:

/dev/kmsg should not be a symlink to /dev/console

Additional info:
already "fixed" on the debian, sshd and archlinux templates:
/usr/share/lxc/templates/lxc-archlinux:133:lxc.kmsg=0
/usr/share/lxc/templates/lxc-sshd:132:lxc.kmsg = 0
/usr/share/lxc/templates/lxc-debian:184:       echo 'lxc.kmsg = 0' >> "$path/config"


worked around in my lxc config with:
lxc.kmsg = 0

Comment 1 Thomas Moschny 2015-03-03 20:23:27 UTC
Already fixed upstream in commit e8a1665, will be in 1.0.8.

Comment 2 Thomas Moschny 2015-03-03 20:24:34 UTC
And, already discussed here: bug 1141456.

*** This bug has been marked as a duplicate of bug 1141456 ***


Note You need to log in before you can comment on or make changes to this bug.