On 9/21/16 8:33 , John Barfield wrote: > Hi Robert any update on the core I posted?
It seems to most likely be related to https://smartos.org/bugview/HVM-824. Though without the core file itself, I can't confirm. Regardless, as I mentioned last time, you should definitely be updating your platform image. Robert > Re: [smartos-discuss] KVM VM Crashing, Core analysis Help > ?<https://www.listbox.com/member/archive/184463/2016/09/20160916163414:EB650BAC-7C4C-11E6-94E8-DA2D75E01411> > > Sent by John Barfield > <[email protected]<mailto:[email protected]>> at Fri, 16 Sep > 2016 20:34:04 +0000 > > Hi Robert thank you for the update. Sorry for the late reply. I ran the > coredump and it appears to be virtio network driver that’s causing the crash. > At least that’s what it looks like to me. Let me know what you think. Here is > the output: debugging core file of qemu-system-x86 (64-bit) from > ab4fa5b1-de93-42aa-9072-b7a9b84265f4 file: /smartdc/bin/qemu-system-x86_64 > initial argv: /smartdc/bin/qemu-system-x86_64 -m 6144 -name > ab4fa5b1-de93-42aa-9072-b7a9b8426 threading model: native threads status: > process terminated by SIGABRT (Abort), pid=45351 uid=0 code=-1 > fffffd7fffded080 libc.so.1`_lwp_kill+0xa() fffffd7fffded0b0 > libc.so.1`raise+0x20(6) fffffd7fffded100 libc.so.1`abort+0x98() > fffffd7fffded190 vnic_receive_iov+0x2fc(f6c260, fffffd7fffdf5400, 2) > fffffd7fffded230 qemu_vlan_deliver_packet_iov+0xe0(182b101f0, 0, > fffffd7fffdf5400, 2, f67140) fffffd7fffded2c0 > qemu_net_queue_deliver_iov+0x72(f67180, 182b101f0, 0, fffffd7fffdf5400, 2) > fffffd7fffded350 qemu_net_queue_send_iov+0x92(f67180, 182b101f0, 0, > fffffd7fffdf5400, 2, 4edb11) fffffd7fffded3c0 > qemu_sendv_packet_async+0xbe(182b101f0, fffffd7fffdf5400, 2, 4edb11) > fffffd7fffdf9440 virtio_net_flush_tx+0x19b(1810abc10, 182b0ee30) > fffffd7fffdf9480 virtio_net_tx_timer+0x8f(1810abc10) fffffd7fffdf94d0 > qemu_run_timers+0xb0(f625a0) fffffd7fffdf94e0 qemu_run_all_timers+0x51() > fffffd7fffdff570 main_loop_wait+0x480(0) fffffd7fffdff5a0 > kvm_main_loop+0x119() fffffd7fffdff5c0 main_loop+0x17() fffffd7fffdff900 > main+0x2da4(30, fffffd7fffdff928, fffffd7fffdffab0) fffffd7fffdff910 > _start+0x6c() Sent by John Barfield > <[email protected]<mailto:[email protected]><mailto:[email protected]>> > at Thu, 8 Sep 2016 13:32:52 +0000 Greetings friends, I have a VM that > crashes once every day or every other day. There are no errors in the VM > logs….it just shows that it may have lost power. In the GZ I’m getting VM > core dumps. Could someone point me in the direction of the documentation or > towards a tool that would help me analyze the VM core dump to determine why > it is crashing? This is a windows server 2008 r2 sp2 VM for the record. GZ: > is joyent_20151104T185720Z Thanks! John Sent by Robert Mustacchi > <[email protected]<mailto:[email protected]><mailto:[email protected]>> at Thu, 8 > Sep 2016 07:52:17 -0700 On 9/8/16 6:32 , John Barfield wrote: > Greetings > friends, > > I have a VM that crashes once every day or every other day. > > > There are no errors in the VM logs….it just shows that it may have lost > power. > > In the GZ I’m getting VM core dumps. > > Could someone point me in > the direction of the documentation or towards a tool that would help me > analyze the VM core dump to determine why it is crashing? > > This is a > windows server 2008 r2 sp2 VM for the record. > > GZ: is > joyent_20151104T185720Z Hi John, So, the best thing to do would be to run mdb > on the core file. I would run something like mdb -e '::status;$C' > /path/to/core/file. If you can share those outputs, we can likely tell you > what happened and if this is a known bug. Please note that there have been > many importa > > nt bug fixes and security fixes since that version, so I'd encourage you to > update, but we should make sure that this is root caused regardless. Robert > smartos-discuss | > ------------------------------------------- smartos-discuss Archives: https://www.listbox.com/member/archive/184463/=now RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00 Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb Powered by Listbox: http://www.listbox.com
