From: linux_kvm@proinbox.com
To: "KVM mailing list" <kvm@vger.kernel.org>
Subject: New @ Proxmox: -device, vhost... Docs, notes?
Date: Sat, 13 Nov 2010 19:35:33 -0500 [thread overview]
Message-ID: <1289694933.5624.1405155671@webmail.messagingengine.com> (raw)
Hi Everyone,
I'm impressed with all the activity I see here since joining the list
this year.
It helps to reinforce that I chose the right technology. Thanks.
The -device method & vhost=on option recently became available to us at
the ProxmoxVE project & I'm preparing to start making use of them this
coming week.
I found some docs on linux-kvm.org, and still have a bit to look through
& see what I can find.
I don't want to state on the record that I will or I won't but it's
crossed my mind to assemble something for our wiki, and if I do decide
to it would be nice to have some fresh material.
So I'm just writing to see if anyone would like to share any of your
favorite reference material- ie. links, benchmarks, drawings, diagrams,
etc.
Kind Regards,
-C
next reply other threads:[~2010-11-14 0:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-14 0:35 linux_kvm [this message]
2010-11-15 8:50 ` New @ Proxmox: -device, vhost... Docs, notes? Markus Armbruster
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=1289694933.5624.1405155671@webmail.messagingengine.com \
--to=linux_kvm@proinbox.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