Serial line doesn't support Spanish keyboard on Intel Mac

[paaguti]

BEFORE SUBMITTING YOUR ISSUE, PLEASE LOOK AT THE PINNED ISSUES AND USE THE SEARCH FUNCTION TO MAKE SURE IT IS NOT ALREADY REPORTED. ALWAYS COMMENT ON AN EXISTING ISSUE INSTEAD OF MAKING A NEW ONE.

Describe the issue
On a Ubuntu VM with serial line attached, I can't access any of |@#~ when I use the serial line to access the VM. On the Spanish keyboard, they are produced with option + 1,2,3 and 4
Configuration

• UTM Version: 4.0.9 owards
• macOS Version: 12.6.5
• Mac Chip (Intel, M1, ...): Intel

Crash log
If the app crashed, you need a crash log. To get your crash log, open Console.app, go to Crash Reports, and find the latest entry for either UTM, QEMU, QEMUHelper, or qemu-*. Right click and choose Reveal in Finder. Attach the report here.

Debug log
For all issues related to running a VM, including crashes, you should attach a debug log. (This is unavailable for macOS-on-macOS VMs. Attach an excerpt of your system log instead.)
To get the Debug log: open UTM, and open the settings for the VM you wish to launch. Near the top of the QEMU page is Debug Log. Turn it on and save the VM. After you experience the issue, open the VM settings again and select Export Log... and attach it here.

Upload VM
If your issue is related to a specific VM, please upload the config.plist from your VM's .utm directory. To get this, right-click the VM in UTM and choose "Show in Finder". Then right-click the selected file in Finder and choose "Show Package Contents". The config.plist file is now visible. Right-click it and choose "Compress". Attach the resulting config.plist.zip file here.
You can upload the entire .utm if needed, but note this includes your VM's drive image and may contain personal data. Since Github has an attachment size limit, you may want to upload to another service such as Google Drive. Link it here.

[osy]

Just to confirm, are you talking about UTM's built in terminal?

[paaguti]

The terminal you get when you add a serial line /PA

…

On Mon, 17 Apr 2023 at 18:12, osy ***@***.***> wrote: Just to confirm, are you talking about UTM's built in terminal? — Reply to this email directly, view it on GitHub <#5202 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAZKU4CHAQUCWR2BPK4HPXTXBVTXPANCNFSM6AAAAAAXBL574I> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- Fragen sind nicht da, um beantwortet zu werden, Fragen sind da um gestellt zu werden Georg Kreisler Headaches with a Juju log: unit-basic-16: 09:17:36 WARNING juju.worker.uniter.operation we should run a leader-deposed hook here, but we can't yet

[osy]

Can you provide a screenshot?

[paaguti]

Sure. This is what I get with iTerm2 when I press Option-1 on a Spanish keyboard: [image: Captura de Pantalla 2023-04-18 a las 9.41.52.png] And this is what I see on the serial line: [image: Captura de Pantalla 2023-04-18 a las 9.40.30.png] Best, /PA

…

On Tue, 18 Apr 2023 at 07:36, osy ***@***.***> wrote: Can you provide a screenshot? — Reply to this email directly, view it on GitHub <#5202 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAZKU4CJWBHCOAXXRCVOVDLXBYR7LANCNFSM6AAAAAAXBL574I> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- Fragen sind nicht da, um beantwortet zu werden, Fragen sind da um gestellt zu werden Georg Kreisler Headaches with a Juju log: unit-basic-16: 09:17:36 WARNING juju.worker.uniter.operation we should run a leader-deposed hook here, but we can't yet

[paaguti]

BTW, it may sound as a stupid question, but examining the command.txt produced when you export, it looks like you tell the VM it has no display. Just for my understanding, wouldn't it be better to pass the display type to QEMU in the -vga param. That's what I do in other OSes with 'stock' QEMUs, but I would understand that you use your own patched QEMU and -vga would do it no good. Thx, /PA On Tue, 18 Apr 2023 at 09:44, Pedro Andres Aranda Gutierrez < ***@***.***> wrote:

…

Sure. This is what I get with iTerm2 when I press Option-1 on a Spanish keyboard: [image: Captura de Pantalla 2023-04-18 a las 9.41.52.png] And this is what I see on the serial line: [image: Captura de Pantalla 2023-04-18 a las 9.40.30.png] Best, /PA On Tue, 18 Apr 2023 at 07:36, osy ***@***.***> wrote: > Can you provide a screenshot? > > — > Reply to this email directly, view it on GitHub > <#5202 (comment)>, or > unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAZKU4CJWBHCOAXXRCVOVDLXBYR7LANCNFSM6AAAAAAXBL574I> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> > -- Fragen sind nicht da, um beantwortet zu werden, Fragen sind da um gestellt zu werden Georg Kreisler Headaches with a Juju log: unit-basic-16: 09:17:36 WARNING juju.worker.uniter.operation we should run a leader-deposed hook here, but we can't yet

-- Fragen sind nicht da, um beantwortet zu werden, Fragen sind da um gestellt zu werden Georg Kreisler Headaches with a Juju log: unit-basic-16: 09:17:36 WARNING juju.worker.uniter.operation we should run a leader-deposed hook here, but we can't yet

[osy]

If you added a display in your vm settings, it should create it separately. Otherwise, it shouldn't create any displays.

[paaguti]

Right, so you add it with a -dev instead of using the -vga Thx

…

El 18 abr 2023, a las 16:38, osy ***@***.***> escribió: If you added a display in your vm settings, it should create it separately. Otherwise, it shouldn't create any displays. — Reply to this email directly, view it on GitHub <#5202 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAZKU4HTOX4LAGBEY75EKQTXB2RPLANCNFSM6AAAAAAXBL574I>. You are receiving this because you authored the thread.

[osy]

I'm not sure if your issue is with UTM's terminal or because you're running a guest whose serial port doesn't support the character set. Can you set your serial port to PTTY or TCP and connect to it with iTerm2 and see if it works?

By the way your screenshot did not attach. Also, it would help if your provide your VM's config.plist like it asked for when you opened the issue. Thanks.