k8r2\x86\". It looks
like they are included only for Windows 7 and XP.
Yup, I haven't updated the installer to take this into account, so this
probably is not getting shipped/installed.
So How should get (and install) the binaries for the QXL driver for
Win2k8r2? Just wait for an
86\". It looks like
they are included only for Windows 7 and XP.
PS: The latest RPM for RHEL6, virtio-win-1.1.16-0.el6.noarch.rpm, also
doest not included the qxl drivers for Win 2008R2.
[]s, Fernando Lozano
___
Spice-devel mailing list
Spi
.
[]s, Fernando Lozano
___
Spice-devel mailing list
Spice-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/spice-devel
ectly thanks Christophe, no dependancy issues and no
crash (build from master).
Any plans to put this new build somewere for other windows users?
It would be nice if someone tried virt-manager besides virt-viewer and
virsh. :-)
[]s, Fernando L
works with TLS and TCP (noauth),
virt-viewer locks up.
Remote-viewer was woking before and continues working. I have not tried
alternative authentications schemes for spice, just TLS and the fixed
(shared) password.
[]s, Fernando Lozano
___
Spice-
setup "polkit" on the host. It complains about a
missing agent. For libvirtd, the auth options are "none", "sasl" and
"polkit". When I manage to get "polkit" working for a linux client, I'll
try on the windows port.
[]s, Fernando Lozano
RPC_TLS_CONTEXT_SESSION_ALLOW entry means that, right?). How strange. So
I also attached also a debug log for the qemu+tcp url.
Hope this helps making virt-viewer work on windows.
[]s, Fernando Lozano
[]s, Fernando Lozano
C:\Program Files\VirtViewer\bin>virt-viewer --debug -c qemu+tcp://kv
27;m eager to try the next release you
are about to build.
PS: Would it be hard to add SASL support to the windows port? It's much
easier to setup than TLS.
[]s, Fernando Lozano
___
Spice-devel mailing list
Spice-devel@lists.freedesktop.o
mbers: if Fedora has libvirt 1.0.5.x
why should the next windows build use older 0.10.2.8? I though
development were being done only on the latest releases.
[]s, Fernando Lozano
___
Spice-devel mailing list
Spice-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/spice-devel
like to use
regular user PAM passwords (either from local files or from LDAP). But I
only managed to get working the other options: no auth, client-cert
(TLS) or SASL digest-md5 own password database.
>>> When I try a "qemu+ssh" remote virsh connection evething works fine.
I f
my case, using SPICE for guest consoles.
While now I understand why all those password prompts, that's very bad
from a usability perspective. And I guess it's also bad from a network
perspective (having multiple TCP connections for the same interative
remote user session). Couln
Hi Christophe,
On Tue, Sep 17, 2013 at 02:57:04PM -0300, Fernando Lozano wrote:
If someone provides newer windows binaries -- which aren't missing
dlls, like the ones at http://teuf.fedorapeople.org/virt-viewer-msi/
-- I will test then.
[...]
Please someone give me newer binaries I can
in password many times!
Maybe people who use ssh keys (passwordless) logins didn't notice, but I
think virt-manager should't require more than one addtional ssh
connection per guest console. Is this a bug?
[]s, Fernando Lozano
__
s-compiling is not for the
faint of heart, and learning the first steps require a significant
investment in time. :-(
Is there a how-to I can follow to generate binaries from the latest
sources? I do have Linux expertize, I use fedora on my personal
computer, but as C developer I can only run
the TLS test I already sent.
[]s, Fernando Lozano
___
Spice-devel mailing list
Spice-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/spice-devel
no promises, free time is very scarse. :-(
[]s, Fernando Lozano
___
Spice-devel mailing list
Spice-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/spice-devel
you want, but I unfortunately can't/don't want to spend a lot of
> time on testing and debugging virsh Windows binaries :(
Thanks for the offer, I'll take it, although without high expectations.
It's a share there's so little interest from Red Hat.
[]s, Fernando Lozan
virt-viewer (and who knows, some
day virt-manager) on Windows, to get test binaries. There should be some
effort on continuing the porting, not stopping on remote-viewer.
[]s, Fernando Lozano
___
Spice-devel mailing list
Spice-devel@lists.
s, but it's too little for my fellow sysadmins. I'm
trying virsh and virt-viewer form the same package.
[]s, Fernando Lozano
___
Spice-devel mailing list
Spice-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/spice-devel
e for windows (like gimp)
makes it look very hard, involving a significand investment in time just
to get started and a deep knowledge about both platforms. Would you be
able to provide a HOW-TO for virsh and maybe virt-viewer? I'm not
telling I'd be able to spare the time, but I&#
ng I
could see to explain why it's locked.
[]s, Fernando Lozano
___
Spice-devel mailing list
Spice-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/spice-devel
is doing that,
because the binaries are updates every few months. :-)
Again, I'm willing to help any way I can, but I can be only a tester,
and a documentation writer. I won't be able to help as a developer. :-(
[]s, Fernando Lozano
___
ubscriptions, The idea is production hosts will be RHEL. :-) If
not, my boss may end up buying XenServer ;-)
[]s, Fernando Lozano
___
Spice-devel mailing list
Spice-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/spice-devel
rt-viewer for windows connect using TLS, and I won't
open access to libvirtd without it. The path
'/usr/i686-w64-mingw32/sys-root/mingw/etc/pki/CA/cacert.pem' is supposed
to point to where on the Windows workstations?
[]s, Fernando Lozano
___
I had to
block the insecure ports on the host using iptables, else virt-viewer
and virt-manager never use the tls port. Looks like this is a libvirt
fault, not qemu.
But on remote-viewer, using the correct URL syntax opens connections
using the tls port even if the insecu
you work as a consultant and will connect to
guests from different customers.
Unfortunately the windows port won't accept --spice-ca-file. :-(
Is there a similar option for virsh and/or virt-viewer?
[]s, Fernando Lozano
___
Spice-devel mailing list
Spice-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/spice-devel
an't connect to
libvirtd on the host yet. I assume by the same reason virsh can't: they
cannot find the certificates. But virt-viewer only tells "unable to
connect to libvirtd with URI..."
[]s, Fernando Lozano
___
Spice-devel mailing list
Spice-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/spice-devel
soles.
Of course everything works fine using Xming and putty, but windows
people doesn't like this. They want native windows tools that take care
of all connection details, without need to start ssh tuneels by hand. :-(
[]s, Fernando Lozano
___
r or virt-viewer handle ssh tunnels.
It looks like on Linux remote-viewer creates the ssh tunnel itself, but
not on the windows port.
[]s, Fernando Lozano
___
Spice-devel mailing list
Spice-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/spice-devel
should be able to get the spice TCP port from libvirtd, instead
of having the user find and provide the correct port on the host for the
desired guest. It should be smart enough to setup a ssh tunnel if needed
or ask for tls certificates if it can't find them.
[]s,
rtificates like "C:\mingw\etc\pki"
and "C:\usr\x86_64-w64-mingw32\sys-root\mingw\etc\pki", none worked.
Any ideas? Or to use remote-viewer / virsh from a Windows machine I need
to allow insecure conections (no TLS) to the libvirtd and spice TCP ports?
[]s, Fernan
ls my guests are listening on
127.0.0.1, netstat tells they are listeing on 0.0.0.0.
[]s, Fernando Lozano
___
Spice-devel mailing list
Spice-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/spice-devel
32 matches
Mail list logo
