(This was a regression in the previous test build that mostly happened on Windows 7.
DOES STOPAD CONFLICT WITH AVAST CODE
This build should fix a number of the "terminated unexpectedly during startup with exit code X" issue, though not all of them. I am wondering if there has been a system level permissions issue or something similar.īut then again, I have my VMWare VM's (Windows 8.1 and Fedora 19) on a separate HDD and Window is having issues there too, while Fedora is not. Updating to 4.3.14 caused all VM's including Linux to stop and VBox errors to pop up similar to those posted above.ī) The only other thing I can think of that has changed on the host over the past two days was a Windows Defender update. Linux was working fine at that point (Fedora, Ubuntu and Zorin VM's). When I went to run the Windows VM this morning, I received a virtualization error message which I could not resolve except by deletingthe Windows VM. The reason I am asking about VM storage location is two-fold:Ī) I installed Comodo Free Firewall on the host yesterday evening. My physical host is fully capable of virtualization, and in fact, both Linux and Windows guests were running perfectly till this morning (a few hours ago). The Fedora log shows the same warning, but in that case I don't know if Fedora requires the NX feature. This doesn't seem to have anything to do with the subject of this thread.
wrote:00:00:00.438661 CPUM: WARNING! Can't turn on NX/XD when the host doesn't support it!
0 kommentar(er)
