device: 0.167
semantic: 0.123
other: 0.110
boot: 0.103
PID: 0.080
performance: 0.067
files: 0.058
permissions: 0.050
graphic: 0.049
vnc: 0.047
debug: 0.046
socket: 0.041
KVM: 0.034
network: 0.027
debug: 0.464
socket: 0.092
device: 0.079
files: 0.063
other: 0.055
boot: 0.047
PID: 0.046
performance: 0.036
KVM: 0.035
network: 0.030
semantic: 0.019
vnc: 0.014
graphic: 0.012
permissions: 0.009

Persistent malfunction after guest shutdown/reboot

Running the VM the first time after the host has booted up is completely fine, no issues at all. However, after shutting down or restarting the VM, certain problems occur. In the Windows 10 VM, it may throw a SYSTEM_THREAD_EXCEPTION error on bootup, and other times it simply won't use the VirtIO drive. Before the latest update of QEMU 2.5.0, I have had no problems.

Recently, I've also downgraded my kernel in order to solve some problems related to Haswell. This is probably the same time I've got the 2.5.0 update. When I did this, I could no longer boot into my main image due to similar problems. I've had to also update the VirtIO storage driver with a new image installation. Before I figured that everything worked fine on a host reboot, the installer would spit out an error that it could not modify the partitions of the drive. Everything else worked fine with SATA or IDE configuration, but not VirtIO. I shouldn't need to restart my computer after shutting down the computer.

I've tried using QEMU with the latest Linux kernel (4.4.x) with the exact same result.

Here is what I have configured:
- Arch Linux with linux-lts (4.1.19-1-lts)
- QEMU 2.5.0
- VirtIO drivers v 0.1.113
- Windows 10 from MSDN
- vfio PCI Passthrough of NVIDIA 970

I'm not sure how to get any more logs so if you need more info I'll be glad to provide it



I've just recently experienced drive corruption and BIOS issues. After a reformat (to ext4 from f2fs), a BIOS re-flash and reinstall with linux-lts, this issue isn't appearing anymore so it was an issue specific to me.