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 -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
