It's been 7 years since this post, and I'm having the exact problem now in 2019 ... i get the following errors in the event viewer each time I plug in our out a USB device ( See detail from Event Viewer below )

I'm running VMware Workstation 15 pro, latest version as of today ( 15.0.2 build-10952284 ), on an ASUS ROG GL702V Notebook, on Windows 10 64 bits latest build (17763).

Reading in ASUS' forums, the only solution that actually works is to disable the "VMWare USB Arbitration Service" , but that is not a real solution since it disables the possibility to attach USB devices to VM's.

Any ideas/suggestions?

Log Name:      System

Source:        hcmon

Date:          2/3/2019 11:01:33 PM

Event ID:      0

Task Category: None

Level:         Warning

Keywords:      Classic

User:          N/A

Computer:      ASUS

Description:

Detected unrecognized USB driver (\Driver\PnpManager).

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="hcmon" />

    <EventID Qualifiers="32768">0</EventID>

    <Level>3</Level>

    <Task>0</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2019-02-04T02:01:33.388210900Z" />

    <EventRecordID>32111</EventRecordID>

    <Channel>System</Channel>

    <Computer>ASUS</Computer>

    <Security />

  </System>

  <EventData>

    <Data>\Device\hcmon</Data>

    <Data>\Driver\PnpManager</Data>

    <Binary>00000000020028000000000000000080000000000000000000000000000000000000000000000000</Binary>

  </EventData>

</Event>

 

 

Log Name:      System

Source:        hcmon

Date:          2/3/2019 11:01:33 PM

Event ID:      0

Task Category: None

Level:         Warning

Keywords:      Classic

User:          N/A

Computer:      ASUS

Description:

Detected unrecognized USB driver (\Driver\nxusbh).

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="hcmon" />

    <EventID Qualifiers="32768">0</EventID>

    <Level>3</Level>

    <Task>0</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2019-02-04T02:01:33.388210900Z" />

    <EventRecordID>32110</EventRecordID>

    <Channel>System</Channel>

    <Computer>ASUS</Computer>

    <Security />

  </System>

  <EventData>

    <Data>\Device\hcmon</Data>

    <Data>\Driver\nxusbh</Data>

    <Binary>00000000020028000000000000000080000000000000000000000000000000000000000000000000</Binary>

  </EventData>

</Event>

 

 

Log Name:      System

Source:        hcmon

Date:          2/3/2019 11:01:33 PM

Event ID:      0

Task Category: None

Level:         Warning

Keywords:      Classic

User:          N/A

Computer:      ASUS

Description:

Detected unrecognized USB driver (\Driver\nxusbf).

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="hcmon" />

    <EventID Qualifiers="32768">0</EventID>

    <Level>3</Level>

    <Task>0</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2019-02-04T02:01:33.388210900Z" />

    <EventRecordID>32109</EventRecordID>

    <Channel>System</Channel>

    <Computer>ASUS</Computer>

    <Security />

  </System>

  <EventData>

    <Data>\Device\hcmon</Data>

    <Data>\Driver\nxusbf</Data>

    <Binary>00000000020028000000000000000080000000000000000000000000000000000000000000000000</Binary>

  </EventData>

</Event>

Dear Community Guru's.

I've found posts as old as 7 years old referring to this issue, and I'm having the exact problem now in 2019. I get the errors below in the event viewer each time I plug in our out a USB device. And also at random times ( without actually plugging in anything.)

I'm running VMware Workstation 15 pro, latest version as of today ( 15.0.2 build-10952284 ), on an ASUS ROG GL702V Notebook, on Windows 10 64 bits latest build (17763).

Reading in ASUS' forums, the only solution that actually works is to disable the "VMWare USB Arbitration Service" , but that is not a real solution since it disables the possibility to attach USB devices to VM's.

Any ideas/suggestions?

Log Name:      System

Source:        hcmon

Date:          2/3/2019 11:01:33 PM

Event ID:      0

Task Category: None

Level:         Warning

Keywords:      Classic

User:          N/A

Computer:      ASUS

Description:

Detected unrecognized USB driver (\Driver\PnpManager).

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="hcmon" />

    <EventID Qualifiers="32768">0</EventID>

    <Level>3</Level>

    <Task>0</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2019-02-04T02:01:33.388210900Z" />

    <EventRecordID>32111</EventRecordID>

    <Channel>System</Channel>

    <Computer>ASUS</Computer>

    <Security />

  </System>

  <EventData>

    <Data>\Device\hcmon</Data>

    <Data>\Driver\PnpManager</Data>

    <Binary>00000000020028000000000000000080000000000000000000000000000000000000000000000000</Binary>

  </EventData>

</Event>

 

 

Log Name:      System

Source:        hcmon

Date:          2/3/2019 11:01:33 PM

Event ID:      0

Task Category: None

Level:         Warning

Keywords:      Classic

User:          N/A

Computer:      ASUS

Description:

Detected unrecognized USB driver (\Driver\nxusbh).

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="hcmon" />

    <EventID Qualifiers="32768">0</EventID>

    <Level>3</Level>

    <Task>0</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2019-02-04T02:01:33.388210900Z" />

    <EventRecordID>32110</EventRecordID>

    <Channel>System</Channel>

    <Computer>ASUS</Computer>

    <Security />

  </System>

  <EventData>

    <Data>\Device\hcmon</Data>

    <Data>\Driver\nxusbh</Data>

    <Binary>00000000020028000000000000000080000000000000000000000000000000000000000000000000</Binary>

  </EventData>

</Event>

 

 

Log Name:      System

Source:        hcmon

Date:          2/3/2019 11:01:33 PM

Event ID:      0

Task Category: None

Level:         Warning

Keywords:      Classic

User:          N/A

Computer:      ASUS

Description:

Detected unrecognized USB driver (\Driver\nxusbf).

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="hcmon" />

    <EventID Qualifiers="32768">0</EventID>

    <Level>3</Level>

    <Task>0</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2019-02-04T02:01:33.388210900Z" />

    <EventRecordID>32109</EventRecordID>

    <Channel>System</Channel>

    <Computer>ASUS</Computer>

    <Security />

  </System>

  <EventData>

    <Data>\Device\hcmon</Data>

    <Data>\Driver\nxusbf</Data>

    <Binary>00000000020028000000000000000080000000000000000000000000000000000000000000000000</Binary>

  </EventData>

</Event>

 

hello

We will purchase a supermicro 6029P-TRT server.

however, I hope to install ESXI 6.7u1 itself on intel P4800x.

I didn't found any article about this.

Could anyone give me some experience?

Thanks all

I'm extremely interested in this Thread as the exact same thing is happening to me ... I just posted a thread about it, here : HCMON Warning in Event Viewer - "Detected unrecognized USB driver (\Driver\nxusbh)" and "\Driver\nxusbf" and "\Driver\Pn…

In it I detail the software versions and hardware I'm running when getting the error. As bonnie201110141 says, the error/BSOD happens when VMWare is running, or not, that doesn't matter. It's absolutely a driver bug that does not work ok in notebooks ( Mine is an ASUS, the other is a Lenovo), so i guess it has to do with an incompatibility with the chipset, or some other subsystem ( audio ? )

I'm eager to read more

Regards,
Mariano

Was there any further development on this thread? Still having the same issue ....

Regards,

Mariano

The physical machine is windows 10 1709.

The physical machine uses a wireless network.

The VMware workstation is 15

The VM is Windows server 2016.

The network of VM configuration is bridged.

The VM cannot get the IP.

This is VMware Workstation network configure:

This is VM network configure:

A VM running on the VMware Workstation.

I want to use RDP connection to the VM on the physical machine.

The VM network configure is NAT.

This is NAT configure:

The VM IP address is 192.168.65.128.

How do connection to the VM use RDP.

What is the IP address of connection to the VM.

I upgraded Fedora 29 with kernel 4.20 ti Fedora 30 (Rawhide).   VMware WS 15.0.2 still works if I boot to Fedora 29 and WS "almost" compiles ib kernel 5.0.2.   Usually I would compress the log but I'm posting it uncompressed this time since somewhere here can probably figure out how to work around these errors. FWIW Virtualbox works with but kernels.

2019-02-03T22:20:42.495-05:00| host-4243| I125: Log for VMware Workstation pid=4243 version=15.0.2 build=build-10952284 option=Release

2019-02-03T22:20:42.495-05:00| host-4243| I125: The process is 64-bit.

2019-02-03T22:20:42.495-05:00| host-4243| I125: Host codepage=UTF-8 encoding=UTF-8

2019-02-03T22:20:42.495-05:00| host-4243| I125: Host is Linux 5.0.0-0.rc4.git3.1.fc30.x86_64 Fedora release 30 (Rawhide)

2019-02-03T22:20:42.495-05:00| host-4243| I125: DictionaryLoad: Cannot open file "/usr/lib/vmware/settings": No such file or directory.

2019-02-03T22:20:42.495-05:00| host-4243| I125: [msg.dictionary.load.openFailed] Cannot open file "/usr/lib/vmware/settings": No such file or directory.

2019-02-03T22:20:42.495-05:00| host-4243| I125: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.

2019-02-03T22:20:42.495-05:00| host-4243| I125: DictionaryLoad: Cannot open file "/home/marty/.vmware/config": No such file or directory.

2019-02-03T22:20:42.495-05:00| host-4243| I125: [msg.dictionary.load.openFailed] Cannot open file "/home/marty/.vmware/config": No such file or directory.

2019-02-03T22:20:42.495-05:00| host-4243| I125: PREF Optional preferences file not found at /home/marty/.vmware/config. Using default values.

2019-02-03T22:20:42.497-05:00| host-4243| W115: Logging to /tmp/vmware-root/vmware-4243.log

2019-02-03T22:20:42.531-05:00| host-4243| I125: Obtaining info using the running kernel.

2019-02-03T22:20:42.531-05:00| host-4243| I125: Created new pathsHash.

2019-02-03T22:20:42.532-05:00| host-4243| I125: Setting header path for 5.0.0-0.rc4.git3.1.fc30.x86_64 to "/lib/modules/5.0.0-0.rc4.git3.1.fc30.x86_64/build/include".

2019-02-03T22:20:42.532-05:00| host-4243| I125: Validating path "/lib/modules/5.0.0-0.rc4.git3.1.fc30.x86_64/build/include" for kernel release "5.0.0-0.rc4.git3.1.fc30.x86_64".

2019-02-03T22:20:42.532-05:00| host-4243| I125: Failed to find /lib/modules/5.0.0-0.rc4.git3.1.fc30.x86_64/build/include/linux/version.h

2019-02-03T22:20:42.532-05:00| host-4243| I125: /lib/modules/5.0.0-0.rc4.git3.1.fc30.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2019-02-03T22:20:42.532-05:00| host-4243| I125: using /usr/bin/gcc for preprocess check

2019-02-03T22:20:42.541-05:00| host-4243| I125: Preprocessed UTS_RELEASE, got value "5.0.0-0.rc4.git3.1.fc30.x86_64".

2019-02-03T22:20:42.541-05:00| host-4243| I125: The header path "/lib/modules/5.0.0-0.rc4.git3.1.fc30.x86_64/build/include" for the kernel "5.0.0-0.rc4.git3.1.fc30.x86_64" is valid.  Whoohoo!

2019-02-03T22:20:42.666-05:00| host-4243| I125: found symbol version file /lib/modules/5.0.0-0.rc4.git3.1.fc30.x86_64/build/Module.symvers

2019-02-03T22:20:42.666-05:00| host-4243| I125: Reading symbol versions from /lib/modules/5.0.0-0.rc4.git3.1.fc30.x86_64/build/Module.symvers.

2019-02-03T22:20:42.679-05:00| host-4243| I125: Read 20774 symbol versions

2019-02-03T22:20:42.679-05:00| host-4243| I125: Reading in info for the vmmon module.

2019-02-03T22:20:42.679-05:00| host-4243| I125: Reading in info for the vmnet module.

2019-02-03T22:20:42.679-05:00| host-4243| I125: Reading in info for the vmci module.

2019-02-03T22:20:42.679-05:00| host-4243| I125: Reading in info for the vsock module.

2019-02-03T22:20:42.679-05:00| host-4243| I125: Setting vsock to depend on vmci.

2019-02-03T22:20:42.680-05:00| host-4243| I125: Invoking modinfo on "vmmon".

2019-02-03T22:20:42.683-05:00| host-4243| I125: "/sbin/modinfo" exited with status 256.

2019-02-03T22:20:42.683-05:00| host-4243| I125: Invoking modinfo on "vmnet".

2019-02-03T22:20:42.686-05:00| host-4243| I125: "/sbin/modinfo" exited with status 256.

2019-02-03T22:20:42.686-05:00| host-4243| I125: Invoking modinfo on "vmci".

2019-02-03T22:20:42.690-05:00| host-4243| I125: "/sbin/modinfo" exited with status 256.

2019-02-03T22:20:42.690-05:00| host-4243| I125: Invoking modinfo on "vsock".

2019-02-03T22:20:42.695-05:00| host-4243| I125: "/sbin/modinfo" exited with status 0.

2019-02-03T22:20:42.705-05:00| host-4243| I125: to be installed: vmmon status: 0

2019-02-03T22:20:42.705-05:00| host-4243| I125: to be installed: vmnet status: 0

2019-02-03T22:20:42.715-05:00| host-4243| I125: Obtaining info using the running kernel.

2019-02-03T22:20:42.716-05:00| host-4243| I125: Setting header path for 5.0.0-0.rc4.git3.1.fc30.x86_64 to "/lib/modules/5.0.0-0.rc4.git3.1.fc30.x86_64/build/include".

2019-02-03T22:20:42.716-05:00| host-4243| I125: Validating path "/lib/modules/5.0.0-0.rc4.git3.1.fc30.x86_64/build/include" for kernel release "5.0.0-0.rc4.git3.1.fc30.x86_64".

2019-02-03T22:20:42.716-05:00| host-4243| I125: Failed to find /lib/modules/5.0.0-0.rc4.git3.1.fc30.x86_64/build/include/linux/version.h

2019-02-03T22:20:42.716-05:00| host-4243| I125: /lib/modules/5.0.0-0.rc4.git3.1.fc30.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2019-02-03T22:20:42.716-05:00| host-4243| I125: using /usr/bin/gcc for preprocess check

2019-02-03T22:20:42.725-05:00| host-4243| I125: Preprocessed UTS_RELEASE, got value "5.0.0-0.rc4.git3.1.fc30.x86_64".

2019-02-03T22:20:42.725-05:00| host-4243| I125: The header path "/lib/modules/5.0.0-0.rc4.git3.1.fc30.x86_64/build/include" for the kernel "5.0.0-0.rc4.git3.1.fc30.x86_64" is valid.  Whoohoo!

2019-02-03T22:20:42.845-05:00| host-4243| I125: found symbol version file /lib/modules/5.0.0-0.rc4.git3.1.fc30.x86_64/build/Module.symvers

2019-02-03T22:20:42.845-05:00| host-4243| I125: Reading symbol versions from /lib/modules/5.0.0-0.rc4.git3.1.fc30.x86_64/build/Module.symvers.

2019-02-03T22:20:42.858-05:00| host-4243| I125: Read 20774 symbol versions

2019-02-03T22:20:42.860-05:00| host-4243| I125: Kernel header path retrieved from FileEntry: /lib/modules/5.0.0-0.rc4.git3.1.fc30.x86_64/build/include

2019-02-03T22:20:42.860-05:00| host-4243| I125: Update kernel header path to /lib/modules/5.0.0-0.rc4.git3.1.fc30.x86_64/build/include

2019-02-03T22:20:42.860-05:00| host-4243| I125: Validating path "/lib/modules/5.0.0-0.rc4.git3.1.fc30.x86_64/build/include" for kernel release "5.0.0-0.rc4.git3.1.fc30.x86_64".

2019-02-03T22:20:42.860-05:00| host-4243| I125: Failed to find /lib/modules/5.0.0-0.rc4.git3.1.fc30.x86_64/build/include/linux/version.h

2019-02-03T22:20:42.860-05:00| host-4243| I125: /lib/modules/5.0.0-0.rc4.git3.1.fc30.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2019-02-03T22:20:42.860-05:00| host-4243| I125: using /usr/bin/gcc for preprocess check

2019-02-03T22:20:42.871-05:00| host-4243| I125: Preprocessed UTS_RELEASE, got value "5.0.0-0.rc4.git3.1.fc30.x86_64".

2019-02-03T22:20:42.871-05:00| host-4243| I125: The header path "/lib/modules/5.0.0-0.rc4.git3.1.fc30.x86_64/build/include" for the kernel "5.0.0-0.rc4.git3.1.fc30.x86_64" is valid.  Whoohoo!

2019-02-03T22:20:42.872-05:00| host-4243| I125: Found compiler at "/usr/bin/gcc"

2019-02-03T22:20:42.876-05:00| host-4243| I125: Got gcc version "9".

2019-02-03T22:20:42.876-05:00| host-4243| I125: The GCC version matches the kernel GCC minor version like a glove.

2019-02-03T22:20:42.880-05:00| host-4243| I125: Got gcc version "9".

2019-02-03T22:20:42.880-05:00| host-4243| I125: The GCC version matches the kernel GCC minor version like a glove.

2019-02-03T22:20:42.882-05:00| host-4243| I125: Trying to find a suitable PBM set for kernel "5.0.0-0.rc4.git3.1.fc30.x86_64".

2019-02-03T22:20:42.882-05:00| host-4243| I125: No matching PBM set was found for kernel "5.0.0-0.rc4.git3.1.fc30.x86_64".

2019-02-03T22:20:42.882-05:00| host-4243| I125: The GCC version matches the kernel GCC minor version like a glove.

2019-02-03T22:20:42.882-05:00| host-4243| I125: Validating path "/lib/modules/5.0.0-0.rc4.git3.1.fc30.x86_64/build/include" for kernel release "5.0.0-0.rc4.git3.1.fc30.x86_64".

2019-02-03T22:20:42.882-05:00| host-4243| I125: Failed to find /lib/modules/5.0.0-0.rc4.git3.1.fc30.x86_64/build/include/linux/version.h

2019-02-03T22:20:42.882-05:00| host-4243| I125: /lib/modules/5.0.0-0.rc4.git3.1.fc30.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2019-02-03T22:20:42.882-05:00| host-4243| I125: using /usr/bin/gcc for preprocess check

2019-02-03T22:20:42.890-05:00| host-4243| I125: Preprocessed UTS_RELEASE, got value "5.0.0-0.rc4.git3.1.fc30.x86_64".

2019-02-03T22:20:42.890-05:00| host-4243| I125: The header path "/lib/modules/5.0.0-0.rc4.git3.1.fc30.x86_64/build/include" for the kernel "5.0.0-0.rc4.git3.1.fc30.x86_64" is valid.  Whoohoo!

2019-02-03T22:20:42.891-05:00| host-4243| I125: The GCC version matches the kernel GCC minor version like a glove.

2019-02-03T22:20:42.891-05:00| host-4243| I125: Validating path "/lib/modules/5.0.0-0.rc4.git3.1.fc30.x86_64/build/include" for kernel release "5.0.0-0.rc4.git3.1.fc30.x86_64".

2019-02-03T22:20:42.891-05:00| host-4243| I125: Failed to find /lib/modules/5.0.0-0.rc4.git3.1.fc30.x86_64/build/include/linux/version.h

2019-02-03T22:20:42.891-05:00| host-4243| I125: /lib/modules/5.0.0-0.rc4.git3.1.fc30.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2019-02-03T22:20:42.891-05:00| host-4243| I125: using /usr/bin/gcc for preprocess check

2019-02-03T22:20:42.900-05:00| host-4243| I125: Preprocessed UTS_RELEASE, got value "5.0.0-0.rc4.git3.1.fc30.x86_64".

2019-02-03T22:20:42.900-05:00| host-4243| I125: The header path "/lib/modules/5.0.0-0.rc4.git3.1.fc30.x86_64/build/include" for the kernel "5.0.0-0.rc4.git3.1.fc30.x86_64" is valid.  Whoohoo!

2019-02-03T22:20:42.900-05:00| host-4243| I125: Using temp dir "/tmp".

2019-02-03T22:20:42.902-05:00| host-4243| I125: Obtaining info using the running kernel.

2019-02-03T22:20:42.902-05:00| host-4243| I125: Setting header path for 5.0.0-0.rc4.git3.1.fc30.x86_64 to "/lib/modules/5.0.0-0.rc4.git3.1.fc30.x86_64/build/include".

2019-02-03T22:20:42.902-05:00| host-4243| I125: Validating path "/lib/modules/5.0.0-0.rc4.git3.1.fc30.x86_64/build/include" for kernel release "5.0.0-0.rc4.git3.1.fc30.x86_64".

2019-02-03T22:20:42.902-05:00| host-4243| I125: Failed to find /lib/modules/5.0.0-0.rc4.git3.1.fc30.x86_64/build/include/linux/version.h

2019-02-03T22:20:42.902-05:00| host-4243| I125: /lib/modules/5.0.0-0.rc4.git3.1.fc30.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2019-02-03T22:20:42.902-05:00| host-4243| I125: using /usr/bin/gcc for preprocess check

2019-02-03T22:20:42.910-05:00| host-4243| I125: Preprocessed UTS_RELEASE, got value "5.0.0-0.rc4.git3.1.fc30.x86_64".

2019-02-03T22:20:42.910-05:00| host-4243| I125: The header path "/lib/modules/5.0.0-0.rc4.git3.1.fc30.x86_64/build/include" for the kernel "5.0.0-0.rc4.git3.1.fc30.x86_64" is valid.  Whoohoo!

2019-02-03T22:20:43.041-05:00| host-4243| I125: found symbol version file /lib/modules/5.0.0-0.rc4.git3.1.fc30.x86_64/build/Module.symvers

2019-02-03T22:20:43.041-05:00| host-4243| I125: Reading symbol versions from /lib/modules/5.0.0-0.rc4.git3.1.fc30.x86_64/build/Module.symvers.

2019-02-03T22:20:43.055-05:00| host-4243| I125: Read 20774 symbol versions

2019-02-03T22:20:43.055-05:00| host-4243| I125: Invoking modinfo on "vmmon".

2019-02-03T22:20:43.059-05:00| host-4243| I125: "/sbin/modinfo" exited with status 256.

2019-02-03T22:20:43.059-05:00| host-4243| I125: Invoking modinfo on "vmnet".

2019-02-03T22:20:43.063-05:00| host-4243| I125: "/sbin/modinfo" exited with status 256.

2019-02-03T22:20:43.126-05:00| host-4243| I125: Setting destination path for vmmon to "/lib/modules/5.0.0-0.rc4.git3.1.fc30.x86_64/misc/vmmon.ko".

2019-02-03T22:20:43.127-05:00| host-4243| I125: Extracting the vmmon source from "/usr/lib/vmware/modules/source/vmmon.tar".

2019-02-03T22:20:43.135-05:00| host-4243| I125: Successfully extracted the vmmon source.

2019-02-03T22:20:43.135-05:00| host-4243| I125: Building module with command "/usr/bin/make -j16 -C /tmp/modconfig-5OVdgg/vmmon-only auto-build HEADER_DIR=/lib/modules/5.0.0-0.rc4.git3.1.fc30.x86_64/build/include CC=/usr/bin/gcc IS_GCC_3=no"

2019-02-03T22:20:44.746-05:00| host-4243| W115: Failed to build vmmon.  Failed to execute the build command.

2019-02-03T22:20:44.749-05:00| host-4243| I125: Setting destination path for vmnet to "/lib/modules/5.0.0-0.rc4.git3.1.fc30.x86_64/misc/vmnet.ko".

2019-02-03T22:20:44.750-05:00| host-4243| I125: Extracting the vmnet source from "/usr/lib/vmware/modules/source/vmnet.tar".

2019-02-03T22:20:44.759-05:00| host-4243| I125: Successfully extracted the vmnet source.

2019-02-03T22:20:44.759-05:00| host-4243| I125: Building module with command "/usr/bin/make -j16 -C /tmp/modconfig-5OVdgg/vmnet-only auto-build HEADER_DIR=/lib/modules/5.0.0-0.rc4.git3.1.fc30.x86_64/build/include CC=/usr/bin/gcc IS_GCC_3=no"

2019-02-03T22:20:46.574-05:00| host-4243| W115: Failed to build vmnet.  Failed to execute the build command.

Thank you for reply but i found the issue and i fixed it. The issue is that in my pc's BIOS setting has secure boot enable so i can't run the OS in VMWare but when is disable the secure boot from pc then OS is running.

What i found myself is that if i import and setup VCSA 6.5+ PSC only-role appliance via VMWare workstation 15, it throws error I shown in my first post. It seems that appliance import via Vmware Workstation 15 is not supported.  However, i imported VCSA 6.5 PSC+vCenter Server appliance via VMware Workstation 14 successfully.

I got around the error by directly importing VCSA PSC role-only appliance inside ESXi 6.5 hosts.

Is provisioning disabled on the pool? If provisioning is enabled make sure the pool size is increased to accommodate the additional VM.

Are you referring to the vCenter Server for Windows? If so that's not possible due to port conflicts. You should deploy a VCSA.

We don't use MFA. Just AD authentication. Even without MFA is it still a known limitation?

hi Luc,

could yu sggest on following.i am trying to installvsphere client on on one windows vm.file is on desktop as shown and run following start-process command .

it went through fine with normal installtionprocesss .

but failed with followingerror

I am trying to un-registered a specific set of vms in a Org in vCloud. The approach which I am following is below.

1.get vms in vapp for a org and poweroff

2.Do consolidation from vcloud

3.get the vcenter name for the vcloud vms

4.get the task (PromoteDisks_Task) or even like consolidation is completed for the vm

5.Once the consolidation is completed Get-AdvancedSetting -Name cloud.uuid and remove that paramater

6.change the mac address from manual to automatic

7.remove the vm from inventory

8.while registering the vm rename it to new name mentioned in $newvmname and add that vm to new resource pool mentioned in $newrsp (The new resourcepool is in same cluster)

9.Get the datastore of the vm and get the datastorecluster where that vm datastore resides and get the highest free space datastore in that cluster and do storage vm motion.( This is to change the vmfolder and vmdk file names to new display name in vcenter.

Here from the 4 step I am failing can someone help with the script.

Ex:

From a set of vms if a single vm consolidation is completed then its should proceed with next stepts 5 to 9

Its not complete script.Is it possible rebuild from start based on above steps.

$newrsp='Resp01'
$civm=Get-CIVApp 'NCompass_W2008_64Bit_Certification_NCA' -Org SEP02 |Get-CIVM
$civm |?{$_.status -eq 'PoweredOn'} |Stop-CIVM -RunAsync -Confirm:$false
$civm |ForEach-Object -Process {$_.ExtensionData.Consolidate_Task()}
(Get-View -RelatedObject $civm.extensionData)
$civm.ExtensionData.Consolidate_Task()
$vcvm= (Get-View -RelatedObject $civm.extensionData)
$tasks = @(Get-Task | where{$_.Name -eq 'PromoteDisks_Task' -and (Get-View -Id $_.ObjectId).name -eq $vcvm.Name -and 'Running','Queued' -contains $_.State})    while ($tasks.Count -ne 0){        sleep 5        $tasks = @(Get-Task | where{$_.Name -eq 'PromoteDisks_Task' -and (Get-View -Id $_.ObjectId).name -eq $vcvm.Name -and 'Running','Queued' -contains $_.State})    }
Get-VM $vcvm.Name |Get-AdvancedSetting -Name cloud.uuid |Set-AdvancedSetting ''
$dsName = $vcvm.ExtensionData.Config.Files.VmPathName.Split(']').TrimStart('[')[0]
$vmxPath = $vcvm.ExtensionData.Config.Files.VmPathName.Split(']')[1].TrimStart(' ')
$vmxName = $vmxPath.Split('/')[-1]
$vmxFolder = [string]::Join('/', ($vmxPath.Split('/')[-99..-2]))
$newvmname= @()
for($i=1; $i -le 110; $i++){
$newvmname+=New-VM -Name "$('LIBFORTPERFTEST0')$($i)" -VMFilePath $vmxPath -ResourcePool $newrsp
} 

Dear all,

This is my first post, so hopefully this is in the right place. Any assistance is greatly appreciated.

ESXi 6.5

Host: Dell R910

Local Disks: Two 3.5tb  , 3par 8000 Series, RAID 5

When I logged in today, I quickly realized that all of my VM's were down:

Datastore look this, 2 datastore missing.

On device are available

When I click one of my two devices

Partition

I'm really at a loss as to what to do. Any advice is greatly appreciated. If there is any other information that I can provide

Thank you

Siverian

Hi All,

I'm planning to take a snapshot for around 400 VM's before VMware tools & VM version upgrade. Can we pull the report for Datastore free space with respect to each VM to data store before taking a snapshot?   Before taking snapshot want to see Datastore having sufficient space.  VM's name will be in C:\Temp\vmliste.txt

E.g. VM1 ---> Data store 1  Free space 15 %   GB - 8

        VM2  --> Datastore 2  Free space 12 %     GB - 6

Thanks

vmk

Hi bluefirestorm,

Thanks for your prompt reply

"The i7-870 is a Lynnfield CPU and won't be able to run Fusion 11 or 10."

I wonder:

A.  What is the reason behind?   some bugs in the Lynnfield CPU, or the chipset, or the BIOS, or what? 

B.  Tested and won't run?

C.  Or not tested, but may run?

Regards

Alex

Here is my problem I have a hp proliant server DL360 G7 intel  Xeon Cpu E5640 at 2.67ghz memory is 32 for now. I created a virtual switch  and Port group  tied to it. Then I created a cisco virtual router csr1000v and that i created a virtual machine using an iso file setup for CUCM 12v. Here comes my problem after the install everything is going I let the system get the background things run and go to the ip address of the cucm server. I then put in the ip address nothing happens but I can ping the cucm server and it pings back and anything thing on my lab network pings back as well using its ipv4 address. When I was the ipv4 address for the cucm as I mention nothing happens but when i use the ipv6 the cucm comes up. I'm totally at a lost of what I could be doing wrong. I search the internet and youtube be i'm still lost. Any help in the right direction i would gladly take. Thanks

Is this applicable for vSphere Client v6.5U2?

Is there a updated documentation for these?