d3spis3m3

The change log doesn't indicate the templates not loading when attempting to add guest VM's which is fixed after update.

This is a support issue

So I don't know where to begin in diagnosing this except for the syslog. KVM's lock up after 4-7 days. Last time I had an issue the cache would not mount when the files system was corrupt. I did the repair on that. This is also the first time I'm able to login to the machine ssh only, so any commands for me to paste the output would be great. Jun 4 03:23:52 Tower kernel: task: ffff88043bcc5400 ti: ffff880375434000 task.ti: ffff880375434000 Jun 4 03:23:52 Tower kernel: RIP: 0010:[<0000000000000000>] [< (null)>] (null) Jun 4 03:23:52 Tower kernel: RSP: 0018:ffff880375437ab8 EFLAGS: 00010087 Jun 4 03:23:52 Tower kernel: RAX: ffff88017f2ffd30 RBX: 0000000000000001 RCX: 0000000000000000 Jun 4 03:23:52 Tower kernel: RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff88017f2ffd30 Jun 4 03:23:52 Tower kernel: RBP: ffff880375437af8 R08: 0000000000000000 R09: 0000000000000000 Jun 4 03:23:52 Tower kernel: R10: 0000000000000000 R11: 00000000000000d0 R12: 0000000000000001 Jun 4 03:23:52 Tower kernel: R13: 0000000000000000 R14: 0000000000000000 R15: ffffffffffffffe8 Jun 4 03:23:52 Tower kernel: FS: 00000000002a8000(0053) GS:ffff88044ec00000(002b) knlGS:00000000002a6000 Jun 4 03:23:52 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jun 4 03:23:52 Tower kernel: CR2: 0000000000000000 CR3: 0000000424029000 CR4: 00000000000406f0 Jun 4 03:23:52 Tower kernel: Stack: Jun 4 03:23:52 Tower kernel: ffffffff81075ab9 0000000000000000 ffff88042418bf20 ffff88042418bf18 Jun 4 03:23:52 Tower kernel: 0000000000000282 ffff880424b38000 0000000000000000 ffff88042418be80 Jun 4 03:23:52 Tower kernel: ffff880375437b28 ffffffff81075b19 0000000100000001 0000000000000000 Jun 4 03:23:52 Tower kernel: Call Trace: Jun 4 03:23:52 Tower kernel: [<ffffffff81075ab9>] ? __wake_up_common+0x50/0x7c Jun 4 03:23:52 Tower kernel: [<ffffffff81075b19>] __wake_up+0x34/0x46 Jun 4 03:23:52 Tower kernel: [<ffffffffa01f05ac>] kvm_vcpu_kick+0x36/0x96 [kvm] Jun 4 03:23:52 Tower kernel: [<ffffffffa0211de3>] __apic_accept_irq+0xcf/0x191 [kvm] Jun 4 03:23:52 Tower kernel: [<ffffffffa0212ce4>] kvm_apic_set_irq+0x25/0x27 [kvm] Jun 4 03:23:52 Tower kernel: [<ffffffffa0216012>] kvm_irq_delivery_to_apic+0x103/0x1ae [kvm] Jun 4 03:23:52 Tower kernel: [<ffffffffa02129a1>] apic_reg_write+0x336/0x492 [kvm] Jun 4 03:23:52 Tower kernel: [<ffffffffa021415a>] kvm_hv_vapic_msr_write+0x40/0x53 [kvm] Jun 4 03:23:52 Tower kernel: [<ffffffffa0218897>] kvm_hv_set_msr_common+0x30a/0x384 [kvm] Jun 4 03:23:52 Tower kernel: [<ffffffffa01f9946>] kvm_set_msr_common+0x7fd/0x983 [kvm] Jun 4 03:23:52 Tower kernel: [<ffffffffa02f628b>] svm_set_msr+0x362/0x369 [kvm_amd] Jun 4 03:23:52 Tower kernel: [<ffffffffa01f63eb>] kvm_set_msr+0x61/0x63 [kvm] Jun 4 03:23:52 Tower kernel: [<ffffffffa02f93fa>] msr_interception+0xe5/0x1b3 [kvm_amd] Jun 4 03:23:52 Tower kernel: [<ffffffffa02f7f18>] handle_exit+0x845/0x865 [kvm_amd] Jun 4 03:23:52 Tower kernel: [<ffffffffa01fff85>] kvm_arch_vcpu_ioctl_run+0x37d/0x104e [kvm] Jun 4 03:23:52 Tower kernel: [<ffffffffa01fa9c8>] ? kvm_arch_vcpu_load+0xe8/0x16c [kvm] Jun 4 03:23:52 Tower kernel: [<ffffffffa01f20e9>] kvm_vcpu_ioctl+0x178/0x499 [kvm] Jun 4 03:23:52 Tower kernel: [<ffffffffa01f3152>] ? kvm_vm_ioctl+0x3e8/0x5d8 [kvm] Jun 4 03:23:52 Tower kernel: [<ffffffff811175fd>] do_vfs_ioctl+0x3a3/0x416 Jun 4 03:23:52 Tower kernel: [<ffffffff8111f5e7>] ? __fget+0x72/0x7e Jun 4 03:23:52 Tower kernel: [<ffffffff811176ae>] SyS_ioctl+0x3e/0x5c Jun 4 03:23:52 Tower kernel: [<ffffffff8161a0ae>] entry_SYSCALL_64_fastpath+0x12/0x6d Jun 4 03:23:52 Tower kernel: Code: Bad RIP value. Jun 4 03:23:52 Tower kernel: RIP [< (null)>] (null) Jun 4 03:23:52 Tower kernel: RSP <ffff880375437ab8> Jun 4 03:23:52 Tower kernel: CR2: 0000000000000000 Jun 4 03:23:52 Tower kernel: ---[ end trace 85759c9f8b8a9a68 ]--- Jun 4 03:23:52 Tower kernel: note: qemu-system-x86[2071] exited with preempt_count 1