From: myglc2@gmail.com
To: Marius Bakke <mbakke@fastmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: best way to reach QEMU VM desktop on headless GuixSD server
Date: Fri, 02 Feb 2018 22:42:57 -0500 [thread overview]
Message-ID: <86wozuhh6m.fsf@gmail.com> (raw)
In-Reply-To: <87po5vxp9t.fsf@fastmail.com> (Marius Bakke's message of "Sat, 27 Jan 2018 17:03:26 +0100")
Hi Marius,
On 01/27/2018 at 17:03 Marius Bakke writes:
> George myglc2 Clemmer <myglc2@gmail.com> writes:
>
>> It appears that there are 3 ways to reach a QEMU VM desktop on headless
>> GuixSD servers: X11, spice, and maybe VNC. Is that right?
>>
>> Can anyone comment on which has the best performance.
>
> Spice was designed to be a better protocol than VNC for accessing
> virtual machine consoles. I haven't done any benchmarks though.
>
> It requires a rather involved QEMU command line[0]:
>
> [qemu] -spice addr=127.0.0.1,port=3001,disable-ticketing -soundhw hda \
> -device virtio-serial -chardev spicevmc,id=vdagent,debug=0,name=vdagent \
> -device virtserialport,chardev=vdagent,name=com.redhat.spice.0 \
>
> Then you can use virt-viewer or "spicy" from spice-gtk along with SSH
> forwarding to access 127.0.0.1:3001 on the remote machine. Setting up
> encryption or authentication requires a few more arguments if you want
> to expose this on a network-facing interface directly.
>
> [0] https://www.spice-space.org/spice-user-manual.html
Many thanks for this ... dropped your lines into my qemu call and it
worked right out of the box \\WOW// ... once I realized the virt-viewer
client is actually called remote-viewer ;-) - George
prev parent reply other threads:[~2018-02-03 3:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-18 21:06 best way to reach QEMU VM desktop on headless GuixSD server George myglc2 Clemmer
2018-01-19 10:17 ` Chris Marusich
2018-01-27 16:03 ` Marius Bakke
2018-02-03 3:42 ` myglc2 [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86wozuhh6m.fsf@gmail.com \
--to=myglc2@gmail.com \
--cc=help-guix@gnu.org \
--cc=mbakke@fastmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.