Great, thanks! Though, this all may be moot. We're considering 5.0 because
4.1 is biting us with its max 6 cores per socket limit (and the nifty new box
I've got has 8 cores/socket). Problem now may be that 5.0 seems to be limited
to 32GB aggregate memory for all VMs, which is a bummer as we've got way more
than that in the box.
The KVM module for VCL can't come soon enough!
That said, thanks again for the info.
On 6 Oct 2011, at 0927h, Andy Kurth wrote:
> NCSU has 1 ESXi 5.0 server running in production. I haven't
> encountered any problems. The VCL 2.2.1 and later code should work.
> The only configuration difference I noticed is that the steps to
> enable SSH are a little different. The authorized_keys file should be
> copied to the ESXi host in the following location:
> On Thu, Oct 6, 2011 at 11:06 AM, Terry McGuire <tmcgu...@ualberta.ca> wrote:
>> Hello VCL folks. I'm considering using VMware ESXi 5.0 (the free version)
>> for a new VCL system I'm setting up, but I'm wondering if there have been
>> changes since 4.1 that will break VCL. Has anyone actually tried this? If
>> so, what have you found?
>> Thanks in advance for any replies.
>> Terry McGuire