VMware Cloud Community
phoneder
Contributor
Contributor
Jump to solution

Licensing problems with evaluation license

Hi!

I have downloaded and installed Virtual Center (2.0.2) on a Windows Server and ESX (3.0.2) on another server. Additionally I received two license files, a host only license file for ESX (VI_SingleHost.lic) and one for virtual center (VI_Centralized_Plus_VCMS.lic).

ESX is running properly (including virtual machines running properly) with the host only file and also with the license server. At the license server I imported the VI_Centralized_Plus_VCMS.lic license file and reloaded the server.

I can successfully connect to both ESX and virtual center with the virtual infrastructure client. The problem now is that I cannot add/connect the esx host to the datacenter in the virtual center. The error message I get is:

"Connection failed for 192.168.0.223 in dc0: Not enough CPU licenses"[/b]

(where 192.168.0.223 is the test ESX and dc0 is the test virtual datacenter in virtual center)

Some more license information for you:

1. output of the lmtools[/b]

\----


Status

\----


Flexible License Manager status on Tue 8/21/2007 13:05

\[Detecting lmgrd processes...]

License server status: 27000@test04

License file(s) on test04: C:\Programme\VMware\VMware License Server\Licenses\vmware.lic:

test04: license server UP (MASTER) v10.1

Vendor daemon status (on test04):

VMWARELM: UP v10.1

Feature usage info:

Users of PROD_VC: (Total of 1 license issued; Total of 1 license in use)

"PROD_VC" v2005.05, vendor: VMWARELM

floating license

SYSTEM test04 test04 (v2005.05) (test04/27000 101), start Tue 8/21 11:38

Users of PROD_ESX_FULL: (Total of 16 licenses issued; Total of 1 license in use)

"PROD_ESX_FULL" v2005.05, vendor: VMWARELM

floating license

root esxhome /dev/tty (v2005.05) (test04/27000 303), start Tue 8/21 13:00

Users of ESX_FULL_BACKUP: (Total of 16 licenses issued; Total of 1 license in use)

"ESX_FULL_BACKUP" v2005.05, vendor: VMWARELM

floating license

root esxhome /dev/tty (v2005.05) (test04/27000 202), start Tue 8/21 13:00

Users of VC_ESXHOST: (Total of 16 licenses issued; Total of 0 licenses in use)

Users of VC_VMOTION: (Total of 16 licenses issued; Total of 0 licenses in use)

Users of VC_DAS: (Total of 16 licenses issued; Total of 0 licenses in use)

Users of VC_DRS: (Total of 16 licenses issued; Total of 0 licenses in use)

2. license status in the virtual center (reflecting the status query)[/b] (remaining/total):

VirtualCenter Management Server (0/1)

VirtualCenter Agent for ESX Server (16/16)

VMotion (16/16)

VMware HA (16/16)

VMware DRS (16/16)

ESX Server Standard (15/16)

VMware Consolidated Backup (15/16)

3. license info in the ESX[/b]

ESX Server Standard Licensed for 1 CPU

iSCSI Usage

SAN Usage

Up to 4-way virtual SMP

NAS Usage

Add-Ons: VMware Consolidated Backup Licensed for 1 CPU

The hardware of the ESX is a core 2 quad (so only one socket).

What could the problem be? do you need any more information?

Thanks for your help,

Peter

Reply
0 Kudos
1 Solution

Accepted Solutions
masaki
Virtuoso
Virtuoso
Jump to solution

Nothing useful nor useless.

Ok let's do some considerations on it.

\[2007-08-21 19:19:47.086 'TaskManager' 49257392 info] Task Completed : haTask-ha-folder-root-vim.host.LocalAccountManager.createUser-48

\[2007-08-21 19:19:47.086 'Vmomi' 49257392 info] Activation \[N5Vmomi10ActivationE:0x9ec5bf0] : Invoke done \[createUser] on \[vim.host.LocalAccountManager:ha-localacctmgr]

\[2007-08-21 19:19:47.086 'Vmomi' 49257392 info] Throw vim.fault.AlreadyExists

Did you set HA on a cluster ??

If so the account already exist.

"2007-08-21 19:19:51.026 'vm:/vmfs/volumes/54dccdcc-e1686579/ubuntu/Ubuntu.vmx' 89033648 error] Disk was not opened successfully. Backing type unknown. "

There is a problem with this vm's disk. Try removing the vm from the inventory but don't erase the disks.

Try doing the same operations with vm switched off.

Try rebooting ESX HOST or killing hostd ps -ef | grep hostd -> kill hostd pid

Always remove the old host entry from the inventory before any try!

View solution in original post

Reply
0 Kudos
21 Replies
esiebert7625
Immortal
Immortal
Jump to solution

Try connecting to the ESX server and removing the Host license first. Then go back to VC and add the ESX server and license it.

Reply
0 Kudos
masaki
Virtuoso
Virtuoso
Jump to solution

There is one ESX Server Standard in use.

So the HOst should be already added.

Don't you see it under Hosts & Clusters?

You should succeed adding the ESX HOST with the host license too then you should change it.

try reverting the ESX license to host licensing and then try again.

Connceting the HOSt with VI client what do you see under Configuration -> licensed features -> License Sources?

Message was edited by:

masaki

Reply
0 Kudos
phoneder
Contributor
Contributor
Jump to solution

@esiebert7625

I just tried to release the license held by esx and then re-added the esx in the virtual center, but I get the some error message

@masaki

yes, there is a standard esx server in use if I select the license server as license source at the esx. I already tried both, a host license file (then the count in the virtual center is 16 and not 15) and using the license server.

The problem remains, neither host licensing nor license server licensing works. I even tried both ways with the "Change host license server settings ..." disabled and enabled, neither works.

so answering your question: depending on host licensing or license server I see either "host license file: Installed" or my license server ip (which is my virtual center ip)

Thanks,

Peter

Reply
0 Kudos
masaki
Virtuoso
Virtuoso
Jump to solution

1. Try re-reading the license file from LMTOOLS.

2. Check your HOST's system time. If not syncronized could lead to unpredictable behaviour.

Reply
0 Kudos
phoneder
Contributor
Contributor
Jump to solution

Hi!

thanks for the tip with time, but it does not help, I even restarted both of them (ESX and virtual center) to make sure everything is aware of the time changes. Re-reading the license file from LMTOOLS does not change the server status query and also does not solve the problem.

The strange thing is that I can enter the details in the add host dialog/wizard and then it displays the virtual machines running on the ESX, then I can chose the datacenter and then after pressing ok it displays the error message, shouldn't it already know earlier?

Thanks,

Peter

Reply
0 Kudos
masaki
Virtuoso
Virtuoso
Jump to solution

Oh yes it's strange indeed.

Try making a new datacenter and put the host on the new one.

Set the Name resolution too (c:\windows\system32\drivers\etc\hosts file at least) and try adding with host name and not ip

Reply
0 Kudos
phoneder
Contributor
Contributor
Jump to solution

I tried to create a new datacenter -> no difference, still not working

same with name resolution, I added all hosts correctly to our internal dns server.

I also just tried to install virtual center on my windows XP PC, no difference.

is there any kind of vmware support to call for evaluating the products? the website states that no support is available, but I have not been able to get esx + virtualcenter running now for quite a long time.

thanks anyway,

Peter

Reply
0 Kudos
masaki
Virtuoso
Virtuoso
Jump to solution

no support for evaluation.

Well let's see if we find any info in the logs.

Post your VC logs here.

Reply
0 Kudos
phoneder
Contributor
Contributor
Jump to solution

ok, here we go Smiley Happy

system log:[/b]

Type Time Description

info 21.08.2007 17:03:48 Alarm Host connection state on esxhome.intranet.hlw.co.at changed from Gray to Green

info 21.08.2007 16:57:37 Created alarm Virtual Machine Memory Usage on Datacenters

info 21.08.2007 16:57:37 Created alarm Virtual Machine CPU Usage on Datacenters

info 21.08.2007 16:57:37 Created alarm Host Memory Usage on Datacenters

info 21.08.2007 16:57:37 Created alarm Host CPU Usage on Datacenters

info 21.08.2007 16:57:37 Created alarm Host connection state on Datacenters

info 21.08.2007 16:57:36 License server 27000@localhost is available

info 21.08.2007 16:57:34 VirtualCenter started

user log (all users):[/b]

Type Time Description

error 21.08.2007 17:03:53 Connection failed for esxhome in test: Not enough CPU licenses

info 21.08.2007 17:03:46 Task: Add Standalone Host

info 21.08.2007 17:03:16 Task: Rename Datacenter

info 21.08.2007 17:03:14 Task: Create Datacenter

info 21.08.2007 17:03:02 User peter@127.0.0.1 logged in

Reply
0 Kudos
masaki
Virtuoso
Virtuoso
Jump to solution

Well can you

ping esxhome from VC Server?

can you telnet on port 902 and 903, 27000 and 27010 esxhome?

Message was edited by:

masaki

Reply
0 Kudos
phoneder
Contributor
Contributor
Jump to solution

yes, I can ping esxhome and I can reach ports 902 and 903, not the others (should I be able to reach them? they are the licensing ports on the virtual center aren't they?)

Message was edited by:

phoneder

Reply
0 Kudos
masaki
Virtuoso
Virtuoso
Jump to solution

Yes they are.

run this from VC server:

netstat -n

look for connections on 27000 and 27010 ports.

Reply
0 Kudos
phoneder
Contributor
Contributor
Jump to solution

they are in listening state on 0.0.0.0, so should be reachable from any other host.

When I use the license server on the ESX computer it is able to communicate with the license server (e.g. the count like posted in my first post changed from 16 to 15, also the VI client directly connected to ESX shows the right license features)

Reply
0 Kudos
masaki
Virtuoso
Virtuoso
Jump to solution

We have only to check ESX server logs.

In particular vpxa.log and hostd.log should be interesting.

You can try restarting host agents too:

service vmware-vpxa restart

service mgmt-vmware restart

Reply
0 Kudos
phoneder
Contributor
Contributor
Jump to solution

restarting the services did not help, here are the logs:

hostd.log (exactly the part retrieved by tail -f white trying to add the server in the virtual center):[/b]

\[2007-08-21 19:19:41.307 'App' 37591984 verbose] Accepted authd connection from: 192.168.0.2:1337

\[2007-08-21 19:19:41.535 'TaskManager' 15936432 info] Task Created : haTask--vim.SessionManager.login-43

\[2007-08-21 19:19:41.539 'Vimsvc' 15936432 info] \[Auth]: User root

\[2007-08-21 19:19:41.539 'ha-eventmgr' 15936432 info] Event 6 : User root@192.168.0.2 logged in

\[2007-08-21 19:19:41.539 'TaskManager' 15936432 info] Task Completed : haTask--vim.SessionManager.login-43

\[2007-08-21 19:19:42.564 'vm:/vmfs/volumes/54dccdcc-e1686579/vm-xp0/vm-xp0.vmx' 89033648 verbose] Retrieved current power state from foundry 0

\[2007-08-21 19:19:42.565 'vm:/vmfs/volumes/54dccdcc-e1686579/vm-xp0/vm-xp0.vmx' 89033648 verbose] Retrieved Summary info

\[2007-08-21 19:19:42.565 'vm:/vmfs/volumes/46b7c54a-b60494e4-b501-001bfc0b81da/vm-xp1/vm-xp1.vmx' 89033648 verbose] Retrieved current power state from foundry 0

\[2007-08-21 19:19:42.565 'vm:/vmfs/volumes/46b7c54a-b60494e4-b501-001bfc0b81da/vm-xp1/vm-xp1.vmx' 89033648 verbose] Retrieved Summary info

\[2007-08-21 19:19:42.565 'vm:/vmfs/volumes/54dccdcc-e1686579/ubuntu/Ubuntu.vmx' 89033648 verbose] Retrieved current power state from foundry 0

\[2007-08-21 19:19:42.565 'vm:/vmfs/volumes/54dccdcc-e1686579/ubuntu/Ubuntu.vmx' 89033648 verbose] Retrieved Summary info

\[2007-08-21 19:19:42.645 'ha-eventmgr' 89033648 info] Event 7 : User root logged out

\[2007-08-21 19:19:42.645 'VmdbAdapter' 89033648 verbose] Removed vmdb connection /db/connection/#5/

\[2007-08-21 19:19:46.617 'App' 49257392 verbose] Accepted authd connection from: 192.168.0.2:1339

\[2007-08-21 19:19:46.874 'TaskManager' 49257392 info] Task Created : haTask--vim.SessionManager.login-47

\[2007-08-21 19:19:46.878 'Vimsvc' 49257392 info] \[Auth]: User root

\[2007-08-21 19:19:46.878 'ha-eventmgr' 49257392 info] Event 8 : User root@192.168.0.2 logged in

\[2007-08-21 19:19:46.878 'TaskManager' 49257392 info] Task Completed : haTask--vim.SessionManager.login-47

\[2007-08-21 19:19:47.085 'TaskManager' 49257392 info] Task Created : haTask-ha-folder-root-vim.host.LocalAccountManager.createUser-48

\[2007-08-21 19:19:47.086 'TaskManager' 49257392 info] Task Completed : haTask-ha-folder-root-vim.host.LocalAccountManager.createUser-48

\[2007-08-21 19:19:47.086 'Vmomi' 49257392 info] Activation \[N5Vmomi10ActivationE:0x9ec5bf0] : Invoke done \[createUser] on \[vim.host.LocalAccountManager:ha-localacctmgr]

\[2007-08-21 19:19:47.086 'Vmomi' 49257392 info] Throw vim.fault.AlreadyExists

\[2007-08-21 19:19:47.086 'Vmomi' 49257392 info] Result:

(vim.fault.AlreadyExists) {

name = "vpxuser"

msg = ""

}

\[2007-08-21 19:19:47.275 'TaskManager' 49257392 info] Task Created : haTask-ha-folder-root-vim.host.LocalAccountManager.updateUser-49

\[2007-08-21 19:19:47.311 'TaskManager' 49257392 info] Task Completed : haTask-ha-folder-root-vim.host.LocalAccountManager.updateUser-49

\[2007-08-21 19:19:47.476 'TaskManager' 20102064 info] Task Created : haTask--vim.AuthorizationManager.setEntityPermissions-50

\[2007-08-21 19:19:47.478 'TaskManager' 20102064 info] Task Completed : haTask--vim.AuthorizationManager.setEntityPermissions-50

\[2007-08-21 19:19:47.479 'Vimsvc' 20102064 info] \[Auth]: User vpxuser

\[2007-08-21 19:19:48.535 'ha-eventmgr' 89033648 info] Event 9 : User root logged out

\[2007-08-21 19:19:48.535 'VmdbAdapter' 89033648 verbose] Removed vmdb connection /db/connection/#6/

\[2007-08-21 19:19:49.994 'Locale' 15936432 warning] Default resource used for 'FirewallInfo.activeDirectorKerberos.label' expected in module 'host'.

\[2007-08-21 19:19:49.994 'Locale' 15936432 warning] Default resource used for 'FirewallInfo.kerberos.label' expected in module 'host'.

\[2007-08-21 19:19:50.747 'EnvironmentBrowser' 49257392 info] Hw info file: /etc/vmware/hostd/hwInfo.xml

\[2007-08-21 19:19:50.750 'EnvironmentBrowser' 49257392 info] Config target info loaded

\[2007-08-21 19:19:50.830 'vm:/vmfs/volumes/54dccdcc-e1686579/vm-xp0/vm-xp0.vmx' 3076448384 verbose] Retrieved current power state from foundry 0

\[2007-08-21 19:19:50.831 'vm:/vmfs/volumes/54dccdcc-e1686579/vm-xp0/vm-xp0.vmx' 3076448384 verbose] Retrieved Summary info

\[2007-08-21 19:19:50.927 'vm:/vmfs/volumes/46b7c54a-b60494e4-b501-001bfc0b81da/vm-xp1/vm-xp1.vmx' 15936432 verbose] Retrieved current power state from foundry 0

\[2007-08-21 19:19:50.927 'vm:/vmfs/volumes/46b7c54a-b60494e4-b501-001bfc0b81da/vm-xp1/vm-xp1.vmx' 15936432 verbose] Retrieved Summary info

\[2007-08-21 19:19:51.011 'vm:/vmfs/volumes/54dccdcc-e1686579/ubuntu/Ubuntu.vmx' 104663984 verbose] Retrieved current power state from foundry 0

\[2007-08-21 19:19:51.011 'vm:/vmfs/volumes/54dccdcc-e1686579/ubuntu/Ubuntu.vmx' 104663984 verbose] Retrieved Summary info

\[2007-08-21 19:19:51.026 'vm:/vmfs/volumes/54dccdcc-e1686579/ubuntu/Ubuntu.vmx' 89033648 error] Disk was not opened successfully. Backing type unknown.

\[2007-08-21 19:19:51.027 'App' 89033648 warning] Failed to serialize result of method vim.VirtualMachine.GetLayout: Not initialized: vim.vm.FileLayout.DiskLayout[] disk.diskFile

\[2007-08-21 19:19:51.027 'Vmomi' 89033648 info] Activation \[N5Vmomi10ActivationE:0x9f604e8] : Invoke done \[GetLayout] on \[vim.VirtualMachine:48]

\[2007-08-21 19:19:51.027 'Vmomi' 89033648 info] Throw vmodl.fault.SystemError

\[2007-08-21 19:19:51.027 'Vmomi' 89033648 info] Result:

(vmodl.fault.SystemError) {

reason = "Failed to serialize result"

msg = ""

}

\[2007-08-21 19:19:51.041 'vm:/vmfs/volumes/54dccdcc-e1686579/vm-xp0/vm-xp0.vmx' 15936432 verbose] Retrieved current power state from foundry 0

\[2007-08-21 19:19:51.041 'vm:/vmfs/volumes/46b7c54a-b60494e4-b501-001bfc0b81da/vm-xp1/vm-xp1.vmx' 15936432 verbose] Retrieved current power state from foundry 0

\[2007-08-21 19:19:51.041 'vm:/vmfs/volumes/54dccdcc-e1686579/ubuntu/Ubuntu.vmx' 15936432 verbose] Retrieved current power state from foundry 0

here the vpxa.log at exactly the same time:[/b]

\[2007-08-21 19:19:40.825 'App' 5372848 info] \[VpxLRO] -- BEGIN task-internal-5 -- -- \[vpxa:getVpxaInfo]

\[2007-08-21 19:19:40.825 'App' 5372848 info] \[VpxLRO] -- FINISH task-internal-5 -- -- \[vpxa:getVpxaInfo]

\[2007-08-21 19:19:46.205 'App' 10247088 info] \[VpxLRO] -- BEGIN task-internal-6 -- -- \[vpxa:getVpxaInfo]

\[2007-08-21 19:19:46.205 'App' 10247088 info] \[VpxLRO] -- FINISH task-internal-6 -- -- \[vpxa:getVpxaInfo]

\[2007-08-21 19:19:48.895 'App' 12454832 info] \[VpxLRO] -- BEGIN task-internal-7 -- -- \[vpxa:retrieveTaskManager]

\[2007-08-21 19:19:48.895 'App' 12454832 info] \[VpxLRO] -- FINISH task-internal-7 -- -- \[vpxa:retrieveTaskManager]

\[2007-08-21 19:19:49.396 'App' 13507504 info] \[VpxLRO] -- BEGIN task-internal-8 -- -- \[vpxa:getChanges]

\[2007-08-21 19:19:51.034 'App' 13507504 warning] ============BEGIN FAILED METHOD CALL DUMP============

\[2007-08-21 19:19:51.034 'App' 13507504 warning] Invoking \[GetLayout] on \[vim.VirtualMachine:48]

\[2007-08-21 19:19:51.034 'App' 13507504 warning] Fault Msg: "A general system error occured: Failed to serialize result"

\[2007-08-21 19:19:51.034 'App' 13507504 warning] ============END FAILED METHOD CALL DUMP============

\[2007-08-21 19:19:51.034 'App' 13507504 error] \[vm.GetLayout] Received exception in GetLayout: vmodl.fault.SystemError

\[2007-08-21 19:19:51.269 'App' 13507504 info] \[VpxLRO] -- FINISH task-internal-8 -- -- \[vpxa:getChanges]

Reply
0 Kudos
masaki
Virtuoso
Virtuoso
Jump to solution

Nothing useful nor useless.

Ok let's do some considerations on it.

\[2007-08-21 19:19:47.086 'TaskManager' 49257392 info] Task Completed : haTask-ha-folder-root-vim.host.LocalAccountManager.createUser-48

\[2007-08-21 19:19:47.086 'Vmomi' 49257392 info] Activation \[N5Vmomi10ActivationE:0x9ec5bf0] : Invoke done \[createUser] on \[vim.host.LocalAccountManager:ha-localacctmgr]

\[2007-08-21 19:19:47.086 'Vmomi' 49257392 info] Throw vim.fault.AlreadyExists

Did you set HA on a cluster ??

If so the account already exist.

"2007-08-21 19:19:51.026 'vm:/vmfs/volumes/54dccdcc-e1686579/ubuntu/Ubuntu.vmx' 89033648 error] Disk was not opened successfully. Backing type unknown. "

There is a problem with this vm's disk. Try removing the vm from the inventory but don't erase the disks.

Try doing the same operations with vm switched off.

Try rebooting ESX HOST or killing hostd ps -ef | grep hostd -> kill hostd pid

Always remove the old host entry from the inventory before any try!

Reply
0 Kudos
phoneder
Contributor
Contributor
Jump to solution

thanks for your comments!

what is HA? I don't have a cluster, which account do you mean?

I tried removing all virtual machines from the esx repository, then I was able to add the ESX to the virtual center. After that I added a new virtual machine through the VI client connected to virtual center, this still worked.

Starting a virtual machine works now too (I just set the license mode to unlicensed in the ESX yesterday night and had to change that back to ESX Standard right now).

So the resolution to the problem is: do not add an ESX to virtual center if there are any virtual machines already available? or was it the problem with the virtual machine disk you found in my log files?

thanks a lot anyway!

Message was edited by:

phoneder

Reply
0 Kudos
masaki
Virtuoso
Virtuoso
Jump to solution

Thanks are welcome but If you finda nay answer helpful please assign points!

HA stands for High Availability and is a VI3 feature that in case of HOSt fault starts vms on another HOST of the same cluster.

I can't say if the problem is about the vm's corrupted disk or that there was vm started on the HOST.

You can try if you want:

Remove the host

start some vm

Readd the HOST

If it works the problem was the vm's corrupted disk.

Let me know

phoneder
Contributor
Contributor
Jump to solution

Hi!

thanks a lot, now even removing and adding with a running virtual machine works, it really seems like it was an issue with the disk image.

The interesting thing is that this ubuntu linux disk image was on an NFS server, does this imply further problems? All the other virtual machines were directly on the local datastore.

Reply
0 Kudos