blob: a96149321abbfc9d261944b21fcc35b0ac984cec (
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
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
|
graphic: 0.888
mistranslation: 0.877
device: 0.834
architecture: 0.762
hypervisor: 0.746
x86: 0.729
semantic: 0.722
boot: 0.704
socket: 0.660
VMM: 0.656
user-level: 0.653
peripherals: 0.651
ppc: 0.640
performance: 0.628
network: 0.617
PID: 0.550
arm: 0.534
permissions: 0.517
register: 0.512
virtual: 0.508
debug: 0.490
kernel: 0.469
files: 0.448
vnc: 0.432
TCG: 0.359
risc-v: 0.339
KVM: 0.281
assembly: 0.229
i386: 0.196
Ubuntu 16.04.1 LightDM Resolution Not Correct
My Specs:
Slackware 14.2 x86_64 > Host
Nvidia GPU GTX660M
nvidia-driver-352.63
QEMU 2.7.0
Ubuntu 16.04.1 x86_64 > Guest
Unity
Xorg nouveau - 1:1.0.12-1build2
These are the startup options for Ubuntu:
qemu-system-x86_64 -drive format=raw,file=ubuntu.img \
-cpu host \
--enable-kvm \
-smp 2 \
-m 4096 \
-vga vmware \
-soundhw ac97 \
-usbdevice tablet \
-rtc base=localtime \
-usbdevice host:0781:5575
Unity desktop resolution set for 1440x900.
I noticed when I come to the login screen to enter my password the LightDM resolution fills my entire desktop.
I searched online and found this solution;
cp ~/.config/monitor.xml /var/lib/lightdm/.config
For now I'm assuming this step should not be needed and the resolution should be correctly detected and set?
Why are you using "-vga vmware" ? Can't you use "-vga std" instead? Also, now that QEMU 2.8 has been released, could you please test again with this latest version? Thanks!
Hi I'll just post to here for both issues;
https://bugs.launchpad.net/qemu/+bug/1649042
LOL TYPO here;
https://bugs.launchpad.net/qemu/+bug/1649040
Using virtio it works nice....
OK, if it works with -vga virtio, I think we should close this bug as WONTFIX, since the -vga vmware code is pretty much unmaintained as far as I know (if somebody is willing to fix this there, too, feel free to open this bug again).
|
