Hm, maybe direct messages got killed in the community platform update, can't seem to find them.
Either way, drop me a note: mroy at vmware dot com
Hm, maybe direct messages got killed in the community platform update, can't seem to find them.
Either way, drop me a note: mroy at vmware dot com
No matter what the reasons are, this introduces a problem of security. You probably should not dump a workstation on a server VLAN. You would probably need to make a new VLAN, perhaps work with the network team, and then fuss with ACLs. I don't know the sensitivity levels of your security, but factoring that complication out, this seems like a reasonable request for a boss with a few potential uses. However, like Raul said, the boss' purpose would be helpful.
The boss would also have a different user experience depending if she or has direct access to your vSphere environment. Perhaps the goal is to test certain application and runtime versions, such as if something works with just java 7, or if it breaks on java 8, or if both versions of java can run at the same time. Perhaps your boss knows PowerShell and wants to test some commands to see their effect on the domain? What I'm getting at is that each of those things would have the benefit of being able to backstep with snapshots.
If your boss does not have vSphere access, which I'm guessing is the case, then the VM could be used over RDP and therefore function as a thin client. This way your boss can store main documents or install a critical app which can be accessed from anyone else's desktop. Regarding the use of a Windows Server instance for general workstation use, this can be a major inconvenience even if it is grubby with the IOPs and CPU resources. For example, trying to use Windows Server 2016 forces you to white list every single website you try to visit, making attempts to browse the web while in an RDP session awkward and cumbersome. This can be worse than it sounds because if trying to download a simple runtime dependency like Adobe then you can expect to need to whitelist over 12 subdomains which run in the background on that site.
Another assumption which might be fair to make is that your boss is simply more comfortable with the UI of Windows 10, even though Server 2016 uses the same kernel. If you are using Windows 2012 R2 and the Windows 8 kernel I can very much relate to why you would not want to use that unless you have to. Windows 2008 R2 with the Windows 7 kernel made it much easier (for me at least) to find simple things, instead of needing to fumble around awkwardly trying to get the search icon to appear and in lieu of using any navigation.
I can also see the use of this if a second "computer" is wanted, even if just as a form of extended storage. Perhaps you have a network file share with tight restrictions on it, and users such as your boss don't even have enough room to store a large PST file.
Windows 10, both as 32-bit and 64-bit, is supported by vSphere 6.5 according to the VMware Compatibility Guide (http://www.vmware.com/resources/compatibility/search.php?deviceCategory=software), so there would be no technical problems aside from the points about efficiency.
Assuming you're talking about update the Internet Explorer browser, try first disable the IE ESC.
Assuming you're talking about Datastore Cluster, the best practice is to have all volumes on a shared storage, this way the vSphere Storage DRS will be able to balance virtual machines between datastores automatically. If you use local disks, the virtual machine files availability will be affected in case of a host failure.
Looks like restarting the appliance has resolved the issue at least for the time being.
I was investigating the status of various services and was seeing some odd messages such as:
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
and this was showing up when I ran 'service vmware-vapi-endpoint start':
Apr 04 17:38:36 vc.elsys.gtri.org vapi-endpoint[45161]: Unable to write to the configured log file: ${vapi_log_dir}/wrapper.log (No such file or directory)
Falling back to the default file in the current working directory: wrapper.log
Apr 04 17:38:36 vc.elsys.gtri.org vapi-endpoint[45161]: Unable to write to the default log file: wrapper.log (Permission denied)
Disabling log file.
I'm super confused on the service management now, as there is both 'service-control' and 'service' and they don't seem to jive.
How to stop, start, or restart vCenter Server 6.x services (2109881) | VMware KB
How to stop, start, or restart vCenter Server Appliance services (2054085) | VMware KB
root@vc [ ~ ]# service vmware-vapi-endpoint status
â— vmware-vapi-endpoint.service - LSB: VMware vAPI Endpoint
Loaded: loaded (/etc/rc.d/init.d/vmware-vapi-endpoint; bad; vendor preset: enabled)
Active: inactive (dead)
Docs: man:systemd-sysv-generator(8)
root@vc [ ~ ]# service-control --status
Running:
applmgmt lwsmd pschealth vmafdd vmcad vmdird vmdnsd vmonapi vmware-cis-license vmware-cm vmware-content-library vmware-eam vmware-perfcharts vmware-psc-client vmware-rhttpproxy vmware-sca vmware-sps vmware-statsmonitor vmware-sts-idmd vmware-stsd vmware-updatemgr vmware-vapi-endpoint vmware-vmon vmware-vpostgres vmware-vpxd vmware-vpxd-svcs vmware-vsan-health vmware-vsm vsphere-client vsphere-ui
Stopped:
vmcam vmware-imagebuilder vmware-mbcs vmware-netdumper vmware-rbd-watchdog vmware-vcha
Anyway, still not sure what caused it, but rebooting got it working again.
I'm not sure if this is a bug or something I am doing wrong. Hopefully in the case of the former it will be brought to the attention of VMware.
I run VMware Workstation on Ubuntu 14.04 LTS to virtualize my Chef provisioning environment. In that environment I have several RHEL 6.8 (fully updated) VMs with the latest version of the VMware Tools OSPs (vmware-tools-esx-nox-10.1.5-1.el6.x86_64 and friends) which as far as I can tell at packages.vmware.com is the latest available version.
Yet when I run my VMs I get the "This VM's version of VMware Tools is out of date" message. Usually, at least in ESXi, the version is ignored as 3rd-party but I am sure that these OSPs are in fact fine to run on VMware Workstation.
Not a terribly big deal, but is there a new OSP release that I am missing?
For now I have only local disks availability which are mounted with 4 running blades. So can we do the clustering on these data store?
Hi, I was wondering how you got it to work?
I have a Tesla P100 GPU and I'm trying to passthrough to a VM on ESXi 6 which is on a Dell PowerEdge R730.
Adding the parameter doesn't seem to work for me. The GPU can be added to the Vsphere passthrough list (Advance Settings). After that I set up a Win 10 vm and installed it on EFI and used your parameter,"pciPassthru.use64bitMMIO", and in Windows it sees an unknown 3D Video Controller (Before and after installing VMWare Tools). The Nvidia Tesla drivers don't install as it says the version of Win is not supported and the graphics card can't be found, even though, the driver was from Nvidia for Win 10 and the GPU was added as a PCI device to the VM. Truly appreciate any help as I couldn't find much information online.
Mikero, thanks for the explanation and update.
But I am still frustrated by lack of progress. While the issue rests heavily on Apple's shoulder as things were working fine prior to 10.12.4 and even until the one of the last beta candidates (I filed a show stopper ticket against Apple when it broke on the last 10.12.4 beta), the fact of the matter is:
I'm very new to vRA and am now having to do this same thing and was wondering by the "same ID set", did you mean the two vCenters have to use the same endpoint name, or use the same credentials, or something completely different?
We currently have our new vCenter up, and have moved everything outside of vRA to it. I'm hoping this weekend to try this move.
Does this sound right?
Would it be easier/possible to just change the existing endpoint's address to the new vCenter after the hosts are moved? If I didn't have to reuse the existing hosts I could have it mostly up before hand.
Just wanted to update the thread hoping it'll be helpful to someone with the same issue.
Till now Office 2013 to 2016 UEM Application Migration is hit and miss.
Some basic settings like Gridlines is not getting migrated. While other settings like Outlook Signatures, Ribbons and Quick Access Toolbar are being migrated successfully.
I have a ticket open with VMware but they are as mute as this thread.
Regards,
Loc.
I have a Tesla P100 GPU and I'm trying to passthrough to a VM on ESXi 6 which is on a Dell PowerEdge R730.
Adding the parameter doesn't seem to work for me. The GPU can be added to the Vsphere passthrough list (Advance Settings). After that I set up a Win 10 vm and installed it on EFI and used the parameter,"pciPassthru.use64bitMMIO", and in Windows it sees an unknown 3D Video Controller (Before and after installing VMWare Tools). The Nvidia Tesla drivers don't install as it says the version of Win is not supported and the graphics card can't be found, even though, the driver was from Nvidia for Win 10 and the GPU was added as a PCI device to the VM. Truly appreciate any help as I couldn't find much information online.
If you plan to have High Availability is not a good idea to use local disks, since that disks are not shared between hosts, and if a single host fails, all virtual machines stored on local disk of that particular host will become unavailable.
Not sure why you can't export the template as OVF, but with release of vCenter 6.5, there is no longer support to export to OVA according with the release notes: VMware vSphere 6.5 Release Notes
vSphere Web Client does not support exporting virtual machines or vApps as OVA templates
In versions earlier than vSphere 6.5, you could export virtual machines and vApps as an OVA template on the vSphere Web Client. This functionality is not available in vSphere 6.5.
Workaround: Export the virtual machine as an OVF template, and then create an OVA template from the OVF template files. The following procedure describes this process using the Linux an Mac commands. Windows systems require installation of a TAR capable utility.
Like I said on my previous post, if that virtual machine as affected by a PDL, that explains the error. Can you confirm the exact build of your vCenter Server? And if you are still unable to power on that virtual machine, a workaround will be recreate a virtual machine and point to the existing virtual disks. Consider make a backup of your virtual disks and virtual machine files before create the new virtual machine.
Hi, we have some hosts that generate multiple logs every seconds such as below...
Any input on how to slow that?
(2017-04-04T23:01:45.918Z cpu28:33517)
--> (2017-04-04T23:01:45.931Z cpu28:33517)
--> (2017-04-04T23:01:46.240Z cpu28:33517)
--> (2017-04-04T23:01:46.430Z cpu28:33517)
--> (2017-04-04T23:01:46.443Z cpu28:33517)
--> (2017-04-04T23:01:46.741Z cpu28:33517)
--> (2017-04-04T23:01:46.752Z cpu28:33517)
--> (2017-04-04T23:01:46.956Z cpu28:33517)
--> (2017-04-04T23:01:47.253Z cpu28:33517)
--> (2017-04-04T23:01:47.287Z cpu28:33517)
--> (2017-04-04T23:01:47.468Z cpu28:33517)
Thanks
Assuming your virtual machine Guest OS is already installed on the VM virtual disk, just select the option "client device" and your virtual machine will boot fine. The ISO is needed only during the installation process or for some particular features that you want install after the installation, but the OS boot after the installation will use the virtual disk and not the ISO.
thanks
Agreed
Hi,
Are you perhaps using Avast or AVG antivirus at the host?
There's been a number of problems reported with both products bringing virtual machines to a halt.
If so, then read the following post:
XP VM suddenly slow, Win 7 fine
--
Wil