VMware Cloud Community
Crowdedisland
Contributor
Contributor
Jump to solution

VShere CLient 4 can't connect to ESXi 3.5 host

I wnat to upgrade my ESXi 3.5 host to 4.0. I found the following doc http://www.vm-help.com/esx40i/ESXi40_upgrade_without_virtualcenter.php and folled the instructions

I followed instructions to download the VMware vSphere client and then install the vSphere Host Update Utility. This priocess went fine but I could not get the utilites to then talk to my esxi 3.5 host.

I uninstalled the 4 versiona dn went back to 3.5 adn was able to reconnect with my host.

What am I doing wriong in this process?

Reply
0 Kudos
1 Solution

Accepted Solutions
DSTAVERT
Immortal
Immortal
Jump to solution

Just for fun you could try restarting the management agents. Also use the IP address rather than the name. Make sure there isn't any firewall or antivirus issues blocking access.

-- David -- VMware Communities Moderator

View solution in original post

Reply
0 Kudos
17 Replies
DSTAVERT
Immortal
Immortal
Jump to solution

Install the Host Update Utility. Run the Host Update Utility and select Add Host. Add the IP address or name. Select the host you just added and click on Update Host.

The Host Update Utility should now download and apply the vSphere 4 Upgrade.

If you have ESXi 3.5 installed on USB the upgrade may fail.

-- David -- VMware Communities Moderator
Reply
0 Kudos
Crowdedisland
Contributor
Contributor
Jump to solution

I'm sorry fro not being clearer. I did just as you said and when I try to add my 3.5 host to the updater it tells me it cannot connect. I can ping the host a nd when I uninstall and reinstall the 3.5 version it works fine.

Reply
0 Kudos
DSTAVERT
Immortal
Immortal
Jump to solution

Just for fun you could try restarting the management agents. Also use the IP address rather than the name. Make sure there isn't any firewall or antivirus issues blocking access.

-- David -- VMware Communities Moderator
Reply
0 Kudos
Crowdedisland
Contributor
Contributor
Jump to solution

I had used the ip address previously but I restarted the managemnt agent and it still tells me that it cannot conenct to the remote host.

Reply
0 Kudos
Crowdedisland
Contributor
Contributor
Jump to solution

Ok so I rebotted the esxi Host and was able to do the upgraade to 4.0

I then went and tried to start my sbs 2003 server vm and it tells me that "File not found"

I checked my settings and the file for hd 1 which has a 0001 attached is on the datastore.

Can anyone help me figure outwhat file is looking for and why it won't start.

Reply
0 Kudos
DSTAVERT
Immortal
Immortal
Jump to solution

Does the VM have any snapshots? I would go to http://sanbarrow.com/sickbay.html

The important thing is to NOT start the VM again until you know what is going on.

-- David -- VMware Communities Moderator
Reply
0 Kudos
Crowdedisland
Contributor
Contributor
Jump to solution

Sorry I realize after my previous post that the flat files are hidden.

I am pasting my log so you can see what error I am getting

Nov 26 14:44:19.967: vmx| Log for VMware ESX pid=10826 version=4.0.0 build=build-208167 option=Release

Nov 26 14:44:19.968: vmx| Host codepage=UTF-8 encoding=UTF-8

Nov 26 14:44:39.975: vmx| Hostname=localhost.CrowdedIslandSolutions.local

Nov 26 14:44:39.975: vmx| IP=127.0.0.1 (lo0)

Nov 26 14:44:39.975: vmx| IP=192.168.2.107 (vmk0)

Nov 26 14:44:39.975: vmx| IP=192.168.168.100 (vmk1)

Nov 26 14:44:39.975: vmx| Command line: "/bin/vmx" "-ssched.group=host/user" "-#" "name=VMware ESX;version=4.0.0;buildnumber=208167;licensename=VMware ESX Server;licenseversion=4.0 build-208167;" "-@" "pipe=/tmp/vmhsdaemon-0/vmx612ad4806cd03585;" "/vmfs/volumes/49c50513-a8e291eb-e674-001ec9e3d4b9/ssb 2003/ssb 2003.vmx"

Nov 26 14:44:39.975: vmx| Msg_SetLocale: HostLocale=UTF-8 UserLocale=NULL

Nov 26 14:44:40.018: vmx| UI Connecting to pipe '/tmp/vmhsdaemon-0/vmx612ad4806cd03585' with user '(null)'

Nov 26 14:44:40.018: vmx| VMXVmdb: Local connection timeout: 60000 ms.

Nov 26 14:44:40.022: vmx| /vmfs/volumes/49c50513-a8e291eb-e674-001ec9e3d4b9/ssb 2003/ssb 2003.vmx: Setup symlink /var/run/vmware/3b938bb1ccc8d418f0df97f3b949f8f9 -> /var/run/vmware/root_0/1259246679976025_10826

Nov 26 14:44:40.022: vmx| Vix: : VMAutomation: Initializing VMAutomation.

Nov 26 14:44:40.023: vmx| Vix: : VMAutomation: Detected the VM is not managed

Nov 26 14:44:40.023: vmx| Vix: : VMAutomationOpenListenerSocket() listening

Nov 26 14:44:40.023: vmx| Sig_Init already initialized

Nov 26 14:44:40.024: vmx| Vix: : VMAutomation_ReportPowerOpFinished: statevar=0, newAppState=1870, success=1

Nov 26 14:44:40.024: vmx| Transitioned vmx/execState/val to poweredOff

Nov 26 14:44:40.024: vmx| Vix: : VMAutomation_ReportPowerOpFinished: statevar=1, newAppState=1873, success=1

Nov 26 14:44:40.024: vmx| Vix: : VMAutomation_ReportPowerOpFinished: statevar=2, newAppState=1877, success=1

Nov 26 14:44:40.024: vmx| Vix: : VMAutomation_ReportPowerOpFinished: statevar=3, newAppState=1881, success=1

Nov 26 14:44:40.024: vmx| CPUID[0] vendor: GenuntelineI

Nov 26 14:44:40.024: vmx| CPUID[0] level 00000000, 0: 0x0000000a 0x756e6547 0x6c65746e 0x49656e69

Nov 26 14:44:40.024: vmx| CPUID[0] level 00000001, 0: 0x00010676 0x00040800 0x000ce3bd 0xbfebfbff

Nov 26 14:44:40.024: vmx| CPUID[0] level 0000000a, 0: 0x07280202 0x00000000 0x00000000 0x00000503

Nov 26 14:44:40.024: vmx| CPUID[0] level 80000000, 0: 0x80000008 0x00000000 0x00000000 0x00000000

Nov 26 14:44:40.024: vmx| CPUID[0] level 80000001, 0: 0x00000000 0x00000000 0x00000001 0x20100800

Nov 26 14:44:40.024: vmx| CPUID[0] level 80000008, 0: 0x00003024 0x00000000 0x00000000 0x00000000

Nov 26 14:44:40.024: vmx| CPUID[1] vendor: GenuntelineI

Nov 26 14:44:40.024: vmx| CPUID[1] level 00000000, 0: 0x0000000a 0x756e6547 0x6c65746e 0x49656e69

Nov 26 14:44:40.024: vmx| CPUID[1] level 00000001, 0: 0x00010676 0x01040800 0x000ce3bd 0xbfebfbff

Nov 26 14:44:40.024: vmx| CPUID[1] level 0000000a, 0: 0x07280202 0x00000000 0x00000000 0x00000503

Nov 26 14:44:40.024: vmx| CPUID[1] level 80000000, 0: 0x80000008 0x00000000 0x00000000 0x00000000

Nov 26 14:44:40.024: vmx| CPUID[1] level 80000001, 0: 0x00000000 0x00000000 0x00000001 0x20100800

Nov 26 14:44:40.024: vmx| CPUID[1] level 80000008, 0: 0x00003024 0x00000000 0x00000000 0x00000000

Nov 26 14:44:40.024: vmx| CPUID[2] vendor: GenuntelineI

Nov 26 14:44:40.024: vmx| CPUID[2] level 00000000, 0: 0x0000000a 0x756e6547 0x6c65746e 0x49656e69

Nov 26 14:44:40.025: vmx| CPUID[2] level 00000001, 0: 0x00010676 0x02040800 0x000ce3bd 0xbfebfbff

Nov 26 14:44:40.025: vmx| CPUID[2] level 0000000a, 0: 0x07280202 0x00000000 0x00000000 0x00000503

Nov 26 14:44:40.025: vmx| CPUID[2] level 80000000, 0: 0x80000008 0x00000000 0x00000000 0x00000000

Nov 26 14:44:40.025: vmx| CPUID[2] level 80000001, 0: 0x00000000 0x00000000 0x00000001 0x20100800

Nov 26 14:44:40.025: vmx| CPUID[2] level 80000008, 0: 0x00003024 0x00000000 0x00000000 0x00000000

Nov 26 14:44:40.025: vmx| CPUID[3] vendor: GenuntelineI

Nov 26 14:44:40.025: vmx| CPUID[3] level 00000000, 0: 0x0000000a 0x756e6547 0x6c65746e 0x49656e69

Nov 26 14:44:40.025: vmx| CPUID[3] level 00000001, 0: 0x00010676 0x03040800 0x000ce3bd 0xbfebfbff

Nov 26 14:44:40.025: vmx| CPUID[3] level 0000000a, 0: 0x07280202 0x00000000 0x00000000 0x00000503

Nov 26 14:44:40.025: vmx| CPUID[3] level 80000000, 0: 0x80000008 0x00000000 0x00000000 0x00000000

Nov 26 14:44:40.025: vmx| CPUID[3] level 80000001, 0: 0x00000000 0x00000000 0x00000001 0x20100800

Nov 26 14:44:40.025: vmx| CPUID[3] level 80000008, 0: 0x00003024 0x00000000 0x00000000 0x00000000

Nov 26 14:44:40.025: vmx| hostCPUID vendor: GenuntelineI

Nov 26 14:44:40.025: vmx| hostCPUID level 00000000, 0: 0x0000000a 0x756e6547 0x6c65746e 0x49656e69

Nov 26 14:44:40.025: vmx| hostCPUID level 00000001, 0: 0x00010676 0x00040800 0x000ce3bd 0xbfebfbff

Nov 26 14:44:40.025: vmx| hostCPUID level 0000000a, 0: 0x07280202 0x00000000 0x00000000 0x00000503

Nov 26 14:44:40.025: vmx| hostCPUID level 80000000, 0: 0x80000008 0x00000000 0x00000000 0x00000000

Nov 26 14:44:40.025: vmx| hostCPUID level 80000001, 0: 0x00000000 0x00000000 0x00000001 0x20100800

Nov 26 14:44:40.025: vmx| hostCPUID level 80000008, 0: 0x00003024 0x00000000 0x00000000 0x00000000

Nov 26 14:44:40.025: vmx| CPUID Maximum Physical Address Bits supported across all CPUs: 36

Nov 26 14:44:40.025: vmx| CPU[0]: MSR 0x480 = 0x5a08000000000d

Nov 26 14:44:40.025: vmx| CPU[1]: MSR 0x480 = 0x5a08000000000d

Nov 26 14:44:40.025: vmx| CPU[2]: MSR 0x480 = 0x5a08000000000d

Nov 26 14:44:40.025: vmx| CPU[3]: MSR 0x480 = 0x5a08000000000d

Nov 26 14:44:40.025: vmx| Common: MSR 0x480 = 0x5a08000000000d

Nov 26 14:44:40.025: vmx| CPU[0]: MSR 0x481 = 0x3f00000016

Nov 26 14:44:40.025: vmx| CPU[1]: MSR 0x481 = 0x3f00000016

Nov 26 14:44:40.025: vmx| CPU[2]: MSR 0x481 = 0x3f00000016

Nov 26 14:44:40.025: vmx| CPU[3]: MSR 0x481 = 0x3f00000016

Nov 26 14:44:40.025: vmx| Common: MSR 0x481 = 0x3f00000016

Nov 26 14:44:40.025: vmx| CPU[0]: MSR 0x482 = 0xf7f9fffe0401e172

Nov 26 14:44:40.025: vmx| CPU[1]: MSR 0x482 = 0xf7f9fffe0401e172

Nov 26 14:44:40.025: vmx| CPU[2]: MSR 0x482 = 0xf7f9fffe0401e172

Nov 26 14:44:40.025: vmx| CPU[3]: MSR 0x482 = 0xf7f9fffe0401e172

Nov 26 14:44:40.025: vmx| Common: MSR 0x482 = 0xf7f9fffe0401e172

Nov 26 14:44:40.025: vmx| CPU[0]: MSR 0x483 = 0x3ffff00036dff

Nov 26 14:44:40.025: vmx| CPU[1]: MSR 0x483 = 0x3ffff00036dff

Nov 26 14:44:40.025: vmx| CPU[2]: MSR 0x483 = 0x3ffff00036dff

Nov 26 14:44:40.025: vmx| CPU[3]: MSR 0x483 = 0x3ffff00036dff

Nov 26 14:44:40.025: vmx| Common: MSR 0x483 = 0x3ffff00036dff

Nov 26 14:44:40.025: vmx| CPU[0]: MSR 0x484 = 0x3fff000011ff

Nov 26 14:44:40.025: vmx| CPU[1]: MSR 0x484 = 0x3fff000011ff

Nov 26 14:44:40.025: vmx| CPU[2]: MSR 0x484 = 0x3fff000011ff

Nov 26 14:44:40.025: vmx| CPU[3]: MSR 0x484 = 0x3fff000011ff

Nov 26 14:44:40.025: vmx| Common: MSR 0x484 = 0x3fff000011ff

Nov 26 14:44:40.025: vmx| CPU[0]: MSR 0x485 = 0x403c0

Nov 26 14:44:40.025: vmx| CPU[1]: MSR 0x485 = 0x403c0

Nov 26 14:44:40.025: vmx| CPU[2]: MSR 0x485 = 0x403c0

Nov 26 14:44:40.025: vmx| CPU[3]: MSR 0x485 = 0x403c0

Nov 26 14:44:40.025: vmx| Common: MSR 0x485 = 0x403c0

Nov 26 14:44:40.025: vmx| CPU[0]: MSR 0x486 = 0x80000021

Nov 26 14:44:40.025: vmx| CPU[1]: MSR 0x486 = 0x80000021

Nov 26 14:44:40.025: vmx| CPU[2]: MSR 0x486 = 0x80000021

Nov 26 14:44:40.025: vmx| CPU[3]: MSR 0x486 = 0x80000021

Nov 26 14:44:40.025: vmx| Common: MSR 0x486 = 0x80000021

Nov 26 14:44:40.025: vmx| CPU[0]: MSR 0x487 = 0xffffffff

Nov 26 14:44:40.025: vmx| CPU[1]: MSR 0x487 = 0xffffffff

Nov 26 14:44:40.025: vmx| CPU[2]: MSR 0x487 = 0xffffffff

Nov 26 14:44:40.025: vmx| CPU[3]: MSR 0x487 = 0xffffffff

Nov 26 14:44:40.025: vmx| Common: MSR 0x487 = 0xffffffff

Nov 26 14:44:40.025: vmx| CPU[0]: MSR 0x488 = 0x2000

Nov 26 14:44:40.025: vmx| CPU[1]: MSR 0x488 = 0x2000

Nov 26 14:44:40.025: vmx| CPU[2]: MSR 0x488 = 0x2000

Nov 26 14:44:40.025: vmx| CPU[3]: MSR 0x488 = 0x2000

Nov 26 14:44:40.025: vmx| Common: MSR 0x488 = 0x2000

Nov 26 14:44:40.025: vmx| CPU[0]: MSR 0x489 = 0x27ff

Nov 26 14:44:40.025: vmx| CPU[1]: MSR 0x489 = 0x27ff

Nov 26 14:44:40.025: vmx| CPU[2]: MSR 0x489 = 0x27ff

Nov 26 14:44:40.025: vmx| CPU[3]: MSR 0x489 = 0x27ff

Nov 26 14:44:40.025: vmx| Common: MSR 0x489 = 0x27ff

Nov 26 14:44:40.025: vmx| CPU[0]: MSR 0x48a = 0x2c

Nov 26 14:44:40.025: vmx| CPU[1]: MSR 0x48a = 0x2c

Nov 26 14:44:40.025: vmx| CPU[2]: MSR 0x48a = 0x2c

Nov 26 14:44:40.025: vmx| CPU[3]: MSR 0x48a = 0x2c

Nov 26 14:44:40.025: vmx| Common: MSR 0x48a = 0x2c

Nov 26 14:44:40.025: vmx| CPU[0]: MSR 0x48b = 0x4100000000

Nov 26 14:44:40.025: vmx| CPU[1]: MSR 0x48b = 0x4100000000

Nov 26 14:44:40.025: vmx| CPU[2]: MSR 0x48b = 0x4100000000

Nov 26 14:44:40.025: vmx| CPU[3]: MSR 0x48b = 0x4100000000

Nov 26 14:44:40.025: vmx| Common: MSR 0x48b = 0x4100000000

Nov 26 14:44:40.025: vmx| CPU[0]: MSR 0x48c = 0

Nov 26 14:44:40.025: vmx| CPU[1]: MSR 0x48c = 0

Nov 26 14:44:40.025: vmx| CPU[2]: MSR 0x48c = 0

Nov 26 14:44:40.025: vmx| CPU[3]: MSR 0x48c = 0

Nov 26 14:44:40.025: vmx| Common: MSR 0x48c = 0

Nov 26 14:44:40.026: vmx| CPU[0]: MSR 0x48d = 0

Nov 26 14:44:40.026: vmx| CPU[1]: MSR 0x48d = 0

Nov 26 14:44:40.026: vmx| CPU[2]: MSR 0x48d = 0

Nov 26 14:44:40.026: vmx| CPU[3]: MSR 0x48d = 0

Nov 26 14:44:40.026: vmx| Common: MSR 0x48d = 0

Nov 26 14:44:40.026: vmx| CPU[0]: MSR 0x48e = 0

Nov 26 14:44:40.026: vmx| CPU[1]: MSR 0x48e = 0

Nov 26 14:44:40.026: vmx| CPU[2]: MSR 0x48e = 0

Nov 26 14:44:40.026: vmx| CPU[3]: MSR 0x48e = 0

Nov 26 14:44:40.026: vmx| Common: MSR 0x48e = 0

Nov 26 14:44:40.026: vmx| CPU[0]: MSR 0x48f = 0

Nov 26 14:44:40.026: vmx| CPU[1]: MSR 0x48f = 0

Nov 26 14:44:40.026: vmx| CPU[2]: MSR 0x48f = 0

Nov 26 14:44:40.026: vmx| CPU[3]: MSR 0x48f = 0

Nov 26 14:44:40.026: vmx| Common: MSR 0x48f = 0

Nov 26 14:44:40.026: vmx| CPU[0]: MSR 0x490 = 0

Nov 26 14:44:40.026: vmx| CPU[1]: MSR 0x490 = 0

Nov 26 14:44:40.026: vmx| CPU[2]: MSR 0x490 = 0

Nov 26 14:44:40.026: vmx| CPU[3]: MSR 0x490 = 0

Nov 26 14:44:40.026: vmx| Common: MSR 0x490 = 0

Nov 26 14:44:40.027: vmx| ACL_InitCapabilities: current IPC thread

Nov 26 14:44:40.027: vmx| ACL_InitCapabilities: done

Nov 26 14:44:40.029: vmx| changing directory to /vmfs/volumes/49c50513-a8e291eb-e674-001ec9e3d4b9/ssb 2003/.

Nov 26 14:44:40.029: vmx| Config file: /vmfs/volumes/49c50513-a8e291eb-e674-001ec9e3d4b9/ssb 2003/ssb 2003.vmx

Nov 26 14:44:40.030: vmx| Vix: : VMAutomation_ReportPowerOpFinished: statevar=1, newAppState=1873, success=1

Nov 26 14:44:40.030: vmx| Vix: : VMAutomation_ReportPowerOpFinished: statevar=2, newAppState=1878, success=1

Nov 26 14:44:40.056: vmx| VMXVmdb_LoadRawConfig: Loading raw config

Nov 26 14:44:40.118: vmx| VMXVmdbCbVmVmxExecState: Exec state change requested to state poweredOn without reset, soft.

Nov 26 14:44:40.118: vmx| TOOLS delaying state change request to state 3

Nov 26 14:44:40.118: vmx| PowerOn

Nov 26 14:44:40.123: vmx| VMXVmdb_LoadRawConfig: Loading raw config

Nov 26 14:44:40.126: vmx| Vix: : VMAutomation_ReportPowerOpFinished: statevar=0, newAppState=1871, success=1

Nov 26 14:44:40.127: vmx| UNAME VMkernel localhost.CrowdedIslandSolutions.local 4.0.0 #1 SMP Release build-208167 Nov 8 2009 01:02:11 x86_64 (uwglibc release: vmware, version: 2.5)

Nov 26 14:44:40.127: vmx| DICT --- USER PREFERENCES

Nov 26 14:44:40.127: vmx| DICT --- USER DEFAULTS

Nov 26 14:44:40.127: vmx| DICT --- HOST DEFAULTS

Nov 26 14:44:40.127: vmx| DICT authd.proxy.vim = vmware-hostd:hostd-vmdb

Nov 26 14:44:40.127: vmx| DICT authd.proxy.nfc = vmware-hostd:ha-nfc

Nov 26 14:44:40.127: vmx| DICT authd.proxy.nfcssl = vmware-hostd:ha-nfcssl

Nov 26 14:44:40.127: vmx| DICT vmauthd.logEnabled = FALSE

Nov 26 14:44:40.127: vmx| DICT log.vmauthdFileName = /var/log/vmware/authd.log

Nov 26 14:44:40.127: vmx| DICT authd.fullpath = /sbin/authd

Nov 26 14:44:40.127: vmx| DICT authd.soapServer = TRUE

Nov 26 14:44:40.127: vmx| DICT vmauthd.server.alwaysProxy = TRUE

Nov 26 14:44:40.127: vmx| DICT vmx.fullpath = /bin/vmx

Nov 26 14:44:40.127: vmx| DICT libdir = /usr/lib/vmware

Nov 26 14:44:40.127: vmx| DICT authd.proxy.vua = vmware-vua:vua

Nov 26 14:44:40.127: vmx| DICT --- SITE DEFAULTS

Nov 26 14:44:40.127: vmx| DICT --- COMMAND LINE

Nov 26 14:44:40.127: vmx| DICT sched.group = host/user

Nov 26 14:44:40.127: vmx| DICT --- CONFIGURATION

Nov 26 14:44:40.127: vmx| DICT config.version = 8

Nov 26 14:44:40.127: vmx| DICT virtualHW.version = 4

Nov 26 14:44:40.127: vmx| DICT floppy0.present = FALSE

Nov 26 14:44:40.127: vmx| DICT nvram = ssb 2003.nvram

Nov 26 14:44:40.127: vmx| DICT deploymentPlatform = windows

Nov 26 14:44:40.127: vmx| DICT virtualHW.productCompatibility = hosted

Nov 26 14:44:40.127: vmx| DICT tools.upgrade.policy = useGlobal

Nov 26 14:44:40.127: vmx| DICT powerType.powerOff = default

Nov 26 14:44:40.127: vmx| DICT powerType.powerOn = default

Nov 26 14:44:40.127: vmx| DICT powerType.suspend = default

Nov 26 14:44:40.127: vmx| DICT powerType.reset = default

Nov 26 14:44:40.127: vmx| DICT displayName = ssb 2003

Nov 26 14:44:40.127: vmx| DICT extendedConfigFile = ssb 2003.vmxf

Nov 26 14:44:40.127: vmx| DICT scsi0.present = TRUE

Nov 26 14:44:40.127: vmx| DICT scsi0.sharedBus = none

Nov 26 14:44:40.127: vmx| DICT scsi0.virtualDev = lsilogic

Nov 26 14:44:40.127: vmx| DICT memsize = 2048

Nov 26 14:44:40.127: vmx| DICT scsi0:0.present = TRUE

Nov 26 14:44:40.127: vmx| DICT scsi0:0.fileName = ssb 2003-000001.vmdk

Nov 26 14:44:40.127: vmx| DICT scsi0:0.deviceType = scsi-hardDisk

Nov 26 14:44:40.127: vmx| DICT ide0:0.present = TRUE

Nov 26 14:44:40.127: vmx| DICT ide0:0.clientDevice = TRUE

Nov 26 14:44:40.127: vmx| DICT ide0:0.deviceType = cdrom-raw

Nov 26 14:44:40.127: vmx| DICT ide0:0.startConnected = FALSE

Nov 26 14:44:40.127: vmx| DICT guestOS = winnetstandard

Nov 26 14:44:40.127: vmx| DICT uuid.location = 56 4d ef 82 5a bc 18 ad-c9 9a ba 7c 58 af 7a 31

Nov 26 14:44:40.127: vmx| DICT uuid.bios = 56 4d ef 82 5a bc 18 ad-c9 9a ba 7c 58 af 7a 31

Nov 26 14:44:40.127: vmx| DICT ethernet0.present = TRUE

Nov 26 14:44:40.127: vmx| DICT ethernet0.networkName = VM Network

Nov 26 14:44:40.127: vmx| DICT ethernet0.addressType = generated

Nov 26 14:44:40.127: vmx| DICT guestOSAltName = Microsoft Windows Server 2003, Standard Edition (32-bit)

Nov 26 14:44:40.127: vmx| DICT bios.bootDelay = 10000

Nov 26 14:44:40.127: vmx| DICT sched.cpu.affinity = all

Nov 26 14:44:40.127: vmx| DICT sched.mem.max = 8622

Nov 26 14:44:40.127: vmx| DICT scsi0:0.redo =

Nov 26 14:44:40.127: vmx| DICT ethernet0.generatedAddress = 00:0c:29:af:7a:31

Nov 26 14:44:40.127: vmx| DICT sched.swap.derivedName = /vmfs/volumes/49c50513-a8e291eb-e674-001ec9e3d4b9/ssb 2003/ssb 2003-a5d6c92e.vswp

Nov 26 14:44:40.127: vmx| DICT ethernet0.generatedAddressOffset = 0

Nov 26 14:44:40.127: vmx| DICT hostCPUID.0 = 0000000a756e65476c65746e49656e69

Nov 26 14:44:40.127: vmx| DICT guestCPUID.0 = 0000000a756e65476c65746e49656e69

Nov 26 14:44:40.127: vmx| DICT userCPUID.0 = 0000000a756e65476c65746e49656e69

Nov 26 14:44:40.127: vmx| DICT hostCPUID.1 = 0001067600040800000ce3bdbfebfbff

Nov 26 14:44:40.127: vmx| DICT guestCPUID.1 = 0001067800010800000822010febbbff

Nov 26 14:44:40.127: vmx| DICT userCPUID.1 = 0001067600040800000822010febbbff

Nov 26 14:44:40.127: vmx| DICT hostCPUID.80000001 = 00000000000000000000000120100000

Nov 26 14:44:40.127: vmx| DICT guestCPUID.80000001 = 00000000000000000000000120100000

Nov 26 14:44:40.127: vmx| DICT userCPUID.80000001 = 00000000000000000000000120100000

Nov 26 14:44:40.127: vmx| DICT evcCompatibilityMode = FALSE

Nov 26 14:44:40.127: vmx| DICT bios.forceSetupOnce = FALSE

Nov 26 14:44:40.127: vmx| DICT tools.remindInstall = FALSE

Nov 26 14:44:40.127: vmx| DICT tools.syncTime = FALSE

Nov 26 14:44:40.127: vmx| DICT ide0:0.fileName = /usr/lib/vmware/isoimages/windows.iso

Nov 26 14:44:40.127: vmx| DICT scsi0:1.present = TRUE

Nov 26 14:44:40.127: vmx| DICT scsi0:1.deviceType = scsi-hardDisk

Nov 26 14:44:40.127: vmx| DICT scsi0:1.filename = /vmfs/volumes/4a32d05e-63b91127-5605-001ec9e3d4b9/ssb 2003/ssb 2003_1.vmdk

Nov 26 14:44:40.127: vmx| DICT scsi0:1.mode = persistent

Nov 26 14:44:40.127: vmx| DICT scsi0:1.redo =

Nov 26 14:44:40.127: vmx| DICT replay.supported = TRUE

Nov 26 14:44:40.127: vmx| DICT --- USER DEFAULTS

Nov 26 14:44:40.127: vmx| DICT --- HOST DEFAULTS

Nov 26 14:44:40.127: vmx| DICT authd.proxy.vim = vmware-hostd:hostd-vmdb

Nov 26 14:44:40.127: vmx| DICT authd.proxy.nfc = vmware-hostd:ha-nfc

Nov 26 14:44:40.127: vmx| DICT authd.proxy.nfcssl = vmware-hostd:ha-nfcssl

Nov 26 14:44:40.127: vmx| DICT vmauthd.logEnabled = FALSE

Nov 26 14:44:40.128: vmx| DICT log.vmauthdFileName = /var/log/vmware/authd.log

Nov 26 14:44:40.128: vmx| DICT authd.fullpath = /sbin/authd

Nov 26 14:44:40.128: vmx| DICT authd.soapServer = TRUE

Nov 26 14:44:40.128: vmx| DICT vmauthd.server.alwaysProxy = TRUE

Nov 26 14:44:40.128: vmx| DICT vmx.fullpath = /bin/vmx

Nov 26 14:44:40.128: vmx| DICT libdir = /usr/lib/vmware

Nov 26 14:44:40.128: vmx| DICT authd.proxy.vua = vmware-vua:vua

Nov 26 14:44:40.128: vmx| DICT --- SITE DEFAULTS

Nov 26 14:44:40.128: vmx| DICT --- GLOBAL SETTINGS

Nov 26 14:44:40.129: vmx| Vix: : VMAutomation_ReportPowerOpFinished: statevar=1, newAppState=1873, success=1

Nov 26 14:44:40.129: vmx| hostCpuFeatures = 0x446001fc

Nov 26 14:44:40.129: vmx| hostNumPerfCounters = 2

Nov 26 14:44:40.129: vmx| MONITOR MODE: allowed modes : BT HV

Nov 26 14:44:40.129: vmx| MONITOR MODE: user requested modes : BT HV HWMMU

Nov 26 14:44:40.129: vmx| MONITOR MODE: guestOS preferred modes: HWMMU HV BT

Nov 26 14:44:40.129: vmx| MONITOR MODE: filtered list : HV BT

Nov 26 14:44:40.129: vmx| HV Settings: virtual exec = 'hardware'; virtual mmu = 'software'

Nov 26 14:44:40.170: vmx| VMMon_ConfigMemSched: vmmon.numVCPUs=1

Nov 26 14:44:40.170: vmx| CreateVM: Swap: generating normal swap file name.

Nov 26 14:44:40.171: vmx| Swap file path: '/vmfs/volumes/49c50513-a8e291eb-e674-001ec9e3d4b9/ssb 2003/ssb 2003-a5d6c92e.vswp'

Nov 26 14:44:40.185: vmx| Using swap file '/vmfs/volumes/49c50513-a8e291eb-e674-001ec9e3d4b9/ssb 2003/ssb 2003-a5d6c92e.vswp'

Nov 26 14:44:40.185: vmx| VMXVmdb_LoadRawConfig: Loading raw config

Nov 26 14:44:40.198: vmx| LogBackupByRenumber: failed to read the directory '/vmfs/volumes/49c50513-a8e291eb-e674-001ec9e3d4b9/ssb 2003/stats'.

Nov 26 14:44:40.198: vmx| LogBackupByRenumber: failed to read the directory '/vmfs/volumes/49c50513-a8e291eb-e674-001ec9e3d4b9/ssb 2003/stats'.

Nov 26 14:44:40.200: vmx| vmm32-modules: [vmm.vmm32 .data:0x2b000-0xe44 .sdata:0x2c000-0x4e4 .statvars:0x2d000-0x3a8 .peer:0x2e000-0x261c0 .shared:0x56000-0x190c0 .bss:0x70000-0x5dc8 .rodata:0x77000-0xbec0 .text:0x84000-0x614bd .kstatvars:0x3000-0x0, mmu-pae.vmm32 .rodata:0x82ec0-0x44 .data:0x2be44-0xc .peer:0x541c0-0x16c0 .shared:0x6f0c0-0x380 .bss:0x75de0-0x51c .text:0xe54c0-0xa927 .comment:0x40000e10-0x10e .statvars:0x2000-0x0 .kstatvars:0x2000-0x0 .scb:0x40004fe0-0x180 .shared_meta:0x40004f50-0x390 .peer_meta:0x40000e70-0x210, sharedmmu-none.vmm32 .text:0xefde8-0x37 .comment:0x40000f1e-0x12, pv-none.vmm32 .shared:0x6f440-0x180 .bss:0x76300-0x84 .text:0xefe20-0xe2 .comment:0x40000f30-0x48 .shared_meta:0x400052e0-0x90, vprobe-none.vmm32 .text:0xeff04-0x19 .comment:0x40000f78-0x12, hv-vt.vmm32 .rodata:0x82f04-0x4 .data:0x1000-0x0 .peer:0x1000-0x0 .shared:0x1000-0x0 .bss:0x1000-0x0 .text:0xeff20-0x1a1 .comment:0x40000f8a-0x12 .statvars:0x1000-0x0 .kstatvars:0x1000-0x0, gphys-sw.vmm32 .peer:0x55880-0x40 .shared:0x6f5c0-0x80 .bss:0x2000-0x0 .text:0xf00d0-0x763 .comment:0x40000f9c-0x12 .scb:0x40005160-0x60 .shared_meta:0x40005370-0x240 .peer_meta:0x40001080-0x30, vassert-none.vmm32 .text:0xf0834-0xf .comment:0x40000fae-0x12, vmsafe-none.vmm32 .text:0xf0844-0x1b .comment:0x40000fc0-0x12, videio-none.vmm32 .rodata:0x82f08-0xdf .data:0x1000-0x0 .peer:0x1000-0x0 .shared:0x1000-0x0 .bss:0x1000-0x0 .text:0xf0860-0xaa .comment:0x40000fd2-0x12 .statvars:0x1000-0x0 .kstatvars:0x1000-0x0, .rodata:0x82fe7-0x3e9]

Nov 26 14:44:40.202: vmx| KHZEstimate 2500004

Nov 26 14:44:40.202: vmx| MHZEstimate 2500

Nov 26 14:44:40.202: vmx| NumVCPUs 1

Nov 26 14:44:40.202: vmx| UUID: location-UUID is 56 4d ef 82 5a bc 18 ad-c9 9a ba 7c 58 af 7a 31

Nov 26 14:44:40.202: vmx| AIOGNRC: numThreads=2 ide=0, scsi=0, passthru=1

Nov 26 14:44:40.202: vmx| WORKER: Creating new group with numThreads=2 (2)

Nov 26 14:44:40.203: vmx| CPU0: PMC: Patch Level 0x60b, smmFrz (hw): (0)

Nov 26 14:44:40.203: vmx| PMC: IA32, Penryn

Nov 26 14:44:40.203: vmx| CPU1: PMC: Patch Level 0x60b, smmFrz (hw): (0)

Nov 26 14:44:40.203: vmx| PMC: IA32, Penryn

Nov 26 14:44:40.203: vmx| CPU2: PMC: Patch Level 0x60b, smmFrz (hw): (0)

Nov 26 14:44:40.203: vmx| PMC: IA32, Penryn

Nov 26 14:44:40.203: vmx| CPU3: PMC: Patch Level 0x60b, smmFrz (hw): (0)

Nov 26 14:44:40.203: vmx| PMC: IA32, Penryn

Nov 26 14:44:40.203: vmx| minDEThreshold: 76

Nov 26 14:44:40.216: vmx| Mapped mainmem as pageable

Nov 26 14:44:40.216: vmx| MStat: Creating Stat vm.uptime

Nov 26 14:44:40.216: vmx| MStat: Creating Stat vm.suspendTime

Nov 26 14:44:40.216: vmx| MStat: Creating Stat vm.powerOnTimeStamp

Nov 26 14:44:40.216: vmx| VMXAIOMGR: Using: simple=Generic unbuf=Generic

Nov 26 14:44:40.224: vmx| VMXVmdb_LoadRawConfig: Loading raw config

Nov 26 14:44:40.227: vmx| DISK: OPEN scsi0:0 '/vmfs/volumes/49c50513-a8e291eb-e674-001ec9e3d4b9/ssb 2003/ssb 2003-000001.vmdk' persistent R[]

Nov 26 14:44:40.248: vmx| DISKLIB-VMFS : "/vmfs/volumes/49c50513-a8e291eb-e674-001ec9e3d4b9/ssb 2003/ssb 2003-000001-delta.vmdk" : open successful (10) size = 28957629952, hd = 2425205. Type 8

Nov 26 14:44:40.248: vmx| DISKLIB-DSCPTR: Opened : "ssb 2003-000001-delta.vmdk" (0xa)

Nov 26 14:44:40.249: vmx| DISKLIB-LINK : Opened '/vmfs/volumes/49c50513-a8e291eb-e674-001ec9e3d4b9/ssb 2003/ssb 2003-000001.vmdk' (0xa): vmfsSparse, 156312450 sectors / 74.5 GB.

Nov 26 14:44:40.249: vmx| DISKLIB-VMFS : "/vmfs/volumes/49c50513-a8e291eb-e674-001ec9e3d4b9/ssb 2003/ssb 2003-flat.vmdk" : open successful (14) size = 80031974400, hd = 1507704. Type 3

Nov 26 14:44:40.249: vmx| DISKLIB-DSCPTR: Opened : "ssb 2003-flat.vmdk" (0xe)

Nov 26 14:44:40.249: vmx| DISKLIB-LINK : Opened '/vmfs/volumes/49c50513-a8e291eb-e674-001ec9e3d4b9/ssb 2003/ssb 2003.vmdk' (0xe): vmfs, 156312450 sectors / 74.5 GB.

Nov 26 14:44:40.250: vmx| DISKLIB-CHAINESX : ChainESXOpenSubChain: numLinks = 2, numSubChains = 1

Nov 26 14:44:40.281: vmx| DISKLIB-LIB : Opened "/vmfs/volumes/49c50513-a8e291eb-e674-001ec9e3d4b9/ssb 2003/ssb 2003-000001.vmdk" (flags 0xa).

Nov 26 14:44:40.281: vmx| DISK: OPEN '/vmfs/volumes/49c50513-a8e291eb-e674-001ec9e3d4b9/ssb 2003/ssb 2003-000001.vmdk' Geo (9730/255/63) BIOS Geo (9730/255/63)

Nov 26 14:44:40.282: vmx| Unable to find file /vmfs/volumes/4a32d05e-63b91127-5605-001ec9e3d4b9/ssb 2003/ssb 2003_1.vmdk

Nov 26 14:44:40.282: vmx| Unable to find file /vmfs/volumes/4a32d05e-63b91127-5605-001ec9e3d4b9/ssb 2003/ssb 2003_1.vmdk

Nov 26 14:44:40.282: vmx| DISK: OPEN scsi0:1 '/vmfs/volumes/4a32d05e-63b91127-5605-001ec9e3d4b9/ssb 2003/ssb 2003_1.vmdk' persistent R[]

Nov 26 14:44:40.282: vmx| Unable to find file /vmfs/volumes/4a32d05e-63b91127-5605-001ec9e3d4b9/ssb 2003/ssb 2003_1.vmdk

Nov 26 14:44:40.282: vmx| FILE: File_GetVMFSAttributes: could not open /vmfs/volumes/4a32d05e-63b91127-5605-001ec9e3d4b9/ssb 2003/ssb 2003_1.vmdk.

Nov 26 14:44:40.282: vmx| FILE: File_GetVMFSfsType: File_GetVMFSAttributes failed

Nov 26 14:44:40.282: vmx| DISKLIB-DSCPTR: DescriptorDetermineType: failed to open '/vmfs/volumes/4a32d05e-63b91127-5605-001ec9e3d4b9/ssb 2003/ssb 2003_1.vmdk': Could not find the file (63)

Nov 26 14:44:40.282: vmx| DISKLIB-LINK : "/vmfs/volumes/4a32d05e-63b91127-5605-001ec9e3d4b9/ssb 2003/ssb 2003_1.vmdk" : failed to open (The system cannot find the file specified).

Nov 26 14:44:40.283: vmx| DISKLIB-CHAIN : "/vmfs/volumes/4a32d05e-63b91127-5605-001ec9e3d4b9/ssb 2003/ssb 2003_1.vmdk" : failed to open (The system cannot find the file specified).

Nov 26 14:44:40.283: vmx| DISKLIB-LIB : Failed to open '/vmfs/volumes/4a32d05e-63b91127-5605-001ec9e3d4b9/ssb 2003/ssb 2003_1.vmdk' with flags 0xa (The system cannot find the file specified).

Nov 26 14:44:40.283: vmx| Msg_Post: Error

Nov 26 14:44:40.283: vmx| http://msg.disk.fileNotFound VMware ESX cannot find the virtual disk "/vmfs/volumes/4a32d05e-63b91127-5605-001ec9e3d4b9/ssb 2003/ssb 2003_1.vmdk". Please verify the path is valid and try again.

Nov 26 14:44:40.283: vmx| http://msg.disk.noBackEnd Cannot open the disk '/vmfs/volumes/4a32d05e-63b91127-5605-001ec9e3d4b9/ssb 2003/ssb 2003_1.vmdk' or one of the snapshot disks it depends on.

Nov 26 14:44:40.283: vmx| http://msg.disk.configureDiskError Reason: The system cannot find the file specified.----


Nov 26 14:44:40.288: vmx| Module DiskEarly power on failed.

Nov 26 14:44:40.288: vmx| VMX_PowerOn: ModuleTable_PowerOn = 0

Nov 26 14:44:40.288: vmx| scsi0:0: numIOs = 0 numMergedIOs = 0 numSplitIOs = 0 ( 0.0%)

Nov 26 14:44:40.289: vmx| DISKLIB-VMFS : "/vmfs/volumes/49c50513-a8e291eb-e674-001ec9e3d4b9/ssb 2003/ssb 2003-000001-delta.vmdk" : closed.

Nov 26 14:44:40.289: vmx| DISKLIB-VMFS : "/vmfs/volumes/49c50513-a8e291eb-e674-001ec9e3d4b9/ssb 2003/ssb 2003-flat.vmdk" : closed.

Nov 26 14:44:40.289: vmx| WORKER: asyncOps=0 maxActiveOps=0 maxPending=0 maxCompleted=0

Nov 26 14:44:40.293: vmx| Vix: : VMAutomation_ReportPowerOpFinished: statevar=1, newAppState=1873, success=1

Nov 26 14:44:40.295: vmx| Vix: : VMAutomation_ReportPowerOpFinished: statevar=0, newAppState=1870, success=1

Nov 26 14:44:40.295: vmx| Transitioned vmx/execState/val to poweredOff

Nov 26 14:44:40.295: vmx| Vix: : VMAutomation_ReportPowerOpFinished: statevar=0, newAppState=1870, success=0

Nov 26 14:44:40.295: vmx| VMX idle exit

Nov 26 14:44:40.296: vmx| Vix: : VMAutomation_LateShutdown()

Nov 26 14:44:40.296: vmx| Vix: : VMAutomationCloseListenerSocket. Closing listener socket.

Nov 26 14:44:40.297: vmx| Flushing VMX VMDB connections

Nov 26 14:44:40.302: vmx| IPC_exit: disconnecting all threads

Nov 26 14:44:40.302: vmx| VMX exit (0).

Nov 26 14:44:40.302: vmx| AIOMGR-S : stat o=6 r=7 w=0 i=5 br=100352 bw=0

Nov 26 14:44:40.302: vmx| VMX has left the building: 0.

The files I have in that direcotry are

Name Last modified Size

-


Parent Directory -

ssb 2003-000001-delta.vmdk 26-Nov-2009 13:17 28957629952

ssb 2003-000001.vmdk 26-Nov-2009 09:11 252

ssb 2003-Snapshot1.vmsn 02-May-2009 10:00 18842

ssb 2003-flat.vmdk 02-May-2009 09:59 80031974400

ssb 2003.nvram 26-Nov-2009 13:17 8684

ssb 2003.vmdk 02-May-2009 09:59 475

ssb 2003.vmsd 02-May-2009 10:00 376

ssb 2003.vmx 26-Nov-2009 14:44 2220

ssb 2003.vmxf 04-Nov-2009 08:28 263

vmware-26.log 20-Nov-2009 23:56 44473

vmware-27.log 26-Nov-2009 08:38 35703

vmware-28.log 26-Nov-2009 13:17 29285

vmware-29.log 26-Nov-2009 13:56 28136

vmware-30.log 26-Nov-2009 13:57 28200

vmware-31.log 26-Nov-2009 14:26 28202

vmware.log 26-Nov-2009 14:44 28202

-


Any help would be aprreciated

Reply
0 Kudos
DSTAVERT
Immortal
Immortal
Jump to solution

Just a quick look shows ssb 2003_1.vmdk in the log but not in the file list. It looks like it is in different datastore than the ssb 2003.vmdk

/vmfs/volumes/4a32d05e-63b91127-5605-001ec9e3d4b9/ssb 2003/ssb 2003_1.vmdk

/vmfs/volumes/49c50513-a8e291eb-e674-001ec9e3d4b9/ssb 2003/ssb 2003-flat.vmdk

Check that you have access to all your datastores

-- David -- VMware Communities Moderator
Reply
0 Kudos
Crowdedisland
Contributor
Contributor
Jump to solution

You are correct. I ahd a second datastore that I used as a backup device that is on a Netgear ReadyNas Pro. I did not realize and vm files would be stored there.

The hard disk 2 of the ssb 2003 server vm is set to vmfs/volumes/4a32d05e-63b91127-5605-001ec9e3d4b9/ssb 2003/ssb 2003_1.vmdk

I do not see the second datastore listed now but I am unsure why. How do I figure this out?

Reply
0 Kudos
DSTAVERT
Immortal
Immortal
Jump to solution

You may need to do a rescan of the storage. http://kb.vmware.com/kb/1003988

-- David -- VMware Communities Moderator
Reply
0 Kudos
Crowdedisland
Contributor
Contributor
Jump to solution

I really wnat to thank you for all your help.

The rescan did not fix the problem. I decided to delete the 2nd hard drive from the vm settings since it was on;y used as a backup drive and now it bopots up fine.

I would love you help geeting my iscsi working but I wnat to eb fair as my roiginal issue was the update to 4.0 which you helped me solve.

I am going to close this question and start a new one for that problem.

Reply
0 Kudos
DSTAVERT
Immortal
Immortal
Jump to solution

The iSCSI issue has been noted before with the update. I'll see if I can locate it.

-- David -- VMware Communities Moderator
Reply
0 Kudos
DSTAVERT
Immortal
Immortal
Jump to solution

http://communities.vmware.com/thread/243415

-- David -- VMware Communities Moderator
Reply
0 Kudos
Crowdedisland
Contributor
Contributor
Jump to solution

I tried to run vihostupdate.pl --server 192.168.2.107 --username root --query

but only got headings no listings. Does that make any sense?

Reply
0 Kudos
Crowdedisland
Contributor
Contributor
Jump to solution

Any ideas?

Reply
0 Kudos
DSTAVERT
Immortal
Immortal
Jump to solution

You need to have both the 3.5 and 4 clients installed. When you connect the launcher decides what client to run. Check to make sure you have both. The launcher usually complains if it doesn't find the missing client.

Beyond that you should post more information than "it doesn't work". Since we can't see anything about your situation you need to be the eyes and ears.

-- David -- VMware Communities Moderator
Reply
0 Kudos
DSTAVERT
Immortal
Immortal
Jump to solution

I would also start a new post for any new questions. This post is marked answered so you risk your new question being ignored.

-- David -- VMware Communities Moderator
Reply
0 Kudos