From: Carsten Aulbert <carsten.aulbert@aei.mpg.de>
To: kvm@vger.kernel.org
Subject: Direct access to GPGPU do-able?
Date: Tue, 1 Dec 2009 08:08:07 +0100 [thread overview]
Message-ID: <200912010808.07998.carsten.aulbert@aei.mpg.de> (raw)
Hi,
I'll start with a one-off question here, so please cc me on the reply.
We are running a largish cluster and are currently buying GPGPU systems (Tesla
and soon Fermi based). We will have at least 2 possibly 4 of these cards per
box and have the problem that some codes need different CUDA kernel drivers to
run. As these boxes have 4 CPU cores, 12 GB of memory and CPU-VT support we
thought that this might be solvable by creating (para-) virtualized guests on
the boxes and passing one GPGPU device into a guest at a time. In there we
then can run any kernel/driver combo necessary.
But since my current virtualization experience only stretches to OpenVZ and
VirtualBox (tinkering with Xen a couple of years back), I don't know if KVM is
the right approach here. We need something which we can automatically set-up
via CLI, i.e. starting and stopping the guests need to be fully automatic, we
don't need a graphical environment within the guests, just plain text is good
enough.
What do you think, is looking at KVM the right choice for this? Can we pass a
device directly into a guest?
Cheers
Carsten
--
Dr. Carsten Aulbert - Max Planck Institute for Gravitational Physics
Callinstrasse 38, 30167 Hannover, Germany
Phone/Fax: +49 511 762-17185 / -17193
http://www.top500.org/system/9234 | http://www.top500.org/connfam/6/list/3
next reply other threads:[~2009-12-01 7:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-01 7:08 Carsten Aulbert [this message]
2009-12-01 8:45 ` Direct access to GPGPU do-able? Weidong Han
2009-12-01 18:33 ` Fede
2010-02-25 14:03 ` André Weidemann
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=200912010808.07998.carsten.aulbert@aei.mpg.de \
--to=carsten.aulbert@aei.mpg.de \
--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