Quantcast
Channel: VMware Communities: Message List
Viewing all 223568 articles
Browse latest View live

Re: How to save/roam locally created desktop shortcuts and files

$
0
0

Ok first, your folder redirection doesn't work...couple of questions:

 

  • Did you configure UEM in/on a clean environment/desktop or straight into the environment where ProfileUnity was installed(or maybe still is) ?
  • Did you create a UEM config file to save the desktop shortcuts ?

 

Raymond


Re: VSphere VCenter Server Appliance install issue

$
0
0

Hi,

My AD/DNS server is indeed on the isolated VLAN

 

If i create a new server purely for DHCP/DNS and place that on .6 instead would that help do you think? I would then have just AD on .1 and use that ip as my gateway..

I did put a DNS entry in my DNS server for my VCSA server but I'm unsure how i'd be able to forward and reversve resolve the IP address to the DNS server.when the VCSA hasn't been created yet?

 

I have a very locked down router from my ISP so I doubt I'd be able to configure a route between the two VLANs on the router as you did. I also don't have any switches, just a server, a laptop and my router.

 

Cheers,

James

Re: How to replace default certificate for Secure Boot Virtual Machine?

Re: ubuntu 16.4 - after updating kernel, vmware workstation-pro 12 does not launch anymore

$
0
0

I found this but: https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2146460

 

a) I dont know if it is the correct solution.

b) I dont understand the instructions - what do they mean by "Replace MOKwith the name of the file you want for the key." - how do I know which name I should give the key?


BTW - I don't even know if my Ubuntu runs with UEFI, I just know that I got all these errors I described in my first post both on cmd and gui, but I don't their origin so I don't know if that vm kb is the answer.


Any help is highly appreciated, desperate here :-(


BTW: doing apt-get install libcanberra-gtk-module did not work and adding this "export LD_LIBRARY_PATH=/usr/lib/vmware/lib/libglibmm-2.4.so.1/:$LD_LIBRARY_PATH" to various files /usr/bin files also did not work.

 



Thanks!


Kitty

ESXi 5.1/6.0 Support of i7-6700 + Z170-A

$
0
0

Hi All:

 

I was wondering if anyone could tell me whether they've had any success running either ESXi 5.1 or ESXi 6.0 on a i7-6700 (Non-K) and Z170-A mobo? I've done extensive research online however I have not yet came across a clear answer.

 

If anyone is able to help it is very appreciated.

 

Thank You.

 

 

EDIT: For anyone who comes across this in the future I can confirm that the i7-6700 (non-k) and MSI Z170A PC-Mate are compatible with ESXi 6.0 (U2) with no issues at all. The NIC won't be detected at first but all you have to do is install the R8168 .VIB driver file and it will detect.

 

Thanks

Re: ubuntu 16.4 - after updating kernel, vmware workstation-pro 12 does not launch anymore

$
0
0

Hi,

 

All the gtk errors/warnings are a red herring. They do not prevent you from using VMware Workstation.

 

The real problem is that you are missing one or more kernel modules (like vmmon) because they cannot be compiled on your new kernel.

 

Can you attach /tmp/vmware-root/vmware-4182.log to a reply here?

 

Also note that if you need this to work -right now- then reboot your host and select the previous kernel in your boot menu.

 

--

Wil

Re: vROps PowerCLI throughput peak

$
0
0

I did some testing and all the time is being spent in group-object.  I don't know a good way to speed this up.  I think using super metrics to sum the read/write averages might be a better way to do this.  You can create custom groups for the VMs in vROps if necessary and assign the super metrics to the groups.

 

If you want try getting two metrics with powercli, put both key names in $omStatNames:

 

$omstatNames =  'virtualDisk|Read_Average', 'virtualDisk|write_average'

 

And then change the last line - this will group by time first, then group by the key names.  The sum of values for each key is added to the results for each time period.  This should accommodate as many metrics as you want, but unfortunately it will still be slow.

 

$p1Stat = Get-OMStat -Resource $omVM -Key $omStat -From $From -To $To | Group-Object -Property Time | %{

    $timeGroups = $_

    $timeGroups | % {

        $results = New-Object psobject -Property @{

                Time = $timeGroups.Name       

        }

        $_.Group | Group-Object -Property Key | % {

            $results | Add-Member -MemberType NoteProperty -Name $_.Name -Value ($_.Group | Measure-Object Value -Sum).Sum

        }

        $results

    }

 

}

 

 

 

Re: ubuntu 16.4 - after updating kernel, vmware workstation-pro 12 does not launch anymore

$
0
0

Hi wila, you are always here to help the community - AMAZING! So many thanks!! Here is the log. I dont need it to work right now, but just out of curiosity, how do I choose a previous kernel on boot, dont remember how to do that. And another question, the fact that vmon is missing is not UEFI's fault as the vmware KB suggested (and which I dont know if I use)?

 

cat /tmp/vmware-root/vmware-4182.log

2017-02-16T23:17:41.350+02:00| vthread-4| I125: Log for VMware Workstation pid=4182 version=12.5.2 build=build-4638234 option=Release

2017-02-16T23:17:41.350+02:00| vthread-4| I125: The process is 64-bit.

2017-02-16T23:17:41.350+02:00| vthread-4| I125: Host codepage=UTF-8 encoding=UTF-8

2017-02-16T23:17:41.350+02:00| vthread-4| I125: Host is Linux 4.4.0-62-generic Ubuntu 16.04.2 LTS

2017-02-16T23:17:41.254+02:00| vthread-4| I125: DictionaryLoad: Cannot open file "/usr/lib/vmware/settings": No such file or directory.

2017-02-16T23:17:41.254+02:00| vthread-4| I125: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.

2017-02-16T23:17:41.281+02:00| vthread-4| I125: DictionaryLoad: Cannot open file "/root/.vmware/config": No such file or directory.

2017-02-16T23:17:41.281+02:00| vthread-4| I125: PREF Optional preferences file not found at /root/.vmware/config. Using default values.

2017-02-16T23:17:41.400+02:00| vthread-4| W115: Logging to /tmp/vmware-root/vmware-4182.log

2017-02-16T23:17:41.438+02:00| vthread-4| I125: Obtaining info using the running kernel.

2017-02-16T23:17:41.438+02:00| vthread-4| I125: Created new pathsHash.

2017-02-16T23:17:41.438+02:00| vthread-4| I125: Setting header path for 4.4.0-62-generic to "/lib/modules/4.4.0-62-generic/build/include".

2017-02-16T23:17:41.438+02:00| vthread-4| I125: Validating path "/lib/modules/4.4.0-62-generic/build/include" for kernel release "4.4.0-62-generic".

2017-02-16T23:17:41.438+02:00| vthread-4| I125: Failed to find /lib/modules/4.4.0-62-generic/build/include/linux/version.h

2017-02-16T23:17:41.438+02:00| vthread-4| I125: /lib/modules/4.4.0-62-generic/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2017-02-16T23:17:41.438+02:00| vthread-4| I125: using /usr/bin/gcc for preprocess check

2017-02-16T23:17:41.443+02:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.4.0-62-generic".

2017-02-16T23:17:41.443+02:00| vthread-4| I125: The header path "/lib/modules/4.4.0-62-generic/build/include" for the kernel "4.4.0-62-generic" is valid.  Whoohoo!

2017-02-16T23:17:41.564+02:00| vthread-4| I125: found symbol version file /lib/modules/4.4.0-62-generic/build/Module.symvers

2017-02-16T23:17:41.564+02:00| vthread-4| I125: Reading symbol versions from /lib/modules/4.4.0-62-generic/build/Module.symvers.

2017-02-16T23:17:41.580+02:00| vthread-4| I125: Read 18828 symbol versions

2017-02-16T23:17:41.580+02:00| vthread-4| I125: Reading in info for the vmmon module.

2017-02-16T23:17:41.580+02:00| vthread-4| I125: Reading in info for the vmnet module.

2017-02-16T23:17:41.580+02:00| vthread-4| I125: Reading in info for the vmblock module.

2017-02-16T23:17:41.580+02:00| vthread-4| I125: Reading in info for the vmci module.

2017-02-16T23:17:41.580+02:00| vthread-4| I125: Reading in info for the vsock module.

2017-02-16T23:17:41.580+02:00| vthread-4| I125: Setting vsock to depend on vmci.

2017-02-16T23:17:41.580+02:00| vthread-4| I125: Invoking modinfo on "vmmon".

2017-02-16T23:17:41.581+02:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.

2017-02-16T23:17:41.581+02:00| vthread-4| I125: Invoking modinfo on "vmnet".

2017-02-16T23:17:41.582+02:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.

2017-02-16T23:17:41.582+02:00| vthread-4| I125: Invoking modinfo on "vmblock".

2017-02-16T23:17:41.583+02:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.

2017-02-16T23:17:41.583+02:00| vthread-4| I125: Invoking modinfo on "vmci".

2017-02-16T23:17:41.584+02:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.

2017-02-16T23:17:41.584+02:00| vthread-4| I125: Invoking modinfo on "vsock".

2017-02-16T23:17:41.585+02:00| vthread-4| I125: "/sbin/modinfo" exited with status 0.

2017-02-16T23:17:41.595+02:00| vthread-4| I125: to be installed: vmmon status: 0

2017-02-16T23:17:41.595+02:00| vthread-4| I125: to be installed: vmnet status: 0

2017-02-16T23:17:41.650+02:00| vthread-4| I125: Obtaining info using the running kernel.

2017-02-16T23:17:41.650+02:00| vthread-4| I125: Setting header path for 4.4.0-62-generic to "/lib/modules/4.4.0-62-generic/build/include".

2017-02-16T23:17:41.650+02:00| vthread-4| I125: Validating path "/lib/modules/4.4.0-62-generic/build/include" for kernel release "4.4.0-62-generic".

2017-02-16T23:17:41.650+02:00| vthread-4| I125: Failed to find /lib/modules/4.4.0-62-generic/build/include/linux/version.h

2017-02-16T23:17:41.650+02:00| vthread-4| I125: /lib/modules/4.4.0-62-generic/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2017-02-16T23:17:41.650+02:00| vthread-4| I125: using /usr/bin/gcc for preprocess check

2017-02-16T23:17:41.656+02:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.4.0-62-generic".

2017-02-16T23:17:41.656+02:00| vthread-4| I125: The header path "/lib/modules/4.4.0-62-generic/build/include" for the kernel "4.4.0-62-generic" is valid.  Whoohoo!

2017-02-16T23:17:41.776+02:00| vthread-4| I125: found symbol version file /lib/modules/4.4.0-62-generic/build/Module.symvers

2017-02-16T23:17:41.776+02:00| vthread-4| I125: Reading symbol versions from /lib/modules/4.4.0-62-generic/build/Module.symvers.

2017-02-16T23:17:41.791+02:00| vthread-4| I125: Read 18828 symbol versions

2017-02-16T23:17:41.791+02:00| vthread-4| I125: Kernel header path retrieved from FileEntry: /lib/modules/4.4.0-62-generic/build/include

2017-02-16T23:17:41.791+02:00| vthread-4| I125: Update kernel header path to /lib/modules/4.4.0-62-generic/build/include

2017-02-16T23:17:41.791+02:00| vthread-4| I125: Validating path "/lib/modules/4.4.0-62-generic/build/include" for kernel release "4.4.0-62-generic".

2017-02-16T23:17:41.791+02:00| vthread-4| I125: Failed to find /lib/modules/4.4.0-62-generic/build/include/linux/version.h

2017-02-16T23:17:41.791+02:00| vthread-4| I125: /lib/modules/4.4.0-62-generic/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2017-02-16T23:17:41.791+02:00| vthread-4| I125: using /usr/bin/gcc for preprocess check

2017-02-16T23:17:41.796+02:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.4.0-62-generic".

2017-02-16T23:17:41.797+02:00| vthread-4| I125: The header path "/lib/modules/4.4.0-62-generic/build/include" for the kernel "4.4.0-62-generic" is valid.  Whoohoo!

2017-02-16T23:17:41.797+02:00| vthread-4| I125: Found compiler at "/usr/bin/gcc"

2017-02-16T23:17:41.799+02:00| vthread-4| I125: Got gcc version "5.4.0".

2017-02-16T23:17:41.799+02:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.

2017-02-16T23:17:41.799+02:00| vthread-4| I125: Using user supplied compiler "/usr/bin/gcc".

2017-02-16T23:17:41.801+02:00| vthread-4| I125: Got gcc version "5.4.0".

2017-02-16T23:17:41.801+02:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.

2017-02-16T23:17:41.802+02:00| vthread-4| I125: Trying to find a suitable PBM set for kernel "4.4.0-62-generic".

2017-02-16T23:17:41.802+02:00| vthread-4| I125: No matching PBM set was found for kernel "4.4.0-62-generic".

2017-02-16T23:17:41.803+02:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.

2017-02-16T23:17:41.803+02:00| vthread-4| I125: Validating path "/lib/modules/4.4.0-62-generic/build/include" for kernel release "4.4.0-62-generic".

2017-02-16T23:17:41.803+02:00| vthread-4| I125: Failed to find /lib/modules/4.4.0-62-generic/build/include/linux/version.h

2017-02-16T23:17:41.803+02:00| vthread-4| I125: /lib/modules/4.4.0-62-generic/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2017-02-16T23:17:41.803+02:00| vthread-4| I125: using /usr/bin/gcc for preprocess check

2017-02-16T23:17:41.808+02:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.4.0-62-generic".

2017-02-16T23:17:41.808+02:00| vthread-4| I125: The header path "/lib/modules/4.4.0-62-generic/build/include" for the kernel "4.4.0-62-generic" is valid.  Whoohoo!

2017-02-16T23:17:41.809+02:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.

2017-02-16T23:17:41.809+02:00| vthread-4| I125: Validating path "/lib/modules/4.4.0-62-generic/build/include" for kernel release "4.4.0-62-generic".

2017-02-16T23:17:41.809+02:00| vthread-4| I125: Failed to find /lib/modules/4.4.0-62-generic/build/include/linux/version.h

2017-02-16T23:17:41.809+02:00| vthread-4| I125: /lib/modules/4.4.0-62-generic/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2017-02-16T23:17:41.809+02:00| vthread-4| I125: using /usr/bin/gcc for preprocess check

2017-02-16T23:17:41.814+02:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.4.0-62-generic".

2017-02-16T23:17:41.814+02:00| vthread-4| I125: The header path "/lib/modules/4.4.0-62-generic/build/include" for the kernel "4.4.0-62-generic" is valid.  Whoohoo!

2017-02-16T23:17:41.814+02:00| vthread-4| I125: Using temp dir "/tmp".

2017-02-16T23:17:41.815+02:00| vthread-4| I125: Obtaining info using the running kernel.

2017-02-16T23:17:41.815+02:00| vthread-4| I125: Setting header path for 4.4.0-62-generic to "/lib/modules/4.4.0-62-generic/build/include".

2017-02-16T23:17:41.815+02:00| vthread-4| I125: Validating path "/lib/modules/4.4.0-62-generic/build/include" for kernel release "4.4.0-62-generic".

2017-02-16T23:17:41.815+02:00| vthread-4| I125: Failed to find /lib/modules/4.4.0-62-generic/build/include/linux/version.h

2017-02-16T23:17:41.815+02:00| vthread-4| I125: /lib/modules/4.4.0-62-generic/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2017-02-16T23:17:41.815+02:00| vthread-4| I125: using /usr/bin/gcc for preprocess check

2017-02-16T23:17:41.820+02:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.4.0-62-generic".

2017-02-16T23:17:41.820+02:00| vthread-4| I125: The header path "/lib/modules/4.4.0-62-generic/build/include" for the kernel "4.4.0-62-generic" is valid.  Whoohoo!

2017-02-16T23:17:41.933+02:00| vthread-4| I125: found symbol version file /lib/modules/4.4.0-62-generic/build/Module.symvers

2017-02-16T23:17:41.933+02:00| vthread-4| I125: Reading symbol versions from /lib/modules/4.4.0-62-generic/build/Module.symvers.

2017-02-16T23:17:41.948+02:00| vthread-4| I125: Read 18828 symbol versions

2017-02-16T23:17:41.948+02:00| vthread-4| I125: Invoking modinfo on "vmmon".

2017-02-16T23:17:41.950+02:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.

2017-02-16T23:17:41.950+02:00| vthread-4| I125: Invoking modinfo on "vmnet".

2017-02-16T23:17:41.951+02:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.

2017-02-16T23:17:42.231+02:00| vthread-4| I125: Setting destination path for vmmon to "/lib/modules/4.4.0-62-generic/misc/vmmon.ko".

2017-02-16T23:17:42.231+02:00| vthread-4| I125: Extracting the vmmon source from "/usr/lib/vmware/modules/source/vmmon.tar".

2017-02-16T23:17:42.236+02:00| vthread-4| I125: Successfully extracted the vmmon source.

2017-02-16T23:17:42.237+02:00| vthread-4| I125: Building module with command "/usr/bin/make -j4 -C /tmp/modconfig-wWZAu8/vmmon-only auto-build HEADER_DIR=/lib/modules/4.4.0-62-generic/build/include CC=/usr/bin/gcc IS_GCC_3=no"

2017-02-16T23:17:43.873+02:00| vthread-4| I125: Successfully built vmmon.  Module is currently at "/tmp/modconfig-wWZAu8/vmmon.o".

2017-02-16T23:17:43.873+02:00| vthread-4| I125: Found the vmmon symvers file at "/tmp/modconfig-wWZAu8/vmmon-only/Module.symvers".

2017-02-16T23:17:43.873+02:00| vthread-4| I125: Installing vmmon from /tmp/modconfig-wWZAu8/vmmon.o to /lib/modules/4.4.0-62-generic/misc/vmmon.ko.

2017-02-16T23:17:43.873+02:00| vthread-4| I125: Registering file "/lib/modules/4.4.0-62-generic/misc/vmmon.ko".

2017-02-16T23:17:45.750+02:00| vthread-4| I125: "/usr/lib/vmware-installer/2.1.0/vmware-installer" exited with status 0.

2017-02-16T23:17:45.750+02:00| vthread-4| I125: Registering file "/usr/lib/vmware/symvers/vmmon-4.4.0-62-generic".

2017-02-16T23:17:46.390+02:00| vthread-4| I125: "/usr/lib/vmware-installer/2.1.0/vmware-installer" exited with status 0.

2017-02-16T23:17:46.392+02:00| vthread-4| I125: Setting destination path for vmnet to "/lib/modules/4.4.0-62-generic/misc/vmnet.ko".

2017-02-16T23:17:46.392+02:00| vthread-4| I125: Extracting the vmnet source from "/usr/lib/vmware/modules/source/vmnet.tar".

2017-02-16T23:17:46.398+02:00| vthread-4| I125: Successfully extracted the vmnet source.

2017-02-16T23:17:46.398+02:00| vthread-4| I125: Building module with command "/usr/bin/make -j4 -C /tmp/modconfig-wWZAu8/vmnet-only auto-build HEADER_DIR=/lib/modules/4.4.0-62-generic/build/include CC=/usr/bin/gcc IS_GCC_3=no"

2017-02-16T23:17:48.387+02:00| vthread-4| I125: Successfully built vmnet.  Module is currently at "/tmp/modconfig-wWZAu8/vmnet.o".

2017-02-16T23:17:48.387+02:00| vthread-4| I125: Found the vmnet symvers file at "/tmp/modconfig-wWZAu8/vmnet-only/Module.symvers".

2017-02-16T23:17:48.387+02:00| vthread-4| I125: Installing vmnet from /tmp/modconfig-wWZAu8/vmnet.o to /lib/modules/4.4.0-62-generic/misc/vmnet.ko.

2017-02-16T23:17:48.388+02:00| vthread-4| I125: Registering file "/lib/modules/4.4.0-62-generic/misc/vmnet.ko".

2017-02-16T23:17:48.972+02:00| vthread-4| I125: "/usr/lib/vmware-installer/2.1.0/vmware-installer" exited with status 0.

2017-02-16T23:17:48.972+02:00| vthread-4| I125: Registering file "/usr/lib/vmware/symvers/vmnet-4.4.0-62-generic".

2017-02-16T23:17:49.600+02:00| vthread-4| I125: "/usr/lib/vmware-installer/2.1.0/vmware-installer" exited with status 0.

2017-02-16T23:19:12.202+02:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.

2017-02-16T23:19:12.202+02:00| vthread-4| I125: Validating path "/lib/modules/4.4.0-62-generic/build/include" for kernel release "4.4.0-62-generic".

2017-02-16T23:19:12.202+02:00| vthread-4| I125: Failed to find /lib/modules/4.4.0-62-generic/build/include/linux/version.h

2017-02-16T23:19:12.203+02:00| vthread-4| I125: /lib/modules/4.4.0-62-generic/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2017-02-16T23:19:12.203+02:00| vthread-4| I125: using /usr/bin/gcc for preprocess check

2017-02-16T23:19:12.210+02:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.4.0-62-generic".

2017-02-16T23:19:12.210+02:00| vthread-4| I125: The header path "/lib/modules/4.4.0-62-generic/build/include" for the kernel "4.4.0-62-generic" is valid.  Whoohoo!

2017-02-16T23:19:12.211+02:00| vthread-4| I125: Using temp dir "/tmp".

2017-02-16T23:19:12.211+02:00| vthread-4| I125: Obtaining info using the running kernel.

2017-02-16T23:19:12.211+02:00| vthread-4| I125: Setting header path for 4.4.0-62-generic to "/lib/modules/4.4.0-62-generic/build/include".

2017-02-16T23:19:12.211+02:00| vthread-4| I125: Validating path "/lib/modules/4.4.0-62-generic/build/include" for kernel release "4.4.0-62-generic".

2017-02-16T23:19:12.211+02:00| vthread-4| I125: Failed to find /lib/modules/4.4.0-62-generic/build/include/linux/version.h

2017-02-16T23:19:12.211+02:00| vthread-4| I125: /lib/modules/4.4.0-62-generic/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2017-02-16T23:19:12.211+02:00| vthread-4| I125: using /usr/bin/gcc for preprocess check

2017-02-16T23:19:12.219+02:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.4.0-62-generic".

2017-02-16T23:19:12.219+02:00| vthread-4| I125: The header path "/lib/modules/4.4.0-62-generic/build/include" for the kernel "4.4.0-62-generic" is valid.  Whoohoo!

2017-02-16T23:19:12.379+02:00| vthread-4| I125: found symbol version file /lib/modules/4.4.0-62-generic/build/Module.symvers

2017-02-16T23:19:12.379+02:00| vthread-4| I125: Reading symbol versions from /lib/modules/4.4.0-62-generic/build/Module.symvers.

2017-02-16T23:19:12.398+02:00| vthread-4| I125: Read 18828 symbol versions

2017-02-16T23:19:12.398+02:00| vthread-4| I125: Invoking modinfo on "vmmon".

2017-02-16T23:19:12.400+02:00| vthread-4| I125: "/sbin/modinfo" exited with status 0.

2017-02-16T23:19:12.400+02:00| vthread-4| I125: Invoking modinfo on "vmnet".

2017-02-16T23:19:12.402+02:00| vthread-4| I125: "/sbin/modinfo" exited with status 0.

2017-02-16T23:19:20.731+02:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.

2017-02-16T23:19:20.732+02:00| vthread-4| I125: Validating path "/lib/modules/4.4.0-62-generic/build/include" for kernel release "4.4.0-62-generic".

2017-02-16T23:19:20.732+02:00| vthread-4| I125: Failed to find /lib/modules/4.4.0-62-generic/build/include/linux/version.h

2017-02-16T23:19:20.732+02:00| vthread-4| I125: /lib/modules/4.4.0-62-generic/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2017-02-16T23:19:20.732+02:00| vthread-4| I125: using /usr/bin/gcc for preprocess check

2017-02-16T23:19:20.740+02:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.4.0-62-generic".

2017-02-16T23:19:20.740+02:00| vthread-4| I125: The header path "/lib/modules/4.4.0-62-generic/build/include" for the kernel "4.4.0-62-generic" is valid.  Whoohoo!

2017-02-16T23:19:20.740+02:00| vthread-4| I125: Using temp dir "/tmp".

2017-02-16T23:19:20.741+02:00| vthread-4| I125: Obtaining info using the running kernel.

2017-02-16T23:19:20.741+02:00| vthread-4| I125: Setting header path for 4.4.0-62-generic to "/lib/modules/4.4.0-62-generic/build/include".

2017-02-16T23:19:20.741+02:00| vthread-4| I125: Validating path "/lib/modules/4.4.0-62-generic/build/include" for kernel release "4.4.0-62-generic".

2017-02-16T23:19:20.741+02:00| vthread-4| I125: Failed to find /lib/modules/4.4.0-62-generic/build/include/linux/version.h

2017-02-16T23:19:20.741+02:00| vthread-4| I125: /lib/modules/4.4.0-62-generic/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2017-02-16T23:19:20.741+02:00| vthread-4| I125: using /usr/bin/gcc for preprocess check

2017-02-16T23:19:20.750+02:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.4.0-62-generic".

2017-02-16T23:19:20.750+02:00| vthread-4| I125: The header path "/lib/modules/4.4.0-62-generic/build/include" for the kernel "4.4.0-62-generic" is valid.  Whoohoo!

2017-02-16T23:19:20.914+02:00| vthread-4| I125: found symbol version file /lib/modules/4.4.0-62-generic/build/Module.symvers

2017-02-16T23:19:20.914+02:00| vthread-4| I125: Reading symbol versions from /lib/modules/4.4.0-62-generic/build/Module.symvers.

2017-02-16T23:19:20.934+02:00| vthread-4| I125: Read 18828 symbol versions

2017-02-16T23:19:20.934+02:00| vthread-4| I125: Invoking modinfo on "vmmon".

2017-02-16T23:19:20.936+02:00| vthread-4| I125: "/sbin/modinfo" exited with status 0.

2017-02-16T23:19:20.936+02:00| vthread-4| I125: Invoking modinfo on "vmnet".

2017-02-16T23:19:20.938+02:00| vthread-4| I125: "/sbin/modinfo" exited with status 0.


NIC Driver Not Recognized During ESXi 6.5 Installation

$
0
0

I'm very new to the ESXi Hypervisor and would like to learn about its capabilities.  Unfortunately, the only test hardware I currently have available is an HP 2000-369WM laptop (calling this hardware far from ideal for this type of testing is an understatement).  I've tried installing ESXi 6.5 but, as anticipated, my NIC (Realtek PCIe FE Family Controller, Hardware ID PCI\VEN_10EC&DEV_8136&SUBSYS_3577103C) was not recognized/supported.  I was hoping to use the ESXi Customizer to include my NIC driver in the installation .iso but can't seem to find an appropriate driver .vib.  Does anyone have any suggestions?  Thanks in advance. 

Re: ubuntu 16.4 - after updating kernel, vmware workstation-pro 12 does not launch anymore

Re: How to save/roam locally created desktop shortcuts and files

$
0
0

So I moved the user to an OU that doesn't have the organization GPOs, including Profile Unity, in order to troubleshoot and narrow this down.  By doing so, folder redirection works.   So now a matter of adding them one at a time, starting with Prof Unity to see if that breaks it.   Progress at least.

Re: ubuntu 16.4 - after updating kernel, vmware workstation-pro 12 does not launch anymore

$
0
0

Hi wil, that's OK, I will wait until you have time to take a look at it, I don't want to be using older kernels, I want it to work with the current one, let me know when you have time and if you need more info from me.

 

And if anyone else has time to take a look or ideas it is more than welcome!

 

Many thanks!!!

How to Export out VSAN back-end performance charts/metric?

$
0
0

hello All, Does any know how to extract/export out by webclient/script the VSAN back-end performance charts/metric? (See screenshot)

Re: How to Export out VSAN back-end performance charts/metric?

Re: Unable to open PSC(Platform Service Controller) VM

$
0
0

Untitledvm(4).jpg

But the screenshot shows there is a file called DC3PVWINPSC01_1.vmdk.  the file type is file instead of virtual disk@@


Re: Things not possible without cloud client

$
0
0

Programmatic? 

 

Some things against IaaS are not readily possible (or well documented).  The best thing to do is to go to the swagger documentation on the VRA appliance and view the REST API for the various services.  (YourApplianceURL/component-registry/services/docs and expand the lists at the bottom with the show/hide link)

 

For example... you cannot move a machine through the provider or consumer catalog-service api to a different business group (that I could find).  Cloud Client makes that easy with...

 

vra machines change reservation --ids _________ --reservationName ________ (this is possible in the GUI)

 

I don't think there is an equivalent for this either...  (this will remove the machine from VRA but leave it unmanaged in virtual center)

 

vra machines forceunregister --name ___________ (I don't think this is possible in the GUI)


There may be more.  (Reservations can be worked with, but I have all of that built out through a REST interface.)


There are still some things where I use SSH (with key) from vRO workflow to a script host to run CC commands.  Works well.  People who are good with command line, but struggle with API calls and/or JS scripting in vRO will find benefit to using Cloud Client.

Re: VSphere VCenter Server Appliance install issue

$
0
0

James,

 

Is there a reason for the environment to be isolated?

 

Have you configured a Gateway address on the Windows AD Server?  If so what is it?

 

Is the AD Server a Virtual Machine on the ESXi Server? Is the WIndows 7 Desktop a Virtual Machine on the ESXi host or is it the Laptop connected to the switch?

 

Personally given the limited equipment you have I would put everything into the 192.168.x.x address space, changed the ISP router's DHCP scope to exclude (lets say) 50 addresses, then statically assign those 50 addresses to anything you need in your home lab and then use the ISP Router as the gateway.  Just because they in the same address space doesn't mean you will have any issues.

 

Also did you try to connect to https://10.0.0.101:5480/ because if name resolution isn't working you should still be able to get it via IP.

 

However if your machine is on the 192.168.x.x network not sure how your going to route to and off of that network.

 

Chris

Re: Guidelines on configuring VMware Integrated Openstack with LDAP authentication against MS AD

$
0
0

Hi, I did all your steps, but in the last step (Grant users to project): If i put the same command, i get an output "Must specify either a domain or project ", is the last command right?

If i put openstack role --user demo@somecorp.com --domain default admin, I get: No user with a name or ID of 'demo@somecorp.com' exists.

if i put openstack role --user demo@somecorp.com --project lab admin, i also get: No user with a name or ID of 'demo@somecorp.com' exists.

Although when i put openstack user list --domain default, I see the user "demo@somecorp.com" listed there.

 

Any ideas?

What is the equivalent command "clear ip ospf process" in DLR and ESG?

$
0
0

Hi, Experts

I have one simple question on "clear ip ospf process" command.

I tried to find its command in DLR and ESG but I can only type "show ~ " command...

What if I need to type "clear ip ospf process" in DLR and ESG, how am I do that?

 

Thanks alot!

Re: List Portgroups with Private VLANS

$
0
0

Hi Luc,

 

This works well, what would i remove to filter out hosts as that info is not needed?

 

Cheers

Viewing all 223568 articles
Browse latest View live


Latest Images

<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>