Hi, All!
Now we want to test our solution powered by spice-kvm/qemu-libvirt,
and we only want to deploy 1 VM for 1 PC host, so what's the best
practice to gain the optimized performance of them?
Referred to
http://www.linux-kvm.org/page/Tuning_KVM
We will configure the cpu/network/storage s
During my dynamic monitor support testing today, I hit the following assert
in red_worker.c:
"red_push_monitors_config: condition `monitors_config != NULL' failed"
This is caused by the following scenario:
1) Guest causes handle_dev_monitors_config_async() to be called
2) handle_dev_monitors_confi
Signed-off-by: Hans de Goede
---
src/vdagent-x11-randr.c | 55 +++--
src/vdagentd.c | 1 +
2 files changed, 40 insertions(+), 16 deletions(-)
diff --git a/src/vdagent-x11-randr.c b/src/vdagent-x11-randr.c
index 59dfe38..7745a6e 100644
--- a/s
Both the spice-widget code, as well as remote-viewer expect that
monitors[i]->id == i, but if ie only the qxl-0 and qxl-2 outputs are
enabled this is not true.
I've chosen to fix this by making this assumption true. This does mean
that the monitors array can now contain 0x0 sized (iow disabled) mo
Signed-off-by: Hans de Goede
---
gtk/channel-main.c | 20 ++--
1 file changed, 14 insertions(+), 6 deletions(-)
diff --git a/gtk/channel-main.c b/gtk/channel-main.c
index 653b989..720fcfa 100644
--- a/gtk/channel-main.c
+++ b/gtk/channel-main.c
@@ -939,11 +939,15 @@ gboolean spic
1) This does not buy us much, as red_marshall_monitors_config() also
removes 0x0 sized monitors and does a much better job at it
(also removing intermediate ones, not only tailing ones)
2) The code is wrong, as it allocs space for real_count heads, where
real_count always <= monitors_confi
Currently the agent expect a monitor config to be continuous. If the user has
3 monitors (3 spice display windows) open and tries to disable the 2nd one,
then instead of the 2nd one being closed, the 3th one ends up closed.
To be able to fix this we need to be able to send a sparse monitor config
This avoids having to screen out bad alu and planemasks;
we let the X driver take care of it.
Signed-off-by: Jeremy White
---
src/dfps.c | 23 ++-
1 file changed, 18 insertions(+), 5 deletions(-)
diff --git a/src/dfps.c b/src/dfps.c
index 3e74d65..e5a2273 100644
--- a/src/
This fixes issues with 1 bit images; some pixman implementations
did not support 1 bit images - the general fbFill implementation
takes care of it for us.
Signed-off-by: Jeremy White
---
src/dfps.c | 27 +++
1 file changed, 19 insertions(+), 8 deletions(-)
diff --git a
This renders all operations to a frame buffer,
and sends updates periodically.
Signed-off-by: Jeremy White
---
src/Makefile.am |1 +
src/dfps.c| 290 +
src/dfps.h| 42
src/qxl.h |5 +
src/qxl_driver
Signed-off-by: Jeremy White
---
src/qxl_driver.c | 48 +++-
1 file changed, 27 insertions(+), 21 deletions(-)
diff --git a/src/qxl_driver.c b/src/qxl_driver.c
index b01845c..72beb0f 100644
--- a/src/qxl_driver.c
+++ b/src/qxl_driver.c
@@ -1622,28 +16
Signed-off-by: Jeremy White
---
examples/spiceqxl.xorg.conf.example |7 +++
src/qxl.h |3 +++
src/qxl_driver.c| 10 ++
3 files changed, 20 insertions(+)
diff --git a/examples/spiceqxl.xorg.conf.example
b/examples/spiceqxl.xorg.
We never actually connected the host_image pixmap to
the primary screen, because we never operate on the bits
of the primary screen.
This causes problems if we wish to use traditional X
operations to modify the primary screen, as they will
fail and corrupt memory as they go.
Signed-off-by: Jeremy
This is a resend of patches I have sent previously.
I had been waiting for comments from Soren on this patch:
http://lists.freedesktop.org/archives/spice-devel/2012-September/010939.html
...and I was too cowardly to just commit without his review.
However, I am shaking off my cowardice. I have
Hi,
Just as a datapoint, I've seen a similar crash in guest-tools-0.2 on my
Windows 8 VM. I switched back to IDE from VIO disk and the crashing stopped.
Regards
Erik
On 01/10/2013 04:44 AM, Han Pilmeyer wrote:
>
> On 09/01/2013 10:46, Han Pilmeyer wrote:
>> Just to follow up on my earlier prob
On 01/10/2013 05:08 PM, Jean Lÿe9olein BEBEY wrote:
Hi Itamar,
I don't see this package spice-devel in the repository in fedora 17.
spice devel is the mailing list of spice group to reply...
Jean
*De :* Itamar Heim
Hi Jean,
We need some details for the c&p issue.
1. which Windows guest are you using?
2. is virtio serial driver installed?
3. is "RHEV Spice Agent" service installed & running (look also for
vdagent.exe & vdservice.exe in taskmgr)
4. anything interesting in %windir%\temp\vdservice.log & vdage
On 09/01/2013 10:46, Han Pilmeyer wrote:
Just to follow up on my earlier problems. I did try the RHEV 3.1 guest
drivers with F17, but those had the same problem. I then switched
laptops and installed F18 on the new laptop together with the
guest-tools-0.3 drivers in the same guest images. My c
Hi,
On 01/10/2013 02:03 AM, Marc-André Lureau wrote:
Hi
V3 of protocol patch looks good to me. It has working implementation
with latest patch for spice-gtk & vdagent from Dunrong. So we have 2
acks now, if nobody speaks tomorrow I will push it.
Not sure if you're counting me as one of those
19 matches
Mail list logo
