Ok, and with the latest drivers: Mini061811-01.dmp 6/18/2011 9:41:49 PM PAGE_FAULT_IN_NONPAGED_AREA 0x10000050 0xe1256884 0x00000000 0xbf013dda 0x00000001 qxldd.dll qxldd.dll+1dda Red Hat QXL Display Driver Spice Red Hat Inc. 1.4.1.1 built by: WinDDK 32-bit qxldd.dll+1dda win32k.sys+196a9 win32k.sys+95a8 win32k.sys+9658 C:\WINDOWS\Minidump\Mini061811-01.dmp 2 15 2600 106,496
After scrolling a website for about 60 seconds. G On Sat, Jun 18, 2011 at 9:21 PM, lucas.g...@gmail.com <lucas.g...@gmail.com>wrote: > Sorry, it just built... Failed in checked environment and succeeded in free > build environment... > > G > > > On Sat, Jun 18, 2011 at 9:19 PM, lucas.g...@gmail.com < > lucas.g...@gmail.com> wrote: > >> I've just tried to build the drivers using the instructions given at: >> >> http://spice-space.org/page/WinQXL >> >> There are some contradictory instructions there, so it could be my setup. >> I've installed the winddk, and set the SPICE_COMMON_DIR to >> c:\common\spice-protocol and also tried c:\common (with file not found >> errors in that case). >> >> >> Results: >> C:\common\qxl>build -cZg >> BUILD: Compile and Link for x86 >> BUILD: Start time: Sat Jun 18 21:17:15 2011 >> BUILD: Examining c:\common\qxl directory tree for files to compile. >> c:\common\qxl\display Auto-cleaning queue for 'root:x86chk' (6 of 8 >> file(s) removed) >> Invalidating OACR warning log for 'root:x86chk' >> 1>BUILD: Compiling and Linking c:\common\qxl\display directory >> 2>BUILD: Compiling and Linking c:\common\qxl\miniport directory >> Configuring OACR for 'root:x86chk' - <OACR on> >> _NT_TARGET_VERSION SET TO WINXP >> _NT_TARGET_VERSION SET TO WINXP >> 2>Compiling resources - miniport\qxl.rc >> 1>Compiling resources - display\driver.rc >> 2>Compiling - miniport\qxl.c >> 1>Compiling - display\driver.c >> 2>Compiling - miniport\wdmhelper.c >> 2>Compiling - miniport\generating code... >> 2>Linking Executable - miniport\miniport\objchk_wxp_x86\i386\qxl.sys >> 1>errors in directory c:\common\qxl\display >> 1>c:\common\qxl\display\driver.c(1079) : error C2065: 'LINE_CAP_ROUND' : >> undeclared identifier >> 1>c:\common\qxl\display\driver.c(1079) : error C2065: 'LINE_CAP_SQUARE' : >> undeclared identifier >> 1>c:\common\qxl\display\driver.c(1079) : error C2065: 'LINE_CAP_BUTT' : >> undeclared identifier >> 1>c:\common\qxl\display\driver.c(1079) : error C2065: 'LINE_JOIN_ROUND' : >> undeclared identifier >> 1>c:\common\qxl\display\driver.c(1079) : error C2065: 'LINE_JOIN_BEVEL' : >> undeclared identifier >> 1>c:\common\qxl\display\driver.c(1079) : error C2065: 'LINE_JOIN_MITER' : >> undeclared identifier >> 1>c:\common\qxl\display\driver.c(1092) : error C2065: 'LINE_STYLED' : >> undeclared identifier >> 1>c:\common\qxl\display\driver.c(1093) : error C2065: >> 'LINE_START_WITH_GAP' : undeclared identifier >> 1>Compiling - display\rop.c >> 1>Compiling - display\res.c >> 1>c:\common\qxl\display\res.c(648) : error C2065: 'area' : undeclared >> identifier >> 1>c:\common\qxl\display\res.c(2162) : error C2039: 'num_bits_pages' : is >> not a member of 'PDev' >> 1>c:\common\qxl\display\res.c(2328) : error C2039: 'num_bits_pages' : is >> not a member of 'PDev' >> 1>Compiling - display\text.c >> 1>Compiling - display\pointer.c >> 1>Compiling - display\brush.c >> 1>Compiling - display\mspace.c >> 1>Compiling - display\quic.c >> 1>c:\common\qxl\display\quic.c(73) : error C2220: warning treated as error >> - no 'object' file generated >> 1>Compiling - display\surface.c >> 1>Compiling - display\generating code... >> 1>Linking Executable - display\display\objchk_wxp_x86\i386\qxldd.dll >> 1>link : error LNK1181: cannot open input file >> 'c:\common\qxl\display\objchk_wxp_x86\i386\driver.obj' >> BUILD: Finish time: Sat Jun 18 21:17:18 2011 >> BUILD: Done >> 17 files compiled - 1 Warning - 12 Errors >> 2 executables built - 1 Error >> On Wed, Jun 15, 2011 at 7:58 AM, lucas.g...@gmail.com < >> lucas.g...@gmail.com> wrote: >> >>> I'll have the spare time on the weekend to get back to both of you. >>> >>> I'll give compiling a new set of drivers a try then as well. >>> >>> Here's the bug report I appended to previously if that's of any help: >>> >>> https://bugs.freedesktop.org/show_bug.cgi?id=30835 >>> >>> Gary Lucas >>> >>> >>> On Wed, Jun 15, 2011 at 6:58 AM, Alon Levy <al...@redhat.com> wrote: >>> >>>> On Tue, Jun 14, 2011 at 09:52:20PM -0700, lucas.g...@gmail.com wrote: >>>> > I've been attempting to use KVM / Spice and QXL to handle my >>>> virtualization >>>> > environment. >>>> > >>>> > I've noticed a couple of issues, and I haven't been able to track down >>>> other >>>> > people having the same issues. >>>> > >>>> > This strikes me as odd as I don't think my setup is particularly >>>> unique. >>>> > >>>> > I'm running Fedora 15 with current versions of everything. (libvirtd >>>> 0.8.8) >>>> > >>>> > The issues I've encountered are: >>>> > Windows Guests: (WinXp - Win 7) >>>> > Blue screen of death after doing something graphically intensive, I >>>> did find >>>> > a mention of this in bugzilla, but only one mention... >>>> > >>>> > Linux guests (FC14 primarily but has occurred in other guests) >>>> > Random logouts that bounce me back to the KDE login screen. It also >>>> resets >>>> > my resolution to something quite low. >>>> > >>>> > If anyone is interested I can dig up memory dumps from the Windows XP >>>> > BSOD... I was unable to find anything useful regarding the FC14 >>>> crashes but >>>> > I would be totally willing to attempt to reproduce them if it would >>>> help. >>>> > >>>> >>>> Thanks for the feedback. I would be interested in trying to reproduce >>>> with newer >>>> drivers, unfortunately I don't have a driver+pdb to give you right now, >>>> so unless >>>> you can compile yourself this will have to wait a little (at least for >>>> me). >>>> >>>> > When these occur I am always running Spice + QXL... Windows QXL >>>> client is >>>> > 0.6.1, I just tried with 0.6.0, I didn't get a meaningful memory dump >>>> but >>>> > the process did eventually crash after about 15 minutes of scrolling >>>> > a Firefox browser up and down and watching flash videos... >>>> > >>>> > I did manually change the ram setting in the XML file and here is the >>>> qemu >>>> > command line that launched the WinXP machine: >>>> > >>>> > qemu 3859 53.1 8.8 2696152 2196932 ? Sl 20:27 0:51 >>>> > /usr/bin/qemu-kvm -S -M pc-0.14 -enable-kvm -m 2048 -smp >>>> > 2,sockets=2,cores=1,threads=1 -name WinXP -uuid >>>> > c35128d3-1c56-2cf9-a6db-3f61a64a964a -nodefconfig -nodefaults -chardev >>>> > >>>> socket,id=charmonitor,path=/var/lib/libvirt/qemu/WinXP.monitor,server,nowait >>>> > -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime >>>> -boot c >>>> > -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5 -drive >>>> > >>>> file=/var/lib/libvirt/images/WinXP.img,if=none,id=drive-virtio-disk0,boot=on,format=qcow2 >>>> > -device >>>> > >>>> virtio-blk-pci,bus=pci.0,addr=0x6,drive=drive-virtio-disk0,id=virtio-disk0 >>>> > -netdev tap,fd=21,id=hostnet0 -device >>>> > >>>> virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:d1:11:3e,bus=pci.0,addr=0x3 >>>> > -chardev pty,id=charserial0 -device >>>> > isa-serial,chardev=charserial0,id=serial0 -chardev >>>> > spicevmc,id=charchannel0,name=vdagent -device >>>> > >>>> virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0 >>>> > -usb -device usb-tablet,id=input0 -spice >>>> > port=5900,addr=127.0.0.1,disable-ticketing -vga qxl -device >>>> > ES1370,id=sound0,bus=pci.0,addr=0x4 -device >>>> > virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7 >>>> > >>>> > >>>> > Thank you. >>>> > >>>> > Gary C. Lucas >>>> >>>> > _______________________________________________ >>>> > Spice-devel mailing list >>>> > Spice-devel@lists.freedesktop.org >>>> > http://lists.freedesktop.org/mailman/listinfo/spice-devel >>>> >>>> >>> >> >
_______________________________________________ Spice-devel mailing list Spice-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/spice-devel
