Novell Defends 'Unstable' Xen Claims
daria42 writes "Novell has fired back at Red Hat's claims that the open source Xen virtualization software is not yet ready for enterprise use. 'We had all the major hardware partners that had virtualization hardware like IBM, Intel and AMD. They all stood up and said "Yes, this technology's ready, and we fully support deployments based on Xen and in combination with SUSE Linux Enterprise 10."', Novell's chief technology officer said today. 'So I guess the other vendors would not do that if it weren't ready.'"
Besides Xen, a few other interesting tidbits appear in the article, but are missing from the summary (and, were also missing in the post on Digg... suspiciously).
1. All desktops in Novell have been using OpenOffice for a year now.
2. 80% of desktops in Novell now use Linux (I presume the remainder use Windows).
3. The article mentions some explanations for the recent personell changes in Novell. Not much content, though, just "we are in a different place now and need different people" (where have I heard that before).
Seems odd that Novell would "Fire Back." Unix Shell, where I host my server, has had no end of troubles with Xen. Personally, I have been mostly stable, and the Xen technology is an awesome thing. However, the message on the front page of Unix Shell "Due to lack of Datacenter space, unixshell# has suspended ordering until further notice" is not entirely accurate. If you read the forums, they are waiting until Xen is stable enough to be able to deploy further accounts.
I Do C++
Never used SusE/Novell's version of Xen, but I CAN tell you that Fedora's is not compiled with PAE enabled, so you cannot address more than 4GB of RAM. It seems to me, like you are looking for a pretty serious VM performance/memory allocation. I am in the same situation, and have to recompile Xen from source with PAE enabled to get more the kind of memory allocation that I need.
To save you some searching here's the make command
make XEN_TARGET_X86_PAE=y install
though for 64bit goodness you'll probably have to throw another flag in there.