ajgringo619's Posts

A few more questions: Are you running any unusual firewall rules? What does `sudo ufw status` show? Have you done anything special with VMware's dhcp server? What does dhcpd.conf show (from your... See more...
A few more questions: Are you running any unusual firewall rules? What does `sudo ufw status` show? Have you done anything special with VMware's dhcp server? What does dhcpd.conf show (from your NAT network, should be vmnet8 by default)?
Did not know that; thanks for the info.
Here's how my Windows 11 VM is setup (using 1 processor, 8 cores per processor): This is how I've setup all of my VMs - Windows, Linux, BSD - and it's always worked.
Just checked my Ubuntu 20 VM and it's on kernel 5.15-41. Where did you get the kernel you're using?
For those of you running kernel 5.18, I would suggest taking a look at the Arch AUR package https://aur.archlinux.org/packages/vmware-workstation and see what the package maintainer has done; maybe i... See more...
For those of you running kernel 5.18, I would suggest taking a look at the Arch AUR package https://aur.archlinux.org/packages/vmware-workstation and see what the package maintainer has done; maybe it would help getting your system working again. For me, this package has always built without fail, going back to kernel 5.15. To @Mikero, since these problems affect all of us, I believe it would be in VMware's best interest to communicate with the aforementioned packager maintainer; at least it would give the impression that the company is actively seeking a fix. Speaking of fixes...is there an easy way to get on the beta test team? I'm retired, so I can spend as much time as you need to troubleshoot bugs or test fixes.  
Not seeing that here: Arch-based host, various VMs. When you say it's "not working", can you please elaborate?
Interesting replies...I did a couple of tests on file transfers and VMware's solution was faster. On that note, I really haven't started hammering the shares yet. I'll give Samba another look (still ... See more...
Interesting replies...I did a couple of tests on file transfers and VMware's solution was faster. On that note, I really haven't started hammering the shares yet. I'll give Samba another look (still installed, just not active).
I recently switched my guests to use VMware shared folders instead of Samba. Is there as easy way to monitor their activity, something equivalent to smbstatus?
  • i
Yeah, I've gone with SCSI on all my new VMs; only the Windows ones seem to use NVMe as the default.
OK - I removed the offending blue/red lines from @continuum's earlier reply, restarted the VMware Workstation gui, and now I can take snapshots. Still not sure why there were left over from deletion ... See more...
OK - I removed the offending blue/red lines from @continuum's earlier reply, restarted the VMware Workstation gui, and now I can take snapshots. Still not sure why there were left over from deletion in the gui, but at least snapshots are working now.
Not sure why you feel that the .vmx is incomplete; it was never manually edited, either. This is why I'm having the problem - these lines remained after I removed the devices from the VMware Workstat... See more...
Not sure why you feel that the .vmx is incomplete; it was never manually edited, either. This is why I'm having the problem - these lines remained after I removed the devices from the VMware Workstation console. Also, the (3) blue lines are not the same vmdk; (2) are, but I tried using both nvme and scsi buses for a performance test. I know what disks are active.
Here's a .vmx file: #!/usr/bin/vmware .encoding = "UTF-8" config.version = "8" virtualHW.version = "19" mks.enable3d = "TRUE" pciBridge0.present = "TRUE" pciBridge4.present = "TRUE" pciBridge... See more...
Here's a .vmx file: #!/usr/bin/vmware .encoding = "UTF-8" config.version = "8" virtualHW.version = "19" mks.enable3d = "TRUE" pciBridge0.present = "TRUE" pciBridge4.present = "TRUE" pciBridge4.virtualDev = "pcieRootPort" pciBridge4.functions = "8" pciBridge5.present = "TRUE" pciBridge5.virtualDev = "pcieRootPort" pciBridge5.functions = "8" pciBridge6.present = "TRUE" pciBridge6.virtualDev = "pcieRootPort" pciBridge6.functions = "8" pciBridge7.present = "TRUE" pciBridge7.virtualDev = "pcieRootPort" pciBridge7.functions = "8" vmci0.present = "TRUE" hpet0.present = "TRUE" nvram = "opensuse-leap.nvram" virtualHW.productCompatibility = "hosted" powerType.powerOff = "soft" powerType.powerOn = "soft" powerType.suspend = "soft" powerType.reset = "soft" displayName = "opensuse-leap" guestOS = "other5xlinux-64" vpmc.enable = "TRUE" tools.syncTime = "FALSE" sound.autoDetect = "TRUE" sound.fileName = "-1" sound.present = "TRUE" numvcpus = "8" cpuid.coresPerSocket = "8" vcpu.hotadd = "TRUE" memsize = "8192" mem.hotadd = "TRUE" scsi0.virtualDev = "lsilogic" scsi0.present = "TRUE" scsi0:0.fileName = "opensuse-leap.vmdk" scsi0:0.present = "TRUE" ide1:0.deviceType = "cdrom-image" ide1:0.fileName = "/media/vms/iso-images/openSUSE-Leap-15.4-DVD-x86_64-Build243.2-Media.iso" ide1:0.present = "TRUE" usb.present = "TRUE" ehci.present = "TRUE" usb_xhci.present = "TRUE" usb.generic.autoconnect = "FALSE" usb.generic.allowHID = "TRUE" svga.graphicsMemoryKB = "4194304" ethernet0.connectionType = "nat" ethernet0.addressType = "generated" ethernet0.virtualDev = "e1000" serial0.startConnected = "FALSE" serial0.fileType = "thinprint" serial0.fileName = "thinprint" ethernet0.present = "TRUE" serial0.present = "TRUE" extendedConfigFile = "opensuse-leap.vmxf" floppy0.present = "FALSE" uuid.bios = "56 4d fd bd 75 99 56 34-0f 76 96 6d 1c 01 0c d8" uuid.location = "56 4d fd bd 75 99 56 34-0f 76 96 6d 1c 01 0c d8" scsi0:0.redo = "" pciBridge0.pciSlotNumber = "17" pciBridge4.pciSlotNumber = "21" pciBridge5.pciSlotNumber = "22" pciBridge6.pciSlotNumber = "23" pciBridge7.pciSlotNumber = "24" scsi0.pciSlotNumber = "16" usb.pciSlotNumber = "32" ethernet0.pciSlotNumber = "33" sound.pciSlotNumber = "34" ehci.pciSlotNumber = "35" usb_xhci.pciSlotNumber = "160" svga.vramSize = "268435456" vmotion.checkpointFBSize = "4194304" vmotion.checkpointSVGAPrimarySize = "268435456" vmotion.svga.mobMaxSize = "1073741824" vmotion.svga.graphicsMemoryKB = "4194304" vmotion.svga.supports3D = "1" vmotion.svga.baseCapsLevel = "9" vmotion.svga.maxPointSize = "189" vmotion.svga.maxTextureSize = "32768" vmotion.svga.maxVolumeExtent = "16384" vmotion.svga.maxTextureAnisotropy = "16" vmotion.svga.lineStipple = "1" vmotion.svga.dxMaxConstantBuffers = "14" vmotion.svga.dxProvokingVertex = "1" vmotion.svga.sm41 = "1" vmotion.svga.multisample2x = "1" vmotion.svga.multisample4x = "1" vmotion.svga.msFullQuality = "1" vmotion.svga.logicOps = "1" vmotion.svga.bc67 = "9" vmotion.svga.sm5 = "1" vmotion.svga.multisample8x = "1" vmotion.svga.logicBlendOps = "1" ethernet0.generatedAddress = "00:0c:29:01:0c:d8" ethernet0.generatedAddressOffset = "0" vmci0.id = "469830872" monitor.phys_bits_used = "45" cleanShutdown = "TRUE" softPowerOff = "TRUE" svga.guestBackedPrimaryAware = "TRUE" guestInfo.detailed.data = "architecture='X86' bitness='64' distroName='openSUSE Leap' distroVersion='15.4' familyName='Linux' kernelVersion='5.14.21-150400.22-default' prettyName='openSUSE Leap 15.4'" isolation.tools.dnd.disable = "TRUE" nvme0.present = "TRUE" nvme0:0.fileName = "/media/vms/vmware-images/shared-swap/shared-swap.vmdk" nvme0:1.fileName = "/media/vms/vmware-images/shared-build/shared-build.vmdk" scsi0:2.fileName = "/media/vms/vmware-images/shared-build/shared-build.vmdk" scsi0:1.fileName = "opensuse-leap-swap.vmdk" scsi0:2.mode = "independent-persistent" scsi0:2.redo = "" scsi0:1.redo = "" nvme0.pciSlotNumber = "192" nvme0.subnqnUUID = "52 e4 02 9f 8e 2d 5a ca-27 d1 b1 a4 84 2d 80 a5" scsi0:1.present = "TRUE" usb_xhci:4.present = "TRUE" usb_xhci:4.deviceType = "hid" usb_xhci:4.port = "4" usb_xhci:4.parent = "-1" My goal is to be able to take snapshots. My previous wishes to have shared vmdks is no longer necessary.
I had tried to setup shared disks between my Linux VMs, one for swap and the other for software builds. This was working, but it caused more problems (not VMware-related) than it was worth. So I remo... See more...
I had tried to setup shared disks between my Linux VMs, one for swap and the other for software builds. This was working, but it caused more problems (not VMware-related) than it was worth. So I removed them for all VMs, deleted the files from the host. However, the info on each disk still remains, which is not allowing me to create any snapshots. Here's what's left over on some guests: $ grep -e 'shared-build' */*.vmx fedora-34/fedora-34.vmx:nvme0:2.fileName = "/media/vms/vmware-images/shared-build/shared-build.vmdk" fedora-34/fedora-34.vmx:scsi0:2.fileName = "/media/vms/vmware-images/shared-build/shared-build.vmdk" gentoo-term-systemd/gentoo-term-systemd.vmx:scsi0:2.fileName = "/media/vms/vmware-images/shared-build/shared-build.vmdk" gentoo-term/gentoo.vmx:scsi0:2.fileName = "/media/vms/vmware-images/shared-build/shared-build.vmdk" opensuse-leap/opensuse-leap.vmx:nvme0:1.fileName = "/media/vms/vmware-images/shared-build/shared-build.vmdk" opensuse-leap/opensuse-leap.vmx:scsi0:2.fileName = "/media/vms/vmware-images/shared-build/shared-build.vmdk" opensuse-tw/opensuse-tw.vmx:scsi0:2.fileName = "/media/vms/vmware-images/shared-build/shared-build.vmdk" ubuntu-18/ubuntu-18.vmx:scsi0:2.fileName = "/media/vms/vmware-images/shared-build/shared-build.vmdk" ubuntu-20/ubuntu-20.vmx:scsi0:2.fileName = "/media/vms/vmware-images/shared-build/shared-build.vmdk"  I'm hesitant to just yank these entries out, because I'm also seeing other entries that reference the old SCSI device: $ grep --color=auto scsi0:2 opensuse-leap/opensuse-leap.vmx scsi0:2.fileName = "/media/vms/vmware-images/shared-build/shared-build.vmdk" scsi0:2.mode = "independent-persistent" scsi0:2.redo = ""  Looking for the safest way to proceed.
Even when using Workstation Player? I have menu icons for both Player and Workstation, never used the Player one after buying a Workstation license. This should not be happening with Player.
At the top of the window, there's a warning about needing to update the tools on the VM. Has that been done?
Does the startup order of the VMs make any difference?
[Host: EndeavourOS, kernel 5.17.1] I have (2) issues with journal messages. Here is what I get after manually starting the required vmware services with sudo systemctl start vmware-networks.service ... See more...
[Host: EndeavourOS, kernel 5.17.1] I have (2) issues with journal messages. Here is what I get after manually starting the required vmware services with sudo systemctl start vmware-networks.service vmware-usbarbitrator.service: Apr 07 10:09:41 sudo[669096]: ajgringo619 : TTY=pts/1 ; PWD=/ ; USER=root ; COMMAND=/usr/bin/systemctl start vmware-networks.service vmware-usbarbitrator.service Apr 07 10:09:41 sudo[669096]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000) Apr 07 10:09:41 audit[669096]: USER_START pid=669096 uid=1000 auid=1000 ses=3 subj==unconfined msg='op=PAM:session_open grantors=pam_systemd_home,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success' Apr 07 10:09:41 systemd[1]: VMware Networks Configuration Generation was skipped because of a failed condition check (ConditionPathExists=!/etc/vmware/networking). Apr 07 10:09:41 systemd[1]: Starting VMware Networks... Apr 07 10:09:41 systemd[1]: Started VMware USB Arbitrator. Apr 07 10:09:41 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=vmware-usbarbitrator comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Apr 07 10:09:41 vmware-usbarbitrator[669100]: DICT --- GLOBAL SETTINGS /usr/lib/vmware/settings Apr 07 10:09:41 vmware-usbarbitrator[669100]: DICT --- NON PERSISTENT (null) Apr 07 10:09:41 vmware-usbarbitrator[669100]: DICT --- HOST DEFAULTS /etc/vmware/config Apr 07 10:09:41 vmware-usbarbitrator[669100]: DICT product.name = "VMware Player" Apr 07 10:09:41 vmware-usbarbitrator[669100]: DICT product.version = "16.0.0" Apr 07 10:09:41 vmware-usbarbitrator[669100]: DICT product.buildNumber = "16894299" Apr 07 10:09:41 vmware-usbarbitrator[669100]: DICT workstation.product.version = "16.0.0" Apr 07 10:09:41 vmware-usbarbitrator[669100]: DICT player.product.version = "16.0.0" Apr 07 10:09:41 vmware-usbarbitrator[669100]: DICT vix.config.version = "1" Apr 07 10:09:41 vmware-usbarbitrator[669100]: DICT bindir = "/usr/bin" Apr 07 10:09:41 vmware-usbarbitrator[669100]: DICT libdir = "/usr/lib/vmware" Apr 07 10:09:41 vmware-usbarbitrator[669100]: DICT vix.libdir = "/usr/lib/vmware-vix" Apr 07 10:09:41 vmware-usbarbitrator[669100]: DICT initscriptdir = "/usr/lib/systemd/scripts" Apr 07 10:09:41 vmware-usbarbitrator[669100]: DICT vmware.fullpath = "/usr/bin/vmware" Apr 07 10:09:41 vmware-usbarbitrator[669100]: DICT authd.fullpath = "/usr/bin/vmware-authd" Apr 07 10:09:41 vmware-usbarbitrator[669100]: DICT gksu.rootMethod = "su" Apr 07 10:09:41 vmware-usbarbitrator[669100]: DICT NETWORKING = "yes" Apr 07 10:09:41 vmware-usbarbitrator[669100]: DICT installerDefaults.autoSoftwareUpdateEnabled = "no" Apr 07 10:09:41 vmware-usbarbitrator[669100]: DICT installerDefaults.dataCollectionEnabled = "no" Apr 07 10:09:41 vmware-usbarbitrator[669100]: DICT installerDefaults.componentDownloadEnabled = "no" Apr 07 10:09:41 vmware-usbarbitrator[669100]: DICT installerDefaults.transferVersion = "1" Apr 07 10:09:41 vmware-usbarbitrator[669100]: DICT acceptOVFEULA = "yes" Apr 07 10:09:41 vmware-usbarbitrator[669100]: DICT acceptEULA = "yes" Apr 07 10:09:41 vmware-usbarbitrator[669100]: DICT --- SITE DEFAULTS /usr/lib/vmware/config Apr 07 10:09:41 vmware-usbarbitrator[669100]: DICT tag.help = "introduction.htm" Apr 07 10:09:41 vmware-usbarbitrator[669100]: DICT tag.configurationEditor = "config_editor_newvm.htm" Apr 07 10:09:41 vmware-usbarbitrator[669100]: DICT tag.ideConfig = "devices_virtualdrive.htm" Apr 07 10:09:41 vmware-usbarbitrator[669100]: DICT tag.floppyConfig = "devices_floppy.htm" Apr 07 10:09:41 vmware-usbarbitrator[669100]: DICT tag.mouseConfig = "devices_mouse.htm" Apr 07 10:09:41 vmware-usbarbitrator[669100]: DICT tag.netConfig = "devices_netadapter.htm" Apr 07 10:09:41 vmware-usbarbitrator[669100]: DICT tag.parallelConfig = "devices_parallel.htm" Apr 07 10:09:41 vmware-usbarbitrator[669100]: DICT tag.serialConfig = "devices_serial.htm" Apr 07 10:09:41 vmware-usbarbitrator[669100]: DICT tag.soundConfig = "devices_sound.htm" Apr 07 10:09:41 vmware-usbarbitrator[669100]: DICT tag.memConfig = "configvm_memory.htm" Apr 07 10:09:41 vmware-usbarbitrator[669100]: DICT tag.miscConfig = "configvm.htm" Apr 07 10:09:41 vmware-usbarbitrator[669100]: DICT tag.usbConfig = "devices_usb.htm" Apr 07 10:09:41 vmware-usbarbitrator[669100]: DICT tag.displayConfig = "configvm_display-problems.htm" Apr 07 10:09:41 vmware-usbarbitrator[669100]: DICT tag.tools = "vmtools.htm" Apr 07 10:09:41 vmware-usbarbitrator[669100]: USBArbRuleStore: Loading device rules from rules file '(null)'. Apr 07 10:09:41 vmware-usbarbitrator[669100]: USBArb: VMware USB Arbitration Service Version 20.5.0 Apr 07 10:09:41 vmware-usbarbitrator[669100]: USBGL: USB Sysfs found at /dev/bus/usb. Apr 07 10:09:41 vmware-usbarbitrator[669100]: USBArb: Attempting to connect to existing arbitrator on '/var/run/vmware/usbarbitrator-socket'. Apr 07 10:09:41 vmware-usbarbitrator[669100]: USBArbLib: USBArbLib initialized successfully, retryIntervalStart(5), retryIntervalMax(120), arbSocketName(/var/run/vmware/usbarbitrator-socket), useLocking(yes), noSetStringVersion(yes). Apr 07 10:09:41 vmware-usbarbitrator[669100]: SOCKET creating new socket, connecting to /var/run/vmware/usbarbitrator-socket Apr 07 10:09:41 vmware-usbarbitrator[669100]: SOCKET connect failed, error 2: No such file or directory Apr 07 10:09:41 vmware-usbarbitrator[669100]: USBArbLib: Failed to connect to USB Arbitrator, arbSocketname(/var/run/vmware/usbarbitrator-socket). Error(0x6): Connection error. Apr 07 10:09:41 vmware-usbarbitrator[669100]: USBArbLib: Failed to register in usbarblib. Apr 07 10:09:41 vmware-usbarbitrator[669100]: USBArb: No other USB arbitrator instance is currently running. Apr 07 10:09:41 vmware-usbarbitrator[669100]: USBArbP: Listening socket(11) created successfully. Apr 07 10:09:41 vmware-usbarbitrator[669100]: USBArbP: Adding listening socket(11) to poll queue. Apr 07 10:09:41 vmware-usbarbitrator[669100]: USBGL: Failed to open '/sys/bus/usb/devices/5-1/serial', error(0x2). Apr 07 10:09:41 vmware-usbarbitrator[669100]: USBGL: DevID(1c4f0002): Failed to read serial number for '5-1'. Apr 07 10:09:41 vmware-usbarbitrator[669100]: USBGL: Failed to open '/sys/bus/usb/devices/5-1/serial', error(0x2). Apr 07 10:09:41 vmware-usbarbitrator[669100]: USBGL: Failed to open '/sys/bus/usb/devices/1-4/manufacturer', error(0x2). Apr 07 10:09:41 vmware-usbarbitrator[669100]: USBGL: DevID(a120001): Failed to read manufacturer string for '1-4'. Apr 07 10:09:41 vmware-usbarbitrator[669100]: USBGL: Failed to open '/sys/bus/usb/devices/1-4/serial', error(0x2). Apr 07 10:09:41 vmware-usbarbitrator[669100]: USBGL: DevID(a120001): Failed to read serial number for '1-4'. Apr 07 10:09:41 vmware-usbarbitrator[669100]: USBGL: Failed to open '/sys/bus/usb/devices/1-4/manufacturer', error(0x2). Apr 07 10:09:41 vmware-usbarbitrator[669100]: USBGL: Failed to open '/sys/bus/usb/devices/1-4/serial', error(0x2). Apr 07 10:09:41 vmware-usbarbitrator[669100]: USBGL: Failed to open '/sys/bus/usb/devices/3-1/manufacturer', error(0x2). Apr 07 10:09:41 vmware-usbarbitrator[669100]: USBGL: DevID(30fa0301): Failed to read manufacturer string for '3-1'. Apr 07 10:09:41 vmware-usbarbitrator[669100]: USBGL: Failed to open '/sys/bus/usb/devices/3-1/serial', error(0x2). Apr 07 10:09:41 vmware-usbarbitrator[669100]: USBGL: DevID(30fa0301): Failed to read serial number for '3-1'. Apr 07 10:09:41 vmware-usbarbitrator[669100]: USBGL: Failed to open '/sys/bus/usb/devices/3-1/manufacturer', error(0x2). Apr 07 10:09:41 vmware-usbarbitrator[669100]: USBGL: Failed to open '/sys/bus/usb/devices/3-1/serial', error(0x2). Apr 07 10:09:41 vmware-usbarbitrator[669100]: USBArb: DevID(1105825da): Device defaults to target 'ask:' with rule(id:1). Apr 07 10:09:41 vmware-usbarbitrator[669100]: USBArb: DevID(1105825da): Device added. Apr 07 10:09:41 vmware-usbarbitrator[669100]: USBArb: DevID(21b1c0c1a): Device defaults to target 'ask:' with rule(id:2). Apr 07 10:09:41 vmware-usbarbitrator[669100]: USBArb: DevID(21b1c0c1a): Device added. Apr 07 10:09:41 vmware-usbarbitrator[669100]: USBArb: DevID(31c4f0002): Bootable hid device is not allowed. Apr 07 10:09:41 vmware-usbarbitrator[669100]: USBArb: DevID(31c4f0002): Device defaults to target 'host:' with rule(id:3). Apr 07 10:09:41 vmware-usbarbitrator[669100]: USBArb: DevID(31c4f0002): Device added. Apr 07 10:09:41 vmware-usbarbitrator[669100]: USBArb: DevID(404e86860): Device defaults to target 'ask:' with rule(id:4). Apr 07 10:09:41 vmware-usbarbitrator[669100]: USBArb: DevID(404e86860): Device added. Apr 07 10:09:41 vmware-usbarbitrator[669100]: USBArb: DevID(5051d0002): Device defaults to target 'ask:' with rule(id:5). Apr 07 10:09:41 vmware-usbarbitrator[669100]: USBArb: DevID(5051d0002): Device added. Apr 07 10:09:41 vmware-usbarbitrator[669100]: USBArb: DevID(60a120001): Device defaults to target 'ask:' with rule(id:6). Apr 07 10:09:41 vmware-usbarbitrator[669100]: USBArb: DevID(60a120001): Device added. Apr 07 10:09:41 vmware-usbarbitrator[669100]: USBArb: DevID(730fa0301): Bootable hid device is not allowed. Apr 07 10:09:41 vmware-usbarbitrator[669100]: USBArb: DevID(730fa0301): Device defaults to target 'host:' with rule(id:7). Apr 07 10:09:41 vmware-usbarbitrator[669100]: USBArb: DevID(730fa0301): Device added. Apr 07 10:09:41 vmware-usbarbitrator[669100]: USBArb: DevID(1105825da): Device 0: name:Western\ Digital\ My\ Book\ 25DA vid:1058 pid:25da path:4/2 speed:super family:storage,storage-bulk serialnum:574343374B3144454C345452 arbRuntimeKey:1 version:4 owner:(null). Apr 07 10:09:41 vmware-usbarbitrator[669100]: USBArb: DevID(21b1c0c1a): Device 1: name:CORSAIR\ Lighting\ Node\ CORE vid:1b1c pid:0c1a path:1/14 speed:full family:hid serialnum:2AD00304E51065AF6B84ED5D001C00F5 arbRuntimeKey:2 version:4 owner:(null). Apr 07 10:09:41 vmware-usbarbitrator[669100]: USBArb: DevID(31c4f0002): Device 2: name:SiGma\ Micro\ USB\ Keyboard vid:1c4f pid:0002 path:5/1 speed:low family:hid,hid-bootable arbRuntimeKey:3 version:4 owner:(null). Apr 07 10:09:41 vmware-usbarbitrator[669100]: USBArb: DevID(404e86860): Device 3: name:SAMSUNG_Android vid:04e8 pid:6860 path:5/4 speed:high family:vendor,comm,imaging serialnum:R5CT112NTSK arbRuntimeKey:4 version:4 owner:(null). Apr 07 10:09:41 vmware-usbarbitrator[669100]: USBArb: DevID(5051d0002): Device 4: name:APC\ Back-UPS\ ES\ 550G\ FW:904.W1\ .D\ USB\ FW:W1 vid:051d pid:0002 path:5/2 speed:low family:hid serialnum:4B1649P23141\ \ arbRuntimeKey:5 version:4 owner:(null). Apr 07 10:09:41 vmware-usbarbitrator[669100]: USBArb: DevID(60a120001): Device 5: name:Cambridge\ Silicon\ Radio\ CSR8510\ A10 vid:0a12 pid:0001 path:1/4 speed:full family:wireless,bluetooth arbRuntimeKey:6 quirks:bluetooth version:4 owner:(null). Apr 07 10:09:41 vmware-usbarbitrator[669100]: USBArb: DevID(730fa0301): Device 6: name:USB\ OPTICAL\ MOUSE vid:30fa pid:0301 path:3/1 speed:low family:hid,hid-bootable arbRuntimeKey:7 version:4 owner:(null). Apr 07 10:09:41 vmware-usbarbitrator[669100]: USBArb: 7 devices enumerated. Apr 07 10:09:42 kernel: vmnet1: Current addr: 00 50 56 c0 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Apr 07 10:09:42 kernel: vmnet1: Expected addr: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Apr 07 10:09:42 kernel: ------------[ cut here ]------------ Apr 07 10:09:42 kernel: netdevice: vmnet1: Incorrect netdev->dev_addr Apr 07 10:09:42 kernel: WARNING: CPU: 3 PID: 669105 at net/core/dev_addr_lists.c:517 dev_addr_check.cold+0x43/0x7d Apr 07 10:09:42 kernel: Modules linked in: vmnet(OE) rndis_host cdc_ether usbnet mii cdc_acm snd_seq_dummy snd_seq snd_seq_device rfcomm cmac algif_hash algif_skcipher af_alg bnep btusb btrtl btbcm btintel btmtk bluetooth ses enclosure scsi_transport_sas mousedev joydev ecdh_generic crc16 intel_rapl_msr intel_rapl_common eeepc_wmi asus_wmi sparse_keymap vfat platform_profile fat video edac_mce_amd snd_hda_codec_realtek wmi_bmof mxm_wmi rfkill kvm_amd snd_hda_codec_generic asus_wmi_sensors ledtrig_audio snd_hda_codec_hdmi snd_hda_intel kvm snd_intel_dspcfg snd_intel_sdw_acpi irqbypass crct10dif_pclmul snd_hda_codec crc32_pclmul ghash_clmulni_intel aesni_intel snd_hda_core crypto_simd snd_hwdep cryptd rapl snd_pcm snd_timer igb tpm_crb snd tpm_tis sp5100_tco nvidia_drm(POE) pcspkr ccp k10temp nvidia_modeset(POE) i2c_piix4 soundcore dca tpm_tis_core tpm pinctrl_amd gpio_amdpt rng_core gpio_generic wmi mac_hid acpi_cpufreq ip6t_REJECT nf_reject_ipv6 xt_hl ip6t_rt ipt_REJECT nf_reject_ipv4 xt_LOG Apr 07 10:09:42 kernel: nf_log_syslog xt_multiport xt_limit xt_addrtype xt_tcpudp xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip6table_filter ip6_tables iptable_filter vmmon(OE) vmw_vmci pkcs8_key_parser nvidia_uvm(POE) nvidia(POE) fuse crypto_user bpf_preload ip_tables x_tables uas usb_storage usbhid btrfs blake2b_generic libcrc32c crc32c_generic xor raid6_pq sr_mod xhci_pci crc32c_intel cdrom xhci_pci_renesas Apr 07 10:09:42 kernel: CPU: 3 PID: 669105 Comm: vmware-networks Tainted: P OE 5.17.1-zen1-1-zen #1 fe4e0fd298e67126bd03f4c33c50f60fa1b563ff Apr 07 10:09:42 kernel: Hardware name: System manufacturer System Product Name/PRIME X470-PRO, BIOS 6024 02/25/2022 Apr 07 10:09:42 kernel: RIP: 0010:dev_addr_check.cold+0x43/0x7d Apr 07 10:09:42 kernel: Code: 01 e8 e9 f5 f9 ff 0f 0b 49 c7 c4 df 39 cd a2 80 3b 00 75 30 48 c7 c6 ea 39 cd a2 4c 89 e2 48 c7 c7 a0 75 d6 a2 e8 c5 f5 f9 ff <0f> 0b e9 0e 85 d7 ff 49 c7 c4 df 39 cd a2 eb d5 4c 8b 24 d5 00 33 Apr 07 10:09:42 kernel: RSP: 0018:ffffaf724c51bb68 EFLAGS: 00010286 Apr 07 10:09:42 kernel: RAX: 0000000000000000 RBX: ffff93148b51a000 RCX: 0000000000000027 Apr 07 10:09:42 kernel: RDX: ffff931b1eae1728 RSI: 0000000000000001 RDI: ffff931b1eae1720 Apr 07 10:09:42 kernel: RBP: ffffffffc34163e0 R08: 0000000000000001 R09: 00000000ffffffea Apr 07 10:09:42 kernel: R10: ffff931b3f24a7c0 R11: ffffaf724c51b938 R12: ffffffffa2c977a1 Apr 07 10:09:42 kernel: R13: 0000000000000001 R14: 0000000000000000 R15: ffff93148b51a000 Apr 07 10:09:42 kernel: FS: 00007f87688cf200(0000) GS:ffff931b1eac0000(0000) knlGS:0000000000000000 Apr 07 10:09:42 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Apr 07 10:09:42 kernel: CR2: 00007ffd0718cefc CR3: 000000037a624000 CR4: 00000000003506e0 Apr 07 10:09:42 kernel: Call Trace: Apr 07 10:09:42 kernel: <TASK> Apr 07 10:09:42 kernel: __dev_open+0x50/0x200 Apr 07 10:09:42 kernel: __dev_change_flags+0x274/0x300 Apr 07 10:09:42 kernel: ? __rtnl_unlock+0x24/0x50 Apr 07 10:09:42 kernel: dev_change_flags+0x3f/0x2b0 Apr 07 10:09:42 kernel: ? bpf_lsm_capset+0x10/0x10 Apr 07 10:09:42 kernel: ? security_capable+0x36/0x50 Apr 07 10:09:42 kernel: devinet_ioctl+0x5f8/0x810 Apr 07 10:09:42 kernel: ? _copy_from_user+0x28/0x60 Apr 07 10:09:42 kernel: inet_ioctl+0x1b1/0x1e0 Apr 07 10:09:42 kernel: sock_do_ioctl+0x82/0x160 Apr 07 10:09:42 kernel: sock_ioctl+0x12a/0x3d0 Apr 07 10:09:42 kernel: __x64_sys_ioctl+0x82/0xb0 Apr 07 10:09:42 kernel: do_syscall_64+0x5c/0x80 Apr 07 10:09:42 kernel: ? exc_page_fault+0x72/0x170 Apr 07 10:09:42 kernel: entry_SYSCALL_64_after_hwframe+0x44/0xae Apr 07 10:09:42 kernel: RIP: 0033:0x7f87689d7e6f Apr 07 10:09:42 kernel: Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <41> 89 c0 3d 00 f0 ff ff 77 1f 48 8b 44 24 18 64 48 2b 04 25 28 00 Apr 07 10:09:42 kernel: RSP: 002b:00007ffd0718d830 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 Apr 07 10:09:42 kernel: RAX: ffffffffffffffda RBX: 00007ffd0718d8e0 RCX: 00007f87689d7e6f Apr 07 10:09:42 kernel: RDX: 00007ffd0718d8e0 RSI: 0000000000008914 RDI: 0000000000000005 Apr 07 10:09:42 kernel: RBP: 0000000000000005 R08: 00007ffd0718d8a0 R09: 0000000000000004 Apr 07 10:09:42 kernel: R10: 0000000000000019 R11: 0000000000000246 R12: 00007ffd0718d8a0 Apr 07 10:09:42 kernel: R13: 00007ffd0718d8b0 R14: 00007ffd0718d8c0 R15: 0000000000000000 Apr 07 10:09:42 kernel: </TASK> Apr 07 10:09:42 kernel: ---[ end trace 0000000000000000 ]--- Apr 07 10:09:42 avahi-daemon[855]: Joining mDNS multicast group on interface vmnet1.IPv4 with address 192.168.136.1. Apr 07 10:09:42 NetworkManager[230235]: <info> [1649351382.9561] device (vmnet1): driver '(null)' does not support carrier detection. Apr 07 10:09:42 avahi-daemon[855]: New relevant interface vmnet1.IPv4 for mDNS. Apr 07 10:09:42 systemd-udevd[669104]: Using default interface naming scheme 'v250'. Apr 07 10:09:42 avahi-daemon[855]: Registering new address record for 192.168.136.1 on vmnet1.IPv4. Apr 07 10:09:42 NetworkManager[230235]: <info> [1649351382.9563] device (vmnet1): driver 'unknown' does not support carrier detection. Apr 07 10:09:42 NetworkManager[230235]: <info> [1649351382.9566] manager: (vmnet1): new Ethernet device (/org/freedesktop/NetworkManager/Devices/4) Apr 07 10:09:43 vmnet-natd[669153]: RTM_NEWLINK: name:enp6s0 index:2 flags:0x00011043 Apr 07 10:09:43 vmnet-natd[669153]: RTM_NEWROUTE: index:2 Apr 07 10:09:43 vmnet-natd[669153]: RTM_NEWADDR: index:2, addr:192.168.0.15 Apr 07 10:09:43 kernel: userif-2: sent link up event. Apr 07 10:09:43 NetworkManager[230235]: <info> [1649351383.0539] device (vmnet8): driver '(null)' does not support carrier detection. Apr 07 10:09:43 NetworkManager[230235]: <info> [1649351383.0540] device (vmnet8): driver 'unknown' does not support carrier detection. Apr 07 10:09:43 NetworkManager[230235]: <info> [1649351383.0542] manager: (vmnet8): new Ethernet device (/org/freedesktop/NetworkManager/Devices/5) Apr 07 10:09:43 avahi-daemon[855]: Joining mDNS multicast group on interface vmnet8.IPv4 with address 172.16.73.1. Apr 07 10:09:43 avahi-daemon[855]: New relevant interface vmnet8.IPv4 for mDNS. Apr 07 10:09:43 avahi-daemon[855]: Registering new address record for 172.16.73.1 on vmnet8.IPv4. Apr 07 10:09:43 kernel: vmnet8: Current addr: 00 50 56 c0 00 08 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Apr 07 10:09:43 kernel: vmnet8: Expected addr: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Apr 07 10:09:43 kernel: ------------[ cut here ]------------ Apr 07 10:09:43 kernel: netdevice: vmnet8: Incorrect netdev->dev_addr Apr 07 10:09:43 kernel: WARNING: CPU: 2 PID: 669105 at net/core/dev_addr_lists.c:517 dev_addr_check.cold+0x43/0x7d Apr 07 10:09:43 kernel: Modules linked in: vmnet(OE) rndis_host cdc_ether usbnet mii cdc_acm snd_seq_dummy snd_seq snd_seq_device rfcomm cmac algif_hash algif_skcipher af_alg bnep btusb btrtl btbcm btintel btmtk bluetooth ses enclosure scsi_transport_sas mousedev joydev ecdh_generic crc16 intel_rapl_msr intel_rapl_common eeepc_wmi asus_wmi sparse_keymap vfat platform_profile fat video edac_mce_amd snd_hda_codec_realtek wmi_bmof mxm_wmi rfkill kvm_amd snd_hda_codec_generic asus_wmi_sensors ledtrig_audio snd_hda_codec_hdmi snd_hda_intel kvm snd_intel_dspcfg snd_intel_sdw_acpi irqbypass crct10dif_pclmul snd_hda_codec crc32_pclmul ghash_clmulni_intel aesni_intel snd_hda_core crypto_simd snd_hwdep cryptd rapl snd_pcm snd_timer igb tpm_crb snd tpm_tis sp5100_tco nvidia_drm(POE) pcspkr ccp k10temp nvidia_modeset(POE) i2c_piix4 soundcore dca tpm_tis_core tpm pinctrl_amd gpio_amdpt rng_core gpio_generic wmi mac_hid acpi_cpufreq ip6t_REJECT nf_reject_ipv6 xt_hl ip6t_rt ipt_REJECT nf_reject_ipv4 xt_LOG Apr 07 10:09:43 kernel: nf_log_syslog xt_multiport xt_limit xt_addrtype xt_tcpudp xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip6table_filter ip6_tables iptable_filter vmmon(OE) vmw_vmci pkcs8_key_parser nvidia_uvm(POE) nvidia(POE) fuse crypto_user bpf_preload ip_tables x_tables uas usb_storage usbhid btrfs blake2b_generic libcrc32c crc32c_generic xor raid6_pq sr_mod xhci_pci crc32c_intel cdrom xhci_pci_renesas Apr 07 10:09:43 kernel: CPU: 2 PID: 669105 Comm: vmware-networks Tainted: P W OE 5.17.1-zen1-1-zen #1 fe4e0fd298e67126bd03f4c33c50f60fa1b563ff Apr 07 10:09:43 kernel: Hardware name: System manufacturer System Product Name/PRIME X470-PRO, BIOS 6024 02/25/2022 Apr 07 10:09:43 kernel: RIP: 0010:dev_addr_check.cold+0x43/0x7d Apr 07 10:09:43 kernel: Code: 01 e8 e9 f5 f9 ff 0f 0b 49 c7 c4 df 39 cd a2 80 3b 00 75 30 48 c7 c6 ea 39 cd a2 4c 89 e2 48 c7 c7 a0 75 d6 a2 e8 c5 f5 f9 ff <0f> 0b e9 0e 85 d7 ff 49 c7 c4 df 39 cd a2 eb d5 4c 8b 24 d5 00 33 Apr 07 10:09:43 kernel: RSP: 0018:ffffaf724c51baf8 EFLAGS: 00010282 Apr 07 10:09:43 kernel: RAX: 0000000000000000 RBX: ffff93148b51c000 RCX: 0000000000000027 Apr 07 10:09:43 kernel: RDX: ffff931b1eaa1728 RSI: 0000000000000001 RDI: ffff931b1eaa1720 Apr 07 10:09:43 kernel: RBP: ffffffffc34163e0 R08: 0000000000000001 R09: 00000000ffffffea Apr 07 10:09:43 kernel: R10: ffff931b3f24a7c0 R11: ffffaf724c51b8c8 R12: ffffffffa2c977a1 Apr 07 10:09:43 kernel: R13: 0000000000000001 R14: 0000000000000000 R15: ffff93148b51c000 Apr 07 10:09:43 kernel: FS: 00007f87688cf200(0000) GS:ffff931b1ea80000(0000) knlGS:0000000000000000 Apr 07 10:09:43 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Apr 07 10:09:43 kernel: CR2: 00007ffd0718cefc CR3: 000000037a624000 CR4: 00000000003506e0 Apr 07 10:09:43 kernel: Call Trace: Apr 07 10:09:43 kernel: <TASK> Apr 07 10:09:43 kernel: __dev_open+0x50/0x200 Apr 07 10:09:43 kernel: __dev_change_flags+0x274/0x300 Apr 07 10:09:43 kernel: dev_change_flags+0x3f/0x2b0 Apr 07 10:09:43 kernel: ? bpf_lsm_capset+0x10/0x10 Apr 07 10:09:43 kernel: ? bpf_lsm_capset+0x10/0x10 Apr 07 10:09:43 kernel: ? security_capable+0x36/0x50 Apr 07 10:09:43 kernel: devinet_ioctl+0x5f8/0x810 Apr 07 10:09:43 kernel: ? _copy_from_user+0x28/0x60 Apr 07 10:09:43 kernel: inet_ioctl+0x1b1/0x1e0 Apr 07 10:09:43 kernel: sock_do_ioctl+0x82/0x160 Apr 07 10:09:43 kernel: sock_ioctl+0x12a/0x3d0 Apr 07 10:09:43 kernel: __x64_sys_ioctl+0x82/0xb0 Apr 07 10:09:43 kernel: do_syscall_64+0x5c/0x80 Apr 07 10:09:43 kernel: ? syscall_exit_to_user_mode+0x23/0x40 Apr 07 10:09:43 kernel: ? do_syscall_64+0x69/0x80 Apr 07 10:09:43 kernel: ? exc_page_fault+0x72/0x170 Apr 07 10:09:43 kernel: entry_SYSCALL_64_after_hwframe+0x44/0xae Apr 07 10:09:43 kernel: RIP: 0033:0x7f87689d7e6f Apr 07 10:09:43 kernel: Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <41> 89 c0 3d 00 f0 ff ff 77 1f 48 8b 44 24 18 64 48 2b 04 25 28 00 Apr 07 10:09:43 kernel: RSP: 002b:00007ffd0718d830 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 Apr 07 10:09:43 kernel: RAX: ffffffffffffffda RBX: 00007ffd0718d8e0 RCX: 00007f87689d7e6f Apr 07 10:09:43 kernel: RDX: 00007ffd0718d8e0 RSI: 0000000000008914 RDI: 0000000000000005 Apr 07 10:09:43 kernel: RBP: 0000000000000005 R08: 00007ffd0718d8a0 R09: 0000000000000004 Apr 07 10:09:43 kernel: R10: 0000000000000019 R11: 0000000000000246 R12: 00007ffd0718d8a0 Apr 07 10:09:43 kernel: R13: 00007ffd0718d8b0 R14: 00007ffd0718d8c0 R15: 0000000000000000 Apr 07 10:09:43 kernel: </TASK> Apr 07 10:09:43 kernel: ---[ end trace 0000000000000000 ]--- Apr 07 10:09:43 vmware-networks[669105]: Enabled hostonly virtual adapter on vmnet1 Apr 07 10:09:43 vmware-networks[669105]: Started DHCP service on vmnet1 Apr 07 10:09:43 vmware-networks[669105]: Started NAT service on vmnet8 Apr 07 10:09:43 vmware-networks[669105]: Enabled hostonly virtual adapter on vmnet8 Apr 07 10:09:43 vmware-networks[669105]: Started DHCP service on vmnet8 Apr 07 10:09:43 vmware-networks[669105]: Started all configured services on all networks Apr 07 10:09:43 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=vmware-networks comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Apr 07 10:09:43 systemd[1]: Started VMware Networks. At this point I can start any of my VMs and they all work. However, I now get spammed with the following messages until I shutdown the vmware services:   Apr 07 10:09:52 vmnet-natd[669153]: RTM_NEWADDR: index:2, addr:192.168.0.15 Apr 07 10:09:52 kernel: userif-2: sent link up event. Apr 07 10:09:55 vmnet-natd[669153]: RTM_NEWADDR: index:2, addr:192.168.0.15 Apr 07 10:09:55 kernel: userif-2: sent link up event. Apr 07 10:09:58 vmnet-natd[669153]: RTM_NEWADDR: index:2, addr:192.168.0.15 Apr 07 10:09:58 kernel: userif-2: sent link up event. Apr 07 10:10:01 vmnet-natd[669153]: RTM_NEWADDR: index:2, addr:192.168.0.15 Apr 07 10:10:01 kernel: userif-2: sent link up event. Apr 07 10:10:04 vmnet-natd[669153]: RTM_NEWADDR: index:2, addr:192.168.0.15 Apr 07 10:10:04 kernel: userif-2: sent link up event. Apr 07 10:10:07 vmnet-natd[669153]: RTM_NEWADDR: index:2, addr:192.168.0.15 Apr 07 10:10:07 kernel: userif-2: sent link up event. Apr 07 10:10:10 vmnet-natd[669153]: RTM_NEWADDR: index:2, addr:192.168.0.15   Again, everything is working. This started about a month ago, so it's not related to the recent v16.2.3 upgrade. UPDATE: I updated to v16.2.3 (from v16.2.1) on 3/15, so maybe it is related to this latest version.
How much memory does your GPU have? How much is allocated to your VMs?
I had an issue with lag in terminals (see https://communities.vmware.com/t5/VMware-Workstation-Pro/Noticeable-typing-lag-in-Linux-VM-terminals-since-v16-2-upgrade/m-p/2872427#M171730), but not outrig... See more...
I had an issue with lag in terminals (see https://communities.vmware.com/t5/VMware-Workstation-Pro/Noticeable-typing-lag-in-Linux-VM-terminals-since-v16-2-upgrade/m-p/2872427#M171730), but not outright freezing. What distros have you tried?
Been running VMware WS 16 while storing my VMs on separate BTRFS subvolumes managed by snapper. In searching for info about enhancing performance on BTRFS, every link I find claims it's not optimal. ... See more...
Been running VMware WS 16 while storing my VMs on separate BTRFS subvolumes managed by snapper. In searching for info about enhancing performance on BTRFS, every link I find claims it's not optimal. But the links are all 5+ years old. Does anyone else have any current experience with VMs on BTRFS subvolumes? I haven't noticed any problems at all, so I'm curious what others are seeing.