From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Tim Deegan <Tim.Deegan@citrix.com>
Cc: Nathan Eisenberg <nathan@atlasnetworks.us>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"Xen-users@lists.xensource.com" <Xen-users@lists.xensource.com>
Subject: Re: Re: [Xen-users] Xen viridian support/features
Date: Thu, 23 Jul 2009 14:28:39 -0700 [thread overview]
Message-ID: <4A68D607.10606@goop.org> (raw)
In-Reply-To: <20090723142715.GG5235@york.uk.xensource.com>
On 07/23/09 07:27, Tim Deegan wrote:
> At 15:19 +0100 on 23 Jul (1248362393), Pasi K?rkk?inen wrote:
>
>> Any plans to write support for paravirtual viridian disk/network backends?
>> (I assume they have stuff like that implemented in hyper-v).
>>
>
> I don't think anyone's doing that, but there is a choice of Xen PV
> drivers for Windows that will do the job. Are the PV driver interfaces
> even public? I don't remember seeing them in the hyper-v spec, though I
> haven't read the latest version.
>
They were implicitly published, at least to some extent, in the form of
the big HyperV PV driver dump for Linux. But I don't think those
drivers are very featureful yet, though they claim to be planning to
release more updates.
J
next prev parent reply other threads:[~2009-07-23 21:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-20 20:44 News - Microsoft Submits Drivers for Paravirtualization Nathan Eisenberg
2009-07-20 20:50 ` [Xen-devel] " Thomas DuBuisson
2009-07-20 23:40 ` Alan Cox
2009-07-21 7:23 ` Pasi Kärkkäinen
2009-07-21 17:15 ` [Xen-devel] Re: Xen viridian support/features Pasi Kärkkäinen
2009-07-23 13:57 ` Pasi Kärkkäinen
2009-07-23 14:11 ` Re: [Xen-users] " Tim Deegan
2009-07-23 14:19 ` Pasi Kärkkäinen
2009-07-23 14:27 ` Tim Deegan
2009-07-23 21:28 ` Jeremy Fitzhardinge [this message]
2009-07-24 14:40 ` [Xen-devel] " Florian Manschwetus
2009-07-24 19:31 ` Re: [Xen-users] " Andrew Lyon
2009-07-24 19:56 ` Florian Manschwetus
2009-07-24 21:29 ` Andrew Lyon
2009-07-24 22:27 ` Florian Manschwetus
2009-07-23 14:45 ` Florian Manschwetus
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=4A68D607.10606@goop.org \
--to=jeremy@goop.org \
--cc=Tim.Deegan@citrix.com \
--cc=Xen-users@lists.xensource.com \
--cc=nathan@atlasnetworks.us \
--cc=xen-devel@lists.xensource.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.