よろしくお願い申し上げます。
VMWARE FUSION11を使用しております。
vmxファイルにmonitor_control.restrict_backdoor = "true"を追記したところ、
ホストOS(OS X) ゲストOS(win10)間でコピペができなくなってしまいました。
他にも共有もこの状況だとできません。
monitor_control.restrict_backdoor = "true"を削除すると元に戻り正常に機能するのですが......
色々調べてみましたが解決できなくてどうかご教示いただきたいです。
どうかよろしくお願い申し上げます。
Hi,
I have been working on a prototype for a Remote Plugin. I have registered the plugin, started it and was able to view the plugin in the web-client. That worked well by just following the documentation.
Working in another location, behind tunnels and firewalls, I try to view the plug-in, but the remote vCenter can't download the plugin.json from my location - I had expected this.
So I tried starting the webClient from the sdk (startup.bat) on my local machine. This webClient is attached to the remote sso server, so it found the registration - it was able to download the plugin.json and performed the validation checks on it (seen in the virgo.log) - After the checks are completed, the reverse proxy should be configured. But this causes an exception.
[2019-05-22T13:22:31.590+02:00] [INFO ] rpx-configurer-thread 70000028 100002 200001 c.v.v.extensionfw.impl.remote.RemotePluginReverseProxyConfigurer Reverse proxy call took 2063ms. [2019-05-22T13:22:31.594+02:00] [ERROR] plugin-discovery4 70000028 100002 200001 com.vmware.vise.vim.extension.VcExtensionManager Couldn't configure reverse proxy. com.vmware.vise.extensionfw.impl.remote.RemotePluginProxyConfigurationException: An error occurred while configuring reverse proxy using EndpointConfig (com.vmware.rhttpproxy.client.model.endpoint_config) => {
fileContent = [EndpointConfigEntry (com.vmware.rhttpproxy.client.model.endpoint_config_entry) => {
comment = , endpoint = EndpointSpec (com.vmware.rhttpproxy.client.model.endpoint_spec) => {
proxyUri = /plugins/acme.remote~1.0.0/localClient.local-8991,
mappingType = remotessl,
serverUri = localClient.local:8991/,
httpConnectAction = reject,
httpsConnectAction = allow,
thumbprint = 55:5d:b1:0d:e0:33:3e:10:ab:1e:f4:86:62:61:f0:7f:93:fe:f6:9b
}
}]
}
at com.vmware.vise.extensionfw.impl.remote.RemotePluginReverseProxyConfigurer.configureProxy(RemotePluginReverseProxyConfigurer.java:190)
at com.vmware.vise.extensionfw.impl.remote.RemotePluginReverseProxyConfigurer.addProxyRules(RemotePluginReverseProxyConfigurer.java:122)
at com.vmware.vise.extensionfw.impl.remote.RemotePluginReverseProxyServiceImpl.addProxyRules(RemotePluginReverseProxyServiceImpl.java:53)
...
Caused by: java.lang.RuntimeException: http://localhost:549/rhttpproxy/config/endpoints/ui-plugins.conf invocation failed with "org.apache.http.conn.HttpHostConnectException: Connect to localhost:549 [localhost/127.0.0.1, localhost/0:0:0:0:0:0:0:1] failed: Connection refused: connect"
... 15 common frames omitted
It seems like the htmlClient is looking for the rhttpproxy on my local host - instead of on the vCenter Server. I found this entry in the virgo.log
[2019-05-22T06:50:27.379+02:00] [ERROR] equinox-activator com.vmware.vise.extensionfw.impl.remote.RemotePluginConfig Did not manage to find reverse proxy configuration file at C:\ProgramData\VMware\vCenterServer\cfg\vmware-rhttpproxy\config.xml. Will try to make requests to the RPx REST API on port 549
And of course that is true, I don't have the file there. I looked in the SDK, but did not find one as well. I found the file on the remote vcenter, but do not know what values to change and how.
I reran the dev-setup.sh on the vCenter, hoping that maybe a config.xml would be generated, but that is not true.
Can some one help me here? I want to tell the RemotePluginReferseProxy to use the rhttpproxy on the remote vcenter - not on local host. (If I understand it correctly)
thanks
Cathy
Not sure what you are trying to say here.
But the point I'm trying to make is demonstrated by this example
""| Select @{N='F1';E={'abc'}}
""| Select @{N='F1';E={'abc'}},@{N='F2';E={'xyz'}}
)
$t2=@(
""| Select @{N='F1';E={'abc'}},@{N='F2';E={'xyz'}}
""| Select @{N='F1';E={'abc'}}
)
$t1|Export-Csv-Path .\report1.csv -NoTypeInformation -UseCulture
Invoke-Item-Path .\report1.csv
$t2|Export-Csv-Path .\report2.csv -NoTypeInformation -UseCulture
Invoke-Item-Path .\report2.csv
VMware 6.5
I want to revert to "BaseSnapshot" for all the GuestVM servers on a certainhost with Powershell.
In other words i want to get rid of all the Changes for all the GuestVM and go back to BaseSnapshot (snapshot 1)
Anyone?
Really appreciate our answer
Sometimes an older version might do the trick. I saw several other articles on this error.
You have to provide some input to the Export-Csv cmdlet.
That can be done through the InputObject parameter (which also accepts pipeline input).
In the following, I use the Foreach-Object cmdlet, since that places objects in the pipeline.
I also assume that you are connected to all vCenters before you run this script?
In that case, you have to provide the Server parameter on the Get-View cmdlet.
If yes, you will have to provide the column name in the code (I assume that is 'Name').
Something like this
ForEach-Object-Process {
$vCenterSettings=Get-View-Id 'OptionManager-VpxSettings'-Server $_.Name
New-Object PSObject -Property @{
'macaddress_begin'=($vCenterSettings.Setting|Where-Object{$_.Key-eq"config.vpxd.macAllocScheme.rangeScheme.range[0].begin"}).Value
'macaddress_end'=($vCenterSettings.Setting|Where-Object{$_.Key-eq"config.vpxd.macAllocScheme.rangeScheme.range[0].end"}).Value
}
}|
Export-Csv-Path ".\vclist2.csv"-NoTypeInformation -UseCulture
When port 80 works and 443 not it could be an issue with the SSL certificate. Did you check the firewall inside the guest OS?
Here is the VMWare Tools icon in the system tray. Hovering the mouse over it produces a flyout text that says "VMWare Tools can be updated".
Also, the only "menu" I can find is in the upper-left corner, i.e. the Player menu dropdown. There is a "Manage" item with a right-arrow on that dropdown menu, and clicking on that right-arrow presents a flyout sub-menu that shows "update VMWare tools" at the top... except that it is grayed out!!! So it cannot be selected. This suggests there really isn't any appropriate new version of VMWare Tools to upgrade to, or maybe something is wrong in my setup.
So I ask again for help. Assuming the yellow exclamation mark over the VMWare Tools icon in the system tray is legitimate, what is it asking me to do? Why is it displayed? And then why is the "Upgrade VMWare tools" menu item grayed out and unavailable for selection?
Doesn't anybody know what this is all about? Either I've done something wrong, or there is some update to VMWare Tools that I need to apply except that I can't find it for download and the presumed automatic menu item which claims "update VMWare Tools" is grayed out and inoperative, suggesting that there is NOT an update pending.
Anybody know what is going on here?
Hi All,
I need some help in modifying and fixing the below script to display the column result properly in.CSV:
The column Host, Cluster, IPAddress and Disk Used in GB somehow is not displaying at all in the exported .CSV
Thanks in advance.
LucD. Thanks so much.
Is there a way to run the script without first connecting to all the vCenters?
Essentially, what I do is log on to a jump host with a userid/password that has admin rights to all the vCenters and want to use that session for authentication.
The vCenter server FQDN names will be specified in the vclist.csv file under a "VC" or "Server" heading.
Is that possible?
That error has got nothing to do with not having appvolumes installed. The thing is that Appvolumes creates a setting in the writable to make sure it won't be deleted by accident.
Just browse to your writable datastore and change the following setting in the .vmdk file (so not the flat file which is the 10GB file or the metadata file which holds appvolumes info).
There should be a setting that is called ddb.deletavble=false, you should change it to ddb.deletable=true. Or just attach the the disk non persistent (so read only) that will do the trick as well.
Try with these changes I made.
Connect-VIServer$VCServerName
$ExportFilePath="C:\RESULT\Export-VMInfo_$($VC).csv"
$Report=@()
$VMs=Get-Datacenter|Get-VM
$Datastores=Get-Datastore|Select-Object Name, Id
$VMHosts=Get-VMHost|Select-Object Name, Parent
ForEach($VMin$VMs)
{
$VMView=$VM|Get-View
$VMInfo={}|Select-Object VMName, Powerstate, OS, Folder, IPAddress, ToolsStatus, Host, Cluster, Datastore, NumCPU, MemMb, DiskGb, DiskFree, DiskUsed
$VMInfo.VMName=$vm.name
$VMInfo.Powerstate=$vm.Powerstate
$VMInfo.OS=$vm.Guest.OSFullName
$VMInfo.IPAddress=$vm.Guest.IPAddress-join' | '
$VMInfo.ToolsStatus=$VMView.Guest.ToolsStatus
$VMInfo.Host=$vm.VMhost.name
$VMInfo.Cluster=$vm.VMhost.Parent.Name
$VMInfo.Datastore=($Datastores|Where-Object{$_.ID-match(($vmview.Datastore|Select-Object-First 1)|Select-Object Value).Value }|Select-Object Name).Name
$VMInfo.NumCPU=$vm.NumCPU
$VMInfo.MemMb=[Math]::Round(($vm.MemoryMB),2)
$VMInfo.DiskGb=[Math]::Round(((Get-Harddisk-VM $vm|Measure-Object-Property CapacityKB -Sum).Sum *1KB/1GB),2)
$VMInfo.DiskFree=[Math]::Round((($vm.Guest.Disks|Measure-Object-Property FreeSpace -Sum).Sum /1GB),2)
$VMInfo.DiskUsed=$VMInfo.DiskGb-$VMInfo.DiskFree
$Report+=$VMInfo
}
$Report=$Report|Sort-Object VMName
IF($Report-ne"")
{
$report|Export-Csv$ExportFilePath-NoTypeInformation
}
$VC=Disconnect-VIServer-Confirm:$False
First of all I would highly suggest upgrading to a newer version, 2.10 is very old and has some bugs in it. Try going for 2.15 first if your reluctant to go to 2.16.
Can i reboot the Windows 2012 box hosting Appvolumes Manager 2.10. ( Standalone). Or do i have to detach all Appstacks first ?
Yes you can reboot Appvolumes manager even if it is a standalone machine, you don't need to detach first although I would not suggest using just a single Appvolumes server. Thing is that users logging in wont get their appstacks attached (not the biggest of your issues, just relog after Appvolumes manager is up) but if a user logs off and your Appvolumes manager is down it wont reconfigure that machine so the appstacks are still attached. You would need to manually reconfigure those machines. If it is just a few it might be an option.
If i do reboot Appvolumes Manager , what is the effect on currently attached appstacks.
They stay attached.
and Lastly when Appvolumes Services start. will it sync and discover all attached Appstacks ?
No, not really. Normally twice a day Appvolumes checks for stale records and will detach the ones it find where a machine has an appstack attached but no user logged in.
Still, I would not suggest rebooting a single Appvolumes server during production..Either create a second one so you do have it load balanced or do this during off hours.
As you have said I was under the impression multiple pre-reqs "should just merge and work". We haven't encountered any issues that we have noticed, I was wondering whether if it would be beneficial to install the pre-reqs into our gold image rather than having them multiple times within the app stacks.
I would always suggest installing middleware in the golden image, so that means all vc redists and .Net framwork but also JRE or other stuff like that. Make sure your packaging machine also has these applications installed on it, otherwise Appvolumes will still install it into the appstack.
But as cH1LL1 says it is always a matter of opinion, whatever suits your needs best.
Yes, you can add a Connect-VIServer and a Disconnect-VIServer to the script.
The problem might be the User and Password.
If you don't want to provide that on the Connect-VIServer line in the script, you might want to use the New-VICredentialStoreItem cmdlet.
That allows you to do the connection without specifying a User/Password in the script.
ForEach-Object-Process {
Connect-VIServer-Server $_.VC|Out-Null
$vCenterSettings=Get-View-Id 'OptionManager-VpxSettings'-Server $_.VC
New-Object PSObject -Property @{
'macaddress_begin'=($vCenterSettings.Setting|Where-Object{$_.Key-eq"config.vpxd.macAllocScheme.rangeScheme.range[0].begin"}).Value
'macaddress_end'=($vCenterSettings.Setting|Where-Object{$_.Key-eq"config.vpxd.macAllocScheme.rangeScheme.range[0].end"}).Value
}
Disconnect-VIServer-Server $_.VC-Confirm:$false
}|
Export-Csv-Path ".\vclist2.csv"-NoTypeInformation -UseCulture
In regards to your original question on the SQL server. In Appvolumes you need to a vCenter and could also add an ESX server local account, you do not need that during installation, those permissions.
Are these delays occurring on config files (on the read-only configuration share), or on profile archives? Not that I have any advice for either scenario at this time... Just out of curiosity.
For as far as I can see it is mostly the read only configuration share, that's the strange thing. These files normally are not a lot larger than just a few kb.
Hello everyone,
We don't have experience with vmware professional solutions but we intend to implement a virtualization platform on a HP/Dell/Supermicro server having a NVIDIA Tesla P40 GPU card. We thought to base this solution on vSphere.
A typical user’s case would be as follows:
To make this scenario real, it seems I could use:
1) The vGPU software with one of vgpu license (Grid vPC or Quadro vDWS) with the correct vSphere license (Enterprise ?)
2) the vSGA from vSphere, but it seems that I need to buy (?) a specific driver from NVIDIA for that
My questions are as follows :
1) Which vSphere license do I need to support the vgpu : Standard or Enterprise?
2) Is vSphere standard enough to share GPU ressources with vSGA?
3) What is the best solution (between vSGA and vGPU) for the user's case described above?
Thank you in advance for your help!
Hi,
I am a new NSX-T user.
I have a cluster contains 3 transport nodes. From NSX-T manager I can see from the tunnel status 2 Remote Transport Node only not the 3 nodes in the cluster. Is that a correct status ?
looks like that:
The Second Node
the third node
