This fixes a bug with x-spice where you could not specify
a default mode in an xorg.conf modeline that was greater
than 1024x768. This also eliminates (and partially
reverts) patch c1b537fc.
It may also fix bug 894421, where gnome modes flicker
and work poorly.
Signed-off-by: Jeremy White
---
> BTW reading patch 1 again, I wonder what exactly it tries to solve, since
> currently when using spice with qemu (no experience with x-spice) you can
> already set modes > 1024x768 without problems.
Alright, I've spent my day relearning this code, and feel I have a
better grasp.
The issue is pr
Since we're talking about spice crashes:
On windows 8 bit64 running spicy.exe 0.15.1-845c-dirty, compiled with
--disable-smartcard --without-sasl --without-audio
Crashing at the beginning of every 5-8 runs but sometimes 2-3 times in a
row. Don't really know how to check how. Few weeks have passed
Aha! I built a qxl_driver from git tip, put that on my fc18 guest, and
now I see 4 displays in my drop down list.
(I had mistakenly presumed that by up to date fc18 guest, you wanted
those stock qxl packages, but the fc18 qxl driver is fairly old).
Cheers,
Jeremy
___
>> I currently have qemu-1.3 + spice server 0.12-2, with spice client gtk
>> and virt-viewer from git tip of yesterday. I am running a fully up to
>> date fc18 guest.
>
> Hmm that should be new enough I think...
>
>> I launch qemu from the command line, adding the -global qxl-vga.revision
>> fla
Hi,
On 01/23/2013 06:27 PM, Jeremy White wrote:
You not getting this to work is not your fault, but ours :) It is a
pretty new feature lacking documentation.
First of all you will need Fedora-18 (preferably fully up2date with
all updates from updates-testing) as both host and guest!
I have t
> You not getting this to work is not your fault, but ours :) It is a
> pretty new feature lacking documentation.
>
> First of all you will need Fedora-18 (preferably fully up2date with
> all updates from updates-testing) as both host and guest!
I have thus far resisted the need to build an enti
> Hi,
> we have been posting all our results on xen-devel too, but we haven't
> made any progress by now. We are trying to narrow down the problem as
> much as possible so that we can ask the right question at the right
> place, any advice is welcome (eg. what tests can be done).
>
> Changing the
Hi,
we have been posting all our results on xen-devel too, but we haven't
made any progress by now. We are trying to narrow down the problem as
much as possible so that we can ask the right question at the right
place, any advice is welcome (eg. what tests can be done).
Changing the debug level of
Hi,
On 01/23/2013 03:18 PM, Christophe Fergeau wrote:
On Wed, Jan 23, 2013 at 01:48:32PM +0100, Marc-André Lureau wrote:
On Wed, Jan 23, 2013 at 10:29 AM, Christophe Fergeau
wrote:
But I agree with Hans that we currently are a bad upstream to work with
from a distro point of view, and that we
On Wed, Jan 23, 2013 at 01:10:15PM +0100, Han Pilmeyer wrote:
> On 23/01/2013 11:01, Christophe Fergeau wrote:
> >Hrm, this means we'll need yet another update for
> >https://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/bin/ :(
> >
> >>>I'm afraid so Christophe.
> >For wha
On Wed, Jan 23, 2013 at 01:48:32PM +0100, Marc-André Lureau wrote:
> On Wed, Jan 23, 2013 at 10:29 AM, Christophe Fergeau
> wrote:
> > But I agree with Hans that we currently are a bad upstream to work with
> > from a distro point of view, and that we need to improve on that...
>
> The fedora pac
Hello Alon.
Thanks for your help.
This is what I get with the qemu debugging options:
qxl/guest-0: 1120951392537: qxldd: __PutBytesAlign
qxl/guest-0: 1120951398601: qxldd: __PutBytesAlign: done
qxl/guest-0: 1120951404632: qxldd: __PutBytesAlign
qxl/guest-0: 1120951410705: qxldd: __PutBytesAlign:
On Wed, Jan 23, 2013 at 10:29 AM, Christophe Fergeau
wrote:
> But I agree with Hans that we currently are a bad upstream to work with
> from a distro point of view, and that we need to improve on that...
The fedora package was updated in fedora/koji for the reporter to
check if it solves his
prob
On 23/01/2013 11:01, Christophe Fergeau wrote:
> >Hrm, this means we'll need yet another update for
> >https://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/bin/ :(
> >
>I'm afraid so Christophe.
For what it's worth, Cole Robinson was kind enough to respin a virtio-win
ISO with updat
On Wed, Jan 23, 2013 at 7:53 AM, Christophe Fergeau wrote:
> Hey,
>
> On Sat, Jan 12, 2013 at 07:02:00PM -0200, Fabiano Fidêncio wrote:
> > spice and spice-common should be consistent about the libraries checking.
>
> Ideally, only spice-common would have a smartcard flag, and it would
> default t
On 01/21/2013 04:16 PM, Yonit Halperin wrote:
Hi,
On 01/17/2013 09:26 AM, Uri Lublin wrote:
Resolves: rhbz#883578
Call qxl_allocate_monitors_config upon memory-remap such
that qxl->monitors_config points to the start of
monitors_config segment in qxl RAM memory.
Currently after memory remap, i
On Tue, Jan 22, 2013 at 02:24:28PM +0100, Han Pilmeyer wrote:
>
> On 22/01/2013 13:50, Christophe Fergeau wrote:
> >On Tue, Jan 22, 2013 at 01:36:33PM +0100, Han Pilmeyer wrote:
> >>Gal was kind enough to take a look at the crash dump and determined
> >>I was running into an issue that was already
Hey,
On Sat, Jan 12, 2013 at 07:02:00PM -0200, Fabiano Fidêncio wrote:
> spice and spice-common should be consistent about the libraries checking.
Ideally, only spice-common would have a smartcard flag, and it would
default to autodetection of whether to enable smartcard or not depending on
libca
Hi,
On Tue, Jan 01, 2013 at 11:37:26AM +0100, Hans de Goede wrote:
> Marc-André just did a new Fedora build fixing the
> SSL issues we we're having with 0.15 (thanks for that),
> but this is based on a git snapshot, and because of
> the way our buildsys code generates git snapshot
> tarbals is num
20 matches
Mail list logo
