The older versions presented in this article and their natively supported kernels are as follows: 15.5 (kernels up to 5.4), 14.1.7 (4.18) and 12.5.9 (4.12).įor VMware bundle versions, a collection of patches needed for the VMware host modules to build against recent kernels can be found from the vmware-host-modules GitHub repository. VMware Workstation 16.0 supports kernel 5.8 out of the box. If it loads for too long without response, please try #Cannot load module vmmon. rvice for sharing virtual machines (not available since version 16).rvice for connecting USB devices to guest.rvice for guest network access (otherwise you will get an error could no connect 'ethernet 0' to virtual network and you will not be able to use vmware-netcfg).Then, as desired, enable some of the following services: It is also necessary to install the appropriate headers package(s) for your installed kernel(s): for example linux-headers or linux-lts-headers.įor vmware-workstation AUR, start rvice first to generate /etc/vmware/networking. Install vmware-workstation AUR, vmware-workstation16 AUR, vmware-workstation15 AUR, vmware-workstation14 AUR, vmware-workstation12 AUR or vmware-workstation11 AUR for respectively versions 17, 16, 15, 14, 12 and 11 of VMware Workstation. If it shows Unable to install all modules, please try #Cannot load module vmmon. (It used to be a problem in Krusader, but that was random and also involved an old spinning drive so I just lived with it, however, I haven't seen the problem in Krusader in at least 3 months.).Tip: To (re)build the modules from terminal later on, use: You're probably right about it being Hardware but I have no idea where to start with diagnosing it, and like I said, VMs are the only thing I have found that I can use to reliably create the issue. Yes the UD is an SSD and its formatted in XFS. Regardless, With the Windows 11 VM I actually made a new pool to test it out before making this post. (MY docker app data is called 'applications' because 'appdata' never existed in earlier versions, Same with the 'System', 'Domain' and 'ISO' dir.) I have been using Unraid since very late version 3, so somethings may not be 'standard'. The vDisk is on a UD because it was installed there before cache pools were a thing. (Its not just restricted to file transfers either, its any HDD activity, hence the unusable VMs) If I get lucky I MIGHT be able to do a file transfer or two before the issue starts. I can make another video showing whatever you like on the screen with any VM if that will help. Like I said, its 100% repeatable within a VM regardless of how the VM is set up. 4GB memory (Initial and max both the same size), Machine was Q35-6.2, Bios was OVMF TPM, the vDisk was qcow with the VirtIO bus. This one had the same number of CPUs (same config, no other VMs running). (It was a brand new install of Windows 11 for testing hence the low ram). The video is just showing the issue that is present in all of them. Why not put that disk in a Pool and do your VMs there?Īs you said before, you need to concentrate on hardware issues. Is it a SSD or a spinner disk? How is it formatted? Did you have the xml setup you posted when you did the video? I can't understand how you can peg your CPU usage at 100% with 3 cores and 6 CPUs doing a file copy. Your xml shows 6GB of memory but your video shows 4GB? That's not what your xml shows. What log files do I need to submit that might show where the problem is? Virtualization is enabled in the BIOS, the vDisk is located on an SSD through Unassigned devices. This has been frustrating me for a while now and I have had no luck figuring it out (reddit posts mainly) so I thought I would try my luck here.Įvery VM I create is insanely slow to the point that its unusable. RAMPAGE IV BLACK EDITION Version Rev 1.xx.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |