<div dir="ltr"><div class="gmail_quote">On Wed, May 4, 2011 at 6:00 PM, Alon Levy <span dir="ltr"><<a href="mailto:alevy@redhat.com">alevy@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div></div><div class="h5">On Wed, May 04, 2011 at 05:10:31PM +0400, Emre Erenoglu wrote:<br>
> On Wed, May 4, 2011 at 2:12 PM, Alon Levy <<a href="mailto:alevy@redhat.com">alevy@redhat.com</a>> wrote:<br>
><br>
> > On Wed, May 04, 2011 at 01:45:39PM +0400, Emre Erenoglu wrote:<br>
> > > On Wed, Apr 27, 2011 at 1:16 AM, Emre Erenoglu <<a href="mailto:erenoglu@gmail.com">erenoglu@gmail.com</a>><br>
> > wrote:<br>
> > ><br>
> > > > Hi,<br>
> > > ><br>
> > > > I started to see frequent crashes with my guests running windows xp and<br>
> > > > windows server 2003 x86. The bsod appears on qxldd.dll. I can give<br>
> > further<br>
> > > > info if needed.<br>
> > > ><br>
> > > > The host is Linux x86_64, qemu 0.14, spice 0.8.1. Guest has qxl 0.6.1<br>
> > > > drivers loaded. I may revert back to 0.8.0 since it was not crashing.<br>
> > > > Nothing changed in the guests when I upgraded spice from 0.8.0 to<br>
> > 0.8.1.<br>
> > > ><br>
> > > ><br>
> > > Some updates on the original issue. I checked a lot and I found out that<br>
> > the<br>
> > > issue continued with any version of spice and guest qxl drivers.<br>
> > ><br>
> > > I finally digged down to the point that, the qemu comment line which<br>
> > states<br>
> > > " -global qxl-vga.vram_size=9xxxxxx " parameter is the problem. When<br>
> > the<br>
> > > guest is started with 9 MB of video memory given as comment line<br>
> > parameter<br>
> > > to qemu, the guest qxldd driver crashes with BSOD.<br>
> ><br>
> > Why was it started with 9MB? anyway, good catch, we should add a check for<br>
> > this<br>
> > in the driver (and probably just refuse to load). Could you open a bug on<br>
> > this<br>
> > in <a href="http://bugzilla.freedesktop.org" target="_blank">bugzilla.freedesktop.org</a>?<br>
> ><br>
><br>
> This is added by libvirt (virt-manager) when launching qemu. Do we need to<br>
> file it against libvirt or against spice? I will post this to the libvirt<br>
> list also.<br>
><br>
> Btw, rather than refusing to load, I think we should just limit the possible<br>
> resolutions. I'm not sure if the resolutions are the issue though. The crash<br>
> was not happening immediately and it was working OK with that 9 MB memory.<br>
> When I launched outlook, or IE8, or just in the middle of an application, it<br>
> could crash and bsod.<br>
<br>
</div></div>But that number doesn't make any sense - the spice default is 64MB, we never tested<br>
with less then that. It is probably fixable like you say, but until that's fixed why<br>
not stick to the spice default?</blockquote><div><br></div><div>Well, this parameter is not configurable from the virt-manager UI and it configures 9 MB to the command line of qemu by libvirt (even latest 0.9.0) version. </div>
<div>When you add a 2nd VGA adapter, it adds 64 MB to that adapter correctly (-device qxl,id=video1,vram_size=67108864,bus=pci.0,addr=0x8)</div><div><br></div><div>I guess i need to file a bug report to libvirt too.</div>
<div><br></div><div>Emre</div><div><br></div></div>
</div>