Slashdot Mirror
Red Hat Open Sources SPICE Desktop Virtualization
laxl writes "Linux vendor Red Hat has open sourced the Simple Protocol for Independent Computing Environment (SPICE) virtual desktop protocol it acquired last year with Qumranet, which used SPICE for its own commercial desktop-virtualization product, called SolidIce. SPICE can be used to deploy virtual desktops from a server out to remote computers, such as desktop PCs and thin-client devices. It is similar to other rendering protocols used for remote desktop management such as Microsoft's Remote Desktop Protocol or Citrix's Independent Computing Architecture. SPICE supports rendering virtual instances of Windows XP and Windows 7, as well as Red Hat Enterprise Linux. According to Red Hat, SPICE has advantages over other protocols in that it can dynamically customize desktop instances to fit specific operating environments. According to the article, most of the SPICE code is available under the GNU GPLv2, though parts are also licensed under LGPL- and BSD-styled licenses."
I wonder what the CHOAM will think about this?
Seriously, SPICE stands for "Simulation Program with Integrated Circuit Emphasis" and is a circuit simulator.
(If this was a couple years ago, I'd rant that UML stands for "Unified Modeling Language" (not User-Mode-Linux), or that X stands for "X Window System" (Not MacOS 10))
This really solves the last remaining hurdle for VDI thin client vertical engineering domain. Going to grab the git source tonight and test it out. Would be cool if an in browser NSAPI based plugin architecture was built on this. Run your thin clients on Google OS ( or something else), and then you can run all your legacy fat clients on your virtual servers and your uses just access them through a browser. I noticed that people have even worked on Javascript level RDP and No-machine client implementations. Obviously a bit slow for real world. Anyone know if KVM has dedicated VDI infrastructure servers yet ? Ged
I currently use NXClient w/Neatx for that kind of remote access/management. It works well with both Linux and Windows backends.
I guess the difference is accessing various os's with a single protocol rather than using NX & RDP (like the NXclient does) + also possibly getting around some of the builtin limitations (available only on certain flavors of Windows, limited # accesses by default etc) of RDP.
Sounds interesting if the performance is decent.
Because it does not matter as both programs are not related at all?
I don't know the fuss about it, I am a IT professional, did some exercises with SPICE (circuit) while in the university and now SPICE (VM) may be interesting for my job as sysadmin. As a sysadmin, I do not need to design circuits anymore, so I don't think I will be ever confused.
Of course, my apologies if your post was just a joke...
Why can't
What about places that might have a need for both SPICEs?
They will need a SPICE rack.
From the summary:
(Emphasis mine). Aha, so it's platform independent? And they support... Two! *badum-ching* operating systems: Windows and Linux. Compare that to VNC, of which it is hard to find an OS that doesn't support it.
8 of 13 people found this answer helpful. Did you?
If so, how does it differ from RDP or NX?
It seems to be better
Graphic commands - processes and transmits 2D graphic commands
Video streaming - heuristically identifies video streams and transmits M-JPEG video streams
Image compression - offers verios compression algorithm that were built specifically for Spice, including QUIC (based on SFALIC), LZ, GLZ (history-based global dictionary), and auto (heuristic compression choice per image)
Hardware cursor - processes and transmits cursor-specific commands
Image, palette and cursor caching - manages client caches to reduce bandwidth requirements
Live migration - supports clients while migrating Spice servers to new hosts, thus avoiding interruptions
Windows drivers - Windows drivers for QXL display device and VDI-port
Multiple monitors
Client for Linux and Window - can be easily ported to additional platform platforms.
Two way audio - supports audio playback and captures; audio data stream is optionally compressed using CELT
Encryption - using OpenSSL
Two mouse modes - provides client (more user-friendly) and server (increased accuracy and fully synchronized) modes
Lip-sync - synchronizes video streams with audio clocks
Spice agent - running on the guest and performs tasks for the client
Sunray's cap at 16
It's more Citrix than RDP or NX. You have a Linux server with multiple qemu/kvm instances, each of which are accessed from a client (Linux/Windows).
The advantage is that you can have multiple clients on a single server, push CPU/GPU-intensive display operations to the client and have access to client-side hardware from within the virtualized server instance.
Normally I'd add a RTFA-sneer, but I read through the site and am only moderately sure I got the above correct. Should be very useful for large-scale Linux desktop deployments however: server-side maintenance with client-side display speed & hardware support. In theory.
This sig is intentionally left blank
This is yet another example of too many to name, of Red Hat being an all-around bunch of warm and fuzzy penguins, guys! And this is so typical of them: buy a proprietary product, and as soon as they decide to do something with it, they open source it first!
RedHat has NEVER deviated from their policy of releasing SRPMS for all their stuff. You can very literally roll your own distro simply by taking their SRPM and compiling them! And a number of groups have done just that: White Box Linux, CentOS and Scientific Linux.
Red Hat employs some of the most prolific contributors to the Linux Kernel and is a vital force in making Linux what it is today. Go Red Hat!
PS: No, I don't work for them, just a very happy customer!
I have no problem with your religion until you decide it's reason to deprive others of the truth.
If the plural of mouse is mice, shouldn't the plural of spouse be spice? /pinky
Buffalo buffalo Buffalo buffalo buffalo buffalo Buffalo buffalo! http://goo.gl/J9bkO
This is not a bad thing. For years, the only alternatives for virtual desktops were either proprietary (ICA comes to mind) or OS-dependent (Sun ALP, MSFT RDP, X, NX), leaving VNC as the only OS-independent option. VNC was (and still is) great, but let's face it, it was never intended to be used for real massive VDI-type deployments, even over the WAN. SPICE is supposed to have a good LAN performance, but still doesn't quite cut it for long latencies over the WAN. May be with this move, SPICE can be improved to also address those use cases.
For now, the most advanced thing I've seen is Teradici's PCoIP protocol that works really well in any environment, and they licensed it to VMware to be used in the new View 4 product line as a pure software implementation (as a disclaimer, I work for VMware, but PCoIP blew my mind way before we did anything with them).
In any case, 2010 is shaping to be the year of the virtual desktop, and competition is a good thing!