From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 110441] KVM guests randomly get I/O errors on VirtIO based devices
Date: Fri, 08 Jan 2016 10:23:54 +0000 [thread overview]
Message-ID: <bug-110441-28872-MAaxw2Pefq@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-110441-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=110441
Jordi Mallach <jordi.mallach@collabora.co.uk> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |INVALID
--- Comment #1 from Jordi Mallach <jordi.mallach@collabora.co.uk> ---
Sorry for the noise. This is actually caused by os-prober opening the devices
and causing corruption and mayhem. See
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788062 for details.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2016-01-08 10:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-06 17:06 [Bug 110441] New: KVM guests randomly get I/O errors on VirtIO based devices bugzilla-daemon
2016-01-08 10:23 ` bugzilla-daemon [this message]
2021-08-25 5:36 ` [Bug 110441] " bugzilla-daemon
2021-10-15 17:59 ` 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-110441-28872-MAaxw2Pefq@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=kvm@vger.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;
as well as URLs for NNTP newsgroup(s).