Win10 VB VM Guest in Maui Host + VB 3D Acceleration + Maui Nouveau graphics driver = Frozen Maui [Tower].
I have 2 VirtualBox VMs of Win10 [yuck]. They're not new, having been created back when i still ran Mint 17.3 KDE4 (ie, < Sept 2016]. I have not needed [or wanted] to boot either of these VMs for months until today, & all previous times i did run them, Mint & Maui were using the proprietary Nvidia graphics drivers. Relatively recently, as per https://forums.mauilinux.org/showthread.php?tid=24237 , I stopped using Maui's Nvidia graphics driver & began using the Nouveau driver [& i still am]. Both my old Win10 VMs had 3D Acceleration enabled in their VB Settings, & before today ran properly.
Today, being as stated the first boot of these VMs since i adopted Nouveau, i was shocked to discover that 6 out of 6 [it might even have been 8 out of 8] VM boot attempts caused my Tower's Maui OS itself to freeze, needing Hard Resets [at first making me think (wrongly), that it was more occurrences of the ongoing random fault as per the above linked thread]. After much investigation & process of elimination, i discovered / proved the root cause of this pain was the VB 3D Acceleration function being enabled in those VMs' Settings. Once i disabled it, both VMs were able to start & run normally & Maui remained running, not freezing.
This mess really shocked me, as it never occurred to me that one price to pay for my decision to revert to the Nouveau driver in lieu of the Nvidia driver, was that it would stop me retaining my previous long-term Win10 VB VM settings. Given today's 100% failure rate though, i can't draw a different [tentative] conclusion. Ie, i presumed this simply meant that Nouveau & 3D Acceleration are mutually exclusive.
However, in that other thread, specifically post https://forums.mauilinux.org/showthread....7#pid41397, this was said:
So now i'm a bit confused; which is correct?
Furthermore, whilst this might(?) be a VirtualBox problem, how is it proper / possible that VirtualBox is able to freeze Maui in this scenario, rather than simply abort the VM run?
I have 2 VirtualBox VMs of Win10 [yuck]. They're not new, having been created back when i still ran Mint 17.3 KDE4 (ie, < Sept 2016]. I have not needed [or wanted] to boot either of these VMs for months until today, & all previous times i did run them, Mint & Maui were using the proprietary Nvidia graphics drivers. Relatively recently, as per https://forums.mauilinux.org/showthread.php?tid=24237 , I stopped using Maui's Nvidia graphics driver & began using the Nouveau driver [& i still am]. Both my old Win10 VMs had 3D Acceleration enabled in their VB Settings, & before today ran properly.
Today, being as stated the first boot of these VMs since i adopted Nouveau, i was shocked to discover that 6 out of 6 [it might even have been 8 out of 8] VM boot attempts caused my Tower's Maui OS itself to freeze, needing Hard Resets [at first making me think (wrongly), that it was more occurrences of the ongoing random fault as per the above linked thread]. After much investigation & process of elimination, i discovered / proved the root cause of this pain was the VB 3D Acceleration function being enabled in those VMs' Settings. Once i disabled it, both VMs were able to start & run normally & Maui remained running, not freezing.
This mess really shocked me, as it never occurred to me that one price to pay for my decision to revert to the Nouveau driver in lieu of the Nvidia driver, was that it would stop me retaining my previous long-term Win10 VB VM settings. Given today's 100% failure rate though, i can't draw a different [tentative] conclusion. Ie, i presumed this simply meant that Nouveau & 3D Acceleration are mutually exclusive.
However, in that other thread, specifically post https://forums.mauilinux.org/showthread....7#pid41397, this was said:
Quote:leszek Wrote:
Nouveau drivers are well capable of running 3D games aswell.
So now i'm a bit confused; which is correct?
Furthermore, whilst this might(?) be a VirtualBox problem, how is it proper / possible that VirtualBox is able to freeze Maui in this scenario, rather than simply abort the VM run?