blob: ed3d5c9b91f3506a6cdfc715124cebb46b0394ae (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
|
virtual: 0.981
graphic: 0.955
device: 0.749
mistranslation: 0.738
user-level: 0.720
semantic: 0.609
performance: 0.567
risc-v: 0.542
VMM: 0.501
architecture: 0.495
vnc: 0.494
boot: 0.486
register: 0.465
PID: 0.443
socket: 0.404
ppc: 0.378
TCG: 0.369
network: 0.363
permissions: 0.330
debug: 0.324
kernel: 0.315
arm: 0.295
files: 0.282
hypervisor: 0.273
i386: 0.269
peripherals: 0.217
x86: 0.212
KVM: 0.209
assembly: 0.158
Emulated monitor EDID reports too few available graphics resolutions
In a Windows guest, not very many resolution modes are available. The available modes are restricted by what the virtual "monitor" EDID reports via DDC. And apparently, your fake monitor has a short list of modes. Please add some more modes like 1152x864, at least. But what would be REALLY nice is much finer granularity so that users can set the guest res to be just enough smaller than the host display so that window decorations and such fit.
If you use -vga std of -vga vmware, you'll have a much larger choice of resolutions.
For -vga vmware, it's actually possible to add custom resolutions but we don't have the tooling to make that user friendly today. I'll mark this bug as a wish list to track adding that feature.
As mentioned in comment #1, -vga std is the way to go, so marking this ticket now as "Won't fix".
|