JeffH322's Posts

The verbiage used to control whether Side Channel Mitigations are enabled/disabled changed in version 17.0.0 from previous versions. Prior to 17.0.0, the setting was labeled: Disable side channel m... See more...
The verbiage used to control whether Side Channel Mitigations are enabled/disabled changed in version 17.0.0 from previous versions. Prior to 17.0.0, the setting was labeled: Disable side channel mitigations for Hyper-V enabled hosts In 17.0.0, the option was changed to: Side channel mitigations is not enable for Hyper-V enabled hosts Yes - "enable" is missing the "d" at the end. What does this option actually do? Does the option enable side-channel mitigations? Does the option disable side-channel mitigations? It's more a rhetorical question - I know it's #2, but I'm playing the role of a confused customer. This would be parity with earlier releases which begs the question - why was the verbiage changed in the first place? There's additional context listed below that states: Enabling side channel mitigations may cause performance degradation. This is helpful context (FYI side channel should be hyphenated - "side-channel"), but does little to explain the checkbox next to the "Side channel mitigations is not enable for Hyper-V enabled hosts" option. While the wording in versions prior to 17.0.0 isn't grammatically correct, it's still easier to understand than the change in version 17.0.0. Both "side channel and Hyper-V enabled should be hyphenated - even with Hyper-V already being hyphenated: Disable side-channel mitigations for Hyper-V-enabled hosts Screenshots: Version 17.0.0 Version 16.2.4    
Hello, There are several settings that I use across all VMs and have to configure them each time I build a new VM. Is there a global VMX file where I can do this? For example, I'd like to be able ... See more...
Hello, There are several settings that I use across all VMs and have to configure them each time I build a new VM. Is there a global VMX file where I can do this? For example, I'd like to be able to automatically apply the following to all newly created VMs: suspend.disabled = "TRUE"  
Hello, Thank you for your response. I'm happy to know that there will eventually be a fix checked into Ubuntu 22.04 but what about 20.04 LTS? Given that 20.04 is a Long Term Support release, I hope ... See more...
Hello, Thank you for your response. I'm happy to know that there will eventually be a fix checked into Ubuntu 22.04 but what about 20.04 LTS? Given that 20.04 is a Long Term Support release, I hope that there are plans to incorporate whatever the fix is there too.  
I kept running into similar issues when trying to install the ARM64 version of Ubuntu 20.04.4 LTS from the official Ubuntu ISO. It never failed - as soon as I got past the page where I accepted the ... See more...
I kept running into similar issues when trying to install the ARM64 version of Ubuntu 20.04.4 LTS from the official Ubuntu ISO. It never failed - as soon as I got past the page where I accepted the option to format the virtual disk and was prompted to enter my name, the installer would crash. What I figured out was the installer was automatically getting updated during the installation routine as the VM was able to connect to the network - subsequently out to the Internet. I decided to try disconnecting (not removing) the network adapter, then rebooting the VM and ran through the installation process again. It worked! And I've been able to demonstrate this consistently. The one thing to keep in mind is that, for any processes where the installer attempts to connect to anything on the network (i.e. cloud-init), the process will take a lot longer to complete and the installer will ask you if you want to continue without network connectivity. Yes you do! Once the installation is complete, select the option to "Reboot Now". You can safely update the OS after the first boot. Make sure you connect the network adapter before rebooting the VM otherwise it will hang during the boot routine. WORD OF WARNING - for whatever reason, updating the kernel did cause the VM to fail to start up. I ended up having to manually select the original kernel, then modify the GRUB configuration so the VM would always boot off the original version of the kernel. I also need to go back and figure out how to disable apt from downloading kernel updates. Good luck!
I just upgraded from 16.1.2 to 16.2.0. I went to create a new VM. When I got to the final page of the wizard, I tried clicking the Customize Hardware button. Instead of the window that normally disp... See more...
I just upgraded from 16.1.2 to 16.2.0. I went to create a new VM. When I got to the final page of the wizard, I tried clicking the Customize Hardware button. Instead of the window that normally displays, I was presented with a small window labeled "Hardware" and it was empty (see below). I tried creating several different VMs and had the same experience each time. I've been using VMware Workstation Pro on this same computer for at least 2 years now and have never encountered this before. If I edit the properties of the VM after saving it, I am able to make configuration changes. It seems to be isolated to using "Customize Hardware" in the New VM wizard.    
Yep - I totally get it. Their marketing is misleading.
My issue is with VMware Workstation Pro, not with VMware Player. I've never even tried with Player but it sounds like the issue you're experiencing is the opposite of mine if your machine locks u... See more...
My issue is with VMware Workstation Pro, not with VMware Player. I've never even tried with Player but it sounds like the issue you're experiencing is the opposite of mine if your machine locks up with VMware Player but not with Workstation. Is this with version 15.5.2? Or another version?
Vincegre​ thanks for this! Please let us know what you find out.
According to the "marketing" details on the VMware Workstation Pro product page (https://www.vmware.com/products/workstation-pro.html), under Tech Specs, the text says: Host Operating Systems (6... See more...
According to the "marketing" details on the VMware Workstation Pro product page (https://www.vmware.com/products/workstation-pro.html), under Tech Specs, the text says: Host Operating Systems (64-bit) Ubuntu 15.04 and above Red Hat Enterprise Linux 6 & above CentOS 7.0 and above Oracle Linux 7.0 and above openSUSE Leap 42.2 and above SUSE Linux 13 and above Windows 7 and above Windows Server 2008 and above
Glad to know it's not just me! I don't know how this product makes it's way out of the QA process???!!! It's amazing to me that there are so many having this issue with such a mainstream release ... See more...
Glad to know it's not just me! I don't know how this product makes it's way out of the QA process???!!! It's amazing to me that there are so many having this issue with such a mainstream release of Ubuntu that it's gone unresolved for so long. I rebuilt my computer...again...this time running Ubuntu 20.04 LTS. Same issue as before! Technically, the release notes state Ubuntu versions X/Y/Z "and newer". That tells me that 20.04 _IS_ supported. If VMware wants to claim that 20.04 LTS is not officially supported, then they need to modify the verbiage on the website. And yes, it seems to happen the most when I go to reboot the VMs. I did try using it without Firefox running as someone else suggested - that made no difference, unfortunately. At this point, I think the only other option available is to pay $50 for the pay-per-incident support. Hopefully I get my money's worth. I'll be happy if it takes hours and hours to resolve - as I've burned an inordinate amount of my own time on troubleshooting to no avail. I'm just not sure when I'll have the time to do that. If anyone else wants to take a stab at that process, you can go to the VMware Online Store and buy a pay-per-incident support for VMware Workstation: Per Incident Support - Workstation Pro
Well that's interesting! I typically do use Chrome but it's entirely possible that I also had Firefox running at the time that it occurred. The issue appears to be a lot more than just high CP... See more...
Well that's interesting! I typically do use Chrome but it's entirely possible that I also had Firefox running at the time that it occurred. The issue appears to be a lot more than just high CPU utilization. The computer completely locks up and is unresponsive to the point where I have to hit the power switch and hold if for 5 seconds to force the computer to power off. Is that also what you experienced? How did you determine the CPU utilization was so high if you weren't able to run any command-line or GUI utilities? I will try this in a bit and ensure that no Firefox processes are running at the time. I'll actually close all applications aside from VMware Workstation 15.5.2. I have made one major change to my computer since I opened the case - I performed a fresh installation of Ubuntu Desktop 20.04 LTS. It's amazing! The release notes for VMware Workstation say "X version and newer". I list it as "X" because I don't remember if the version started at 12.x/14.x/16.x, but it definitely included 16.04, 17.10, and 18.04, and also said "and newer" so that would include 19.10 and 20.04 based on my understanding of "and newer". Thanks for the tip paultechguy​!
dariusd​ I'm at a loss for what to do next. I re-read your email about the output from 'lsmod' not looking right on my computer, so I went and ran lsmod on a few other Ubuntu systems on my net... See more...
dariusd​ I'm at a loss for what to do next. I re-read your email about the output from 'lsmod' not looking right on my computer, so I went and ran lsmod on a few other Ubuntu systems on my network - one a guest on VMware Workstation 15.5.2 on Windows 10 and a few others running as guests on ESXi 6.7.0 and 6.5.0. I can't really see anything noticeably different between them. Maybe I've just been staring at this for too long??? I decided to try a couple of things... 1. To eliminate any possibility of the issue being related to the Samsung EVO 860 SSD, I opened my computer, disconnected the SATA cables from the Samsung SSD and the 2x 2TB hard drives I use for additional storage, and connected a spare hard drive (Seagate Momentus XT 750GB Hybrid) such that it's the only hard drive in the computer. 2. I downloaded a fresh ISO image of Ubuntu Desktop 18.04.4 (64-bit) and installed it on the new hard drive, then installed all of the official Ubuntu updates. Then I installed VMware Workstation Pro 15.5.2 and brought up the same Windows and Linux guest VMs. I was about to celebrate a victory, then the computer froze. 4. Yesterday, I decided to see if perhaps the issue I'm having is related to Ubuntu 18.04.4, so I downloaded Fedora Workstation 30, performed a fresh installation on the Seagate Momentus XT 750 GB drive, applied all updates, then installed VMware Workstation Pro 15.5.2. When I launched Workstation 15.5.2 the first time, I got a message about how the kernel modules needed to be compiled/installed, so I clicked 'Install' and got a message about VMware not being able to find the kernel-headers. I tried to find a version of the kernel headers that matched the version of the kernel, but there was a mismatch. I ended up just leaving the kernel-headers that were already there, installed the kernel-devel package, and allowed VMware Workstation to compile/install the kernel modules. When I brought my Windows and Linux VMs up, VMware complained that it couldn't enable 3D graphics acceleration. I realized I hadn't installed the Nvidia driver for my graphics card. It is NOT easy to install the Nvidia drivers on Fedora!!! I ended up following some instructions I found online to download the drivers and run the installation, but something didn't go right and I wasn't able to recover. Game over for Fedora Workstation 30. 4. Last night, I downloaded Fedora Workstation 29, performed a fresh installation on the Seagate Momentus XT 750 GB drive, applied all updates, then installed VMware Workstation Pro 15.5.2 and brought up the same Windows and Linux guest VMs. I disabled 3D Graphics acceleration on the Windows and Linux guests so I didn't need to worry about installing the Nvidia driver. So far, things seem OK. I haven't experienced a crash - yet. That said, I am not anywhere remotely as comfortable with Fedora as I am with Ubuntu and I want to go back to troubleshooting this with Ubuntu 18.0.4 which, as far as everything I've read shows, it is a fully supported host operating system for VMware Workstation Pro 15.5.2. So what's your advice? What can I provide you with that would help you diagnose this?
dariusd​ You are correct about the command output. I'm not sure why the output of lsmod looked the way it did. I ran it again - the output is down near the bottom of this update. I also che... See more...
dariusd​ You are correct about the command output. I'm not sure why the output of lsmod looked the way it did. I ran it again - the output is down near the bottom of this update. I also checked under /var/crash to see if there were any kernel panics. There are two crash files - none of them are related to VMware Workstation. Both were created during times when VMware Workstation wasn't even running. _usr_lib_x86_64-linux-gnu_brisk-menu_brisk-menu.1000.crash _usr_sbin_lightdm.0.crash It looks like Samsung made enhancements in the EVO 860 to improve compatibility with Ubuntu Linux as the EVO 850 had issues. I am running a 1 TB EVO 860 so, in theory, it includes the enhancements. But I would think that upgrading the firmware (as I mentioned I did in my last update) would have addressed any stability issues that were present in earlier firmware releases. I created an Ubuntu Desktop 18.04 bootable USB and used it to run smartctl and fsck.ext4. The smartctl output looks good. Running fsck.ext4 did find a couple of errors and was able to repair them. In the response where I provided the support logs, I mentioned that VMware Tools did not show as running when I went to execute the support log collection. I was able to resolve that issue by removing VMware Tools, running 'sudo apt purge open-vm-tools open-vm-tools-desktop' then rebooting and reinstalling VMware Tools. I have two traditional hard drives in the same computer. I copied the Windows 10 and Ubuntu VMs over to the Seagate 2TB disk and have been running them from there. The host did freeze again last night and I got an "Error 11" message when I started the Ubuntu Desktop 18.04 VM. I thought I captured the pop-up window of the Error 11 message but I can't seem to find it. It should show up in the logs I've provided via Google Drive (see below). This tells me that the issue isn't related to the SSD drive. I just created a new set of support logs with the VMs running on the Seagate 2TB hard drive (as opposed to the Samsung EVO 860 1TB SSD) and uploaded them to the Google Drive link I shared the other day (again for your convenience). Filename: vm-2020-04-08.9842.tgz https://drive.google.com/open?id=1EYoGRKpqEFMcE_2A523ERXEdme84MPCa fsck.ext4 root@ubuntu:~# fsck.ext4 -f /dev/sda2 e2fsck 1.44.1 (24-Mar-2018) Pass 1: Checking inodes, blocks, and sizes Inode 26899879 extent tree (at level 2) could be narrower.  Fix<y>? yes Inode 27656501 extent tree (at level 2) could be narrower.  Fix<y>? yes Pass 1E: Optimizing extent trees Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information /dev/sda2: ***** FILE SYSTEM WAS MODIFIED ***** /dev/sda2: 811056/61022208 files (0.7% non-contiguous), 74512439/244059136 blocks smartctl root@ubuntu:~# smartctl --all /dev/sda smartctl 6.6 2016-05-31 r4324 [x86_64-linux-5.3.0-28-generic] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Device Model:     Samsung SSD 860 EVO 1TB Serial Number:    S3Z8NB0KC63085E LU WWN Device Id: 5 002538 e40b44588 Firmware Version: RVT04B6Q User Capacity:    1,000,204,886,016 bytes [1.00 TB] Sector Size:      512 bytes logical/physical Rotation Rate:    Solid State Device Form Factor:      2.5 inches Device is:        Not in smartctl database [for details use: -P showall] ATA Version is:   Unknown(0x09fc), ACS-4 T13/BSR INCITS 529 revision 5 SATA Version is:  SATA 3.2, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is:    Wed Apr  8 16:36:31 2020 UTC SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status:  (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status:      (   0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: (    0) seconds. Offline data collection capabilities: (0x53) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. No Offline surface scan supported. Self-test supported. No Conveyance Self-test supported. Selective Self-test supported. SMART capabilities:            (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability:        (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: (   2) minutes. Extended self-test routine recommended polling time: (  85) minutes. SCT capabilities:        (0x003d) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 1 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE   5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0   9 Power_On_Hours          0x0032   098   098   000    Old_age   Always       -       5662 12 Power_Cycle_Count       0x0032   099   099   000    Old_age   Always       -       84 177 Wear_Leveling_Count     0x0013   097   097   000    Pre-fail  Always       -       41 179 Used_Rsvd_Blk_Cnt_Tot   0x0013   100   100   010    Pre-fail  Always       -       0 181 Program_Fail_Cnt_Total  0x0032   100   100   010    Old_age   Always       -       0 182 Erase_Fail_Count_Total  0x0032   100   100   010    Old_age   Always       -       0 183 Runtime_Bad_Block       0x0013   100   100   010    Pre-fail  Always       -       0 187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0 190 Airflow_Temperature_Cel 0x0032   068   050   000    Old_age   Always       -       32 195 Hardware_ECC_Recovered  0x001a   200   200   000    Old_age   Always       -       0 199 UDMA_CRC_Error_Count    0x003e   100   100   000    Old_age   Always       -       0 235 Unknown_Attribute       0x0012   099   099   000    Old_age   Always       -       39 241 Total_LBAs_Written      0x0032   099   099   000    Old_age   Always       -       52433523381 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 No self-tests have been logged.  [To run self-tests, use: smartctl -t] SMART Selective self-test log data structure revision number 1 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS     1        0        0  Not_testing     2        0        0  Not_testing     3        0        0  Not_testing     4        0        0  Not_testing     5        0        0  Not_testing Selective self-test flags (0x0):   After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. lsmod root@castamere:/var/crash# lsmod Module                  Size  Used by rfcomm                 77824  16 vmnet                  49152  13 vmw_vsock_vmci_transport    32768  0 vsock                  36864  1 vmw_vsock_vmci_transport vmw_vmci               69632  1 vmw_vsock_vmci_transport vmmon                 106496  0 ip6table_filter        16384  1 ip6_tables             28672  1 ip6table_filter cmac                   16384  1 bnep                   20480  2 iptable_filter         16384  1 arc4                   16384  2 binfmt_misc            20480  1 dell_wmi               16384  0 dell_smbios            24576  1 dell_wmi nls_iso8859_1          16384  1 wmi_bmof               16384  0 intel_wmi_thunderbolt    16384  0 dell_wmi_descriptor    16384  2 dell_wmi,dell_smbios sparse_keymap          16384  1 dell_wmi 8250_dw                16384  0 mxm_wmi                16384  0 intel_rapl             20480  0 x86_pkg_temp_thermal    16384  0 dcdbas                 16384  1 dell_smbios intel_powerclamp       16384  0 coretemp               16384  0 kvm_intel             217088  0 snd_hda_codec_hdmi     49152  2 kvm                   610304  1 kvm_intel irqbypass              16384  1 kvm crct10dif_pclmul       16384  0 crc32_pclmul           16384  0 snd_hda_codec_realtek   106496  1 snd_hda_codec_generic    73728  1 snd_hda_codec_realtek ghash_clmulni_intel    16384  0 pcbc                   16384  0 ath10k_pci             49152  0 aesni_intel           188416  2 ath10k_core           360448  1 ath10k_pci aes_x86_64             20480  1 aesni_intel ath                    28672  1 ath10k_core crypto_simd            16384  1 aesni_intel glue_helper            16384  1 aesni_intel cryptd                 24576  3 crypto_simd,ghash_clmulni_intel,aesni_intel snd_hda_intel          45056  4 mac80211              786432  1 ath10k_core btusb                  45056  0 snd_hda_codec         126976  4 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek btrtl                  16384  1 btusb snd_usb_audio         204800  0 btbcm                  16384  1 btusb snd_hda_core           81920  5 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek snd_usbmidi_lib        32768  1 snd_usb_audio btintel                16384  1 btusb snd_hwdep              20480  2 snd_usb_audio,snd_hda_codec bluetooth             548864  43 btrtl,btintel,btbcm,bnep,btusb,rfcomm snd_seq_midi           16384  0 snd_seq_midi_event     16384  1 snd_seq_midi snd_rawmidi            32768  2 snd_seq_midi,snd_usbmidi_lib intel_cstate           20480  0 joydev                 24576  0 snd_pcm                98304  5 snd_hda_codec_hdmi,snd_hda_intel,snd_usb_audio,snd_hda_codec,snd_hda_core input_leds             16384  0 ecdh_generic           24576  2 bluetooth snd_seq                65536  2 snd_seq_midi,snd_seq_midi_event cfg80211              634880  3 ath,mac80211,ath10k_core snd_seq_device         16384  3 snd_seq,snd_seq_midi,snd_rawmidi intel_rapl_perf        16384  0 snd_timer              32768  2 snd_seq,snd_pcm mei_me                 40960  0 snd                    81920  21 snd_hda_codec_generic,snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_usb_audio,snd_usbmidi_lib,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_pcm,snd_rawmidi idma64                 20480  0 virt_dma               16384  1 idma64 soundcore              16384  1 snd mei                    94208  1 mei_me intel_lpss_pci         20480  0 shpchp                 36864  0 intel_lpss             16384  1 intel_lpss_pci wmi                    24576  6 intel_wmi_thunderbolt,dell_wmi,wmi_bmof,dell_smbios,dell_wmi_descriptor,mxm_wmi acpi_pad              180224  0 mac_hid                16384  0 nvidia_uvm            937984  0 sch_fq_codel           20480  7 parport_pc             32768  0 ppdev                  20480  0 lp                     20480  0 parport                49152  3 parport_pc,lp,ppdev ip_tables              28672  1 iptable_filter x_tables               40960  4 ip6table_filter,iptable_filter,ip6_tables,ip_tables autofs4                40960  2 dm_mirror              24576  0 dm_region_hash         20480  1 dm_mirror dm_log                 20480  2 dm_region_hash,dm_mirror nvidia_drm             45056  4 nvidia_modeset       1110016  9 nvidia_drm hid_generic            16384  0 nvidia              20385792  441 nvidia_uvm,nvidia_modeset i915                 1622016  2 i2c_algo_bit           16384  1 i915 drm_kms_helper        172032  2 nvidia_drm,i915 syscopyarea            16384  1 drm_kms_helper sysfillrect            16384  1 drm_kms_helper sysimgblt              16384  1 drm_kms_helper fb_sys_fops            16384  1 drm_kms_helper usbhid                 49152  0 drm                   401408  9 drm_kms_helper,nvidia_drm,i915 alx                    49152  0 hid                   118784  2 usbhid,hid_generic ahci                   40960  3 mdio                   16384  1 alx ipmi_devintf           20480  0 libahci                32768  1 ahci ipmi_msghandler        53248  2 ipmi_devintf,nvidia video                  45056  2 dell_wmi,i915
dariusd​ Thanks so much for your response. Unfortunately, I am still having issues with VMware Workstation Pro 15.5.2 causing my Ubuntu Linux machine to freeze. It seems as though it happens w... See more...
dariusd​ Thanks so much for your response. Unfortunately, I am still having issues with VMware Workstation Pro 15.5.2 causing my Ubuntu Linux machine to freeze. It seems as though it happens when the utilization of a particular VM reaches a relatively high level. Things like installation of applications & Windows Updates, even shutting the VMs down cause the host to completely lock up to the point where the only option is to hold down the power button for several seconds to force the computer to shut down. This is a critical stability issue and I would love any additional help possible to determine the root cause and to resolve the issue. One thing I forgot to mention - I used to run Windows 10 Pro on this same computer. I decided to make the jump to Ubuntu Linux to see how it would work for me. I used to run VMware Workstation Pro (starting with version 13 all the way through version 15.5 without any issues while I was running Windows 10 on this computer. With respect to the points that you raised in your response: 1. "We've had problems in the past with Samsung SSDs freezing up for extended periods of time when Workstation is running.  Might be worth checking that you have the latest firmware installed on that drive." The Samsung EVO 860 SSD drive was behind in terms of firmware revisions. After an incredibly frustrating process of building a bootable USB stick via Unetbootin (per Samsung's instructions), I was successful. I ended up using Rufus on a Windows box to create a USB boot stick that worked with the UEFI BIOS in my Dell XPS 8930. The drive was running firmware revision RVT02B6Q and is currently on RVT04B6Q after using the Samsung Magician bootable ISO to apply the firmware update. 2. "The module list you posted looks like output from a kernel oops/panic... If so, are there any related oops/panic messages in the logs?  I could not find any in the support bundle." Neither of the sets of details about modules/installed hardware was the result of a kernel oops/panic. I actually specified the commands that I used to provide the output. The first list was the result of issuing: sudo lsmod The second list was the result of issuing: sudo lspci -v Did you happen to review the contents of the logs I made available via the Google Drive link? https://drive.google.com/open?id=1EYoGRKpqEFMcE_2A523ERXEdme84MPCa NOTE: You should be able to access the folder without being prompted for authentication. Please let me know if you have any issues accessing the shared folder. Thank you once again for your willingness to assist! I look forward to your response! Best Regards, -JeffH
As requested... Two Guests: Guest 1: Windows 10 Pro 10.0.18363.720 Guest 2: Ubuntu Desktop 18.04.4 FYI - I've tried with 3D graphics acceleration enabled and disabled for each of the gu... See more...
As requested... Two Guests: Guest 1: Windows 10 Pro 10.0.18363.720 Guest 2: Ubuntu Desktop 18.04.4 FYI - I've tried with 3D graphics acceleration enabled and disabled for each of the guests to see if that was possibly an issue - that didn't seem to make a difference Logs (from Help -> Support -> Collect Support Data (VMware Workstation Pro 15.5.2 for Linux) available here: LINK REMOVED! vm-2020-04-05.2268.tgz vm-2020-04-05.8670.tgz Ubuntu 18.04.4 LTS (Bionic Beaver) 64-bit Kernel Linux 4.15.0-91-generic x86_64 MATE 1.20.1 Dell XPS 8930 Intel Core i7-8700 CPU @ 3.20 GHz x 12 cores 16 GB RAM (2x 8GB) 1x 1TB Samsung SSD Boot Disk 1x 2TB Seagate 7200 RPM SATA 1x 2TB Western Digital 7200 RPM SATA 1x Hitachi/LG DVD+/- RW-ROM Internal Qualcomm Atheros Killer E2400 Gigabit Ethernet Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (not used - admin disabled) Nvidia GeForce GTX 1050 Ti Intel UHD Graphics 630 (not used) Gory details below: lsmod [639990.209536] Modules linked in: vmnet(OE) parport_pc vmw_vsock_vmci_transport vsock vmw_vmci vmmon(OE) pci_stub xt_tc pudp binfmt_misc rfcomm ip6table_filter ip6_tables arc4 cmac iptable_filter bnep nls_iso8859_1 8250_dw dell_wmi dell_smb ios sparse_keymap intel_wmi_thunderbolt dell_wmi_descriptor wmi_bmof mxm_wmi dcdbas intel_rapl x86_pkg_temp_thermal inte l_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc snd_hda_codec_hdmi aesni_intel aes_x86_64 crypto_simd snd_hda_codec_realtek glue_helper snd_hda_codec_generic cryptd idma64 virt_dma btusb btrtl btbcm btintel joydev bluetooth snd_usb_audio snd_usbmidi_lib ath10k_pci ecdh_generic ath10k_core input_leds ath sn d_hda_intel intel_cstate mac80211 snd_seq_midi snd_hda_codec snd_seq_midi_event snd_hda_core [639990.209551]  snd_hwdep snd_rawmidi snd_pcm intel_rapl_perf snd_seq cfg80211 snd_seq_device snd_timer snd mei_me inte l_lpss_pci mei intel_lpss shpchp soundcore mac_hid wmi acpi_pad nvidia_uvm(OE) sch_fq_codel ppdev lp parport ip_tables x _tables autofs4 dm_mirror dm_region_hash dm_log nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) hid_generic i915 uas i2c _algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops usbhid alx drm hid ahci usb_storage mdio ipmi_dev intf libahci ipmi_msghandler video [last unloaded: vmnet] lspci -v 00:00.0 Host bridge: Intel Corporation 8th Gen Core Processor Host Bridge/DRAM Registers (rev 07) Subsystem: Dell Device 0859 Flags: bus master, fast devsel, latency 0 Capabilities: [e0] Vendor Specific Information: Len=10 <?> Kernel driver in use: skl_uncore 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) (rev 07) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 16 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: 0000e000-0000efff Memory behind bridge: eb000000-ec0fffff Prefetchable memory behind bridge: 00000000a0000000-00000000b1ffffff Capabilities: [88] Subsystem: Dell Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) Capabilities: [80] Power Management version 3 Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit- Capabilities: [a0] Express Root Port (Slot+), MSI 00 Capabilities: [100] Virtual Channel Capabilities: [140] Root Complex Link Capabilities: [d94] #19 Kernel driver in use: pcieport Kernel modules: shpchp 00:02.0 Display controller: Intel Corporation UHD Graphics 630 (Desktop) Subsystem: Dell Device 0859 Flags: bus master, fast devsel, latency 0, IRQ 132 Memory at 2ffe000000 (64-bit, non-prefetchable) [size=16M] Memory at 2fa0000000 (64-bit, prefetchable) [size=256M] I/O ports at f000 [size=64] Capabilities: [40] Vendor Specific Information: Len=0c <?> Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00 Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [d0] Power Management version 2 Capabilities: [100] Process Address Space ID (PASID) Capabilities: [200] Address Translation Service (ATS) Capabilities: [300] Page Request Interface (PRI) Kernel driver in use: i915 Kernel modules: i915 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model Subsystem: Dell Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model Flags: fast devsel, IRQ 255 Memory at 2fff027000 (64-bit, non-prefetchable) [disabled] [size=4K] Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit- Capabilities: [dc] Power Management version 2 Capabilities: [f0] PCI Advanced Features 00:14.0 USB controller: Intel Corporation 200 Series/Z370 Chipset Family USB 3.0 xHCI Controller (prog-if 30 [XHCI]) Subsystem: Dell 200 Series PCH USB 3.0 xHCI Controller Flags: bus master, medium devsel, latency 0, IRQ 122 Memory at 2fff010000 (64-bit, non-prefetchable) [size=64K] Capabilities: [70] Power Management version 2 Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+ Kernel driver in use: xhci_hcd 00:16.0 Communication controller: Intel Corporation 200 Series PCH CSME HECI #1 Subsystem: Dell 200 Series PCH CSME HECI Flags: bus master, fast devsel, latency 0, IRQ 135 Memory at 2fff026000 (64-bit, non-prefetchable) [size=4K] Capabilities: [50] Power Management version 3 Capabilities: [8c] MSI: Enable+ Count=1/1 Maskable- 64bit+ Kernel driver in use: mei_me Kernel modules: mei_me 00:17.0 RAID bus controller: Intel Corporation SATA Controller [RAID mode] Subsystem: Dell SATA Controller [RAID mode] Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 131 Memory at ec180000 (32-bit, non-prefetchable) [size=32K] Memory at ec18c000 (32-bit, non-prefetchable) [size=256] I/O ports at f090 [size=8] I/O ports at f080 [size=4] I/O ports at f060 [size=32] Memory at ec100000 (32-bit, non-prefetchable) [size=512K] Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [70] Power Management version 3 Capabilities: [a8] SATA HBA v1.0 Kernel driver in use: ahci Kernel modules: ahci 00:1c.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #2 (rev f0) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 17 Bus: primary=00, secondary=02, subordinate=02, sec-latency=0 Memory behind bridge: ec500000-ec5fffff Capabilities: [40] Express Root Port (Slot+), MSI 00 Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit- Capabilities: [90] Subsystem: Dell 200 Series PCH PCI Express Root Port Capabilities: [a0] Power Management version 3 Capabilities: [100] #00 Capabilities: [140] Access Control Services Capabilities: [220] #19 Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.2 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #3 (rev f0) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 18 Bus: primary=00, secondary=03, subordinate=03, sec-latency=0 Memory behind bridge: ec200000-ec3fffff Capabilities: [40] Express Root Port (Slot+), MSI 00 Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit- Capabilities: [90] Subsystem: Dell 200 Series PCH PCI Express Root Port Capabilities: [a0] Power Management version 3 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Access Control Services Capabilities: [220] #19 Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.3 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #4 (rev f0) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 19 Bus: primary=00, secondary=04, subordinate=04, sec-latency=0 I/O behind bridge: 0000d000-0000dfff Memory behind bridge: ec400000-ec4fffff Capabilities: [40] Express Root Port (Slot+), MSI 00 Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit- Capabilities: [90] Subsystem: Dell 200 Series PCH PCI Express Root Port Capabilities: [a0] Power Management version 3 Capabilities: [100] #00 Capabilities: [140] Access Control Services Capabilities: [220] #19 Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.4 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #5 (rev f0) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 16 Bus: primary=00, secondary=05, subordinate=6f, sec-latency=0 I/O behind bridge: 00002000-00002fff Memory behind bridge: bc000000-ea0fffff Prefetchable memory behind bridge: 0000002fb0000000-0000002ff9ffffff Capabilities: [40] Express Root Port (Slot+), MSI 00 Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit- Capabilities: [90] Subsystem: Dell 200 Series PCH PCI Express Root Port Capabilities: [a0] Power Management version 3 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Access Control Services Capabilities: [220] #19 Kernel driver in use: pcieport Kernel modules: shpchp 00:1e.0 Signal processing controller: Intel Corporation 200 Series/Z370 Chipset Family Serial IO UART Controller #0 Subsystem: Dell 200 Series PCH Serial IO UART Controller Flags: bus master, fast devsel, latency 0, IRQ 20 Memory at 2fff025000 (64-bit, non-prefetchable) [size=4K] Capabilities: [80] Power Management version 3 Capabilities: [90] Vendor Specific Information: Len=14 <?> Kernel driver in use: intel-lpss Kernel modules: intel_lpss_pci 00:1f.0 ISA bridge: Intel Corporation Z370 Chipset LPC/eSPI Controller Subsystem: Dell Device 0859 Flags: bus master, medium devsel, latency 0 00:1f.2 Memory controller: Intel Corporation 200 Series/Z370 Chipset Family Power Management Controller Subsystem: Dell 200 Series PCH PMC Flags: fast devsel Memory at ec188000 (32-bit, non-prefetchable) [disabled] [size=16K] 00:1f.3 Audio device: Intel Corporation 200 Series PCH HD Audio Subsystem: Dell 200 Series PCH HD Audio Flags: bus master, fast devsel, latency 32, IRQ 136 Memory at 2fff020000 (64-bit, non-prefetchable) [size=16K] Memory at 2fff000000 (64-bit, non-prefetchable) [size=64K] Capabilities: [50] Power Management version 3 Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+ Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:1f.4 SMBus: Intel Corporation 200 Series/Z370 Chipset Family SMBus Controller Subsystem: Dell 200 Series PCH SMBus Controller Flags: medium devsel, IRQ 255 Memory at 2fff024000 (64-bit, non-prefetchable) [size=256] I/O ports at f040 [size=32] Kernel modules: i2c_i801 01:00.0 VGA compatible controller: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GP107 [GeForce GTX 1050 Ti] Flags: bus master, fast devsel, latency 0, IRQ 141 Memory at eb000000 (32-bit, non-prefetchable) [size=16M] Memory at a0000000 (64-bit, prefetchable) [size=256M] Memory at b0000000 (64-bit, prefetchable) [size=32M] I/O ports at e000 [size=128] [virtual] Expansion ROM at 000c0000 [disabled] [size=128K] Capabilities: [60] Power Management version 3 Capabilities: [68] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [78] Express Legacy Endpoint, MSI 00 Capabilities: [100] Virtual Channel Capabilities: [250] Latency Tolerance Reporting Capabilities: [128] Power Budgeting <?> Capabilities: [420] Advanced Error Reporting Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 <?> Capabilities: [900] #19 Kernel driver in use: nvidia Kernel modules: nvidiafb, nouveau, nvidia_drm, nvidia 01:00.1 Audio device: NVIDIA Corporation GP107GL High Definition Audio Controller (rev a1) Subsystem: Dell GP107GL High Definition Audio Controller Flags: bus master, fast devsel, latency 0, IRQ 17 Memory at ec080000 (32-bit, non-prefetchable) [size=16K] Capabilities: [60] Power Management version 3 Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [78] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 02:00.0 USB controller: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller (prog-if 30 [XHCI]) Subsystem: Dell ASM1142 USB 3.1 Host Controller Flags: bus master, fast devsel, latency 0, IRQ 17 Memory at ec500000 (64-bit, non-prefetchable) [size=32K] Capabilities: [50] MSI: Enable- Count=1/8 Maskable- 64bit+ Capabilities: [68] MSI-X: Enable+ Count=8 Masked- Capabilities: [78] Power Management version 3 Capabilities: [80] Express Endpoint, MSI 00 Capabilities: [100] Virtual Channel Capabilities: [200] Advanced Error Reporting Capabilities: [280] #19 Capabilities: [300] Latency Tolerance Reporting Kernel driver in use: xhci_hcd 03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31) Subsystem: Dell QCA9377 802.11ac Wireless Network Adapter Flags: bus master, fast devsel, latency 0, IRQ 134 Memory at ec200000 (64-bit, non-prefetchable) [size=2M] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable+ Count=1/8 Maskable+ 64bit- Capabilities: [70] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [148] Virtual Channel Capabilities: [168] Device Serial Number 00-00-00-00-00-00-00-00 Capabilities: [178] Latency Tolerance Reporting Capabilities: [180] L1 PM Substates Kernel driver in use: ath10k_pci Kernel modules: ath10k_pci 04:00.0 Ethernet controller: Qualcomm Atheros Killer E2400 Gigabit Ethernet Controller (rev 10) Subsystem: Dell Killer E2400 Gigabit Ethernet Controller Flags: bus master, fast devsel, latency 0, IRQ 19 Memory at ec400000 (64-bit, non-prefetchable) [size=256K] I/O ports at d000 [size=128] Capabilities: [40] Power Management version 3 Capabilities: [58] Express Endpoint, MSI 00 Capabilities: [c0] MSI: Enable- Count=1/16 Maskable+ 64bit+ Capabilities: [d8] MSI-X: Enable+ Count=16 Masked- Capabilities: [100] Advanced Error Reporting Capabilities: [180] Device Serial Number ff-2a-09-a2-14-b3-1f-ff Kernel driver in use: alx Kernel modules: alx
Hello, I recently switched over to using Ubuntu 18.04 LTS on my desktop computer. I installed VMware Workstation Pro 15.5.2 and have run into multiple cases where any of the guest VMs I run (W... See more...
Hello, I recently switched over to using Ubuntu 18.04 LTS on my desktop computer. I installed VMware Workstation Pro 15.5.2 and have run into multiple cases where any of the guest VMs I run (Windows 10 or Ubuntu 18.04) cause my entire computer to freeze. The system becomes completely unresponsive and I have to hard reset with the power switch to recover. I'm only running supported versions of guest operating systems and of course, Ubuntu 18.0.4 is a supported host operating system for VMware Workstation Pro 15.5.2. Obviously, if I happen to be working on anything that wasn't saved at the time the host freezes up, it's completely lost! I've tried switching the VM Tools in my Ubuntu 18.04 guest from open-vm-tools to use the official VMware Tools for Linux and the Windows 10 guest is running the most up-to-date version of VMware Tools that comes with VMware Workstation Pro 15.5.2. I removed VMware Workstation Pro 15.5.2 and installed Oracle VirtualBox 6.1 instead. I don't experience the system freezes so there's definitely something awry with VMware Workstation Pro. I found a few articles online that recommended a variety of changes including: Forcing VMware to rebuild the kernel modules: vmware-modconfig --console --install-all Switching from open-vm-tools to VMware Tools (as mentioned earlier) Limiting the amount of physical RAM available to virtual machines (host has 24 GB of RAM - I restricted the total amount available to VMs to 12 GB). I only had one VM running at a time and the maximum amount of memory allocated to any guest is no more than 6 GB for Windows and 3 GB for Linux Disabling khugepaged defragmenting: echo never | sudo tee /sys/kernel/mm/transparent_hugepage/defrag I'm at a loss for what else to try. I rely on VMware Workstation, vCenter, and ESXi for other aspects of my job. Using Linux on my desktop has been an amazing change but not having Workstation is severely hindering my productivity! Any ideas? Thanks!
How is it that it’s “likely an Apple Bluetooth problem”? If Bluetooth device pairing works under Mac OS and it works with another hypervisor running on Mac OS (I.e. Parallels), then I don’t un... See more...
How is it that it’s “likely an Apple Bluetooth problem”? If Bluetooth device pairing works under Mac OS and it works with another hypervisor running on Mac OS (I.e. Parallels), then I don’t understand the speculation. Unless someone collects the needed log files and provides a proper analysis to determine root cause, I don’t know that it’s safe to point the finger in any direction.
I’ve been fighting to get a serial Bluetooth device to connect to the guest all night. Then I found this article! I’m using High Sierra with latest update and Fusion 10.1.2 and a Windows 7 Pro... See more...
I’ve been fighting to get a serial Bluetooth device to connect to the guest all night. Then I found this article! I’m using High Sierra with latest update and Fusion 10.1.2 and a Windows 7 Pro SP1 Guest. I hope a resolution becomes available soon!
I'm having exactly the same issue.  It's not only with VMs that have been migrated from earlier versions of Workstation (or other VMware solutions) it affects new VMs that were just built on Work... See more...
I'm having exactly the same issue.  It's not only with VMs that have been migrated from earlier versions of Workstation (or other VMware solutions) it affects new VMs that were just built on Workstation 8 and definitely have the latest and greatest VMware Tools installed.