9:39 a.m.
Spinning of from this, I think there is some mess around the Virtio
drivers; I would be glad if someone could explain that to me.
Sorry for the length of this mail but I could not shorten it.
Let's say I would like to grab the latest virtio drivers and tools for my
Windows guest and the accompanying source code; this is what I found:
1) Recent version from Fedora in iso format
- No WHQL, no changelog, no QXL drivers, no Spice Agent available, no source
- Updated every once in a while
http://secondary.fedoraproject.org/pub/alt/virtio-win/latest/images/bin/
2) Roughly the same versions of Fedora, in zip format
- No WHQL, no changelog, no QXL drivers, no Spice Agent but the changelog
available.
- All the changelog points to an internal Redhat git repository.
- From my understanding, these tarballs are the one that every once in a
while make their way into the Fedora iso and the "pre WHQL" Redhat ones.
- The source is there in a zip file.
http://people.redhat.com/vrozenfe/
3) Official Spice Agent (very old and buggy):
http://spice-space.org/download/binaries/vdagent-win32_20111124.zip
4) Spice Guest Tools setup
- Unofficial Spice Agent, built from the latest sources using the mingw
based package:
- Latest Fedora iso drivers
- Recent built from source QXL driver, but unfortunately unsigned so it
doesn't work properly in Fedora.
- The Balloon Service is not installed as part of the setup
http://spice-space.org/download/binaries/spice-guest-tools/
5) Official RHEL drivers (need an account for this)
- virtio-win-1.5.3-1.el6_3.noarch.rpm
- Contains signed and WHQL drivers for everything.
- Always a bit older than the Fedora ones.
- Follows the same numbering and logs as no. 2.
- Contains signed WHQL drivers for Windows XP and Windows 7 32/64 bits, but
outside of the normal iso (why?)
- Does not contain the Spice Agent.
6) Yan Vugenfirer's repository
- Contains only source, and is public.
- Does not match with Fedora or RHEL provided drivers.
- Contains only the Virtio drivers, no Spice Agent or QXL driver.
https://github.com/YanVugenfirer/kvm-guest-drivers-windows/commits/master
7) QXL drivers for various targets
- Sometime, someone builds an updated driver and posts it to the
spice-devel mailing list.
- All the drivers are not signed, of course.
======
So far, my best setup is to recreate an iso everytime there is an update to
the following:
- Latest Fedora drivers for Windows XP, 2003
- Latest QXL binary from the Spice Guest Tools for Windows XP
- Latest signed RHEL drivers for Windows Vista and up
- Latest signed QXL driver for Windows Vista and up
- Latest Spice Agent binary from the Spice Guest Tools
I would say this is suboptimal, especially when I try to explain someone
moving from Windows that si trying to virtualize Windows on their newly
converted laptop.
At the best case, they don't have the QXL driver, causing lag in the
desktop, no Spice Agent for cut&paste and usually a lot of problems with
Windows 7.
Before this, I used to compile drivers myself with the DDK following the
instructions. This gave me the option to compile the QXL drivers for
Windows 2003 and Windows 2008 targets as well, but I always had the same
problems with signing.
======
Since all the problems go back to signing the binaries for making them work
out of the box in Windows Vista/7/2008/2008r2/8, I would like to know if
it's possible to do this from time to time:
- Have Fedora build the latest Virtio drivers (this is already done)
- Build also the Spice Agent for 32/64 bit (this is done at
spice-space.orgas part of the Spice Guest Tools)
- Build the latest QXL drivers for all the Windows targets supported by the
Virtio drivers (I know the Windows 8 XWDM driver will come eventually later)
- Sign everything with the Redhat key, as it's doing for the drivers at
point 2.
- Pack everything into an iso.
I'm not asking for WHQL as I understand this is a "benefit" for the Redhat
subscriptions.
All the bits are there except they are dispersed everywhere, so I don't
think it's a big effort.
Regards,
--Simone
--
You cannot discover new oceans unless you have the courage to lose sight of
the shore (R. W. Emerson).
9:43 a.m.
On 9 January 2013 16:39, Simone Caronni <negativo17(a)gmail.com> wrote:
5) Official RHEL drivers (need an account for this)
- virtio-win-1.5.3-1.el6_3.noarch.rpm
- Contains signed and WHQL drivers for everything.
- Always a bit older than the Fedora ones.
- Follows the same numbering and logs as no. 2.
- Contains signed WHQL drivers for Windows XP and Windows 7 32/64 bits,
but outside of the normal iso (why?)
- Does not contain the Spice Agent.
A note on this; the point regarding Windows XP and 7 is for the QXL drivers.
--Simone
--
You cannot discover new oceans unless you have the courage to lose sight of
the shore (R. W. Emerson).
11:33 a.m.
On 09/01/13 15:39, Simone Caronni wrote:
- Build also the Spice Agent for 32/64 bit (this is done at
spice-space.org <http://spice-space.org> as part of the Spice Guest Tools)
Actually that's 32 bit only. I've never found a spice agent for 64 bit
versions of Windows anywhere.
Tom
--
Tom Hughes (tom(a)compton.nu)
http://compton.nu/
3:11 a.m.
On 09/01/13 17:33, Tom Hughes wrote:
On 09/01/13 15:39, Simone Caronni wrote:
> - Build also the Spice Agent for 32/64 bit (this is done at
> spice-space.org <http://spice-space.org> as part of the Spice Guest
> Tools)
Actually that's 32 bit only. I've never found a spice agent for 64 bit
versions of Windows anywhere.
It turns out that I skim read the error a bit too much, and it is
actually specifically XP64 that it refuses to install on rather than 64
bit Windows in general.
Tom
--
Tom Hughes (tom(a)compton.nu)
http://compton.nu/
9:12 a.m.
On Thu, Jan 10, 2013 at 09:11:45AM +0000, Tom Hughes wrote:
On 09/01/13 17:33, Tom Hughes wrote:
>On 09/01/13 15:39, Simone Caronni wrote:
>
>>- Build also the Spice Agent for 32/64 bit (this is done at
>>spice-space.org <http://spice-space.org> as part of the Spice Guest
>>Tools)
>
>Actually that's 32 bit only. I've never found a spice agent for 64 bit
>versions of Windows anywhere.
It turns out that I skim read the error a bit too much, and it is
actually specifically XP64 that it refuses to install on rather than
64 bit Windows in general.
Yes, iirc we don't have virtio/qxl 64 bit builds. The agent can be built on
64 bit.
Christophe
1:20 a.m.
On 01/09/13 16:39, Simone Caronni wrote:
6) Yan Vugenfirer's repository
- Contains only source, and is public.
- Does not match with Fedora or RHEL provided drivers.
- Contains only the Virtio drivers, no Spice Agent or QXL driver.
https://github.com/YanVugenfirer/kvm-guest-drivers-windows/commits/master
spice git repos are here: http://cgit.freedesktop.org/spice/
spice libraries, spice server, spice client, guest agent, guest drivers,
everything. Well, except the xorg qxl driver, that one is here:
http://cgit.freedesktop.org/xorg/driver/xf86-video-qxl/
Spice Guest Tools are built from these repos as far I know.
cheers,
Gerd
7:24 p.m.
On Wed, Jan 09, 2013 at 04:39:06PM +0100, Simone Caronni wrote:
I'm not asking for WHQL as I understand this is a
"benefit" for the Redhat
subscriptions.
Actually WHQL simply cannot be done by Fedora even if we wanted to.
It's an MSFT test programme that costs money, plus MSFT refuse to do
it for GPL drivers.
However we could write a trivial virt-win-reg script which would
disable signing in a Windows VM automatically, so this shouldn't be a
problem.
- - -
Do the virtio drivers now build using the mingw-* stack in Fedora?
IIRC this should be possible now that Fedora has switched over to
using mingw-w64.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
virt-p2v converts physical machines to virtual machines. Boot with a
live CD or over the network (PXE) and turn machines into KVM guests.
http://libguestfs.org/virt-v2v
11:09 a.m.
On 12 January 2013 02:24, Richard W.M. Jones <rjones(a)redhat.com> wrote:
Actually WHQL simply cannot be done by Fedora even if we wanted to.
It's an MSFT test programme that costs money, plus MSFT refuse to do
it for GPL drivers.
Now i understand why we don't have the sources, thanks.
Do the virtio drivers now build using the mingw-* stack in Fedora?
IIRC this should be possible now that Fedora has switched over to
using mingw-w64.
I follow as a user, and as far as I know the WinDDK is still needed. The
Spice Agent can now be built with mingw, though.
Regards,
--Simone
--
You cannot discover new oceans unless you have the courage to lose sight of
the shore (R. W. Emerson).
12:59 p.m.
Richard W.M. Jones schreef op za 12-01-2013 om 01:24 [+0000]:
Do the virtio drivers now build using the mingw-* stack in Fedora?
IIRC this should be possible now that Fedora has switched over to
using mingw-w64.
The git repo for the virtio drivers only contains msvc project files, so
in order to get the virtio drivers built using the mingw-w64
cross-compiler would require new Makefile's to be written.
The mingw-w64 compiler which is currently in Fedora should be capable of
building virtio as the DDK pieces are also bundled (in the
folder /usr/i686-w64-mingw32/sys-root/mingw/include/ddk).
I just took a quick attempt to manually compile these drivers using the
mingw-w64 compiler in Fedora and I think it should be possible. Right
now I've got some errors like "redefinition of 'struct foo'" in some
of
the DDK headers, but I'm sure upstream mingw-w64 devs (and indirectly
the ReactOS project) would be interested in helping out with this.
Regards,
Erik van Pienbroek
4:40 a.m.
On Sat, Jan 12, 2013 at 07:59:24PM +0100, Erik van Pienbroek wrote:
Richard W.M. Jones schreef op za 12-01-2013 om 01:24 [+0000]:
> Do the virtio drivers now build using the mingw-* stack in Fedora?
> IIRC this should be possible now that Fedora has switched over to
> using mingw-w64.
The git repo for the virtio drivers only contains msvc project files, so
in order to get the virtio drivers built using the mingw-w64
cross-compiler would require new Makefile's to be written.
The mingw-w64 compiler which is currently in Fedora should be capable of
building virtio as the DDK pieces are also bundled (in the
folder /usr/i686-w64-mingw32/sys-root/mingw/include/ddk).
I just took a quick attempt to manually compile these drivers using the
mingw-w64 compiler in Fedora and I think it should be possible.
Do you happen to have a log of these attempts? You just quickly passed the
driver C files to mingw-gcc, or did you do something more sophisticated?
Thanks,
Christophe
11:11 a.m.
Christophe Fergeau schreef op do 24-01-2013 om 11:40 [+0100]:
On Sat, Jan 12, 2013 at 07:59:24PM +0100, Erik van Pienbroek wrote:
> The mingw-w64 compiler which is currently in Fedora should be capable of
> building virtio as the DDK pieces are also bundled (in the
> folder /usr/i686-w64-mingw32/sys-root/mingw/include/ddk).
>
> I just took a quick attempt to manually compile these drivers using the
> mingw-w64 compiler in Fedora and I think it should be possible.
Do you happen to have a log of these attempts? You just quickly passed the
driver C files to mingw-gcc, or did you do something more sophisticated?
I think it would be easier if we could discuss this on IRC:
#fedora-mingw @ FreeNode. This subject is a bit off-topic for this list.
Regards,
Erik van Pienbroek
10:20 a.m.
On Sat, Jan 12, 2013 at 2:24 AM, Richard W.M. Jones <rjones(a)redhat.com> wrote:
On Wed, Jan 09, 2013 at 04:39:06PM +0100, Simone Caronni wrote:
> I'm not asking for WHQL as I understand this is a "benefit" for the
Redhat
> subscriptions.
Actually WHQL simply cannot be done by Fedora even if we wanted to.
It's an MSFT test programme that costs money, plus MSFT refuse to do
it for GPL drivers.
If that is the case then GPL is a poor license choice in that case
(unless it links to GPL libraries and thus have no choice).
10:49 a.m.
On 23 January 2013 17:20, drago01 <drago01(a)gmail.com> wrote:
> Actually WHQL simply cannot be done by Fedora even if we wanted
to.
> It's an MSFT test programme that costs money, plus MSFT refuse to do
> it for GPL drivers.
If that is the case then GPL is a poor license choice in that case
(unless it links to GPL libraries and thus have no choice).
I don't recall seeing any GPL reference to the drivers. In the RHEL
virtio-win iso there's a text file with a Redhat License and a notice that
you can buy the source code for $10; in the Fedora one there's one which is
almost the same.
I think this is a good workaround to make the source available but still
certify the drivers.
--
You cannot discover new oceans unless you have the courage to lose sight of
the shore (R. W. Emerson).
9:11 a.m.
On Wed, Jan 09, 2013 at 04:39:06PM +0100, Simone Caronni wrote:
Spinning of from this, I think there is some mess around the Virtio
drivers; I would be glad if someone could explain that to me.
Sorry for the length of this mail but I could not shorten it.
Let's say I would like to grab the latest virtio drivers and tools for my
Windows guest and the accompanying source code; this is what I found:
1) Recent version from Fedora in iso format
- No WHQL, no changelog, no QXL drivers, no Spice Agent available, no source
Err, there are sources, see
http://secondary.fedoraproject.org/pub/alt/virtio-win/latest/images/src/
3) Official Spice Agent (very old and buggy):
http://spice-space.org/download/binaries/vdagent-win32_20111124.zip
4) Spice Guest Tools setup
- Unofficial Spice Agent, built from the latest sources using the mingw
based package:
I'd tend to consider this agent as an official build, though it probably
needs to be put in a zip file next to the older build.
======
So far, my best setup is to recreate an iso everytime there is an update to
the following:
- Latest Fedora drivers for Windows XP, 2003
- Latest QXL binary from the Spice Guest Tools for Windows XP
- Latest signed RHEL drivers for Windows Vista and up
- Latest signed QXL driver for Windows Vista and up
- Latest Spice Agent binary from the Spice Guest Tools
I would say this is suboptimal, especially when I try to explain someone
moving from Windows that si trying to virtualize Windows on their newly
converted laptop.
At the best case, they don't have the QXL driver, causing lag in the
desktop, no Spice Agent for cut&paste and usually a lot of problems with
Windows 7.
For this use case, all they need to do is to grab the spice-guest-tools
installer and run that, the mess you describe is the exact reason why I'm
building this installer.
- Have Fedora build the latest Virtio drivers (this is already done)
- Build also the Spice Agent for 32/64 bit (this is done at
spice-space.orgas part of the Spice Guest Tools)
- Build the latest QXL drivers for all the Windows targets supported by the
Virtio drivers (I know the Windows 8 XWDM driver will come eventually later)
- Sign everything with the Redhat key, as it's doing for the drivers at
point 2.
Hmm I thought each binary driver release was signed with the Red Hat key
(but not WHQL'ed), maybe I missed something...
- Pack everything into an iso.
Is that better than having an installer for everything (aka
spice-guest-tools)?
Christophe
10:18 a.m.
On 23 January 2013 16:11, Christophe Fergeau <cfergeau(a)redhat.com> wrote:
> 1) Recent version from Fedora in iso format
> - No WHQL, no changelog, no QXL drivers, no Spice Agent available, no
source
Err, there are sources, see
http://secondary.fedoraproject.org/pub/alt/virtio-win/latest/images/src/
Well, here are the code "drops" every once in a while, no git repository or
any way to see what's "cooking" or the status of things.
> 4) Spice Guest Tools setup
> - Unofficial Spice Agent, built from the latest sources using the mingw
> based package:
I'd tend to consider this agent as an official build, though it probably
needs to be put in a zip file next to the older build.
That would be nice.
> At the best case, they don't have the QXL driver, causing
lag in the
> desktop, no Spice Agent for cut&paste and usually a lot of problems with
> Windows 7.
For this use case, all they need to do is to grab the spice-guest-tools
installer and run that, the mess you describe is the exact reason why I'm
building this installer.
The installer works good and is a very nice addition, but the QXL drivers
do not work, as it's not signed.
The only one signed I found are in the RHEL virtio-win iso.
> - Have Fedora build the latest Virtio drivers (this is already
done)
> - Build also the Spice Agent for 32/64 bit (this is done at
> spice-space.orgas part of the Spice Guest Tools)
> - Build the latest QXL drivers for all the Windows targets supported by
the
> Virtio drivers (I know the Windows 8 XWDM driver will come eventually
later)
> - Sign everything with the Redhat key, as it's doing for the drivers at
> point 2.
Hmm I thought each binary driver release was signed with the Red Hat key
(but not WHQL'ed), maybe I missed something...
It's as you said, everything in the Fedora iso is signed and not WHQL, but
the QXL drivers are not included in the iso and signed.
> - Pack everything into an iso.
Is that better than having an installer for everything (aka
spice-guest-tools)?
I think the Spice Guest Tools are a great addition, but on Windows 7 I do
the installation directly on the virtio drivers as this speeds up the
installation to one tenth of the time and I can't do that with the Spice
Guest Tools; and the standalone drivers are in the Fedora virtio iso.
In addition to this, for various testing reasons at work we prepare Windows
silent install kits and test them on RHEV, so I add all drivers in the iso.
To summarize, what would be nice to have is the addition of recently built
Spice Agents and signed QXL drivers in the Fedora iso.
A nice addition would also be to have QXL drivers compiled for xp/2003 64
bit. I compiled that once more than a year ago and it was working fine.
Thanks & regards,
--Simone
--
You cannot discover new oceans unless you have the courage to lose sight of
the shore (R. W. Emerson).
4:31 a.m.
On Wed, Jan 23, 2013 at 05:18:10PM +0100, Simone Caronni wrote:
On 23 January 2013 16:11, Christophe Fergeau
<cfergeau(a)redhat.com> wrote:
> > 1) Recent version from Fedora in iso format
> > - No WHQL, no changelog, no QXL drivers, no Spice Agent available, no
> source
>
> Err, there are sources, see
> http://secondary.fedoraproject.org/pub/alt/virtio-win/latest/images/src/
>
Well, here are the code "drops" every once in a while, no git repository or
any way to see what's "cooking" or the status of things.
http://www.linux-kvm.org/page/WindowsGuestDrivers/Download_Drivers
My understanding is that they are based on the git repo linked there if
this is the information you want.
> For this use case, all they need to do is to grab the
spice-guest-tools
> installer and run that, the mess you describe is the exact reason why I'm
> building this installer.
>
The installer works good and is a very nice addition, but the QXL drivers
do not work, as it's not signed.
I'm not sure how to test whether it's signed or not, but I just tested that
the driver works in a winxp 32 bit install.
To summarize, what would be nice to have is the addition of recently
built
Spice Agents and signed QXL drivers in the Fedora iso.
I'm not sure qxl + spice agent really belongs in the virtio-win ISO on
alt.fedoraproject.org, as these virtio drivers can be useful to people not
using SPICE at all. However, if you are willing to build such an ISO from
the bits and pieces from this virtio-win ISO and from spice-space.org, it
would make sense to provide it alongside the spice-guest-tools installer on
spice-space.org.
Christophe
5:25 a.m.
Hello,
On 24 January 2013 11:31, Christophe Fergeau <cfergeau(a)redhat.com> wrote:
http://www.linux-kvm.org/page/WindowsGuestDrivers/Download_Drivers
My understanding is that they are based on the git repo linked there if
this is the information you want.
Unfortunately no, they're totally different than the one Fedora provides.
The one Fedora provides follow the same versioning of the RHEL ones except
they're not WHQL signed.
An example; netkvm for xp in the git repo:
DriverVer = 03/15/2007,1.0.0.0
In the Fedora iso:
DriverVer=01/22/2013,51.64.104.5200
This is the RHEL numbering, where the ".64." means it's slated for the RHEL
6.4 inclusion.
Also if you fetch this [1], on which the fedora iso are based, it unpacks
as "internal-kvm-guest-drivers-windows" and the changelog is totally
different. The 2 source codes are totally unrelated, they are separate
repositories. The one on github seems a repository where some fixes are
tested, that's all.
[1]
http://people.redhat.com/vrozenfe/build-48/virtio-win-prewhql-0.1-48-sour...
> For this use case, all they need to do is to grab the
spice-guest-tools
> > installer and run that, the mess you describe is the exact reason why
I'm
> > building this installer.
> >
>
> The installer works good and is a very nice addition, but the QXL drivers
> do not work, as it's not signed.
I'm not sure how to test whether it's signed or not, but I just tested that
the driver works in a winxp 32 bit install.
That's exactly the problem, XP allows unsigned drivers; windows 7 doesn't.
> To summarize, what would be nice to have is the addition of
recently
built
> Spice Agents and signed QXL drivers in the Fedora iso.
I'm not sure qxl + spice agent really belongs in the virtio-win ISO on
alt.fedoraproject.org, as these virtio drivers can be useful to people not
using SPICE at all.
I don't know, I don't understand why a user should choose a worst user
experience when they could have it better with the same functionality. I
mean, using QXL/Spice with virt-manager does not have any drawback compared
to Cirrus+VNC. The client is different, but on the contrary there are only
benefits.
Anyway the problem leads back to the QXL drivers; if the latest QXL drivers
were signed and parked at spice-space.org it would not be a big deal even
if not included in the iso; but unfortunately they are not.
However, if you are willing to build such an ISO from
the bits and pieces from this virtio-win ISO and from
spice-space.org, it
would make sense to provide it alongside the spice-guest-tools installer on
spice-space.org.
I will do, a new "52" iso has come out for Fedora. Waiting on your Spice
Guest Tools 0.4 with latest Balloon Service and latest Spice Agent. :D
Many thanks.
--Simone
--
You cannot discover new oceans unless you have the courage to lose sight of
the shore (R. W. Emerson).
7:23 a.m.
On Thu, Jan 24, 2013 at 12:25:19PM +0100, Simone Caronni wrote:
> > For this use case, all they need to do is to grab the
spice-guest-tools
> > > installer and run that, the mess you describe is the exact reason why
> I'm
> > > building this installer.
> > >
> >
> > The installer works good and is a very nice addition, but the QXL drivers
> > do not work, as it's not signed.
>
> I'm not sure how to test whether it's signed or not, but I just tested that
> the driver works in a winxp 32 bit install.
>
That's exactly the problem, XP allows unsigned drivers; windows 7 doesn't.
Win7 32 bit does allow unsigned (by MS/WHQL) drivers, Win7 64 bit does not.
I've tested the latest qxl driver on a Win7 32 bit installation and it
installed properly, so I don't know what problem you are trying to point
at, I don't see any different behaviour between the qxl driver and the
virtio ones.
Anyway the problem leads back to the QXL drivers; if the latest QXL
drivers
were signed and parked at spice-space.org it would not be a big deal even
if not included in the iso; but unfortunately they are not.
Please be more specific about the signature issue you keep mentioning, I
haven't been able to reproduce any different behaviour between the qxl
driver and the virtio drivers from alt.fedoraproject.org.
Christophe
8:56 a.m.
Hello,
On 29 January 2013 14:23, Christophe Fergeau <cfergeau(a)redhat.com> wrote:
Win7 32 bit does allow unsigned (by MS/WHQL) drivers, Win7 64 bit
does not.
I've tested the latest qxl driver on a Win7 32 bit installation and it
installed properly, so I don't know what problem you are trying
to point
at, I don't see any different behaviour between the qxl driver and the
virtio ones.
I'm running Windows 7 64 bit in fact; apparently there's no difference but
QXL does not work. It seems Windows needs signed drivers only for VGA
devices.
In the archive (drivers-details.tar.gz) are the driver details from the
windows hardware manager; none is signed.
Attached is a screenshot (qxl-error.png) with the QXL driver exhibiting
this odd behaviour (error 52); the other drivers work fine.
To make it work, I have to enable testsigning in the guest
(test-signing.png):
**
bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
bcdedit.exe -set TESTSIGNING ON
Might I ask you if you could create an additional screen in Spice Guest
Tools to enable "Test Signing"? Like a tick mark or something like that.
Or maybe a simple notice that it has been enabled in Windows 7+.
I'm available for testing if you would like some help.
Thanks & regards,
--Simone
--
You cannot discover new oceans unless you have the courage to lose sight of
the shore (R. W. Emerson).
10:46 a.m.
Christophe,
Sorry for a delay on this thread, i just found it. To illuminate
Simone's issue (that also adversely effect me) is that, though the QXL
drivers work in 32 bit Windows 7, we are unable to install them in the
64bit version of Windows 7 without having to either permanently disable
driver signing and place the system in "test mode" (which for myself is
a security policy violation at the day job) or not use QXL.
Windows 7 x64 and all Windows 8 systems require signed drivers to start
the device. I currently have an unsigned QXL driver installed - but
windows will not allow it to start.
This makes the switch to the slower, more CPU intensive, and less useful
Virtualbox appealing. However, that saddles us with some other issues
and ties us back to oracle.
This would not be an issue if the Spice QXL drivers were signed,
allowing operation in Windows 7 x64 and above.
I do not know how Red Hat/Fedora would fit in with driver signing for
the Spice QXL vs FreeDesktop position, but I hope this is a good
explanation of the issue.
Frank Moss
--
Frank Moss
Cloud and Virtualization Architect
<frank(a)nine13tech.com>
4007
days inactive
4125
days old
19 comments
8 participants
participants (8)
-
Christophe Fergeau -
drago01 -
Erik van Pienbroek -
Frank Moss -
Gerd Hoffmann -
Richard W.M. Jones -
Simone Caronni -
Tom Hughes