VMware

This Question is Possibly Answered

1 "correct" answer available (10 pts) 2 "helpful" answers available (6 pts)
3 Replies Last post: Feb 23, 2009 8:52 AM by arkturas  

Commit after putting VM in Hotmode takes very long... posted: Jan 14, 2009 1:08 AM

Click to view Omar Muntslag's profile Novice 15 posts since
Jul 13, 2006
I have recently upgraded mij 3.0.2 server to 3.5 Update 3 with the latest patches.
One of my VM's has 9 disks of 1 TB each on different LUN's
After the upgrade it takes about 30 mintues to doe a commit after creating a snapshot. Even when i commit straight after making a snapshot. (this was not the case in the older ESX build)
In the vmkernel log i see a couple of strange new errors :

Jan 14 07:16:11 shr-ipbv-esx021 vmkernel: 1:19:02:49.265 cpu3:1095)VSCSI: 4060: Creating Virtual Device for world 1096 vscsi0:0 (handle 10448)
Jan 14 07:16:11 shr-ipbv-esx021 vmkernel: 1:19:02:49.266 cpu3:1095)VSCSI: 4060: Creating Virtual Device for world 1096 vscsi0:1 (handle 10449)
Jan 14 07:16:11 shr-ipbv-esx021 vmkernel: 1:19:02:49.266 cpu3:1095)VSCSI: 4060: Creating Virtual Device for world 1096 vscsi0:2 (handle 10450)
Jan 14 07:16:11 shr-ipbv-esx021 vmkernel: 1:19:02:49.266 cpu3:1095)VSCSI: 4060: Creating Virtual Device for world 1096 vscsi0:3 (handle 10451)
Jan 14 07:16:11 shr-ipbv-esx021 vmkernel: 1:19:02:49.312 cpu3:1095)VSCSI: 4060: Creating Virtual Device for world 1096 vscsi0:8 (handle 10452)
Jan 14 07:16:11 shr-ipbv-esx021 vmkernel: 1:19:02:49.367 cpu3:1095)VSCSI: 4060: Creating Virtual Device for world 1096 vscsi0:9 (handle 10453)
Jan 14 07:16:11 shr-ipbv-esx021 vmkernel: 1:19:02:49.419 cpu3:1095)VSCSI: 4060: Creating Virtual Device for world 1096 vscsi0:10 (handle 10454)
Jan 14 07:16:11 shr-ipbv-esx021 vmkernel: 1:19:02:49.454 cpu3:1095)VSCSI: 4060: Creating Virtual Device for world 1096 vscsi0:11 (handle 10455)
Jan 14 07:16:11 shr-ipbv-esx021 vmkernel: 1:19:02:49.532 cpu3:1095)VSCSI: 4060: Creating Virtual Device for world 1096 vscsi0:12 (handle 10456)
Jan 14 07:16:11 shr-ipbv-esx021 vmkernel: 1:19:02:49.584 cpu3:1095)VSCSI: 4060: Creating Virtual Device for world 1096 vscsi0:13 (handle 10457)
Jan 14 07:17:10 shr-ipbv-esx021 vmkernel: 1:19:03:48.288 cpu2:1095)DevFS: 2222: Unable to find device: 6c27e-shr-ipvl-mat001-000009-delta.vmdk
Jan 14 07:17:10 shr-ipbv-esx021 vmkernel: 1:19:03:48.303 cpu2:1095)DevFS: 2222: Unable to find device: 15281-shr-ipvl-mat001-000008-delta.vmdk
Jan 14 07:17:10 shr-ipbv-esx021 vmkernel: 1:19:03:48.321 cpu2:1095)DevFS: 2222: Unable to find device: 8284-shr-ipvl-mat001-000007-delta.vmdk
Jan 14 07:17:10 shr-ipbv-esx021 vmkernel: 1:19:03:48.332 cpu2:1095)DevFS: 2222: Unable to find device: 1beb287-shr-ipvl-mat001-000006-delta.vmdk
Jan 14 07:17:10 shr-ipbv-esx021 vmkernel: 1:19:03:48.347 cpu2:1095)DevFS: 2222: Unable to find device: c28a-shr-ipvl-mat001-000005-delta.vmdk
Jan 14 07:17:10 shr-ipbv-esx021 vmkernel: 1:19:03:48.369 cpu2:1095)DevFS: 2222: Unable to find device: 1328d-shr-ipvl-mat001-000004-delta.vmdk
Jan 14 07:17:10 shr-ipbv-esx021 vmkernel: 1:19:03:48.383 cpu2:1095)DevFS: 2222: Unable to find device: 9290-shr-ipvl-mat001-000003-delta.vmdk
Jan 14 07:17:10 shr-ipbv-esx021 vmkernel: 1:19:03:48.386 cpu2:1095)DevFS: 2222: Unable to find device: 6b293-shr-ipvl-mat001-000002-delta.vmdk
Jan 14 07:17:10 shr-ipbv-esx021 vmkernel: 1:19:03:48.397 cpu2:1095)DevFS: 2222: Unable to find device: 3296-shr-ipvl-mat001_1-000001-delta.vmdk
Jan 14 07:17:10 shr-ipbv-esx021 vmkernel: 1:19:03:48.426 cpu2:1095)DevFS: 2222: Unable to find device: 3299-shr-ipvl-mat001-000001-delta.vmdk
Jan 14 07:17:11 shr-ipbv-esx021 vmkernel: 1:19:03:49.653 cpu3:1102)StorageMonitor: 196: vmhba1:0:111:0 status = 24/0 0x0 0x0 0x0
Jan 14 07:17:12 shr-ipbv-esx021 vmkernel: 1:19:03:50.167 cpu3:1095)StorageMonitor: 196: vmhba1:0:7:0 status = 24/0 0x0 0x0 0x0
Jan 14 07:17:21 shr-ipbv-esx021 vmkernel: 1:19:03:59.583 cpu1:1095)VSCSI: 4060: Creating Virtual Device for world 1096 vscsi0:0 (handle 10458)

These errors keep repeating for about 30 minutes..and then suddenly the job is done.
Does anyone know why this could be taking so long?


The Commit kept crashing after the upgrade, but after changing the COQ.MaxHeapSize.MB from 32 to 64, the commit strated to work. It just takes very long and the VM stops responding during the commit.

Thanks,
Omar

Click to view titaniumlegs's profile Enthusiast 52 posts since
Feb 28, 2005

Is this on NFS?

If so you need to apply and activate patch ESX350-200808401-BG. You said you have ESX3.5u3, so the patch is built in. You activate it by inserting
prefvmx.consolidateDeleteNFSLocks = "TRUE"
in /etc/vmware/config and reboot ESX. (Vmotion, shutdown or suspend VMs first)

Details in http://media.netapp.com/documents/tr-3428.pdf p.12-13.

This only applies to NFS datastores. Although TR3428 is NetApp, this bit applies to any NFS storage.

Enjoy!

Click to view arkturas's profile Enthusiast 58 posts since
Aug 17, 2005

Just out of curiosity, how long did it take to mount your VM to the VCB staging area with ESX3.02 ?, also what is the total size of your VM?

VMware Developer

SDKs, APIs, Videos, Learn and much more in the Developer community.

Learn More

Developer Sample Code

Increase your developer productivity with VMware API sample code.

Learn More

VMworld Sessions & Labs

Online access to the latest VMworld Sessions & Labs and online services.

Learn more

Purchase PSO Credits Online

Purchase credits to redeem training and consulting services online.

Buy Now

Community Hardware Software

View reported configurations or report your own.

Learn More

VMware vSphere

Come witness the next giant leap in virtualization.

Register Today

Communities