From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>,
"Jean-Louis SOLATGES" <jean-louis.solatges@wanadoo.fr>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Unknown X11 keycode mapping report
Date: Tue, 2 Apr 2019 16:46:53 +0200 [thread overview]
Message-ID: <dd916931-1d1f-50db-cb09-5f6a82b4fbba@redhat.com> (raw)
In-Reply-To: <20190402132846.GG413@redhat.com>
On 4/2/19 3:28 PM, Daniel P. Berrangé wrote:
> On Tue, Apr 02, 2019 at 02:47:25PM +0200, Jean-Louis SOLATGES wrote:
>> Bonjour, par tightvnc server sur clipper depuis un linux connecté en vncviewer,
>
> Google translate doesn't do a good job here.
Google isn't that wrong here, I'm also having difficulties to understand.
>
> Is this saying that you are running QEMU from inside a TightVNC server
> session running on Linux ? IOW the X11 server would be Xvnc, not your
> regular desktop Xorg server ?
This is what I understand indeed.
Jean-Louis uses a Linux workstation where he uses vncviewer to connect
to a tightvnc server running on the 'clipper' server (Slackware 14.2).
Within the VNC session, he runs as root the qemu-system-x86_64 command
on 'clipper'. I suppose "Linux useit1 3.16.0-0.bpo.4-amd64" is the image
he tries to run.
>>
>> je lance :
>> qemu-system-x86_64 -m 16G -cpu kvm64 -accel kvm,thread=multi -smp 6,maxcpus=12 -net nic -net tap -net socket,listen=127.0.0.1:1234 -vga cirrus -boot c -hda uis1.img
>
>
> Can you say what version of QEMU you are using too ?
>
>
> Regards,
> Daniel
>
next prev parent reply other threads:[~2019-04-02 14:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-02 12:47 [Qemu-devel] Unknown X11 keycode mapping report Jean-Louis SOLATGES
2019-04-02 13:28 ` Daniel P. Berrangé
2019-04-02 14:46 ` Philippe Mathieu-Daudé [this message]
2019-04-02 15:18 ` Daniel P. Berrangé
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=dd916931-1d1f-50db-cb09-5f6a82b4fbba@redhat.com \
--to=philmd@redhat.com \
--cc=berrange@redhat.com \
--cc=jean-louis.solatges@wanadoo.fr \
--cc=qemu-devel@nongnu.org \
/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 NNTP newsgroup(s).