Thanks for replying ;) At the moment I had to stay with VBox 2.2.x, because 3.x was a panic at the time of deployment. Problem is, 2.2.x does not support multiprocessors, and my 12 cores cannot be allocated into the virtual machines. Second problem is windows 2003 machines are installed with single processor kernel, maybe bringing problems when I'll switch to 3.x and multiprocessor.
My typical situation is a Solaris host running base services like firewall, dns, gateway, dual network (lan and wan), network backup ecc. This Solaris host will run the VBox machines (or the xen hypervisor) I usually have 3 guests: 2 Solaris and 1 Windows. One Solaris is for all the internet stuff (cyrus, postfix, spamassassin, clamd, proxy, apache, tomcat ecc. ecc.). Second Solaris is for legacy applications (old style legacy). One windows is for LAN Windows Domain. The host takes care of all the network protection and stuff to direct traffic between LAN, WAN and Virtual Machines, via ipfilter. I'm having problems of performance on the Windows DC. Every time I dcpromo a virtualized machine, it slows down a lot, and DC tools are a pain (takes 1-5 mins to open DC users, freezing the machine until open). This happen always, with simple straightforward domain, never happened on bare metal. On Solaris guests, sharings with samba are very slow, sometimes producing error on high network traffic. Can't say if 3.x would help me at the moment, as 3.0.x was a real pain (crashes everywhere), and I'm waiting to see people happy about new releases. I was hoping xVM would take me out of this hell... :) -- This message posted from opensolaris.org _______________________________________________ xen-discuss mailing list [email protected]
