From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@kernel.org
Subject: [Bug 197449] New: 4.13 kernel with KVM and libvirt freezes Windows 10 virtual machine
Date: Thu, 26 Oct 2017 19:41:27 +0000 [thread overview]
Message-ID: <bug-197449-28872@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=197449
Bug ID: 197449
Summary: 4.13 kernel with KVM and libvirt freezes Windows 10
virtual machine
Product: Virtualization
Version: unspecified
Kernel Version: 4.13.*
Hardware: Intel
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: kvm
Assignee: virtualization_kvm@kernel-bugs.osdl.org
Reporter: erikmnkl@gmail.com
Regression: No
Created attachment 260411
--> https://bugzilla.kernel.org/attachment.cgi?id=260411&action=edit
Crash screen (from virt-manager app)
I have Windows 10 virtual image on my laptop, running under KVM and libvirt.
When under 4.13 kernel and use virtual machine - it just randomly freezes
(freezes are quite rare, but happens time to time when using virtual machine
for several hours. There was no issues at all with 4.12 and 4.9 kernels (did
not test other kernels).
When virtual machine crashes, virt-manager is still working, so I was able to
take a screenshot and attach it here.
I am also using virtIO Windows drivers 0.1.141.1 for Windows 10 (64bit).
Operating system: Arch Linux (64bit).
Kernel: 4.13.9.
Hardware (laptop): Asus Zenbook UX430UQ
Please let me know if there is anything I can help or provide in order to get
this fixed.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2017-10-26 19:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-26 19:41 bugzilla-daemon [this message]
2017-12-12 1:45 ` [Bug 197449] 4.13 kernel with KVM and libvirt freezes Windows 10 virtual machine bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-197449-28872@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=kvm@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox