[Spice-devel] codec passthrough and guest ram surface allocation status
I'm interested in these two proposed features: http://spice-space.org/page/Features/CodecPassthrough http://spice-space.org/page/Features/GuestRamSurfaceAllocation I wanted to ask if anyone is working on them or planning to work on them at the moment, just in case the wiki is not up to date. Also since this has not been discussed for some time, I wanted to mention that I'm still looking for solutions to make the mouse pointer usable in the html5 client, any ideas welcome. Thanks, DC ___ Spice-devel mailing list Spice-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/spice-devel
Re: [Spice-devel] Higher (quadratical) resolution
Hi David, installing all updates for Fedora 18 didn't help, but enabling the Test Updates repository did help - so obviously this feature is still not officially released. Now the output of xrandr looks like this: Screen 0: minimum 320 x 200, current 2560 x 1600, maximum 8192 x 8192 qxl-0 connected 2560x1600+0+0 0mm x 0mm 2560x1600 60.0*+ 2560x1440 60.0 2048x1536 60.0 1920x1440 60.0 1920x1200 60.0 1920x1080 60.0 1600x1200 60.0 1680x1050 60.0 1400x1050 60.0 1600x900 60.0 1280x1024 60.0 1440x900 60.0 1280x960 60.0 1366x768 60.0 1360x768 60.0 1280x800 60.0 1152x870 60.0 1152x864 60.0 1280x768 60.0 1280x760 60.0 1280x720 60.0 1024x768 60.0 1024x600 60.0 960x64060.0 832x62460.0 800x60060.0 800x48060.0 640x48060.0 qxl-1 disconnected qxl-2 disconnected qxl-3 disconnected Now the highest resolution which the Displays tool offers is 2560x1600 Pixels. Therefore I tried to change the resolution with the comand: xrandr --output qxl-0 --mode 2048x2048 But the error message: xrandr: cannot find mode 2048x2048 was displayed. Any idea how I could achieve this? (I would prefer a static xorg.conf but don't know the configuration options) Best regards and thanks in advance Dennnis Von: David Jaša [dj...@redhat.com] Gesendet: Montag, 11. Februar 2013 16:23 An: Dennis Böck Cc: spice-devel@lists.freedesktop.org Betreff: Re: [Spice-devel] Higher (quadratical) resolution Hi, Dennis Böck píše v Po 11. 02. 2013 v 15:04 +: Hi David, I am using Fedora 18 as guest and host system. The output of xrandr is the following: Screen 0: minimum 640 x 480, current 1024 x 768, maximum 1920 x 1200 default connected 1024x768+0+0 0mm x 0mm 1920x1200 60.0 1920x1080 60.0 1600x1200 75.0 70.0 65.0 60.0 1680x1050 60.0 1400x1050 75.0 60.0 1600x900 60.0 1280x1024 75.0 60.0 1440x900 60.0 1280x960 60.0 1366x768 60.0 1360x768 60.0 1280x800 60.0 1152x870 60.0 1152x864 75.0 1280x768 60.0 1280x760 60.0 1280x720 60.0 1024x768 75.0*70.0 60.0 960x64060.0 1024x600 60.0 832x62475.0 800x60075.0 72.0 60.0 56.0 800x48060.0 640x48075.0 73.0 60.0 The highest resolution which I can chose from the tool Display Settings ist 1920 x 1200. So what do I have to change in order to get a resolution of 2048x2048 pixels? 1) make sure that you use qxl driver and you have spice-vdagentd and spice-vdagent running (at least two processes of the latter - one for *DM, one for desktop environment) 2) go fullscreen (or generally, resize the window) Spice in F18 should support arbitrary resolution so if you don't resolution in the list, you can still resize the client, client then sends new resolution to the agent and agent sets it. If it doesn't work for you, the necessary versions may be in updates or still in updates-testing. David Best regards Dennis Von: David Jaša [dj...@redhat.com] Gesendet: Montag, 11. Februar 2013 15:44 An: Dennis Böck Cc: spice-devel@lists.freedesktop.org Betreff: Re: [Spice-devel] Higher (quadratical) resolution Hi Dennis, that limit was increased to much higher value few years ago and there should be no issue with 2048x2048 screens. David Dennis Böck píše v Po 11. 02. 2013 v 11:24 +: Dear Spice-Mailing-List, since we use quadratically monitors with 2048x2048 pixels and we need to work in full-screen mode, I would like to use such a resolution with Spice in my KVM-VM. According to my information the corresponding KVM graphic card qxl only supports up to 1920 x 1200 pixels. Is there any way to increase this limit? Best regards and thanks in advance Dennis ___ Spice-devel mailing list Spice-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/spice-devel -- David Jaša, RHCE SPICE QE based in Brno GPG Key: 22C33E24 Fingerprint: 513A 060B D1B4 2A72 7F0D 0278 B125 CD00 22C3 3E24 ___ Spice-devel mailing list Spice-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/spice-devel -- David Jaša, RHCE SPICE QE based in Brno GPG Key: 22C33E24 Fingerprint: 513A 060B D1B4 2A72 7F0D 0278 B125 CD00 22C3 3E24 ___ Spice-devel mailing list Spice-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/spice-devel
[Spice-devel] Rotate graphical output of vm
Dear Spice-list, I would like to rotate the graphical output of a vm. I tried it with a Fedora 18 and OpenSuse 12.2 guest and: xrandr -o left, but I got the error message: X Error of failed request: BadMatch (invalid parameter attributes) Major opcode of failed request: 139 (RANDR) Minor opcode of failed request: 2 (RRsetScreenConfig) Serial number of failed request: 12 Current serial number in output stream: 14 Also my try to change the xorg.conf in SLES11SP1 did not change the rotation, because the Xserver log says: Option Rotate is not used The only vga option which worked partly is: cirrus. But with cirrus the graphical output is not displayed correctly in my vnc-viewer. I tried it with a SLES11SP2 host (Kernel 3.0.13-0.27) and a Fedora17 host (Kernel 3.7.6 and repository Test Updates). Any ideas? Best regards and thanks in advance Dennis ___ Spice-devel mailing list Spice-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/spice-devel
Re: [Spice-devel] Fixing the spice-gtk version scheme mess
On Wed, Jan 23, 2013 at 01:48:32PM +0100, Marc-André Lureau wrote: The fedora package was updated in fedora/koji for the reporter to check if it solves his problem, before doing the release which was planned to come quickly after, as it did. There was only a few days between the two releases, and it was Christmas break. After this thread and the spice-gtk 0.17 release, I'm _very_ surprised to see some patches on top of the F18 and rawhide package, including (at least) one patch which is mandatory to build spice-gtk with newer gtk+ versions. jhbuild is one downstream user which is impacted by this issue. I haven't even seen this patch being sent to the mailing list, and I can't find it in the archive. If this was pushed without being sent to the list, this makes it even harder for anyone to be aware of the issue, and that it's fixed in git. Last but not least, your patches to the Fedora package are buggy: $ pkg-config --modversion spice-client-gtk-2.0 0.17-dirty Can we get a 0.17.1 release to fix all of this? Thanks, Christophe pgpC7XW5zERS4.pgp Description: PGP signature ___ Spice-devel mailing list Spice-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/spice-devel
Re: [Spice-devel] Fixing the spice-gtk version scheme mess
On Wed, Feb 13, 2013 at 4:19 PM, Christophe Fergeau cferg...@redhat.com wrote: After this thread and the spice-gtk 0.17 release, I'm _very_ surprised to see some patches on top of the F18 and rawhide package, including (at least) one patch which is mandatory to build spice-gtk with newer gtk+ versions. jhbuild is one downstream user which is impacted by this issue. We don't go through review for trivial build fixes in spice-gtk. Also, those fixes are only necessary for unstable gtk+ releases afaik. Last but not least, your patches to the Fedora package are buggy: $ pkg-config --modversion spice-client-gtk-2.0 0.17-dirty It's on purpose, since it's not official version. Is that a problem? Can we get a 0.17.1 release to fix all of this? I'll do a new release, since other people depends on unstable gtk+ release. -- Marc-André Lureau ___ Spice-devel mailing list Spice-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/spice-devel
[Spice-devel] spice-gtk release v0.18
Hello! The Spice team is pleased to release a new spice-gtk version: - Build fix with Gtk+ unstable. - MinGW build fixes with old headers - Fix USB coldplug race - Fixes rhbz#908057 http://spice-space.org/download/gtk/spice-gtk-0.18.tar.bz2 md5sum: bcd73f857d137bca8e24380e8f7977d2 sha1sum: 8654f02bc7308ce87a718092375157278c5608ba cheers -- Marc-André Lureau ___ Spice-devel mailing list Spice-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/spice-devel
Re: [Spice-devel] Fixing the spice-gtk version scheme mess
On Wed, Feb 13, 2013 at 4:44 PM, Christophe Fergeau cferg...@redhat.com wrote: In my opinion, we should follow what libvirt does here, send the patch to the list with a note indicating that it has already been pushed to fix the build. This is very helpful to let others know about such fixes. People have been reporting this issue on IRC for a few days now, and it was only when someone said git was building fine that I noticed this fix and could help them. I would probably have remembered about it if I had seen the patch on the ML.. It should be first contributor reaction (or user who want to help) to try a git build. Not searching through a general ML treating various problems and projects related to Spice, at various point in time. I follow spice-commits list. I invite others who needs your approach to do that too. -- Marc-André Lureau ___ Spice-devel mailing list Spice-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/spice-devel
Re: [Spice-devel] Fixing the spice-gtk version scheme mess
On Wed, Feb 13, 2013 at 04:49:53PM +0100, Marc-André Lureau wrote: On Wed, Feb 13, 2013 at 4:44 PM, Christophe Fergeau cferg...@redhat.com wrote: In my opinion, we should follow what libvirt does here, send the patch to the list with a note indicating that it has already been pushed to fix the build. This is very helpful to let others know about such fixes. People have been reporting this issue on IRC for a few days now, and it was only when someone said git was building fine that I noticed this fix and could help them. I would probably have remembered about it if I had seen the patch on the ML.. It should be first contributor reaction (or user who want to help) to try a git build. Not searching through a general ML treating various problems and projects related to Spice, at various point in time. In this case, their initial reaction was to ask on IRC, which makes sense to me. And I couldn't help them as I didn't really have time to update gtk+, see if I could reproduce, ... I follow spice-commits list. I invite others who needs your approach to do that too. Well, spice-commits is not that convenient as you can sometimes get multiple commits in the same email. Moreover, 95% of the mails there are redundant with patches from the mailing list, so it's easy to miss the one commit that you did not see on the mailing list. So it would be very nice if you could run a quick git send-email --annotate after pushing such commits... Christophe pgpUQE4BEOg0V.pgp Description: PGP signature ___ Spice-devel mailing list Spice-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/spice-devel
Re: [Spice-devel] Fixing the spice-gtk version scheme mess
On Wed, Feb 13, 2013 at 04:44:10PM +0100, Christophe Fergeau wrote: On Wed, Feb 13, 2013 at 04:23:12PM +0100, Marc-André Lureau wrote: On Wed, Feb 13, 2013 at 4:19 PM, Christophe Fergeau cferg...@redhat.com wrote: After this thread and the spice-gtk 0.17 release, I'm _very_ surprised to see some patches on top of the F18 and rawhide package, including (at least) one patch which is mandatory to build spice-gtk with newer gtk+ versions. jhbuild is one downstream user which is impacted by this issue. We don't go through review for trivial build fixes in spice-gtk. In my opinion, we should follow what libvirt does here, send the patch to the list with a note indicating that it has already been pushed to fix the build. FYI libvirt Fedora packages no longer carry patches as a general rule. Instead for libvirt we aim to provide stable release branches with trivial fixes applied. This ensures that the stable packages are easily available to everyone, not merely Fedora users. I'd encourage the same approach for spice too really. Daniel. -- |: http://berrange.com -o-http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| ___ Spice-devel mailing list Spice-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/spice-devel
Re: [Spice-devel] Fixing the spice-gtk version scheme mess
On Wed, Feb 13, 2013 at 05:17:25PM +0100, Marc-André Lureau wrote: Hi On Wed, Feb 13, 2013 at 5:14 PM, Daniel P. Berrange berra...@redhat.com wrote: FYI libvirt Fedora packages no longer carry patches as a general rule. Instead for libvirt we aim to provide stable release branches with trivial fixes applied. This ensures that the stable packages are easily available to everyone, not merely Fedora users. I'd encourage the same approach for spice too really. That's what I discussed earlier too, not maintaining patches in fedora but in upstream stable branch, so I agree. How often do you do a stable release then? I would just call that a stable snapshot, hmm whatever.. There is no fixed time frame. They are simply done whenever there is a critical mass of fixes to get out to users Daniel -- |: http://berrange.com -o-http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| ___ Spice-devel mailing list Spice-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/spice-devel
