FS#46227 - [linux] Kernel panic when running qemu / libvirt / kvm virtualization on 4.1.6-1

Attached to Project: Arch Linux
Opened by Sebastian (cmdrsweeper) - Tuesday, 08 September 2015, 19:20 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 09 July 2016, 03:18 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Thomas Bächler (brain0)
Architecture x86_64
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

Description:
When running the latest kernel which is 4.1.6-1 as I write this, the computer will lock up / freeze after a couple of days with a kernel panic.
The stack trace for this trails back to virtualization and kvm virtualization.
I am running this on my home server which has the following specifications:

CPU: Intel Core 2 Quad Q9450
Motherboard: ABIT IX38 QuadGT (Intel VT-d enabled in the BIOS and passes checks for it in the OS too.)
RAM: 8Gb
GPU: ATi Radeon HD 4670 (Mainly just there to give me a graphical console when I hook up a monitor.)
Harddrives: 4x 1.5Tb Seagates, 2x 2Tb Seagates (These 6 drives of different size, both host a mdadm RAID 6 array.) and a 160Gb WD IDE drive as the drive that hosts the OS, not the virtual machines.

On this "host" I got 4x VMs running via Qemu:
1x Windows Server 2008 R2
2x Ubuntu 12.04 Server
1x PFSense FreeBSD 10.1

How to reproduce on this hardware:
Enable and install the prerequisites for the qemu / libvirtd (Includes enabling VT-d in BIOS) and from there set up the virtual machines and let it run.
After about 1-3 days of runtime, the machine will kernel panic with the attached log.
This task depends upon

Closed by  Doug Newgard (Scimmia)
Saturday, 09 July 2016, 03:18 GMT
Reason for closing:  Fixed
Comment by Samantha McVey (samcv) - Friday, 10 June 2016, 22:06 GMT
Sebastian,
Did this problem ever get resolved? Can you let me know if this is still an issue for you? Your response is greatly appreciated.
Comment by Sebastian (cmdrsweeper) - Friday, 08 July 2016, 21:07 GMT
Sorry for the late reply to this issue.
However, I have been monitoring this issue in the past few months and year and I think it would be safe to say that it is resolved.
I just wish we got to know when a dev either upstream or somebody from the arch project sent this bug report on further, maybe not that it is fixed, but that they are aware of it.
In any case, I have been stable and haven't seen ANY Kernel Panics, so I would stamp this as fixed, either by upstream devs or something the Arch devs did.

Loading...