Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 576944 - app-emulation/qemu: unmask USE=spice on x86 systems
Summary: app-emulation/qemu: unmask USE=spice on x86 systems
Status: RESOLVED WONTFIX
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Eclasses (show other bugs)
Hardware: x86 Linux
: Normal normal (vote)
Assignee: Gentoo QEMU Project
URL: https://lists.freedesktop.org/archive...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-03-10 08:30 UTC by dtr
Modified: 2017-05-19 08:49 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
GNS3 window running a network of virtual machines (1457597893.png,84.45 KB, image/png)
2016-03-10 08:30 UTC, dtr
Details
Template for QEMU VMs, my i386 binary can be seen (1457598438.png,51.95 KB, image/png)
2016-03-10 08:31 UTC, dtr
Details
spicy from spice-gtk window connected to the VM1 shows SystemRescueCd loading (1457597967.png,195.36 KB, image/png)
2016-03-10 08:33 UTC, dtr
Details

Note You need to log in before you can comment on or make changes to this bug.
Description dtr 2016-03-10 08:30:08 UTC
Created attachment 427866 [details]
GNS3 window running a network of virtual machines

Currently this USE flag is masked by /usr/portage/profiles/arch/x86/package.use.mask

# Doug Goldstein <cardoe@gentoo.org> (17 Jan 2012)
# The SPICE server is only supported on 64-bit platforms and not on 32-bit
app-emulation/qemu spice

While in fact, QEMU on x86 does support SPICE server and it works perfectly, see the screenshots below.
Comment 1 dtr 2016-03-10 08:31:32 UTC
Created attachment 427868 [details]
Template for QEMU VMs, my i386 binary can be seen
Comment 2 dtr 2016-03-10 08:33:09 UTC
Created attachment 427870 [details]
spicy from spice-gtk window connected to the VM1 shows SystemRescueCd loading
Comment 3 Doug Goldstein (RETIRED) gentoo-dev 2016-03-11 14:21:16 UTC
The SPICE server is not supported on x86 by upstream. They only support x86_64. Hence why this is disabled.
Comment 4 SpanKY gentoo-dev 2016-03-11 18:57:04 UTC
(In reply to Doug Goldstein from comment #3)

can we add that link to the mask notice so it's shown to users ?
Comment 5 Doug Goldstein (RETIRED) gentoo-dev 2016-03-11 19:53:37 UTC
(In reply to SpanKY from comment #4)
> (In reply to Doug Goldstein from comment #3)
> 
> can we add that link to the mask notice so it's shown to users ?

Yes. I wish I could find the original announcement rather than the recent-ish patch that made the error more clear.
Comment 7 dtr 2016-03-12 05:15:43 UTC
(In reply to Doug Goldstein from comment #3)
> The SPICE server is not supported on x86 by upstream. 
Did you see https://bugs.gentoo.org/attachment.cgi?bugid=576944&action=viewall ? Am I supposed to be a wizard because I run it on x86?
> They only support x86_64. Hence why this is disabled.
> https://lists.freedesktop.org/archives/spice-devel/2015-September/021846.html
If you actually followed that link of yours, then in the last message you would find

From: Frediano Ziglio <fziglio at redhat.com>
Date: Fri, 4 Sep 2015 11:22:01 +0100
Subject: [PATCH] build-sys: Update warning message

arch_warn was set to 1 only if architecture is not x86, x64 or arm.
Update the message as we actually main test x64.
> > Saying that spice-server has been tested 'extensively' on x86 is not
> > really true imo, even less so for arm.

I’ll attach the current state of configure.ac
# grep -A6 '# Check for the CPU' /var/tmp/portage/app-emulation/spice-0.13.0/work/spice-0.13.0/configure.ac                                                                                                                  
# Check for the CPU we are using
case $host_cpu in
  x86_64)
        ;;
  *)
        SPICE_WARNING([spice-server on non-x86_64 architectures hasn't been extensively tested])
esac

It only says that x86 wasn’t extensively tested. Not that it’s not supported. If you disable that mask in the profile, like I did, you will /probably/ see it working as well as on my computer. Why didn’t you? You’re the maintainer after all.
Comment 8 Sergey Popov gentoo-dev 2017-05-19 08:49:19 UTC
We mask it not because it is not working, but because it is officially unsupported by upstream due to lack of testing. Feel free to unmask and use it on your own - just do not blame us for any troubles that may come in this configuration.

Package and USE masks exist not only for broken software, but also - for not widely tested or supported. In that case - it is up to maintainer if he wish to support it on his own or stick to upstream guidelines.