From: Lucio Crusca <lucio@sulweb.org>
To: kvm@vger.kernel.org
Subject: Hardware requirements for SPICEd desktops
Date: Mon, 18 May 2015 18:14:38 +0200 [thread overview]
Message-ID: <555A0FEE.50900@sulweb.org> (raw)
Hello,
I'm considering to build a new server and to use SPICE protocol to
deploy all the Windows guests to the local network.
It's my understanding that:
1. I should create the guests on the server
2. I should use remote-viewer on a minimal desktop linux on the clients
over SPICE protocol
3. I should enable QXL on the server
4. I can get clients USB ports and soundcards working in the guests
Now, assuming I've understood the above correctly, I haven't understood
what are the hardware requirements server and client side:
1. Assuming I assign 4GB of RAM to each guest and that the network has
20 running guests at any given time, should the server have at least
80GB (20 by 4) of RAM or can I "oversell" a bit and bet on the fact that
only few guests will actually use 4GB?
2. What's a reasonable amount of RAM to have installed client-side, for
4GB-RAM guests?
3. Should the clients have a CPU that supports VT-x?
4. Is it possible to have QXL supported on the clients regardless of the
physical video adapter installed?
5. And what about the soundcard support? Will any linux-supported
soundcard do on the clients?
reply other threads:[~2015-05-18 16:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=555A0FEE.50900@sulweb.org \
--to=lucio@sulweb.org \
--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