From: "Andreas Färber" <afaerber@suse.de>
To: Wincy Van <fanwenyi0529@live.com>
Cc: qemu-devel@nongnu.org, kvm <kvm@vger.kernel.org>,
Stefan Weil <sw@weilnetz.de>
Subject: Re: [Qemu-devel] Cross-Platform KVM
Date: Wed, 21 Aug 2013 20:48:49 +0200 [thread overview]
Message-ID: <52150B91.7020705@suse.de> (raw)
In-Reply-To: <BAY405-EAS13634B5E69213B91666002FA8470@phx.gbl>
Hi,
Am 16.08.2013 09:41, schrieb Wincy Van:
> Hi,there:
>
> I have implemented a version of cross-platform KVM. Now, it can
> works on Linux and Windows(kernel version 7600-9200, amd64). Is it
> useful? If so, I want make it as a branch of current KVM. Here are some
> screenshots:
Let's CC the KVM mailing list.
More telling than screenshots would be some info about your code! Is
there a public Git repository to look at? Is it based on a current
kvm.git or some older Win32 KVM fork on SourceForge? If so, how invasive
are your changes? Or is it a clean-room implementation of your own
against the header/ioctl interface? How does it work technically? etc.
Regards,
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
WARNING: multiple messages have this Message-ID (diff)
From: "Andreas Färber" <afaerber@suse.de>
To: Wincy Van <fanwenyi0529@live.com>
Cc: Stefan Weil <sw@weilnetz.de>,
qemu-devel@nongnu.org, kvm <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] Cross-Platform KVM
Date: Wed, 21 Aug 2013 20:48:49 +0200 [thread overview]
Message-ID: <52150B91.7020705@suse.de> (raw)
In-Reply-To: <BAY405-EAS13634B5E69213B91666002FA8470@phx.gbl>
Hi,
Am 16.08.2013 09:41, schrieb Wincy Van:
> Hi,there:
>
> I have implemented a version of cross-platform KVM. Now, it can
> works on Linux and Windows(kernel version 7600-9200, amd64). Is it
> useful? If so, I want make it as a branch of current KVM. Here are some
> screenshots:
Let's CC the KVM mailing list.
More telling than screenshots would be some info about your code! Is
there a public Git repository to look at? Is it based on a current
kvm.git or some older Win32 KVM fork on SourceForge? If so, how invasive
are your changes? Or is it a clean-room implementation of your own
against the header/ioctl interface? How does it work technically? etc.
Regards,
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2013-08-21 18:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-16 7:41 [Qemu-devel] Cross-Platform KVM Wincy Van
2013-08-21 18:48 ` Andreas Färber [this message]
2013-08-21 18:48 ` Andreas Färber
2013-09-27 10:11 ` 答复: " Wincy Van
2013-09-27 10:11 ` [Qemu-devel] " Wincy Van
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=52150B91.7020705@suse.de \
--to=afaerber@suse.de \
--cc=fanwenyi0529@live.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
/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.