From: Eric Houby <ehouby@yahoo.com>
To: Sander Eikelenboom <linux@eikelenboom.it>
Cc: xen@lists.fedoraproject.org,
Fabio Fantoni <fabio.fantoni@m2r.biz>,
xen-devel@lists.xen.org
Subject: Re: [TestDay] F20 Xen 4.4 RC3 Spice support
Date: Wed, 05 Feb 2014 17:17:44 -0700 [thread overview]
Message-ID: <1391645864.2751.9.camel@astar.houby.net> (raw)
In-Reply-To: <15510565929.20140205090647@eikelenboom.it>
On Wed, 2014-02-05 at 09:06 +0100, Sander Eikelenboom wrote:
> Wednesday, February 5, 2014, 5:00:08 AM, you wrote:
>
> > On Tue, 2014-02-04 at 17:01 +0100, Fabio Fantoni wrote:
> >> Il 04/02/2014 16:41, Eric Houby ha scritto:
> >> > Xen list,
> >> >
> >> > I am trying to boot a F20 guest and connect using Spice but have run
> >> > into an issue.
> >> >
> >> > My VM config file includes:
> >> > spice = 1
> >> > spicehost='0.0.0.0'
> >> > spiceport=6001
> >> > spicedisable_ticketing=1
> >> >
> >> >
> >> > Is Spice supported with qemu-xen-traditional?
> >>
> >> No, only with upstream qemu and if compile xen and qemu from source you
> >> also enable spice support on qemu build, for example on my xen build
> >> tests I add:
> >>
> >> tools/Makefile
> >> @@ -201,6 +201,8 @@ subdir-all-qemu-xen-dir: qemu-xen-dir-find
> >> --datadir=$(SHAREDIR)/qemu-xen \
> >> --localstatedir=/var \
> >> --disable-kvm \
> >> + --enable-spice \
> >> + --enable-usb-redir \
> >> --disable-docs \
> >> --disable-guest-agent \
> >> --python=$(PYTHON) \
> >>
> >> If you use upstream qemu from distribution package probably have already
> >> spice build-in, for example, on debian I've already tested and working.
> >>
>
> > It is my understanding that the qemu package in F20 does not support xen
> > so I compiled xen from source per the RC3 Test Day instructions and the
> > instructions here:
>
> > http://wiki.xenproject.org/wiki/Compiling_Xen_From_Source
>
> > After adding --enable-spice and --enable-usb-redir to tools/Makefile I
> > see the following error when I make xen:
>
> > ERROR: User requested feature spice
> > configure was not able to find it
>
> Do you have the libspice-dev packages installed for your distro ?
>
I do now. I also have the usbredir-devel package.
Thanks for the help.
next prev parent reply other threads:[~2014-02-06 0:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-04 15:41 [TestDay] F20 Xen 4.4 RC3 Spice support Eric Houby
2014-02-04 16:01 ` Fabio Fantoni
2014-02-05 4:00 ` Eric Houby
2014-02-05 8:06 ` Sander Eikelenboom
2014-02-06 0:17 ` Eric Houby [this message]
2014-02-06 4:23 ` Eric Houby
2014-02-06 7:35 ` Fabio Fantoni
2014-02-07 5:03 ` Eric Houby
2014-02-07 7:23 ` Fabio Fantoni
2014-02-07 9:08 ` Dario Faggioli
2014-02-07 10:52 ` Fabio Fantoni
2014-02-07 23:37 ` Eric Houby
2014-02-08 8:56 ` Fabio Fantoni
2014-02-06 0:30 ` Dario Faggioli
2014-02-10 17:05 ` George Dunlap
2014-02-11 9:56 ` Fabio Fantoni
2014-03-13 14:47 ` Fabio Fantoni
2014-04-10 12:26 ` Fabio Fantoni
2014-04-10 16:21 ` George Dunlap
2014-04-11 7:52 ` Fabio Fantoni
2014-04-11 11:55 ` George Dunlap
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1391645864.2751.9.camel@astar.houby.net \
--to=ehouby@yahoo.com \
--cc=fabio.fantoni@m2r.biz \
--cc=linux@eikelenboom.it \
--cc=xen-devel@lists.xen.org \
--cc=xen@lists.fedoraproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).