From: Stefan Hajnoczi <stefanha@gmail.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: kvm@vger.kernel.org, "Michael S. Tsirkin" <mst@redhat.com>,
ghammer@redhat.com, Markus Armbruster <armbru@redhat.com>,
Jason Wang <jasowang@redhat.com>,
qemu-devel@nongnu.org, linux-kernel@vger.kernel.org,
Alejandro Comisario <alejandro.comisario@mercadolibre.com>
Subject: Re: [Qemu-devel] Massive read only kvm guests when backing file was missing
Date: Fri, 28 Mar 2014 09:47:49 +0100 [thread overview]
Message-ID: <20140328084749.GA11688@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <53351E2C.3070508@msgid.tls.msk.ru>
On Fri, Mar 28, 2014 at 11:01:00AM +0400, Michael Tokarev wrote:
> 27.03.2014 20:14, Alejandro Comisario wrote:
> > Seems like virtio (kvm 1.0) doesnt expose timeout on the guest side
> > (ubuntu 12.04 on host and guest).
> > So, how can i adjust the tinmeout on the guest ?
>
> After a bit more talks on IRC yesterday, it turned out that the situation
> is _much_ more "interesting" than originally described. The OP claims to
> have 10500 guests running off an NFS server, and that after NFS server
> downtime, the "backing files" were disappeared (whatever it means), so
> they had to restore those files. More, the OP didn't even bother to look
> at the guest's dmesg, being busy rebooting all 10500 guests.
>
> > This solution is the most logical one, but i cannot apply it!
> > thanks for all the responses!
>
> I suggested the OP to actually describe the _real_ situation, instead of
> giving random half-pictures, and actually take a look at the actual problem
> as reported in various places (most importantly the guest kernel log), and
> reoirt _those_ hints to the list. I also mentioned that, at least for some
> NFS servers, if a client has a file open on the server, and this file is
> deleted, the server will report error to the client when client tries to
> access that file, and this has nothing at all to do with timeouts of any
> kind.
Thanks for the update and for taking time to help on IRC. I feel you're
being harsh on Alejandro though.
Improving the quality of bug reports is important but it shouldn't be at
the expense of quality of communication. We can't assume that everyone
is an expert in troubleshooting KVM or Linux. Therefore we can't blame
them, which will only drive people away and detract from the community.
TL;DR post logs and error messages +1, berate him -1
Stefan
next prev parent reply other threads:[~2014-03-28 8:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAMrG31z=oy-53Lfya4svhNniD_7Q1YETuHeZsotHj8U5xJNYmw@mail.gmail.com>
2014-03-27 6:41 ` [Qemu-devel] Massive read only kvm guests when backing file was missing Michael S. Tsirkin
2014-03-27 7:36 ` Markus Armbruster
2014-03-27 8:10 ` Michael S. Tsirkin
2014-03-27 8:53 ` Stefan Hajnoczi
2014-03-27 16:13 ` Alejandro Comisario
2014-03-27 16:14 ` Alejandro Comisario
2014-03-28 7:01 ` Michael Tokarev
2014-03-28 8:47 ` Stefan Hajnoczi [this message]
2014-04-01 0:51 ` Alejandro Comisario
2014-04-01 13:52 ` Stefan Hajnoczi
2014-04-01 14:09 ` Alejandro Comisario
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=20140328084749.GA11688@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=alejandro.comisario@mercadolibre.com \
--cc=armbru@redhat.com \
--cc=ghammer@redhat.com \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjt@tls.msk.ru \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.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).