How much resources are you devoting to your VMs?
I got 16 GB ram and 2x Quadcore prosessors with enough power I'd believe. Problem started with the first VM, so i'm definately not out of resourses.
I don't mean how many resources the server has, but how much are you giving to your virtual machine?
I haven't allocated any resource pools, but I figured it gets all avaible resourses. I have only used VMWare workstation before so I'm not sure.
Atleast if I check resources in use I can see Virtual Machine using 2 GB ram and 1 Ghz CPU time to time.
1 person found this helpful
Check the /var/log/vmkernel file - I guess you have a san mismatch.
1 person found this helpful
Another thing to check is your install media and method. Try installing from an ISO, or a different CD. If you are installing from CD, where is the CD, in the ESX server, or on your system?
Once you get one working the way you want you should create a template so you don't have to do a new install every time.
VMware Communities User Moderator
The Windows Install indeed comes from image located in the machine I run client from and not the esx machine. I how ever those are in same lan.
And that wouldn't explain the problems with SP2. I have tried install SP2 from windows update, cd located in esx and copying the cd to the virtual machines local driver. Both get slow when checking the components of the virtual machine.
I checked the file. There were no errors but few warnings.
WARNING: VSCSI: vm 1166: 5843: closing handle 0x2016 with 2 pending cmds, 2 ref count
WARNING: VSCSI: 2837: Ignoring double reset on handle 8214
That seems to be clear.
Last night I made new images of Win2k3 and this time R2. I uploaded the images to the esx server. This morning it was still installing.
Can you try such installation on another blade?
Have you checked the log from this vm?
Can you check how fast (MB/esc.) is your vm cloning (esxtop / d)? That can give us a clue about san throughput/problem.
Logs in Windows or VI Client show nothing really.
Another blade has been ordered and after I get my hands on it, I will try if similar error occurst with it.
I forgot to mention that we didn't purchase virtual center license, so I believe templates are out of question. This is our pilot project. If it fails it would be serious back set on virtualizing in our company.
I couldn't find out with that command about the cloning speed. However I managed to several times crash the client trying to upload files in to the data storage. I sent files earlier using FastScp.
I'm starting to believe that the HBA-card is the reason for this. I can't test it until new one comes. I should get totaly new hardware by next week.
I believe my ESX is now working. I got yet another HBA card and finaly the install of Windows 2k3 went ok. Also updating SP2 went without problems.
It seems that HBA cards are the weakpoint of HP Blade system, because we have had 3 broken cards already.
Thanks for everyone helping.