Screen resolution inside the VM not resized correctly after double-clicking (to Zoom) the title bar of the VM window

[rxhfcy]

Describe the issue
Screen resolution inside the VM is not resized correctly after double-clicking (to Zoom) the title bar of the VM window

(when the host macOS has the following setting: in System Settings... / Desktop & Dock / "Double-click a window's title bar is" -> "Zoom")

Steps to reproduce

1. Make a new Fedora Linux VM (New VM, virtualize, aarch64, newest is currently Fedore 38 aarch64)
2. After installing (default settings), inside the VM: Settings / Displays
3. Resize the VM window (make it as small as possible by dragging the VM window borders)
4. Look at "Resolution" inside the VM: 800 x 600 or something like that
5. Resize the VM window (make it a little bit taller) by dragging the VM window border
6. Look at "Resolution": now it's 800 x 627 or whatever
7. (in host macOS, make sure that System Settings... / Desktop & Dock / "Double-click a window's title bar to" -> "Zoom")
8. Double-click the host VM window title bar to "Zoom" (to make the window bigger)

What happens: the VM now has black borders inside its window. Guest VM resolution didn't change.
What I expected: behave exactly like if I had manually made the window bigger by resizing it by dragging the VM window's borders (no black borders inside VM window, change the guest resolution normally)

Screen shot of what happened after step 8. (black borders, resolution didn't change)

Configuration

• UTM Version: Version 4.3.5 (87)
• macOS Version: 14.0 Beta (23A5337a)
• Mac Chip (Intel, M1, ...): M1

[osy]

Can you try v4.4 beta, I think this is related to #5577 which was fixed.

[rxhfcy]

@osy the VM doesn't work at all on the v4.4 beta for some reason, is it OK if I test this again when a new beta is released? (Any ETA?)

[osy]

I think it would be even better if you can provide more details and maybe in an new issue? There's no way it'll be fixed in the new beta if I don't know what the issue is.

[rxhfcy]

More details? I thought I was very thorough here. Happy to help though, if you can give me a hint: what details are missing?

[osy]

the VM doesn't work at all on the v4.4 beta

What does this mean? You pressed start and nothing happened? Did it crash and you have a crash log? Did you see an error message?

[rxhfcy]

If you meant details about what's not working in the v4.4 beta: nothing is working. The VM doesn't start. Also I couldn't follow my steps above to make the VM (had to follow the steps in 4.3.5 (bug present), then went back to 4.4 beta, VM didn't start at all)

[osy]

Okay I understand the part about "didn't start at all" but I need to know precisely what that means. Ideally provide a screen recording if you don't know how to explain it. Did you see any error message? Did you see a crash report dialog pop up?

[rxhfcy]

What does this mean? You pressed start and nothing happened?

Pretty much that. Here's a screen shot:

Did it crash and you have a crash log? Did you see an error message?

No crash, no crash log, no error message.

Okay I understand the part about "didn't start at all" but I need to know precisely what that means. Ideally provide a screen recording if you don't know how to explain it.

OK here's a screen recording:

Did you see any error message? Did you see a crash report dialog pop up?

No.
...but here is a debug log, is it userful? I have 2 Fedora test VMs and I had a little bit of trouble acquiring a debug log for some reason. Let me know if you need something else?
debug.log

[rxhfcy]

...I can open a new issue for this if you want ("unable to make a new Fedora ARM64 VM on Version 4.4.1 beta" or something?)

[osy]

Yes, that would be useful. Attach the debug.log and the screenshot from above please.

[rxhfcy]

Sure. Unfortunately I don't have any more time right now, will try to file the new issue tomorrow.

[osy]

No worries, I will file it then

[rxhfcy]

Can you try v4.4 beta, I think this is related to #5577 which was fixed.

Fixed now in the new 4.4.2 beta (taking the liberty to close this issue).