[qubes-users] 80x24 geometry used by qvm-console-dispvm

Hello,

What is the reason for the '80x24' geometry of xterm used by
qvm-console-dispvm through the management_dispvm?

I tried to remove the option in the policy file in order to utilize the
full available workspace, as well as to change it to a bigger window,
but in both cases it just stops working.

P.S. I posted that initially in qubes-devel because it fits completely
the "Why did you implement XYZ this way and not the other way?" example
in Help, support, mailing lists, and forum | Qubes OS but it was rejected. Quite confusing.

Haven't done it for ages, but can't you configure the size using X resources?
Like this:
Now to set the size of the console itself, you would add this to the ~/.Xresources file:xterm*geometry: 127x37

Hello,

What is the reason for the '80x24' geometry of xterm used by
qvm-console-dispvm through the management_dispvm?

I tried to remove the option in the policy file in order to utilize the
full available workspace, as well as to change it to a bigger window,
but in both cases it just stops working.

That's the standard terminal size that various tools assume in lack of
other information. Technically you can use bigger window, but tools like
vim or top will still assume it's 80x24. The way that console works does
not support sending information about window size (changes).

P.S. I posted that initially in qubes-devel because it fits completely
the "Why did you implement XYZ this way and not the other way?" example
in Help, support, mailing lists, and forum | Qubes OS but it was rejected. Quite confusing.

You must subscribe to qubes-devel mailing list to post there.

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab

1 Like

The way that console works does not support sending information about
window size (changes).

Do I understand correctly there is no way to change it and it is
impossible, hence not planned?

You must subscribe to qubes-devel mailing list to post there.

I am subscribed. I was subscribed at the time of posting it, yet it was
explicitly rejected:

It isn't the problem of changing xterm window size. It's a problem of
telling the target VM what the size is. You can probably do that
manually by calling `stty cols W rows H` inside (after you resize the
window), but I don't know how to make automatic. If anybody has some
idea, patches welcome.

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab

I rejected it, because although it contains a "Why did you implement XYZ this way...?" question, the rest of the message implies a "How do I...?" request for help or support.

For PV consoles, I wonder if there should be a side-channel in the
protocol.
- --
Sincerely,
Demi Marie Obenour (she/her/hers)
Invisible Things Lab

Maybe? I don't think there is one. BTW I think the same issue applies to
a real serial console too. SSH has such side-channel. And AFAIR telnet
does it in-band via some special bytes.

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab

There isn’t one _right now_, hence me proposing that one should be
added. I assume that it would be sufficiently simple that if we need to
do any conversions in dom0, those conversions could be done securely.
- --
Sincerely,
Demi Marie Obenour (she/her/hers)
Invisible Things Lab

Well, it was rather "I am trying to modify existing functionality".
Anyway, thanks for clarifying. It's a blurry line I guess. :slight_smile: