On Sat, Nov 29, 2014 at 08:34:48PM -0600, Charles Ricketts wrote:
Christophe
The segfault was simply a configuration error. it was dynamically
linking the distribution-provided libspice-server.so.1.8.0 rather than
the newly compiled libspice-server.so.1.9.0 due to the 1.8.0 version
having a
I'm pretty sure that is actually the case. I know that I got a compilation
error at first on Ubuntu because I had forgotten to install the development
headers from the git sources. Compiling against the 1.8.0 headers in the
14.04 repositories gave me an error related to either
On Mon, Dec 01, 2014 at 04:33:49AM -0600, Charles Ricketts wrote:
I'm pretty sure that is actually the case. I know that I got a compilation
error at first on Ubuntu because I had forgotten to install the development
headers from the git sources. Compiling against the 1.8.0 headers in the
I just did a verification and the symbol was actually
VD_AGENT_MAX_CLIPBOARD, not that it matters all that much but perhaps
you'll know what this is and won't have to look it up and dig through git
or anything ;).
By the way, tarball sources were mentioned as being more manageable in
general. As
The actual commit that made this change is here:
http://cgit.freedesktop.org/spice/spice-protocol/commit/spice/vd_agent.h?id=5ff3fa7080bd08392fc011175657264d57dddcec.
It's about a year old and if I'm reading the tags correctly in the
.../spice/spice repository, 0.8.0 was released March 2012. So,
On 11/28/2014 07:00 AM, Christophe Fergeau wrote:
On Fri, Nov 28, 2014 at 12:03:59AM -0600, Charles Ricketts wrote:
Despite my problem with building within my VM environment, I went ahead
and attempted a Fedora LXC+Spice configuration. I'm happy to report it
was successful as well. The only
Hey,
On Thu, Nov 27, 2014 at 11:27:00PM -0600, Charles Ricketts wrote:
This simply adds the -f parameter to spice-vdagentd since
/tmp/xspice-uinput is a pipe and not a character devices and, therefore,
fake. Without the parameter, spice-vdagend (pretty sure it was
vdagentd) exits complaining
On Fri, Nov 28, 2014 at 12:03:59AM -0600, Charles Ricketts wrote:
Despite my problem with building within my VM environment, I went ahead
and attempted a Fedora LXC+Spice configuration. I'm happy to report it
was successful as well. The only change that had to be made was adding
the -f
On Wed, Nov 26, 2014 at 05:16:52PM -0600, Charles Ricketts wrote:
Yes, I had seen those options. That was part of why I was asking about the
ucds socket. I found now that the ucds socket is used to talk to multiple
agents. I have tried both setting each argument to specify the paths of
each
Well, I have Spice working perfectly fine in a Windows install. However,
seeing as that's not pertinent to the Linux side of things I went ahead
and installed Ubuntu 14.04 in Qemu and, as expected, everything worked.
I didn't bother with the git sources in this install, because I was 99%
sure it
On 11/27/2014 02:02 PM, Charles Ricketts wrote:
Well, I have Spice working perfectly fine in a Windows install. However,
seeing as that's not pertinent to the Linux side of things I went ahead
and installed Ubuntu 14.04 in Qemu and, as expected, everything worked.
I didn't bother with the git
Finally got it set up in an Ubuntu VM, but I get the same segfault error
sans-LXC. Just a note, in order to actually get it compiled within
Ubuntu I had to make a change to a Makefile:
spice/server/tests/Makefile: add -lm to LDFLAGS (looks like the LIBM
line below doesn't get used?)
(hand typed
Despite my problem with building within my VM environment, I went ahead
and attempted a Fedora LXC+Spice configuration. I'm happy to report it
was successful as well. The only change that had to be made was adding
the -f argument to the Xspice script to keep spice-vdagentd from
attempting ioctl
Yes, I had seen those options. That was part of why I was asking about the
ucds socket. I found now that the ucds socket is used to talk to multiple
agents. I have tried both setting each argument to specify the paths of
each piece (ucds socket, uinput, and virtio port) and letting Xspice set
them
Yes, I was hoping to see a difference because of the version bumps between
Fedora/Ubuntu package sources, but no such luck.
I don't think it's a packaging issue specifically since I didn't package
the build, just did a straight 'make install' instead (using /usr as the
path rather than
Hey,
On Mon, Nov 24, 2014 at 11:47:36PM -0600, Charles Ricketts wrote:
Using the Spice for Newbies (which doesn't really seem to fit its
title IMO) documentation I was able to answer some of my questions
regarding data flow. However, I'm not closer to solving my problem.
After building from
Hey,
I'm not really familiar with Xspice, and never tried what you are trying
to achieve, a few pointers though which you may already have found.
On Sat, Nov 22, 2014 at 06:30:46AM -0600, Charles Ricketts wrote:
I've been surfing and source diving and now I'm all wet! I just
discovered LXC a
Using the Spice for Newbies (which doesn't really seem to fit its
title IMO) documentation I was able to answer some of my questions
regarding data flow. However, I'm not closer to solving my problem.
After building from the git repositories I get the same results in a
Fedora LXC while an Ubuntu
I've been surfing and source diving and now I'm all wet! I just
discovered LXC a couple days ago after having been a Qemu fan for years.
I really like the idea behind it and it seems to be far better on
resources! However, I wanted to get the same kind of user experience out
of these LXC
19 matches
Mail list logo
