From: Weidong Han <weidong.han@intel.com>
To: Carsten Aulbert <carsten.aulbert@aei.mpg.de>
Cc: "kvm@vger.kernel.org ; Fede [slashack@gmail.com]; Jurgen Baier
[Jurgen.Baier@cdu.edu.au]" <kvm@vger.kernel.org>
Subject: Re: Direct access to GPGPU do-able?
Date: Tue, 01 Dec 2009 16:45:59 +0800 [thread overview]
Message-ID: <4B14D7C7.5010304@intel.com> (raw)
In-Reply-To: <200912010808.07998.carsten.aulbert@aei.mpg.de>
Carsten Aulbert wrote:
> 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?
>
KVM already supports device assignment (e.g. NIC) to guest, but graphics
card assignment is not supported yet.
Federico, you said you were porting xen graphics assignment patches to
kvm, what's your progress?
Regards,
Weidong
> Cheers
>
> Carsten
>
>
next prev parent reply other threads:[~2009-12-01 8:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-01 7:08 Direct access to GPGPU do-able? Carsten Aulbert
2009-12-01 8:45 ` Weidong Han [this message]
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=4B14D7C7.5010304@intel.com \
--to=weidong.han@intel.com \
--cc=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