![]() In the next step you need to select how much RAM and how many CPU cores the VM should have. Select the option Local install media and choose the Windows 10 ISO. In this case we use a Windows 10 ISO image. The first thing you have to do is to select how you would like to install the operating system. Click on the upper left button to open the New VM window. To create a new virtual machine start “Virtual Machine Manager”, which opens up a simple GUI. VT-x / AMD-V) in your BIOS / UEFI settings before you continue (thanks for the tip to include this in the note). I don't envy whomever has to hunt down this bug and port up to the latest kernel version, good luck on your journey in the magical forest.Sudo apt-get install qemu-kvm libvirt-bin bridge-utils virt-manager qemu virt-viewer spice-vdagent My guess is that it is somewhere in the ether of Linux UI handling. There appears to be a breaking change somewhere between 5.15.0-46-generic and 5.15.0-58-generic. This solution "works on my box" and is no under no guarantee to work for you $ sudo vmware-installer -u vmware-workstation Start VMWare Workstation Pro 17.if for whatever reason Workstation doesn't feel like recompiling the kernel modulesĭownload the bundle installer for your version of Vmware Workstation Pro Select 5.15.0-46-generic from Ubuntu kernel menu, if menu doesn't appear do this: I expect this kind of thing from virtualbox because its opensource and community, but not from a for profit product.ĭowngrade and freeze Linux kernel version to 5.15.0-46-generic. Additionally I continue to use Ubuntu 20.04 instead of upgrading to 22.04 because the virtual machine manager refuses to capture the menu (windows) key and breaks all GNOME shortcuts. Prior built virtual machines still s only new virtual machines that are the problem. If I downgrade the virtual machine compatibility to 16.X the virtual machine will boot but the splash screen overlays over the virtual machine window, approximately 3/4 of the window, making it impossible to use. Behavior consistent even with a blank virtual machine with the install the OS later checked. The vmware "connecting" splash screen comes up and spins saying "connecting" then freezes. Vmware-vmx.exe seems to be freezing up as wellĬannot create new virtual machines. T23:13:25.419Z In(05) main MKSRoleMain: Skipping SSL (already exited) T23:13:25.387Z In(05) main MKSRoleMain: Powering off MKS T23:13:25.387Z In(05) main MKS/SVGA threads are stopped T23:13:25.386Z In(05) svga MKSRoleReplay: MKSRoleReplay_Run: Finished. T23:13:25.386Z In(05) svga MKSSandboxComm: ISB closed the channel while reading T23:13:25.386Z In(05) mks MKSThread: Requesting MKS exit T23:12:30.753Z In(05) svga MKSSandboxComm: ISBRenderer might be unresponsive, retrying. T23:11:29.616Z In(05) svga MKSSandboxComm: ISBRenderer might be unresponsive, retrying. T23:10:27.832Z In(05) svga MKSSandboxComm: ISBRenderer might be unresponsive, retrying. T23:09:26.593Z In(05) svga MKSSandboxComm: ISBRenderer might be unresponsive, retrying. ![]() T23:08:16.304Z In(05) main Cannot open file "C:\Users\xxxxxx\AppData\Roaming\VMware\config.ini": The system cannot find the file specified. ![]() T23:08:16.304Z In(05) main DictionaryLoad: Cannot open file "C:\Users\xxxxx\AppData\Roaming\VMware\config.ini": The system cannot find the file specified. All my windows 10 VM's are not booting with VMware Workstation Pro 17.01
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |