From: Dor Laor <dlaor@redhat.com>
To: "Alpár Török" <torokalpar@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: Virtio and WinXP (disk drivers)
Date: Wed, 25 Feb 2009 14:16:09 +0200 [thread overview]
Message-ID: <49A53689.5010501@redhat.com> (raw)
In-Reply-To: <8d3051340902250403p195af7cfyf19c2beccc1333b5@mail.gmail.com>
Alpár Török wrote:
> Hi,
>
> First of all please allow me to salute the community since this is my
> first post.
>
Congratulations, hoping for the next ones :)
> Now my problem. I have been using KVM to conduct tests for various
> software on windows, so far it worked out just fine. I use savevm and
> loadvm to assure that the VM is in the same state for each test. I do
> a savevm manually, then start the automatic tests.
>
> Lately i was trying to optimize parts of my tests, to increase the throughput.
>
> First the network I/O was slow with the default device, and i needed
> to copy some files to the VM for each test. The virtio network driver
> was fast, but with my bridge networking, on Win XP, after starting the
> VM with loadvm. This isn't such a big issue since i then started using
> e1000 device, and speed increased. I am not sure just how much would
> virtio be faster, so the question remains : Doesn't virtio work with
> loadvm/savevm, or (most probably) am i doing something wrong?
>
Indeed virtio performs better than e1000.
It should work, please provide host kernel version, kvm version, virtio
net version and
windows guest type. Also the cmdline and monitor command will help.
> The second issue, even a greather one, is disk access speed in the VM.
> Again i have looked at virtio, but it seems that there is no Win
> direver. Is that so? What can i do to improove disk access
> performance?
>
>
We have beta code for windows pv block. We plan to publish them as soon
they will be rock stable. Scsi emulation also exist but might not be
100% stable.
> The final issue isn't related to performance. With the e1000 device,
> accessing or writing files on a samba share from the host failes
> saying that the file doesn't exists, (the file exists, i am sure).
> This doesn't happen all that often, less than 1% of the time, but it's
> rather anolying because it influences the tests. it seems to be happen
> randomly, i caoudm't identify a factor that might be causing it.
>
>
Seems like a samba related bug and not necessarily network bug.
> Thank you in advance for your advices.
>
> --
> Alpar Torok
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2009-02-25 12:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8d3051340902240144h18568e0etf9c0cef5dbdac1e4@mail.gmail.com>
2009-02-25 12:03 ` Virtio and WinXP (disk drivers) Alpár Török
2009-02-25 12:16 ` Dor Laor [this message]
2009-02-25 13:43 ` Alpár Török
2009-02-25 15:52 ` Tomasz Chmielewski
2009-02-25 16:20 ` Alpár Török
2009-02-25 16:53 ` Tomasz Chmielewski
2009-02-25 17:04 ` Alpár Török
2009-03-02 10:07 ` Dor Laor
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=49A53689.5010501@redhat.com \
--to=dlaor@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=torokalpar@gmail.com \
/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