From: Erik Rull <erik.rull@rdsoftware.de>
To: Avi Kivity <avi@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: kvm-77 Excessive Disk Access causes real time clock hang!
Date: Mon, 27 Apr 2009 19:19:50 +0200 [thread overview]
Message-ID: <49F5E936.1050706@rdsoftware.de> (raw)
In-Reply-To: <49F55051.1000409@redhat.com>
Hi Avi,
Avi Kivity wrote:
> interface: virtio
> cache: none
> format: raw, using a partition or logical volume
>
> What are you using?
uhm, I'm not sure, I call qemu with:
qemu-system-x86_64 -usb -hda /dev/hda2 -m 1536 -net nic,macaddr=$MACADDR
-net tap,script=/etc/qemu-ifup -no-acpi -monitor stdio -usbdevice tablet
-boot c
The /dev/hda2 is NTFS formatted - does this make sense, because you wrote
sth. with raw...
Maybe another file system would be faster? Or is it ignored by the guest
system?
Best regards,
Erik
next prev parent reply other threads:[~2009-04-27 17:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-24 15:29 kvm-77 Excessive Disk Access causes real time clock hang! Erik Rull
2009-04-24 23:30 ` Marcelo Tosatti
2009-04-26 10:46 ` Avi Kivity
2009-04-26 23:12 ` Erik Rull
2009-04-27 6:27 ` Avi Kivity
2009-04-27 17:19 ` Erik Rull [this message]
2009-04-29 8:21 ` Avi Kivity
2009-05-04 19:30 ` Erik Rull
2009-05-04 19:30 ` Erik Rull
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=49F5E936.1050706@rdsoftware.de \
--to=erik.rull@rdsoftware.de \
--cc=avi@redhat.com \
--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