All of lore.kernel.org
 help / color / mirror / Atom feed
From: 韦理 <knight99@mails.tsinghua.edu.cn>
To: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Help:System crash when a large file is copied.
Date: Thu, 31 May 2007 17:16:57 +0800	[thread overview]
Message-ID: <B1929468828188.11462@mail2> (raw)

Hi everyone


I am trying to run qemu(v0.8.2) on a diskless linux system whose root file system is NFS. The disk image of Qemu is located on the NFS server. But we found the guest os  would crash down if a large file (e.g. 200M) is replicated to emulate hard disk. I have tested serveral guest os such as WinXp SP2, linux(kernel 2.6) and this problem always happens. And I also copy lager files on guest os which runs on normal linux (Disk image is located on local disk) and it's alright. I guess maybe it is caused by IO rate of NFS is not match the hard disk emulated by qemu? I don't kow whether it's reasonable, since there is nothing on the log about this problem.Please give me some advices to find the reason and fix this problem. Thanks a lot.


				 Wei Li 

          knight99@mails.tsinghua.edu.cn
          2007-05-31

                 reply	other threads:[~2007-05-31  9:19 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=B1929468828188.11462@mail2 \
    --to=knight99@mails.tsinghua.edu.cn \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.