Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: Michael Waite <mwaite@redhat.com>
To: kvm@vger.kernel.org
Subject: KVM for the enterprise
Date: Fri, 18 Nov 2011 11:25:38 -0500	[thread overview]
Message-ID: <4EC68702.3060804@redhat.com> (raw)

  Hi,
The Open Virtualization Alliance is going to be having a webinar on 
December 8th which is intended to help promote KVM as an enterprise 
class hypervisor. I see so much great engineering work going on to make 
KVM a really robust technology and we want to help tell this story to 
the world-wide audience.

We will have a couple companies presenting how they deployed KVM in 
their infrastructure and the benefits they realized.
There will also be a speaker from IDC discussing virtualization-specific 
performance-enhancing features–like SR-IOV, hugepages, asynchronous I/O 
and more.
If anyone would like to attend this webinar (or help promote it) I have 
posted a link on the OVA site here:
http://www.openvirtualizationalliance.org/news/index.html

Thanks.

----Mike


             reply	other threads:[~2011-11-18 16:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-18 16:25 Michael Waite [this message]
2011-11-19  9:54 ` KVM for the enterprise Christoph Hellwig

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=4EC68702.3060804@redhat.com \
    --to=mwaite@redhat.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