<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#CCCCCC">
<div class="moz-cite-prefix">On 10/30/2014 08:01 PM, Tom Maneiro
wrote:<br>
</div>
<blockquote
cite="mid:20141030143105.2310.76828.reportbug@mersys-devel.mersys"
type="cite">
<pre wrap="">Yes, any VM where 3D acceleration is disabled works fine under the new version,
although of course 3D-enabled things work slowly or not at all. I get that 3D
is still marked as "experimental", but on 4.3.14 it actually works without
issues for any of my 3D-enabled VMs, which I've been using for months, so these
crashes are new to me. I mostly require 3D for testing newer Windows versions
(like for example the Win10 tech preview, where with 3D disabled, desktop slows
down to a crawl, and 3D acceleration is required for some components). Having a
VM crashing right after boot exposes me to potential data loss on such VMs (or
even in the host PC, when the video driver crashes bringing down my X session),
and I actually use them for software development and testing purposes, hence it
does fit the "grave" criteria, according to the description in Reportbug.
I've tried both versions under the latest kernel available for Testing
(3.16.3), and a slightly older revision of the same kernel. I don't really know
who to blame: Virtualbox or Nouveau (again: old Virtualbox + Nouveau = OK, new
Virtualbox + same Nouveau = crashes)</pre>
</blockquote>
<br>
It seems there are other (non VBox) issues reported with a similar
error string.<br>
<br>
<a class="moz-txt-link-freetext" href="https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1314405">https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1314405</a><br>
<pre class="moz-signature" cols="72">--
Ritesh Raj Sarraf
RESEARCHUT - <a class="moz-txt-link-freetext" href="http://www.researchut.com">http://www.researchut.com</a>
"Necessity is the mother of invention."
</pre>
</body>
</html>