From: Vadim Rozenfeld <vrozenfe@redhat.com>
To: Kenni Lund <kenni@kelu.dk>
Cc: Yan Vugenfirer <yvugenfi@redhat.com>,
Saul Tamari <stamari@gmail.com>, kvm <kvm@vger.kernel.org>
Subject: Re: MS Window virtio drivers certification status
Date: Mon, 11 Jan 2010 22:15:21 +0200 [thread overview]
Message-ID: <1263240921.2005.48.camel@localhost> (raw)
In-Reply-To: <3b1f68ef1001111143s174a4989md01fa64f435f24d8@mail.gmail.com>
On Mon, 2010-01-11 at 20:43 +0100, Kenni Lund wrote:
> 2010/1/11 Yan Vugenfirer <yvugenfi@redhat.com>:
> >
> >
> >> -----Original Message-----
> >> From: kvm-owner@vger.kernel.org [mailto:kvm-owner@vger.kernel.org] On
> >> Behalf Of Saul Tamari
> >> Sent: Monday, January 11, 2010 6:26 PM
> >> To: Yan Vugenfirer
> >> Cc: kvm
> >> Subject: Re: MS Window virtio drivers certification status
> >>
> >> Hi,
> >>
> >> Are you talking about both network & block drivers?
> >
> > [YV] Yes. Only difference for block - Windows XP certified driver wasn't
> > release with RHEL5.4. It should be in RHEL 5.5.
>
> Will these block drivers for XP be optimized in terms of performance
> or will they, like the current ones, still be slower than the regular
> IDE emulated block devices? [1]
>
> [1] http://article.gmane.org/gmane.comp.emulators.kvm.devel/40762
should be faster.
>
> Best Regards
> Kenni
> --
> 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
prev parent reply other threads:[~2010-01-11 20:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-11 14:49 MS Window virtio drivers certification status Saul Tamari
2010-01-11 15:49 ` Yan Vugenfirer
2010-01-11 16:26 ` Saul Tamari
2010-01-11 16:43 ` Yan Vugenfirer
2010-01-11 19:43 ` Kenni Lund
2010-01-11 20:15 ` Vadim Rozenfeld [this message]
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=1263240921.2005.48.camel@localhost \
--to=vrozenfe@redhat.com \
--cc=kenni@kelu.dk \
--cc=kvm@vger.kernel.org \
--cc=stamari@gmail.com \
--cc=yvugenfi@redhat.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 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.