(I had never seen a process use 112% of the cpu before )Ĭode: Select all Expand view Collapse view $ps augxw In this last case, here are some relevant lines from ps on the host. But although it runs in this case, it is too slow to be useable AND it makes the host machine unuseably slow also. As was noted in other threads here, I tried both with 3D acceleration on and off, and it seems to run and not freeze if I have 3D acceleration checked in the settings of the VM AND transparency effects turned off within Windows. But it still froze, and once actually aborted.
After much trial and error, the machine would last much longer if I did NOT start in "scaled mode" or "seamless mode". ( i could click to get to the screen to enter my PIN, but the machine froze after entering the first digit of the PIN). The install seemed to go fine, but upon reboot the machine seemed to freeze after the first keypress. All worked great until I installed the Guest Additions. making the host partition which was the "C:\ drive" of the windows install into a raw disk of the VM). making a host partition into "raw disk", as the EFI partition ("system partition") of the VM and 2. (if relevant, the guest was a "real" bare-metal install that I turned into a VM by 1. There is still the issue that the VM is using more than 100% of the CPU according to ps on the host, but I will open a separate thread for this issue if it continues. I now seem to have a working WIndows 11 guest with guest additions install.
Once I removed the TPM, I followed the advice in a few posts in the forum (basically: uninstall from the command line, reboot, Enable 3D, reinstall guest additions, shutdown, configure VBoxVGA, reboot, wait a few minutes, shutdown, configure VBoxSVGA and 3D, reboot, install the WDDM driver). I now run Windows 11 without a TPM in the VM. I found nothing online about how to fix this, so I just deleted the TPM 2.0. I can't be certain that this was the root cause, but: in the VM, the TPM 2.0 would not start because of a "protocol error between the driver and the device".
0 kommentar(er)
