From: Marius Bakke <mbakke@fastmail.com>
To: George myglc2 Clemmer <myglc2@gmail.com>, help-guix <help-guix@gnu.org>
Subject: Re: best way to reach QEMU VM desktop on headless GuixSD server
Date: Sat, 27 Jan 2018 17:03:26 +0100 [thread overview]
Message-ID: <87po5vxp9t.fsf@fastmail.com> (raw)
In-Reply-To: <86607yswqr.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 980 bytes --]
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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2018-01-27 16:03 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 [this message]
2018-02-03 3:42 ` myglc2
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87po5vxp9t.fsf@fastmail.com \
--to=mbakke@fastmail.com \
--cc=help-guix@gnu.org \
--cc=myglc2@gmail.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).