VMWare ESXi 3.5 on free download

Stolly said:
I think thats the idea yes. Not installed it yet though. I know you can manage it with Virtual Center though, and you use the VI client to manage that.
Click to expand...


J1nxy said:
Yep, you use the VI Client to manage it. You log onto the web interface and pull the client, bash in the IP/Hostname, userid and password and away you go.
Click to expand...

Cheers guys, i wasn't looking forward to managing the whole hog using the cli.

Regards
 
Caged said:
Who wants to compete for the prize of "least suitable ESXi box"? I installed this on a ThinkCentre A52 (P4 3.0Ghz, 4GB RAM) at the weekend and it didn't throw any warnings at all, and is actually running really well.
Click to expand...

Athlon 3800+, A8N-SLI DLX, 2gig PC3200... :|
Built from spares and purely for testing at the moment, seems alright though.
 
The reason it is free is that Microsoft just screwed VMWare on licencing.

if you do run ESX with HA Vmotion clusters you need to buy MS licences for every physical node you have in that HA cluster.

If you run one SQL server (a VM) and have six physical servers in a HA cluster MS say you need to buy 6 SQL licences.

They have done this because Hypervisor can not do the same as Vmotion.

i bet my left leg as soon as MS develop something similar to Vmotion these licencing rules become a lot more relaxed.
 
BTW there is a good bug in ESX3 and 3i with update 2 where you can't power on VMs if the date is after 00.01 on the 12th August...
 
CraigN said:
The reason it is free is that Microsoft just screwed VMWare on licencing.

if you do run ESX with HA Vmotion clusters you need to buy MS licences for every physical node you have in that HA cluster.

If you run one SQL server (a VM) and have six physical servers in a HA cluster MS say you need to buy 6 SQL licences.

They have done this because Hypervisor can not do the same as Vmotion.

i bet my left leg as soon as MS develop something similar to Vmotion these licencing rules become a lot more relaxed.
Click to expand...

Thats how its been for years...
 
CraigN said:
The reason it is free is that Microsoft just screwed VMWare on licencing.

if you do run ESX with HA Vmotion clusters you need to buy MS licences for every physical node you have in that HA cluster.

If you run one SQL server (a VM) and have six physical servers in a HA cluster MS say you need to buy 6 SQL licences.

They have done this because Hypervisor can not do the same as Vmotion.

i bet my left leg as soon as MS develop something similar to Vmotion these licencing rules become a lot more relaxed.
Click to expand...


According to the licence matrix for virtual environments thats only true if you buy Windows Standard. If you buy Windows 2003 Enterprise R2 you only need one licence per 4 VM's.

Have a look at this calculator

http://www.microsoft.com/windowsserver2003/howtobuy/licensing/calculator.mspx

It may not be as bad as you think.
 
I have just installed this and I have run into a problem when creating a datastore

it can see the 2TB raid 5 array but for some reason it says 44GB available! If I go to add the datastore is knows the HDD is blank and reads the capacity as 2TB but the max capiacity of the datastore is still only 44GB!

any ideas?
 
Last edited:
topher said:
I have just installed this and I have run into a problem when creating a datastore

it can see the 2TB raid 5 array but for some reason it says 44GB available! If I go to add the datastore is knows the HDD is blank and reads the capacity as 2TB but the max capiacity of the datastore is still only 44GB!

any ideas?
Click to expand...

Maybe something to do with the block size ? Or is this even before you format the VMFS ?
 
Stolly said:
According to the licence matrix for virtual environments thats only true if you buy Windows Standard. If you buy Windows 2003 Enterprise R2 you only need one licence per 4 VM's.

Have a look at this calculator

http://www.microsoft.com/windowsserver2003/howtobuy/licensing/calculator.mspx

It may not be as bad as you think.
Click to expand...

My understanding is for Windows OS licences you need 1 licence per OS VM for standard 1 OS licence per Processor For Datacentre and 1 OS licence per 2 VMs for enterprise.

That calc is very interesting i will look at it.

the way we got half arround the issue is to make our HA clusters smaller by limiting the hosts they could vmotion on.
 
topher said:
Intel SRCSATAWB it also has 240GB raid 1 array, I am able to create a datastore using the whole 240GB..
Click to expand...

Try using vmkfstools from the service console to create the vmfs might be some wierd bug in vi client...

edit ***

Oh its a thread about ESXi ;)

errrr yeah. let me drink some more coffee and get back to you on that one ;)
 
Last edited:
Haha you know that a vendor has made a big mistake when you receive an email entitled.

"EXTREMELY URGENT PROBLEM WITH ESX 3.5 U2 and ESXi U2 - SECOND UPDATE"

:p
 
Curiosityx said:
Haha you know that a vendor has made a big mistake when you receive an email entitled.

"EXTREMELY URGENT PROBLEM WITH ESX 3.5 U2 and ESXi U2 - SECOND UPDATE"

:p
Click to expand...

no kidding, plus the profuse apologies in the first update email.

They got the patch out yet ?

Dodged a bullet on this one. Just deployed 8 new hosts for a well known customer, but on update 1.
 
Stolly said:
no kidding, plus the profuse apologies in the first update email.

They got the patch out yet ?

Dodged a bullet on this one. Just deployed 8 new hosts for a well known customer, but on update 1.
Click to expand...



Thankfully im only in the testing stages, but i dont see how Vmware can avoid getting taken to court on this one, specially by large HA customers who haven't followed a period of testing prior to deployment.




http://now.eloqua.com/e/es.aspx?s=5...870d30bb&elq=FA2AD1E930EE4972975EDC7D2EE5D6A6

Problem:

An issue has been discovered by many VMware customers and partners with ESX/ESXi 3.5 Update 2 where Virtual Machines fail to power on or VMotion successfully. This problem began to occur on August 12, 2008 for customers that had upgraded to ESX 3.5 Update 2. The problem is caused by a build timeout that was mistakenly left enabled for the release build.
The following message is displayed in the vmware.log file for the virtual machine:
This product has expired. Be sure that your host machine's date and time are set correctly.
There is a more recent version available at the VMware web site: http://www.vmware.com/info?id=4.
--------------

Module License Power on failed.

Affected Products:
- VMware ESX 3.5 Update 2 & ESXi 3.5 Update 2.
- The problem will be seen if ESX350-200806201-UG is applied to a system.
- No other VMware products are affected.
Resolution:
VMware Engineering has produced express patches for impacted customers to resolve the issue.
 
Last edited:
Yeah its a pretty bad state of affairs for them, especially as they've just gained a shed load of publicity releasing ESXi for free and Microsoft pushing for Hyper-V deployments. Publicly posting that this could take 36 hours to fix with global production systems down is not good.

There's a 40 + page thread on fixes / berating VMWare here > http://communities.vmware.com/thread/162377?tstart=0&start=0

Glad we haven't put it into prod, not sure our testing would have caught this one. Looks like a few people were caught out by update manager putting down parts of update 2 which had the problem in....

I hope they learn their lesson quickly.
 
You must log in or register to reply here.
Back
Top Bottom