From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>, qemu-s390x <qemu-s390x@nongnu.org>
Subject: Re: [Qemu-devel] qemu crashes with vnc and multiple outputs + console redirection
Date: Thu, 8 Mar 2018 16:37:45 +0100 [thread overview]
Message-ID: <1befeac9-9468-3604-a9c2-df321453ffd9@de.ibm.com> (raw)
In-Reply-To: <20180308152603.x6ysyb4vq5py67mb@sirius.home.kraxel.org>
On 03/08/2018 04:26 PM, Gerd Hoffmann wrote:
> Hi,
>
>> I am playing with the virtio-gpu support on s390 and for that I also wanted to multiplex
>> the existing consoles.
>> So I basically used the max_outputs=2 of virtio gpu to be able
>> to switch with ctrl+alt+1 and 3 between the virtio gpu and the sclplm console.
>
> Why max_outputs=2? Do you want two fbdev devices?
I had the situation that the vc device does not appear via vnc
(only the virtio-gpu was then available). But I can no longer reproduce. So
with max_outputs=1 this now works as well. No idea what was wrong. And here
I can no longer see the crash.
>
>> -chardev pty,id=charconsole0 -device sclpconsole,chardev=charconsole0,id=console0
>> -chardev vc,id=charconsole1 -device sclplmconsole,chardev=charconsole1,id=console1
>> -device virtio-keyboard-ccw,id=input0,devno=fe.0.0001
>> -vnc 0.0.0.0:0
>> -k en-us
>> -device virtio-gpu-ccw,id=video0,max_outputs=2,devno=fe.0.0008
>>
>>
>> This seems to work fine, vrtio-gpu is on 1 and sclplm is on 3. Problem is,
>> when I randomly do ctrl+alt+[^1..9] sooner or later qemu crashes with
>
> Any chance this is ctrl-alt-2 ?
yes.
prev parent reply other threads:[~2018-03-08 15:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-08 12:42 [Qemu-devel] qemu crashes with vnc and multiple outputs + console redirection Christian Borntraeger
2018-03-08 15:26 ` Gerd Hoffmann
2018-03-08 15:37 ` Christian Borntraeger [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=1befeac9-9468-3604-a9c2-df321453ffd9@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@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).