why dose the spice only support 64-bit system ? I can't use spice in ubuntu 11.04 (i386). <div class="gmail_quote">2011/6/17 <<a href="mailto:spice-devel-request@lists.freedesktop.org">spice-devel-request@lists.freedesktop.org</a>> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Send Spice-devel mailing list submissions to <a href="mailto:spice-devel@lists.freedesktop.org">spice-devel@lists.freedesktop.org</a> To subscribe or unsubscribe via the World Wide Web, visit <a href="http://lists.freedesktop.org/mailman/listinfo/spice-devel" target="_blank">http://lists.freedesktop.org/mailman/listinfo/spice-devel</a> or, via email, send a message with subject or body 'help' to <a href="mailto:spice-devel-request@lists.freedesktop.org">spice-devel-request@lists.freedesktop.org</a> You can reach the person managing the list at <a href="mailto:spice-devel-owner@lists.freedesktop.org">spice-devel-owner@lists.freedesktop.org</a> When replying, please edit your Subject line so it is more specific than "Re: Contents of Spice-devel digest..." Today's Topics: 1. Re: Windows QXL driver - low pixel depth, low resolution, laggard mouse (John A. Sullivan III) 2. Re: Adaptive video compression by default? (John A. Sullivan III) 3. Re: Using Windows 7 qxl (John A. Sullivan III) 4. Re: SPICE Fedora 15 guest X running at 100% (John A. Sullivan III) 5. Re: SPICE Fedora 15 guest X running at 100% (--[ UxBoD ]--) 6. Re: SPICE Fedora 15 guest X running at 100% (John A. Sullivan III) ---------------------------------------------------------------------- Message: 1 Date: Thu, 16 Jun 2011 15:47:17 -0400 From: "John A. Sullivan III" <<a href="mailto:jsullivan@opensourcedevel.com">jsullivan@opensourcedevel.com</a>> Subject: Re: [Spice-devel] Windows QXL driver - low pixel depth, low resolution, laggard mouse To: Alon Levy <<a href="mailto:alevy@redhat.com">alevy@redhat.com</a>> Cc: <a href="mailto:spice-devel@lists.freedesktop.org">spice-devel@lists.freedesktop.org</a> Message-ID: <<a href="mailto:1308253637.11030.19.camel@denise.theartistscloset.com">1308253637.11030.19.camel@denise.theartistscloset.com</a>> Content-Type: text/plain; charset="UTF-8" On Thu, 2011-06-16 at 12:22 -0400, John A. Sullivan III wrote: > On Thu, 2011-06-16 at 10:22 -0400, John A. Sullivan III wrote: > > On Thu, 2011-06-16 at 15:54 +0200, Alon Levy wrote: > > > On Thu, Jun 16, 2011 at 01:42:07AM -0400, John A. Sullivan III wrote: > > > > On Thu, 2011-06-16 at 01:34 +0200, Alon Levy wrote: > > > > > On Wed, Jun 15, 2011 at 09:35:57PM +0100, Damien Churchill wrote: > > > > > > On 15 June 2011 21:11, --[ UxBoD ]-- <<a href="mailto:uxbod@splatnix.net">uxbod@splatnix.net</a>> wrote: > > > > > > > ----- Original Message ----- > > > > > > >> Hello, all. We have recently jumped into SPICE with both hands and > > > > > > >> feet > > > > > > >> as we are intrigued with the possibilities. But, we've hit a few > > > > > > >> rocks > > > > > > >> along the way! > > > > > > >> > > > > > > >> The immediate problems with our two test Windows installations > > > > > > >> (Windows7 > > > > > > >> and Windows Server 2008 running as KVM guests in Fedora 15) using the > > > > > > >> QXL driver is that the pixel depth appears to be 4-bits, the only > > > > > > >> available resolutions are 640x480 and 800x600, and the mouse is > > > > > > >> unusably > > > > > > >> lagged. > > > > > <snip>> > > > > > > > > Alon (Redhat Dev) has a patch for QEMU which should hopefully fix the 4bpp issue but the binary and necessary libraries he sent me would not run successfully on our server. It was execute and then hang and eventually time out. Perhaps, as discussed, we could build from source though I wonder why that patch has not been fully committed yet? > > > > > > > -- > > > > > > > > > > > > Is the patch available to try anywhere? I'd like to give it a test and > > > > > > see what happens. > > > > > > > > > > attached. > > > > <snip> > > > > > > > > Argh!!! I recompiled the rpms from the srpms after applying the patch > > > > and thought for sure our woes would be ended! Alas, perhaps we have 8 > > > > bit color now and we still have a maximum resolution of 800x600 :( > > > > > > > > What next? > > > > > > > > I double checked the BUILD directory to confirm the patch was applied. > > > > > > > <snip>> > > > > > > Forgot to mention: to let the vm accept self signed certificates you need to: > > > bcdedit.exe -set TESTSIGNING ON > > > > > > (see <a href="http://spice-space.org/page/WinQXL" target="_blank">http://spice-space.org/page/WinQXL</a>, and the source is <a href="http://stackoverflow.com/questions/5698617/signing-x64-driver-with-test-certificate" target="_blank">http://stackoverflow.com/questions/5698617/signing-x64-driver-with-test-certificate</a>) > > > > > Strange, after doing this with the new drivers, there is an ! mark next > > to the driver and I'm falling back to the VGA drivers. I wonder if we > > mangled something in our original signing. I'm going to resign the > > drivers we compiled and try again - John > <snip> > Good news! It appears to be working. The only difference between what > Phil did and what I did was that I used the utilities provided with the > SDK and WinQual whereas Phil used the tools in the DDK. Whatever it is, > it is looking quite good. On to the W2K8 test now. Thanks very, very > much - John <snip> W2K8 is working fine. Now on to tweaking and finding out why the WIndows Agent keeps failing. Thanks for all the help - John ------------------------------ Message: 2 Date: Thu, 16 Jun 2011 16:37:57 -0400 From: "John A. Sullivan III" <<a href="mailto:jsullivan@opensourcedevel.com">jsullivan@opensourcedevel.com</a>> Subject: Re: [Spice-devel] Adaptive video compression by default? To: Marian Krcmarik <<a href="mailto:mkrcmari@redhat.com">mkrcmari@redhat.com</a>> Cc: <a href="mailto:spice-devel@lists.freedesktop.org">spice-devel@lists.freedesktop.org</a> Message-ID: <<a href="mailto:1308256677.11030.20.camel@denise.theartistscloset.com">1308256677.11030.20.camel@denise.theartistscloset.com</a>> Content-Type: text/plain; charset="UTF-8" On Thu, 2011-06-16 at 13:50 -0400, Marian Krcmarik wrote: > > <snip> So I am assuming our version of libvirt does not support > > those > > parameters and thus we are using defaults. What are the defaults? No > > great pressure for anyone to answer unless one knows it off the top of > > their head. We'll keep experimenting to find out. Thanks - John > > Please see man qemu. > Duh! Thanks for ending my brain cramp and reminding me I need to think qemu and not just SPICE - John ------------------------------ Message: 3 Date: Thu, 16 Jun 2011 16:46:04 -0400 From: "John A. Sullivan III" <<a href="mailto:jsullivan@opensourcedevel.com">jsullivan@opensourcedevel.com</a>> Subject: Re: [Spice-devel] Using Windows 7 qxl To: ??? <<a href="mailto:wangyongbo90@gmail.com">wangyongbo90@gmail.com</a>> Cc: <a href="mailto:spice-devel@lists.freedesktop.org">spice-devel@lists.freedesktop.org</a> Message-ID: <<a href="mailto:1308257164.11030.25.camel@denise.theartistscloset.com">1308257164.11030.25.camel@denise.theartistscloset.com</a>> Content-Type: text/plain; charset="UTF-8" On Fri, 2011-06-17 at 00:35 +0800, ??? wrote: > how to use qxl driver in windows 7 . win7 also choose zhe standar vga > driver itself . > > and say that is zhe best and newest. > <snip> I assume this is the question you are asking from the digest. We followed the instructions at <a href="http://spice-space.org/page/WinQXL" target="_blank">http://spice-space.org/page/WinQXL</a> The only part where we stumbled was signing the drivers. Here are our internal notes on what we did to make that work. There is probably an easier way but I am pretty Windows ignorant: Download and install the WinQual toolkit: <a href="https://winqual.microsoft.com/member/SubmissionWizard/controls/WinqualSubmissionTool.msi" target="_blank">https://winqual.microsoft.com/member/SubmissionWizard/controls/WinqualSubmissionTool.msi</a> This is to obtain Inf2Cat.exe Download and install the MS SDK: <a href="http://www.microsoft.com/downloads/en/details.aspx?FamilyID=6b6c21d2-2006-4afa-9702-529fa782d63b" target="_blank">http://www.microsoft.com/downloads/en/details.aspx?FamilyID=6b6c21d2-2006-4afa-9702-529fa782d63b</a> This is for Makecert.exe and signtool.exe Go to the SDK Bin directory and run: Makecert -r -pe -n "CN=TestCertForQXL" -ss "QXLTestCert" C:\qxldriver\qxlcert.cer Go to the WinQual directory and run: Inf2cat.exe /driver:C:\qxldriver\ /os:7_X64 Return to the SDK Bin directory and run: signtool sign /a /v /s "QXLTestCert" /n "TestCertForQXL" c:\qxldriver\<a href="http://qxl.cat" target="_blank">qxl.cat</a> signtool sign /a /v /s "QXLTestCert" /n "TestCertForQXL" c:\qxldriver\qxl.sys signtool sign /a /v /s "QXLTestCert" /n "TestCertForQXL" c:\qxldriver\qxldd.dll bcdedit.exe -set TESTSIGNING ON Go to the Device Manager, choose the QXL Video Driver and update it pointing specifically to the new, signed driver. This assumes we are updating. I suppose we would simply install the driver when prompted for new hardware if this was the first attempt. It appears we can simply copy the driver directory to W2K8 and install the same way. ------------------------------ Message: 4 Date: Thu, 16 Jun 2011 17:55:41 -0400 From: "John A. Sullivan III" <<a href="mailto:jsullivan@opensourcedevel.com">jsullivan@opensourcedevel.com</a>> Subject: Re: [Spice-devel] SPICE Fedora 15 guest X running at 100% To: Marian Krcmarik <<a href="mailto:mkrcmari@redhat.com">mkrcmari@redhat.com</a>> Cc: <a href="mailto:spice-devel@lists.freedesktop.org">spice-devel@lists.freedesktop.org</a> Message-ID: <<a href="mailto:1308261341.11030.32.camel@denise.theartistscloset.com">1308261341.11030.32.camel@denise.theartistscloset.com</a>> Content-Type: text/plain; charset="UTF-8" On Thu, 2011-06-16 at 11:26 -0400, Marian Krcmarik wrote: > > ----- Original Message ----- > > From: "John A. Sullivan III" <<a href="mailto:jsullivan@opensourcedevel.com">jsullivan@opensourcedevel.com</a>> > > To: "Alon Levy" <<a href="mailto:alevy@redhat.com">alevy@redhat.com</a>> > > Cc: <a href="mailto:spice-devel@lists.freedesktop.org">spice-devel@lists.freedesktop.org</a> > > Sent: Wednesday, June 15, 2011 11:54:17 PM > > Subject: Re: [Spice-devel] SPICE Fedora 15 guest X running at 100% > > On Thu, 2011-06-16 at 01:41 +0200, Alon Levy wrote: > > > On Wed, Jun 15, 2011 at 04:58:21PM -0400, John A. Sullivan III > > > wrote: > > > > On Wed, 2011-06-15 at 16:08 -0400, John A. Sullivan III wrote: > > > <snip>> > > > > I checked my Xorg.0.log file and noticed that I was getting > > > > persistent > > > > messages about cache failures and out of memory. It looks like the > > > > vram > > > > parameter was set to something like 9216. > > > > > > > > So I changed it to 256000. To my surprise, the SPICE client > > > > connected > > > > but I had no mouse and no keyboard. I stopped the VM and redefined > > > > it > > > > with 128000 and I now had keyboard and video but still had the > > > > same > > > > excessive X utilization - John > > > > > > hmm.. yes, this is a well known problem - I thought libvirt fixed > > > it. What > > > version of libvirt are you using? The default memory is 64MB btw. > > > > 0.8.8-4.fc15 Thanks - John > > Try newer libvirt. Changing attribute vram in element model (i.e. <model type='qxl' vram='65536' heads='1'/>) seems to have no impact on qemu instance when I use 0.8.8-4 libvirt. When I use libvirt-0.9.2-1 I can see that option -global qxl-vga.vram_size is passed to qemu. <snip> It has been an interesting afternoon working on this one. We dumped the libvirt configuration with domxml-to-native. The original configuration translates into: LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin QEMU_AUDIO_DRV=spice /usr/bin/qemu-kvm -S -M pc-0.14 -enable-kvm -m 2048 -smp 2,sockets=2,cores=1,threads=1 -name <a href="http://lindesk01.pacifera.com" target="_blank">lindesk01.pacifera.com</a> -uuid 6beff77b-efef-41ab-5e3f-0206c94a3e84 -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/lindesk01.pacifera.com.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=readline -rtc base=utc -boot c -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5 -drive file=/dev/mapper/ilindesk01,if=none,id=drive-virtio-disk0,boot=on,format=raw -device virtio-blk-pci,bus=pci.0,addr=0x6,drive=drive-virtio-disk0,id=virtio-disk0 -drive if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -netdev tap,script=/etc/qemu/br0/qemu-ifup,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=00:00:00:00:00:00 -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=5700,addr=0.0.0.0,disable-ticketing -vga qxl -device intel-hda,i d=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7 I then edited it by removing the -S, a couple of the early parameters like uuid and nodefconfig and added -global qxl-vga.vram_size=131072. The new command line was: QEMU_AUDIO_DRV=spice /usr/bin/qemu-kvm -M pc-0.14 -enable-kvm -m 2048 -smp 2,sockets=2,cores=1,threads=1 -name <a href="http://lindesk01.pacifera.com" target="_blank">lindesk01.pacifera.com</a> -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5 -drive file=/dev/mapper/ilindesk01,if=none,id=drive-virtio-disk0,boot=on,format=raw -device virtio-blk-pci,bus=pci.0,addr=0x6,drive=drive-virtio-disk0,id=virtio-disk0 -drive if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -netdev tap,script=/etc/qemu/br0/qemu-ifup,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=00:00:00:00:00:00 -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=5700,addr=0.0.0.0,disable-ticketing -vga qxl -global qxl-vga.vram_size=131072 -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7 The result was much better. Still slower than Windows it seemed and X still ran hot but not impossibly hot. I then wanted to see if the only difference was adding the vga.ram parameter so I added it to the old command line (and stripped the -S). Performance seemed somewhere in between. X was running a little hotter but it was still usable though slow. I then wondered if it was just KDE4 bloat, e.g., when I click on Klipper, I get a corrupted block of screen until it sorts out a second or two later. So I exited KDE4 and started twm. To my great surprise, X shot to 100%. I then rebooted into the earlier modified, better behaving command line and started twm. Lo and behold, 100% CPU on X again. I'm not sure what that means but I thought I'd pass it along. I'll let you know what else I find. Thanks - John ------------------------------ Message: 5 Date: Thu, 16 Jun 2011 23:00:17 +0100 (BST) From: "--[ UxBoD ]--" <<a href="mailto:uxbod@splatnix.net">uxbod@splatnix.net</a>> Subject: Re: [Spice-devel] SPICE Fedora 15 guest X running at 100% To: "John A. Sullivan III" <<a href="mailto:jsullivan@opensourcedevel.com">jsullivan@opensourcedevel.com</a>> Cc: <a href="mailto:spice-devel@lists.freedesktop.org">spice-devel@lists.freedesktop.org</a> Message-ID: <<a href="mailto:5232434d-2fab-471c-a4e8-023acbecc040@office.splatnix.net">5232434d-2fab-471c-a4e8-023acbecc040@office.splatnix.net</a>> Content-Type: text/plain; charset=utf-8 ----- Original Message ----- > On Thu, 2011-06-16 at 11:26 -0400, Marian Krcmarik wrote: > > > > ----- Original Message ----- > > > From: "John A. Sullivan III" <<a href="mailto:jsullivan@opensourcedevel.com">jsullivan@opensourcedevel.com</a>> > > > To: "Alon Levy" <<a href="mailto:alevy@redhat.com">alevy@redhat.com</a>> > > > Cc: <a href="mailto:spice-devel@lists.freedesktop.org">spice-devel@lists.freedesktop.org</a> > > > Sent: Wednesday, June 15, 2011 11:54:17 PM > > > Subject: Re: [Spice-devel] SPICE Fedora 15 guest X running at > > > 100% > > > On Thu, 2011-06-16 at 01:41 +0200, Alon Levy wrote: > > > > On Wed, Jun 15, 2011 at 04:58:21PM -0400, John A. Sullivan III > > > > wrote: > > > > > On Wed, 2011-06-15 at 16:08 -0400, John A. Sullivan III > > > > > wrote: > > > > <snip>> > > > > > I checked my Xorg.0.log file and noticed that I was getting > > > > > persistent > > > > > messages about cache failures and out of memory. It looks > > > > > like the > > > > > vram > > > > > parameter was set to something like 9216. > > > > > > > > > > So I changed it to 256000. To my surprise, the SPICE client > > > > > connected > > > > > but I had no mouse and no keyboard. I stopped the VM and > > > > > redefined > > > > > it > > > > > with 128000 and I now had keyboard and video but still had > > > > > the > > > > > same > > > > > excessive X utilization - John > > > > > > > > hmm.. yes, this is a well known problem - I thought libvirt > > > > fixed > > > > it. What > > > > version of libvirt are you using? The default memory is 64MB > > > > btw. > > > > > > 0.8.8-4.fc15 Thanks - John > > > > Try newer libvirt. Changing attribute vram in element model (i.e. > > <model type='qxl' vram='65536' heads='1'/>) seems to have no > > impact on qemu instance when I use 0.8.8-4 libvirt. When I use > > libvirt-0.9.2-1 I can see that option -global qxl-vga.vram_size is > > passed to qemu. > <snip> > It has been an interesting afternoon working on this one. We dumped > the > libvirt configuration with domxml-to-native. The original > configuration > translates into: > > LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin > QEMU_AUDIO_DRV=spice /usr/bin/qemu-kvm -S -M pc-0.14 -enable-kvm -m > 2048 > -smp 2,sockets=2,cores=1,threads=1 -name <a href="http://lindesk01.pacifera.com" target="_blank">lindesk01.pacifera.com</a> -uuid > 6beff77b-efef-41ab-5e3f-0206c94a3e84 -nodefconfig -nodefaults > -chardev > socket,id=charmonitor,path=/var/lib/libvirt/qemu/lindesk01.pacifera.com.monitor,server,nowait > -mon chardev=charmonitor,id=monitor,mode=readline -rtc base=utc > -boot c -device > virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5 -drive > file=/dev/mapper/ilindesk01,if=none,id=drive-virtio-disk0,boot=on,format=raw > -device > virtio-blk-pci,bus=pci.0,addr=0x6,drive=drive-virtio-disk0,id=virtio-disk0 > -drive if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw > -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 > -netdev tap,script=/etc/qemu/br0/qemu-ifup,id=hostnet0 -device > rtl8139,netdev=hostnet0,id=net0,mac=00:00:00:00:00:00 -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=5700,addr=0.0.0.0,disable-ticketing -vga qxl -device > intel-hda,i > d=sound0,bus=pci.0,addr=0x4 -device > hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device > virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7 > > I then edited it by removing the -S, a couple of the early parameters > like uuid and nodefconfig and added -global qxl-vga.vram_size=131072. > The new command line was: > > QEMU_AUDIO_DRV=spice /usr/bin/qemu-kvm -M pc-0.14 -enable-kvm -m 2048 > -smp 2,sockets=2,cores=1,threads=1 -name <a href="http://lindesk01.pacifera.com" target="_blank">lindesk01.pacifera.com</a> > -device > virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5 -drive > file=/dev/mapper/ilindesk01,if=none,id=drive-virtio-disk0,boot=on,format=raw > -device > virtio-blk-pci,bus=pci.0,addr=0x6,drive=drive-virtio-disk0,id=virtio-disk0 > -drive if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw > -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 > -netdev tap,script=/etc/qemu/br0/qemu-ifup,id=hostnet0 -device > rtl8139,netdev=hostnet0,id=net0,mac=00:00:00:00:00:00 -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=5700,addr=0.0.0.0,disable-ticketing -vga qxl -global > qxl-vga.vram_size=131072 -device > intel-hda,id=sound0,bus=pci.0,addr=0x4 -device > hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device > virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7 > > The result was much better. Still slower than Windows it seemed and > X > still ran hot but not impossibly hot. > > I then wanted to see if the only difference was adding the vga.ram > parameter so I added it to the old command line (and stripped the > -S). > Performance seemed somewhere in between. X was running a little > hotter > but it was still usable though slow. I then wondered if it was just > KDE4 bloat, e.g., when I click on Klipper, I get a corrupted block of > screen until it sorts out a second or two later. So I exited KDE4 > and > started twm. To my great surprise, X shot to 100%. > > I then rebooted into the earlier modified, better behaving command > line > and started twm. Lo and behold, 100% CPU on X again. > > I'm not sure what that means but I thought I'd pass it along. I'll > let > you know what else I find. Thanks - John > >From what I was told before it is due to the whole image being passed back through the X driver. -- Thanks, Phil ------------------------------ Message: 6 Date: Thu, 16 Jun 2011 18:16:33 -0400 From: "John A. Sullivan III" <<a href="mailto:jsullivan@opensourcedevel.com">jsullivan@opensourcedevel.com</a>> Subject: Re: [Spice-devel] SPICE Fedora 15 guest X running at 100% To: "--[ UxBoD ]--" <<a href="mailto:uxbod@splatnix.net">uxbod@splatnix.net</a>> Cc: <a href="mailto:spice-devel@lists.freedesktop.org">spice-devel@lists.freedesktop.org</a> Message-ID: <<a href="mailto:1308262593.11030.33.camel@denise.theartistscloset.com">1308262593.11030.33.camel@denise.theartistscloset.com</a>> Content-Type: text/plain; charset="UTF-8" On Thu, 2011-06-16 at 23:00 +0100, --[ UxBoD ]-- wrote: > ----- Original Message ----- > > On Thu, 2011-06-16 at 11:26 -0400, Marian Krcmarik wrote: > > > > > > ----- Original Message ----- > > > > From: "John A. Sullivan III" <<a href="mailto:jsullivan@opensourcedevel.com">jsullivan@opensourcedevel.com</a>> > > > > To: "Alon Levy" <<a href="mailto:alevy@redhat.com">alevy@redhat.com</a>> > > > > Cc: <a href="mailto:spice-devel@lists.freedesktop.org">spice-devel@lists.freedesktop.org</a> > > > > Sent: Wednesday, June 15, 2011 11:54:17 PM > > > > Subject: Re: [Spice-devel] SPICE Fedora 15 guest X running at > > > > 100% > > > > On Thu, 2011-06-16 at 01:41 +0200, Alon Levy wrote: > > > > > On Wed, Jun 15, 2011 at 04:58:21PM -0400, John A. Sullivan III > > > > > wrote: > > > > > > On Wed, 2011-06-15 at 16:08 -0400, John A. Sullivan III > > > > > > wrote: > > > > > <snip>> > > > > > > I checked my Xorg.0.log file and noticed that I was getting > > > > > > persistent > > > > > > messages about cache failures and out of memory. It looks > > > > > > like the > > > > > > vram > > > > > > parameter was set to something like 9216. > > > > > > > > > > > > So I changed it to 256000. To my surprise, the SPICE client > > > > > > connected > > > > > > but I had no mouse and no keyboard. I stopped the VM and > > > > > > redefined > > > > > > it > > > > > > with 128000 and I now had keyboard and video but still had > > > > > > the > > > > > > same > > > > > > excessive X utilization - John > > > > > > > > > > hmm.. yes, this is a well known problem - I thought libvirt > > > > > fixed > > > > > it. What > > > > > version of libvirt are you using? The default memory is 64MB > > > > > btw. > > > > > > > > 0.8.8-4.fc15 Thanks - John > > > > > > Try newer libvirt. Changing attribute vram in element model (i.e. > > > <model type='qxl' vram='65536' heads='1'/>) seems to have no > > > impact on qemu instance when I use 0.8.8-4 libvirt. When I use > > > libvirt-0.9.2-1 I can see that option -global qxl-vga.vram_size is > > > passed to qemu. > > <snip> > > It has been an interesting afternoon working on this one. We dumped > > the > > libvirt configuration with domxml-to-native. The original > > configuration > > translates into: > > > > LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin > > QEMU_AUDIO_DRV=spice /usr/bin/qemu-kvm -S -M pc-0.14 -enable-kvm -m > > 2048 > > -smp 2,sockets=2,cores=1,threads=1 -name <a href="http://lindesk01.pacifera.com" target="_blank">lindesk01.pacifera.com</a> -uuid > > 6beff77b-efef-41ab-5e3f-0206c94a3e84 -nodefconfig -nodefaults > > -chardev > > socket,id=charmonitor,path=/var/lib/libvirt/qemu/lindesk01.pacifera.com.monitor,server,nowait > > -mon chardev=charmonitor,id=monitor,mode=readline -rtc base=utc > > -boot c -device > > virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5 -drive > > file=/dev/mapper/ilindesk01,if=none,id=drive-virtio-disk0,boot=on,format=raw > > -device > > virtio-blk-pci,bus=pci.0,addr=0x6,drive=drive-virtio-disk0,id=virtio-disk0 > > -drive if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw > > -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 > > -netdev tap,script=/etc/qemu/br0/qemu-ifup,id=hostnet0 -device > > rtl8139,netdev=hostnet0,id=net0,mac=00:00:00:00:00:00 -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=5700,addr=0.0.0.0,disable-ticketing -vga qxl -device > > intel-hda,i > > d=sound0,bus=pci.0,addr=0x4 -device > > hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device > > virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7 > > > > I then edited it by removing the -S, a couple of the early parameters > > like uuid and nodefconfig and added -global qxl-vga.vram_size=131072. > > The new command line was: > > > > QEMU_AUDIO_DRV=spice /usr/bin/qemu-kvm -M pc-0.14 -enable-kvm -m 2048 > > -smp 2,sockets=2,cores=1,threads=1 -name <a href="http://lindesk01.pacifera.com" target="_blank">lindesk01.pacifera.com</a> > > -device > > virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5 -drive > > file=/dev/mapper/ilindesk01,if=none,id=drive-virtio-disk0,boot=on,format=raw > > -device > > virtio-blk-pci,bus=pci.0,addr=0x6,drive=drive-virtio-disk0,id=virtio-disk0 > > -drive if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw > > -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 > > -netdev tap,script=/etc/qemu/br0/qemu-ifup,id=hostnet0 -device > > rtl8139,netdev=hostnet0,id=net0,mac=00:00:00:00:00:00 -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=5700,addr=0.0.0.0,disable-ticketing -vga qxl -global > > qxl-vga.vram_size=131072 -device > > intel-hda,id=sound0,bus=pci.0,addr=0x4 -device > > hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device > > virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7 > > > > The result was much better. Still slower than Windows it seemed and > > X > > still ran hot but not impossibly hot. > > > > I then wanted to see if the only difference was adding the vga.ram > > parameter so I added it to the old command line (and stripped the > > -S). > > Performance seemed somewhere in between. X was running a little > > hotter > > but it was still usable though slow. I then wondered if it was just > > KDE4 bloat, e.g., when I click on Klipper, I get a corrupted block of > > screen until it sorts out a second or two later. So I exited KDE4 > > and > > started twm. To my great surprise, X shot to 100%. > > > > I then rebooted into the earlier modified, better behaving command > > line > > and started twm. Lo and behold, 100% CPU on X again. > > > > I'm not sure what that means but I thought I'd pass it along. I'll > > let > > you know what else I find. Thanks - John > > > > From what I was told before it is due to the whole image being passed back through the X driver. Yes but it is interesting that we were able to go from unusable to quite usable except for twm. And that, as reported, libvirt 0.8.8 is not passing the vram parameter. Thanks - John ------------------------------ _______________________________________________ Spice-devel mailing list <a href="mailto:Spice-devel@lists.freedesktop.org">Spice-devel@lists.freedesktop.org</a> <a href="http://lists.freedesktop.org/mailman/listinfo/spice-devel" target="_blank">http://lists.freedesktop.org/mailman/listinfo/spice-devel</a> End of Spice-devel Digest, Vol 17, Issue 25 ******************************************* </blockquote></div>