On Thu, 21 Jul 2022 at 03:46, Jakob Bohm wrote:
> It would be a lot more helpful if your error message was explicit about
> which items were conflicting rather than demanding the full configuration
> from people affected. And don't fall for the temptation of printing out a
> list of potential
On 2022-07-20 14:35, Peter Maydell wrote:
On Wed, 20 Jul 2022 at 13:14, Chan Kim wrote:
Hi, Peter Maydell,
Thank you for the advice.
So I uncommented the stdio_in_use guard, and used this option
(because the second uart will be used)
-chardev null,mux=off,id=char0 -serial chardev:char0
On Wed, 20 Jul 2022 at 13:14, Chan Kim wrote:
>
> Hi, Peter Maydell,
>
> Thank you for the advice.
> So I uncommented the stdio_in_use guard, and used this option
> (because the second uart will be used)
>
> -chardev null,mux=off,id=char0 -serial chardev:char0 -chardev
> stdio,mux=off,id=char1
-generated fdt is
not used at all, is this correct?
Best regards,
Chan Kim
>-Original Message-
>From: Peter Maydell
>Sent: Wednesday, July 20, 2022 7:44 PM
>To: Chan Kim
>Cc: qemu-discuss
>Subject: Re: linux shell comes out to qemu-monitor when I enter anything.
>(I have
On Wed, 20 Jul 2022 at 11:27, Chan Kim wrote:
>
> Hello qemu experts,
>
> In my virtual machine I have two uart and I want to use the input/output in
> my host machine.
> For that I commented out these lines in qemu_chr_open_stdio function in
> chardev/char-stdio.c. (qemu-6.2.0)
>
> /*
> if
Hello qemu experts,
In my virtual machine I have two uart and I want to use the input/output in
my host machine.
For that I commented out these lines in qemu_chr_open_stdio function in
chardev/char-stdio.c. (qemu-6.2.0)
/*
if (stdio_in_use) {
error_setg(errp, "cannot use stdio by
