Starting a LXC Container can lead to a kernel oops
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Chuck Short |
Bug Description
If you are using a qcow iamge with an lxc container, starting a lxc container will lead to a kernel oops (attached below), this is due to the nbd being disconnected while the lxc container is still running.
Feb 4 15:10:58 homer kernel: [ 2483.980180] Kernel BUG at ffffffff811c50b4 [verbose debug info unavailable]
Feb 4 15:10:58 homer kernel: [ 2483.982652] Modules linked in: ebt_arp(F) ebt_ip(F) veth(F) xt_conntrack(F) xt_nat(F) openvswitch ip6table_filter(F) ip6_tables(F) ebtable_nat(F) ebtables(F) xt_state(F) ipt_REJECT(F) xt_CHECKSUM(F) iptable_mangle(F) xt_tc
pudp(F) iptable_filter(F) ipt_MASQUERADE(F) iptable_nat(F) nf_conntrack_
F) libiscsi_tcp(F) libiscsi(F) scsi_transport_
da_codec kvm_amd snd_hwdep(F) cfg80211 kvm snd_pcm(F) snd_page_alloc(F) eeprom_93cx6<4>[ 2484.001668] CPU 0
Feb 4 15:10:58 homer kernel: [ 2484.007849] RIP: 0010:[<
Feb 4 15:10:58 homer kernel: [ 2484.014575] RAX: 0000000000040005 RBX: ffff88006cdbdb60 RCX: 0000000000000019
Feb 4 15:10:58 homer kernel: [ 2484.021599] RBP: ffff8800cf925aa0 R08: 000000000a000020 R09: 0000000000000000
Feb 4 15:10:58 homer kernel: [ 2484.028831] R13: ffff880067b5a400 R14: 0000000000005bc8 R15: ffff8801dfb9ec00
Feb 4 15:10:58 homer kernel: [ 2484.036334] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Feb 4 15:10:58 homer kernel: [ 2484.044179] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Feb 4 15:10:58 homer kernel: [ 2484.052237] Process init (pid: 10006, threadinfo ffff8800cf924000, task ffff8801df86dd00)
Feb 4 15:10:58 homer kernel: [ 2484.060569] ffff88006cdbdb60 0000000000000411 ffff880067b5a400 0000000000005bc8
Feb 4 15:10:58 homer kernel: [ 2484.069418] ffff8800cf925ad0 ffffffff811c6263 ffff8800cf925b18 ffffffff812526e8
Feb 4 15:10:58 homer kernel: [ 2484.078454] [<ffffffff811c6
Feb 4 15:10:58 homer kernel: [ 2484.087813] [<ffffffff81252
Feb 4 15:10:58 homer kernel: [ 2484.097368] [<ffffffff81253
Feb 4 15:10:58 homer kernel: [ 2484.107094] [<ffffffff811ca
Feb 4 15:10:58 homer kernel: [ 2484.116986] [<ffffffff8123b
Feb 4 15:10:58 homer kernel: [ 2484.127088] [<ffffffff8123c
Feb 4 15:10:58 homer kernel: [ 2484.137356] [<ffffffff8119d
Feb 4 15:10:58 homer kernel: [ 2484.147795] [<ffffffff811a1
Feb 4 15:10:58 homer kernel: [ 2484.158434] [<ffffffff8117c
Feb 4 15:10:58 homer kernel: [ 2484.169290] [<ffffffff811a1
Feb 4 15:10:58 homer kernel: [ 2484.180358] [<ffffffff81307
Feb 4 15:10:58 homer kernel: [ 2484.191661] [<ffffffff81192
Feb 4 15:10:58 homer kernel: [ 2484.203168] [<ffffffff81192
Feb 4 15:10:58 homer kernel: [ 2484.214875] Code: e4 a1 44 89 e0 41 5c 41 5d 41 5e 5d c3 66 2e 0f 1f 84 00 00 00 00 00 40 f6 c7 01 0f 84 14 ff ff ff f0 80 66 01 f7 e9 0a ff ff ff <0f> 0b 48 8b 53 70 c1 e0 09 41 f6 c5 01 89 43 30 89 42 08 75 9a
Feb 4 15:10:58 homer kernel: [ 2484.234017] RSP <ffff8800cf925a80>
Feb 4 15:10:58 homer kernel: [ 2484.480951] block nbd3: Attempted send on closed socket
tags: | added: lxc |
Changed in nova: | |
milestone: | none → grizzly-3 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | grizzly-3 → 2013.1 |
I guess we can workaround it in userland, but I'd think that kernel should not OOPS anyway, so there might be a kernel issue to fix as well.