jmroth's Posts

I have reported this to support and (after stopping their attempts to do lengthy webexes and convincing them to read my problem description) they have suggested to remove the duplicate item not conta... See more...
I have reported this to support and (after stopping their attempts to do lengthy webexes and convincing them to read my problem description) they have suggested to remove the duplicate item not containing a "Node ID" property. That seems to have worked fine. HTH
Interestingly they are still able to power on a VM using the "Play" button inside Remote Console....
That actually works but is not realistic to implement since for example in our case the user is supposed to be restricted to a folder in the "VMs and templates" view.
The important part is probably this:
We have the same problem. Using ESXi 6.5 U2C (build 9298722) Did someone maybe make progress with this? We found the following scenarios 1) Network witout name service (no DNS) When w... See more...
We have the same problem. Using ESXi 6.5 U2C (build 9298722) Did someone maybe make progress with this? We found the following scenarios 1) Network witout name service (no DNS) When we specify a proxy, it results in a name resolution error (which should not happen since the host itself has no DNS, but the proxy would be able to resolve!) 2) Network with DNS When we specify a proxy, it nevertheless tries to connect directly. I tried contacting support about this and I believe they don't even understand what a proxy is.
Note: it seems you are not able to move specifically the VM config (vmx + swap + snapshots) this way or with Move-VM for that matter. *sigh*
I guess it would, the point being: You have to get the $hd object from "Get-HardDisk -VM $vm -Datastore $srcds" Just getting it from "Get-HardDisk -Datastore $srcds" and iterating over that, d... See more...
I guess it would, the point being: You have to get the $hd object from "Get-HardDisk -VM $vm -Datastore $srcds" Just getting it from "Get-HardDisk -Datastore $srcds" and iterating over that, does not seem to be enough.
I said you have to use Move-Harddisk in combination with Get-VM (like you showed). Simply using "Move-HardDisk" like this is not working: $hdsrc = Get-HardDisk -Datastore $srcds foreach ($... See more...
I said you have to use Move-Harddisk in combination with Get-VM (like you showed). Simply using "Move-HardDisk" like this is not working: $hdsrc = Get-HardDisk -Datastore $srcds foreach ($hd in $hdsrc) {   Move-HardDisk $hd -Datastore $dstds   ...
Since I'm using 5.5 and "Get-HardDisk... | Move-HardDisk ..." works alright, I'm not sure what requirement you mean.
Yeah ok, the point is you have to go through "Get-VM" first... You can't simply "Move-HardDisk" like this: $hdsrc = Get-HardDisk -Datastore $srcds foreach ($hd in $hdsrc) {   Move-HardDis... See more...
Yeah ok, the point is you have to go through "Get-VM" first... You can't simply "Move-HardDisk" like this: $hdsrc = Get-HardDisk -Datastore $srcds foreach ($hd in $hdsrc) {   Move-HardDisk $hd -Datastore $dstds   ... Because then it will tell you that the disk is locked.
Oh man :smileygrin: That's really sick. So you have to create these RelocateSpec and RelocateSpecDiskLocator objects etc. and then use some part of the API instead of having a high-level funct... See more...
Oh man :smileygrin: That's really sick. So you have to create these RelocateSpec and RelocateSpecDiskLocator objects etc. and then use some part of the API instead of having a high-level function for this task, wow. As far as I understand it, internally to ESXi an svMotion actually is a vMotion, which is why you have to set a destination for all disks, even though you want to move only one of them, again wow. Well, this also explains why the event log of vCenter Server shows both vMotion and svMotion as "Migrating from a to b" with no info about the datastore being changed for any specific disk (it only shows the destination disk in case you chose to migrate the VMX I guess).
How do I svMotion a single disk in PowerCLI 5.5? Trying Set-HardDisk gives the following warning: WARNING: Parameter 'Datastore' is obsolete. 'Datastore' parameter is obsolete. To move hard ... See more...
How do I svMotion a single disk in PowerCLI 5.5? Trying Set-HardDisk gives the following warning: WARNING: Parameter 'Datastore' is obsolete. 'Datastore' parameter is obsolete. To move hard disk to another datastore and change it's storage format, use 'Move-HardDisk' cmdlet instead. Set-HardDisk fails anyway with a message that the disk is locked (hence I guess you can't use it for an online migration). Move-HardDisk only seems to be able to move disks in offline mode too (cold migration), however I'd like to perform a Storage vMotion. Move-VM can only move all disks of a VM, which is not what I want. (Too many and too big disks on a VM, will never fit on one destination LUN) In essence, I'd like to script what you can do with the "advanced" dialog for migrating disks in vCenter Server. But how?
Alright, we've now disabled power management in the new hosts' BIOSes...:smileyplain:
Platform 1 is 4 or 6 core X5550 or X5650 @2.6GHz (outside of any cluster) on ESXi 5.1 r1312873 Platform 2 is 4 core E5-2637v2 @3.5GHz (Cluster with SandyBridge EVC Mode) on ESXi 5.5 r2068190 ... See more...
Platform 1 is 4 or 6 core X5550 or X5650 @2.6GHz (outside of any cluster) on ESXi 5.1 r1312873 Platform 2 is 4 core E5-2637v2 @3.5GHz (Cluster with SandyBridge EVC Mode) on ESXi 5.5 r2068190 After vmotion from Platform 1 to 2 (database servers) users are reporting performance penalties. Looking at our Cacti graphs representing CPU usage we see the following. (You can imagine when the vmotion happened.) Is this normal? Why is this? The specific VM I am showing here is a VM in version 7 with 2 vCPU and 18G RAM using SLES Linux (kernel 2.6.27). Note after complete shutdown and restart, it's ok (tested on other machines affected the same way)
I've tried to debug this together with support. What they found already were different VML IDs on different hosts for the same datastore/LUN. Indeed, in vCenter, when you go to a host, then... See more...
I've tried to debug this together with support. What they found already were different VML IDs on different hosts for the same datastore/LUN. Indeed, in vCenter, when you go to a host, then select "Storage Views", then Reports -> Show all SCSI Volumes (LUNs) you see an ID that is some SCSI info concatenated by the naa ID. They do indeed differ in my case from host to host for several LUNs. Probably, the "SCSI ID" as seen in vCenter is generated by the host the *first* time it sees the LUNs, and even when the LUN ID later changes, the SCSI ID remains the same. And I also assume the name you give to the device is linked to the SCSI ID. That's probably why the names are not updated everywhere: the SCSI IDs are not the same everywhere.
I'm also not sure why "vCenter has nothing to do with it". If I have shared storage and I update the device name by going to a host -> Configuration -> Storage (for any host in vcenter) it is su... See more...
I'm also not sure why "vCenter has nothing to do with it". If I have shared storage and I update the device name by going to a host -> Configuration -> Storage (for any host in vcenter) it is supposed to update the device name when I look at any host, isn't it? So, vCenter very well plays some role here. I'm indeed not sure if the device name is something solely stored on the hosts or also in the vCenter DB.... Anyway, what happens in my case, I find strange.
Oh, but look what I tried to accomplish the day before that: Setting LUN display name (programatically, for host and vcenter) Going to the hosts directly doesn't work at all. What I showed ... See more...
Oh, but look what I tried to accomplish the day before that: Setting LUN display name (programatically, for host and vcenter) Going to the hosts directly doesn't work at all. What I showed in the screenshot above exactly corresponds to what I see on the hosts using "esxcli storage core device list"... I've tried refreshing, rescanning, everything. No luck.
Hi, Currently using VCSA 5.5 Build 1623101, I'm seeing this: I'm trying to rename storage devices. I do this on the host called esxb10 You see, all is well. Now I go to another host ... See more...
Hi, Currently using VCSA 5.5 Build 1623101, I'm seeing this: I'm trying to rename storage devices. I do this on the host called esxb10 You see, all is well. Now I go to another host You see some of the changes are there, some are not. On even other hosts, none of the changes are there. It is not the first time I see this. I'm now experiencing this on the appliance, I've had it before on Windows vCenters.... What is the problem here? Thanks.
OK forget it, probably you have to do this through vcenter... I guess I'll use PowerCLI or better vCLI as I don't want to use PowerShell.
Hi, The goal: Having meaningful display names in vCenter. How I try to accomplish this: using esxcli on the individual host. ~ # esxcli storage core device list -d naa.600000e00d10000000... See more...
Hi, The goal: Having meaningful display names in vCenter. How I try to accomplish this: using esxcli on the individual host. ~ # esxcli storage core device list -d naa.600000e00d100000001030XXXXbc0000 naa.600000e00d100000001030XXXbc0000    Display Name: FUJITSU Fibre Channel Disk (naa.600000e00d100000001030XXXXbc0000)    Has Settable Display Name: true ... ~ # esxcli storage core device set -d naa.600000e00d100000001030XXXbc0000 -n LUN.naa.600000e00d100000001030XXXbc0000 ~ # esxcli storage core device list -d naa.600000e00d100000001030XXXbc0000 naa.600000e00d100000001030XXXbc0000    Display Name: LUN.naa.600000e00d100000001030XXXbc0000    Has Settable Display Name: true ... (a few seconds later) ... ~ # esxcli storage core device list -d naa.600000e00d100000001030XXXXbc0000 naa.600000e00d100000001030XXXbc0000    Display Name: FUJITSU Fibre Channel Disk (naa.600000e00d100000001030XXXbc0000)    Has Settable Display Name: true Why does it revert to the previous device name almost instantly? Oh, and I also want to show the updated device names in vCenter. I don't want to go and click through every device on each host in vCenter in order to give the LUNs meaningful names. I want to set them programatically. Best regards, Marki