vitoolkitextensions Work Item Rss Feed

Created Issue: New-TkeLinkedClone fails with error registering new VM, timing related error [25323]

peterbach — Fri, 13 Nov 2009 02:16:04 GMT

When using New-TkeLinkedClone to create a large cluster full of clones, registering the new clone VM would occasionally fail, complaining it could not find the vmx file specified. I tracked this down to a timing issue between when the new clone VMX file is uploaded to the cluster, and the Register-TkeVM immediately after. Inserting a ten second sleep seemed long enough to make the errors go away. This is a crude workaround, there may be a better way to fix this.

Environment: 11 node VMware VI 3.5 cluster, with iSCSI storage.

# Copy the modified VMX file into this new subdirectory.
$encoding = New-Object system.Text.UTF8Encoding
$newVmxBytes = $encoding.GetBytes([string]::Join("`n", $newVmx) + "`n")
$newVmxBytes | Set-Content -Encoding byte $tempVmxFile
Copy-TkeDatastoreFile -source $tempVmxFile -destination $newVmxFile -destinationDatacenter $datacenter -noprogress

## see if sleeping help with the errors.
Start-Sleep -Seconds 10

# Register this clone.
$moRef = Register-TkeVM -vmxfile $newVmxFile -vmhost $vmhost -folder $folder -resourcepool $resourcepool
$newVM = $moRef | Get-VIObjectByVIView

Commented Issue: get-thesnapshotextended SizeMb returns 0 [24446]

flipster — Wed, 09 Sep 2009 21:01:42 GMT

Hi

When running this on my env i get a size of 0 on all vm's with a snapshot:

---
$b = get-vm | Get-TkeSnapshotExtended
$b |select SizeMb
----

any ideas on why?

I connect to a Vitrual center server 2.4 u4 and im running PowerCLI and powershell V2 CTP3 as per requisite.
Comments: ** Comment from web user: flipster **

I'm having this issue too. The reutrned snapshot size is 0 MB.

Created Issue: get-thesnapshotextended SizeMb returns 0

AllanChristiansen — Wed, 26 Aug 2009 09:50:46 GMT

Created Issue: get-tkeloglastmodifieddate

houghtp — Mon, 11 May 2009 11:00:38 GMT

This function needs updating. It seems to be calling get-datastorefiles which doesn't exist.

Also this line doesn't seems to return anything $entry = $files | where { $_.Path -eq $logFile }. $logfile only holds "vmname/vmware.log". I've updated it to $entry = $files | where { $_.Path -match $logFile } and it works now.

Created Issue: Size of VMSN file

codeplexfan — Wed, 11 Feb 2009 18:25:06 GMT

We have VMs with 2 and more VMDKs.
I think the VMSN file is not always $snapshot.snapshotFile[1] in Cmdlet Get-TkeSnapshotExtended

Cmdlet Get-TkeSnapshotExtended
...
# First, let's find the size of this snapshot's VMSN file.
$totalSize = Add-TkeFileSize $files $snapshot.snapshotFile[1] -simpleMatch
...

We have replaced with
...
# First, let's find the size of this snapshot's VMSN file.
foreach ($vmsnfile in $snapshot.snapshotFile) {
if ($vmsnfile -like "*.vmsn") {
$totalSize = Add-TkeFileSize $files $vmsnfile $true
break
}
}
...

Commented Issue: Total System Packaged up?

ewannemacher — Thu, 22 Jan 2009 20:41:13 GMT

Would it be feasible to get a full dump of all the supplied functions, cmdlets, etc packaged up into a deployable solution?
Comments: ** Comment from web user: ewannemacher **

The install.cmd in the source worked just fine for me.

Commented Issue: get-tkesnapshotextended functionality

cartershanklin — Thu, 22 Jan 2009 17:21:27 GMT

I've updated two systems to Powershell 2 CTP3 and the latest toolkit extensions(45952). Now, the get-tkesnapshotextended function doesn't appear to want to accept more than one vm as input. Example below...

Works with one:
get-vm seactx01 | get-tkesnapshotextended

Name Description PowerState
---- ----------- ----------
January 13th, 200... January 13th, 2009 @ 7:20am PoweredOn

get-vm | get-tkesnapshotextended
No output comes back

Here is a sample of output from get-vm. I limited it to our Seattle DC due to size reasons.

get-vm -location (get-datacenter seattle)

Name PowerState Num CPUs Memory (MB)
---- ---------- -------- -----------
sea1schd2 PoweredOn 1 2048
sea1mon01 PoweredOn 1 2048
Win2K8_X64 PoweredOff 1 1024
sea1lp01 PoweredOn 1 2048
sea1bavm05 PoweredOn 1 1024
sea1schd1 PoweredOn 1 2048
rex-test PoweredOn 1 1024
sea1www09 PoweredOn 1 1024
sea1lnx01 PoweredOn 1 1024
sea1fil04 PoweredOn 1 2048
seaesx000 PoweredOn 1 2048
sea1bavm01 PoweredOn 1 1024
sea1www02 PoweredOn 1 2048
rhel5.2x64 PoweredOn 1 1024
sea1req01 PoweredOn 1 1024
sea1bavm03 PoweredOn 1 1024
sea1bavm02 PoweredOn 1 1024
seactx01 PoweredOn 2 4096
sea1fil05 PoweredOn 1 2048
sea1bavm04 PoweredOn 1 1024

get-vm -location (get-datacenter seattle) | get-tkesnapshotextended
No output. Returns to shell prompt.
Comments: ** Comment from web user: cartershanklin **

I can confirm the behavior you're seeing, I'll take a look soon. The short-term workaround is Get-VM | foreach { $_ | Get-TkeSnapshotExtended }

Created Issue: get-tkesnapshotextended functionality

jasonah — Thu, 22 Jan 2009 15:04:39 GMT

Commented Issue: Total System Packaged up?

cartershanklin — Tue, 20 Jan 2009 03:57:53 GMT

Would it be feasible to get a full dump of all the supplied functions, cmdlets, etc packaged up into a deployable solution?
Comments: ** Comment from web user: cartershanklin **

If you download the latest source bundle the install.cmd is in there. I ported it to XP as I had the same problems you did.

Commented Issue: Total System Packaged up?

ewannemacher — Tue, 20 Jan 2009 01:29:25 GMT

Would it be feasible to get a full dump of all the supplied functions, cmdlets, etc packaged up into a deployable solution?
Comments: ** Comment from web user: ewannemacher **

LucD - I like the script. It is good to see some cmd.exe skills in use.

One issue will be that choice.exe is not included on a default install of all operating systems. My 32bit XP system does not have it. I am not sure if there are any issues redistributing it or not. As a workaround you could change the script to require a parameter. Something like the following could be used to validate a parameter was passed:

If /I "%1" == "PerUser" goto PerUser
If /I "%1" == "Machine" goto Machine
goto Usage

:PerUser
echo PerUser
goto :EOF

:Machine
echo Machine
goto :EOF

:Usage
echo Usage: Install.cmd ^<PerUser ^| Machine^>
goto :EOF

Commented Issue: Total System Packaged up?

cartershanklin — Mon, 19 Jan 2009 06:28:37 GMT

Would it be feasible to get a full dump of all the supplied functions, cmdlets, etc packaged up into a deployable solution?
Comments: ** Comment from web user: cartershanklin **

I went ahead with Luc's script because it handles the case of PowerShell not being installed. I ported it to XP so hopefully it's still working on Vista.

Anyone care to validate it?

Commented Issue: Total System Packaged up?

LucD — Sun, 18 Jan 2009 20:51:22 GMT

Would it be feasible to get a full dump of all the supplied functions, cmdlets, etc packaged up into a deployable solution?
Comments: ** Comment from web user: LucD **

Apparently we were on the same track here.
Attached something I cooked up this afternoon.
The difference with the PS1 script:
- it's a CMD script
- it checks if PowerShell and the correct version of PowerShell is installed
- it allows for a "per user" or "per machine" installation

The idea is to ZIP this CMD file together with the PSM1 file into an auto-extract archive.
When executed the CMD file checks the environment, install the module and updates the profile.
But that part is still to come.

Can some brave ones test and give feedback ?
Place the PSM1 file and the CMD file in the same folder and execute the CMD file.
For per machine installation you administrator authority

Commented Issue: Total System Packaged up?

ewannemacher — Sun, 18 Jan 2009 19:39:19 GMT

Would it be feasible to get a full dump of all the supplied functions, cmdlets, etc packaged up into a deployable solution?
Comments: ** Comment from web user: ewannemacher **

As usually happens I found an issue after I posted this (Let me know of any others). Not a huge one, but the backup functionality was broken. Line 48 should be replace with this:
Copy-Item $ViTkPath -Destination ($ViTkPath + $dateString)

Commented Issue: Total System Packaged up?

ewannemacher — Sun, 18 Jan 2009 19:10:44 GMT

Would it be feasible to get a full dump of all the supplied functions, cmdlets, etc packaged up into a deployable solution?
Comments: ** Comment from web user: ewannemacher **

Here is a script that will install the modules and add the appropriate Import-Module line to the user's profile. Just put it in the same directory as the viTookKitExtensions.psm1 file and run it.

Commented Issue: Total System Packaged up?

LucD — Sun, 18 Jan 2009 18:00:57 GMT

Would it be feasible to get a full dump of all the supplied functions, cmdlets, etc packaged up into a deployable solution?
Comments: ** Comment from web user: LucD **

We are working on a packaged solution with a (nearly) full automated installation.
For a list of the available functions you can do this (provided the module is already imported).

Get-Module vitoolkitextensions | select -ExpandProperty ExportedFunctions

Created Issue: Total System Packaged up?

iguy — Fri, 09 Jan 2009 21:01:34 GMT

Would it be feasible to get a full dump of all the supplied functions, cmdlets, etc packaged up into a deployable solution?

Commented Issue: Cannot convert value "2718957606" to type "System.Int32"

cartershanklin — Mon, 01 Dec 2008 17:58:42 GMT

The previous issue with "-" in LUN name is fixed, now it shows this:

Cannot convert value "2718957606" to type "System.Int32". Error: "Value was either too large or too small for an Int32."
At C:\customer\vmware\scripts\viToolkitExtensions.psm1:1101 char:18
+ $totalSize += <<<< Add-TkeFileSize $files ($disk + ".vmdk")

and for a bunch of snapshots it shows a size of either 0 or 609.000036239624 for this command: Get-VM | Get-TkeSnapshotExtended | Select Name, VM, SizeMB

The performance are really bad, it takes several (litterally) minutes to complete the task for a Datacenter with 200 VMs of which about 15 have snapshots.
Comments: ** Comment from web user: cartershanklin **

Changeset 44249 addresses this problem and also a problem that was preventing this cmdlet from working on VirtualCenter (as opposed to directly connected to ESX)

Commented Issue: Cannot convert value "2718957606" to type "System.Int32"

johnlennon — Sun, 23 Nov 2008 01:41:31 GMT

The performance increased quite a bit and most errors are gone but I still get this:
Cannot convert value "7801571616" to type "System.Int32". Error: "Value was either too large or too small for an Int32."
At C:\customer\vmware\scripts\viToolkitExtensions.psm1:1099 char:18
+ $totalSize += <<<< Add-TkeFileSize $files $matches[1]

Closed Issue: Cannot convert value "2718957606" to type "System.Int32"

cartershanklin — Sat, 22 Nov 2008 00:41:49 GMT

Created Issue: Cannot convert value "2718957606" to type "System.Int32"

johnlennon — Thu, 20 Nov 2008 04:40:45 GMT