<div><br><div class="gmail_quote">On Thu, Feb 10, 2011 at 16:30, Alon Levy <span dir="ltr"><<a href="mailto:alevy@redhat.com">alevy@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Thu, Feb 10, 2011 at 03:44:59PM -0200, Avi Alkalay wrote:<br>
> Ok, so the 'host=' argument is unsupported on qemu 0.13 and the spice<br>
> documentation is wrong.<br>
<br>
</div>so the user guide pdf is wrong?<br></blockquote><div> </div><meta http-equiv="content-type" content="text/html; charset=utf-8">The user guide PDF on spice-space seems wrong, at least the part related to 'qemu -spice host=blablabla'.</div>
<div class="gmail_quote"><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">> This is quite dirty and insecure cause anybody anywhere will be able to<br>
> connect to your VMs with the spice protocol. But we are testing new stuff<br>
> here, right!?<br>
</div>You could still supply a password, and use tls.</blockquote><div><br></div><div>If current libvirt can't handle current qemu simple thing as the 'host=' parameter, I won't risk trying things as TLS and certificates. Of course you can write your configs and initscripts manualy, but then what is the point on libvirt and virt-manager ?</div>
<div><br></div><div>Regards,</div><div>Avi</div></div></div>