search for: tlsport

Hi,everyone, there is a problem with libvirt support spice protocol. i use the following patch file,but it seems not success.anyone have an idea about that? thanks. patch file: This adds an element <graphics type='spice' port='5903' tlsPort='5904' listen='127.0.0.1'/> This is the bare minimum that should be exposed in the guest config for SPICE. Other parameters are better handled as per host level configuration tunables * docs/schemas/domain.rng: Define the SPICE <graphics> schema * src/domain_conf.h, src/d...

Is TLS required for the usage of Spice with KVM/libvirtd? I've been through the virt-install manpage a few times now to no avail. What is wrong with my syntax here (seen below)? Thanks. ~]# virt-install --connect qemu:///system -n blahhost -r2048 --vcpus=4 --arch=x86_64 --video qxl --graphics spice,port=5931 --noautoconsole --os-type linux --accelerate --network=bridge:kickstart_br0 --hvm

...k > > path=/dev/vmdisks/fedora-test2,bus=virtio --cdrom /tmp/fedora.iso > > To also reply to nevis2us: I have the Spice TLS config commented presently so it is not active (afaik). At one point I did try switching the value from 1 to 0 when I did have it uncommented. > See if adding tlsport=0 to the --graphics option fixes your problem? > > --graphics spice,port=5931,tlsport=0 > I did try that before (though didn't note it in my first message). ERROR Error in graphics device parameters: TLS port must be a number between 5900 and 65535, or -1 for auto allocation ~]#...

...install --connect qemu:///system -n blahhost -r2048 --vcpus=4 > --arch=x86_64 --video qxl --graphics spice,port=5931 --noautoconsole > --os-type linux --accelerate --network=bridge:kickstart_br0 --hvm --disk > path=/dev/vmdisks/fedora-test2,bus=virtio --cdrom /tmp/fedora.iso See if adding tlsport=0 to the --graphics option fixes your problem? --graphics spice,port=5931,tlsport=0 Compare http://www.spice-space.org/page/Features/Xspice#--tls-port_0_required Regards, Leonard. -- mount -t life -o ro /dev/dna /genetic/research

...nbd_tls, migrate_tls, backup_tls, and you can even configure different certificates for each of them. >spice_tls option and certificates ? > That, and also don't forget to configure the domain XML so that it uses what you want, probably something like: <graphics type='spice' tlsPort='-1'/> and then some, check the following for more details: https://libvirt.org/formatdomain.html#graphical-framebuffers >KJ > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc:...

(Posted few days ago on qemu group but no reactions) Do I understand correctly that ssl shoudl be configured independently for libvirt and each hypervisor? I asked because I configured libvirt connection as qemu+tls://bambus.kjonca/system?pkipath=... (and on bambus in /etc/libvirt/libvirtd.conf) I set key_file = ... cert_file = ... ca_file = ... But after connect and lauching (on bambus) vm I