From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 37152] New: file system become read only after live migration
Date: Fri, 10 Jun 2011 14:37:18 GMT [thread overview]
Message-ID: <bug-37152-28872@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=37152
Summary: file system become read only after live migration
Product: Virtualization
Version: unspecified
Kernel Version: 2.6.32-5-amd64
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: kvm
AssignedTo: virtualization_kvm@kernel-bugs.osdl.org
ReportedBy: martin.chamberland@fadq.qc.ca
Regression: No
Dell T610
Intel Xeon 2.40ghz
kvm version 1:0.12.5+dfsg-5+squeeze2
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next reply other threads:[~2011-06-10 14:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-10 14:37 bugzilla-daemon [this message]
2011-06-10 15:38 ` [Bug 37152] file system become read only after live migration bugzilla-daemon
2011-06-10 15:39 ` bugzilla-daemon
2011-06-10 15:42 ` bugzilla-daemon
2011-07-21 14:59 ` bugzilla-daemon
2011-07-21 15:02 ` 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-37152-28872@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